Proposals and human confirmation
An AI proposal is a saved intention with its own identity, preview and review state. It is not yet the native business action it describes. Confirmation uses the current authorized human’s authority and the operation’s source/revision checks. Different proposal families have different atomicity and replay contracts.
Proposal families
Section titled “Proposal families”| Family | Before confirmation | Confirmation boundary |
|---|---|---|
| Quote draft | Normalized proposed customer/lines, blockers, immutable revisions and expiry | confirm_agent_quote_draft creates native customer/quote structures and closes the proposal in its SQL transaction; quote send and customer acceptance remain separate. |
| User invitation | Proposed person/role and preview, with role containment checked | Recheck the deciding person’s authority and role containment, run ordinary invitation logic, then conditionally close the proposal. Sending and proposal closure are not one database transaction. |
| Document review | Candidate reference, version, source hash and proposed action | Human document-review permission plus checked document-confirmation RPC; no direct model approval of business facts. |
| Imported project supplement | Preserved source/hash and exact missing fields | The dedicated imported-source workflow rechecks current source/target before applying permitted missing fields. |
Document intake owns candidate classification/routing. Quote acceptance owns publication, named responses and accepted agreement evidence. Confirming an AI quote proposal does not send a quote, accept it for the customer or create billing authority.
Revisions and replay
Section titled “Revisions and replay”MCP quote drafts belong to their proposing author within the company. Identical active creates can converge on the existing proposal. An edit uses its draft reference and expected revision. Repeating the current content returns the current revision; a conflicting intervening edit is refused. Replaying an original create can return the still-active draft after later edits, rather than replacing them. Restoring older content requires the current revision and explicit review.
The reviewed quote draft has a seven-day lifetime and limits of 100 lines and 50,000 encoded payload bytes. Its default text cap is 4,000 characters, with tighter bounds for individual fields such as the title. An explicit revision can renew an expired draft under its contract. Document proposals use a separate 24-hour lifetime and bind candidate version/hash. Do not transfer one family’s expiry or idempotency assumptions to another.
sequenceDiagram participant Client as AI client participant API as Proposal service participant Human as Authorized reviewer participant Domain as Owning operation Client->>API: Propose or revise with source and revision API-->>Client: Reference preview blockers and expiry Human->>API: Confirm current proposal API->>API: Check authority current state and source API->>Domain: Apply family-specific operation Domain-->>API: Native identity or refused conflict API-->>Human: Confirmed result or recovery requirement
Authority and technical effects
Section titled “Authority and technical effects”Invitation roles cannot include rights beyond the proposing/deciding person’s permitted set, and platform-only roles are not ordinary company invitations. Document technical operation and human review permissions are distinct. The confirmation path rechecks current state; the model’s earlier permission or a preview generated yesterday does not authorize today’s decision.
Some AI-facing tools already perform technical writes: saving proposals, queuing interpretation or storing draft images. Their annotations do not prove an explicit human confirmation, nor do they make every call read-only. Successful technical work remains separate from native business approval and provider delivery.
Conflict and uncertain-result recovery
Section titled “Conflict and uncertain-result recovery”For synthetic Draft A, another editor changes revision 3 after a reviewer opens it. Reload revision 4 and compare its fields/blockers before confirming. Do not merely replace the expected revision and apply an unreviewed change. For an invitation whose send result is uncertain, inspect the existing invitation/person and proposal outcome before another send; its post-send proposal update is a separate boundary.
Expired, declined or already decided proposals should use the family’s supported resume/new-proposal path. Keep result identity and unresolved questions visible. The PR distinguishes synthetic proposal tests, SQL transaction evidence and any named shared outcomes. This review creates no real invitation, quote, approval or accounting write.