Define the reader contract first
- Name the intended reader and the decision or task.
- Separate current facts, recommendations, and unknowns.
- State the evidence cutoff and maintenance owner.
- Choose read-only sharing, feedback, or a blocking decision before publishing.
Build and validate the typed artifact
Author through the supported draft operations so structure, facts, presentation bindings, media, and links can be checked before upload.
ow a2ui draft check ./artifact
ow a2ui draft build ./artifact
ow a2ui digest ./artifact/document.mdwPublish with the least authority
- Use a view URL for ordinary readers.
- Send feedback or review capabilities only to the people who need them.
- Use Public visibility only when tokenless reading is intentional.
- Enable search indexing separately and only for maintained public work.
Verify the handoff, not only the command
Open the returned page in a real browser, check desktop and mobile layout, follow important links, confirm media and access behavior, and record the immutable version when the document supports an approval or audit.
FAQ
Frequently asked questions
Should I share the complete Agent conversation with the document?
Only when collaborators need the prompt and tool history. Most readers need the reviewed work product, not the full session.
Does a successful publish command prove the handoff is complete?
No. It proves delivery. You still need browser acceptance, access verification, and a content review.
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.