Acceptance and closeout
Collects the issued version, acceptance evidence and open obligations; acceptance must be evidenced.
Serve clients
The saved work
A draft that cannot clear an unresolved hold
Recommend HOLD internal closeout. The server-supplied deterministic readiness gate is HOLD and says AI drafting cannot clear it. Its recorded reasons are: the current report needs exact professional review; report13/source3 does not cover the changed scope2; there is no delivery reference; there is no explicit client acceptance; and the remaining Northline support and retention handover is open or unreconciled. These reasons explain the hold; this draft does not independently decide or alter readiness.
A related local example. It shows the stated part of the work, not every step in this design. Read it in saved outputs
- Starts when
- Deliverable issued or response received
- What it works from
- Issued versions, scope, actual client response and open obligations
- What it prepares
- Delivery/acceptance gaps, outstanding actions and closeout record
- What your team decides
- Actual acceptance evidenced; lead and finance retain separate decisions
What this helps your team do
This path has been checked in the fictional local build.
Responsibilities connected
See what each agent is responsible for preparing in this workflow. These are designs and local examples, not a set of independently running agents.
When it stops and asks
Unclear commitment, stale advice or missing recipient/authority is returned to the client owner; no agreement or delivery is inferred.
Supported scope, source access and authority are agreed for each installation.