Draft, approve and save a customer document
Status: Upcoming — not yet available.
Section: DOC-WF-agent-coordination#overview.
Use agents to draft and validate a customer document, route the exact revision to a person for approval and confirm the approved revision was saved. Start with this bounded workflow before adding recurring or parallel work.
You need the authorized source records, the system that owns the final document, permitted operations, an eligible reviewer and a finite work budget. The finished result is the owning system's saved revision and receipt; a persuasive assistant message alone does not establish completion.
The complete coordination journey and customer API are not yet available. For current interactions, use tool use and approvals.
Step 1: define the document and its acceptance condition
Status: Upcoming — not yet available.
Section: DOC-WF-agent-coordination#business-completion.
Choose the document to produce and identify its organization, project, environment, customer and beneficiary. Record the source revisions, required computations or validation, permitted actions and review authority.
Define completion as the owning system confirming the approved document revision. A draft, validation result or approval is progress; the saved revision is the business outcome. Set the overall time/tool budget and allocate child work within it.
If an input or validation rule changes, recompute or repeat review where required. Changing the procedure does not remove underlying business validation or grant new access.
Ready to start: the procedure names the inputs, allowed operations, human decision, limits and final record that proves the work finished.
Step 2: draft, validate, approve and save
Status: Upcoming — not yet available.
Section: DOC-WF-agent-coordination#coordination-flow.
- Select the approved instruction revision and reusable operations for this document.
- Assign a bounded drafting task using the recorded inputs.
- Validate the candidate through the required computations and business checks. The final operation stays gated on these prerequisites.
- Present the exact validated proposal to an eligible reviewer. Keep work pending or unavailable if no required reviewer is available.
- After approval, perform the permitted save through the owning system.
- Inspect the returned document revision and receipt.
The procedure references owning records rather than copying identity, billing or every private application field into its coordination state. When drafting and validation run as children, each has a defined input revision and output; the parent keeps partial or failed contributions visible.
Finished result: the approved document revision is saved and confirmed. If validation, review or save is incomplete, retain the useful draft and show the missing stage instead of claiming completion.
Add reminders only with permitted consent, time zone, quiet hours and frequency. A timer or reminder is not a completed review and does not imply continuous human monitoring.
Handle a partial document or a failed stage
Status: Upcoming — not yet available.
Section: DOC-WF-agent-coordination#progress-and-results.
Use the state to choose the next action without overstating progress:
| State | Next action |
|---|---|
| In progress | Follow the existing task |
| Awaiting approval | Route the specific proposal to an eligible person |
| Candidate or partial result | Inspect the draft and unfinished prerequisites |
| Business committed | Use the owning record revision and receipt |
| Unknown outcome | Reconcile the original operation before another attempt |
| Failed or stopped | Inspect unfinished work and separately completed effects |
If drafting succeeds but validation fails, the document remains a candidate. If the budget ends, new tool actions stop and the result identifies unfinished work. A late child result retains its input/output revisions and cannot replace a newer accepted result.
Recover an interrupted save without creating another document revision
Status: Upcoming — not yet available.
Section: DOC-WF-agent-coordination#coordination-recovery.
Return to the original run and recover its task/operation references, procedure/input revisions and last confirmed outcome. If saving may have succeeded before the response was lost, reconcile that operation and use the recorded result. A recovered saved revision finishes the original intent; lost progress does not require another commit.
After access removal, suspension or deletion, distinguish blocked new work, already-dispatched effects and pending cleanup. Delayed reminders, callbacks and restored state cannot recreate deleted data or resume work under revoked access. For upgrades, account for active cases, approvals, children and retained history through process recovery.
See process and case recipes, current tool approvals and billing for related flows.
Document ID: DOC-WF-agent-coordination. Section identities and revisions.