openwiki

Guide · Governed plans

Publish an AI-generated plan for human approval

A well-formatted plan is still only a proposal. The safe workflow separates generation, review, decision, and execution, then returns the decision to the Agent as structured state.

Updated August 3, 2026Practical guide

Make the plan decision-ready

  1. State the objective, scope, and assumptions.
  2. Show the proposed changes, affected systems, risks, and rollback path.
  3. Separate confirmed facts from Agent judgment.
  4. List the exact authority requested from the reviewer.

Publish a blocking candidate

ow a2ui draft check ./plan
ow a2ui draft build ./plan
ow a2ui digest ./plan/document.mdw
ow publish ./plan/document.mdw --review --no-open --timeout 900

Map the result to Agent behavior

  1. Approved: execute only the reviewed scope.
  2. Changes requested: revise the source plan and submit a new candidate.
  3. Rejected: stop and preserve the decision record.
  4. Timeout or error: do not execute; report the missing decision.

Keep later changes governed

When the plan changes materially, append a candidate update at the same document identity and require review again. Do not rely on an approval for an older revision to authorize a different plan.

ow publish ./plan/document.mdw --update <document_id> --review --no-open

FAQ

Frequently asked questions

Can the Agent continue after a request-changes result?

It can revise and resubmit the plan, but it must not execute the rejected or changes-requested candidate.

Does approving one revision authorize later material changes?

No. A materially different candidate needs a new decision tied to that exact revision.

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.

Choose HostedSign in