Skip to Content
WorkflowsTemplate Pipeline

Template Pipeline

A template defines both the structure of a note (sections, headers) and the rules it has to follow (required fields, locked regions). Every agent run goes through the same pipeline, which is how the rules get enforced.

Pipeline

  1. Select template: load the structure and its anchor/field definitions.
  2. Bind field values: resolve SELECT, MULTISELECT, and DYNAMIC_SELECT inputs and insert them at their anchors.
  3. Run agent transforms: agents propose edits against the bound document.
  4. Validate locked regions: any proposed change that overlaps a locked anchor is dropped here, before it reaches the review queue.
  5. Queue pending edits: what’s left goes into the review queue for you to accept or reject.

Guardrails

  • Agents can’t write to locked regions at any step.
  • Required fields are checked at export, not at drafting. You can fill sections in any order.
Last updated on