Make the requested authority explicit
- Name the exact action that is blocked.
- Show scope, evidence, risk, rollback, and open questions.
- Identify the intended reviewer.
- Set a realistic wait window and escalation path.
Keep the current publication stable
Publish a candidate rather than silently replacing the current formal revision. Readers keep a stable current document while the reviewer evaluates the proposed change.
ow publish ./plan.mdw --update <document_id> --review --no-open --timeout 900Fail closed for every other result
- Changes requested: revise and resubmit.
- Rejected: stop the proposed path.
- Timeout: report no decision and remain blocked.
- Transport or server error: preserve current state and remain blocked.
Preserve approval evidence
Record the immutable approved version beside the execution evidence. Do not let a later candidate inherit authority solely because it shares the canonical document URL.
FAQ
Frequently asked questions
Can an Agent treat silence as approval?
No. Missing decisions, timeout, and errors are non-approval outcomes.
Does a small edit require another review?
A new review is required whenever the change materially affects the scope, risk, action, evidence, or authority that was approved.
Use the real workflow
Publish what your agent creates.
Give every report, document, or plan its own reader-ready page. Comments, review decisions, and formal revisions can flow back from there.