Skip to main content

​
Draft Workflow: Editing & Testing Safely

Changing the prompts (Instructions, Rubrics, Directions) for an Analysis Field can significantly alter its output. To prevent deploying untested or broken changes that could affect live analysis results and downstream automations, Fabius uses a Draft Workflow.

​
Why Use Drafts?

  • Safety: Edit and experiment with prompts without impacting real-time analysis.
  • Testing: Validate changes against actual call or document data before making them live.
  • Collaboration (Implicit): Allows review of proposed changes before deployment (though formal approval flows may vary).
  • Iteration: Easily try different prompting approaches and compare results.
  • AI Assistance: Provides an environment (the Chat Editor) where AI can help you write and refine prompts based on examples and feedback.

​
Creating a Draft

You can initiate a draft in several ways:
  1. From a Field Page:
    • Navigate to the specific Field you want to edit (Settings -> Analysis -> Fields -> [Field Name]).
    • Click the “Create Draft” button.
    • You’ll likely see options:
      • “Edit Field” (Recommended): Takes you to the AI-assisted Chat Editor.
      • “AI Generate Draft”: Opens a modal to generate initial draft prompts based on the field’s Purpose and any additional context you provide. You’ll still likely want to refine this generated draft in the Chat Editor.
    • This creates a draft based on the current live version of the field.
  2. From a Configuration Link:
    • Navigate to a specific Configuration (Settings -> Analysis -> Configurations -> [Config Name]).
    • In the “Analysis Fields” table, find the field you want to modify specifically for this configuration.
    • Click the “Create Draft” action on that table row.
    • This creates a draft that overrides the base field’s prompts only when run by this specific configuration. This is useful for tailoring a field’s behavior for different contexts (e.g., slightly different “Next Steps” instructions for Discovery vs. Closing calls). Edits are made via the Chat Editor or Manual Editor.
Creating a draft copies the current live prompts of the field (or the existing override if drafting from a config link) into a new, editable version.

​
Draft Lifecycle & Statuses

A draft typically moves through these statuses:
  1. In Progress: The initial state. The draft is being edited and tested. It has no impact on live analysis.
  2. Deployed: The changes in the draft have been tested and approved. They have replaced the previous live version of the field’s prompts (or the config link’s override). The draft itself is usually archived or marked as deployed. New analyses will use these updated prompts.
  3. Rejected: The draft was deemed incorrect or unnecessary and has been archived. It has no impact on the live prompts.
Drafts also have Versions, allowing you to track the history of changes within the drafting process itself before deployment.

​
Viewing Drafts

  • On a Field Page: The Drafts table lists all historical and active drafts associated with that field.
  • On a Configuration Page: The Drafts table might be shown within the context of a specific field link if a draft override exists for that link.
Clicking on a draft in these tables usually takes you to the editor for that specific draft version. The Draft Workflow is essential for maintaining the quality and reliability of your automated analysis system while allowing for continuous improvement and adaptation. Next: Using the Chat Editor (Recommended)