Evidence and claim checks
- Every material claim is supported or clearly labeled as judgment.
- Source links resolve and identify the relevant evidence.
- Dates and observation windows are explicit.
- Unknowns and limitations remain visible.
- No roadmap capability is written as already shipped.
Privacy and media checks
- Remove secrets, private repository paths, customer data, and conversation-only context.
- Import photos through the metadata-stripping workflow.
- Inspect visible pixels for tokens, emails, and personal data.
- Confirm image rights and write useful alternative text.
Package and link checks
Use a review candidate when the report authorizes actions, makes sensitive recommendations, or will be externally cited.
ow a2ui draft check ./report
ow a2ui draft build ./report
ow a2ui digest ./report/document.mdw
ow publish ./report/document.mdw --no-openBrowser acceptance and maintenance
- Open the real page at the intended visibility.
- Test navigation, tables, figures, and mobile layout.
- Record the source cutoff and next review date.
- Share the canonical URL for a living report and a fixed version for evidence.
FAQ
Frequently asked questions
Does passing ow a2ui draft check prove every claim is true?
No. It validates the typed document contract and bindings. Human evidence review is still required for factual accuracy and judgment.
When should an AI report require formal review?
Use review when the report drives an external claim, operational action, high-impact recommendation, or other decision that should not advance silently.
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.