Publish an AI Agent’s work without sharing the conversation

Why a session link is the wrong handoff for many tasks

A session can contain abandoned ideas, proprietary code, credentials, personal notes, and later messages unrelated to the result. It is also organized around how the answer was produced rather than what the recipient needs to decide or use.

Create a work product boundary

1. Name the recipient and the decision or task the document must support.
2. Move only supported conclusions, evidence, constraints, and next actions into the document.
3. Keep source references and state what remains unknown.
4. Remove conversation-only context, secrets, and speculative branches.

Build and publish from the Agent

ow a2ui draft init ./artifact --title "Architecture decision" --description "Reviewed recommendation and evidence" --language en
# Add typed sections, evidence, tables, diagrams, and decisions.
ow a2ui draft check ./artifact
ow a2ui draft build ./artifact
ow a2ui digest ./artifact/document.mdw
ow publish ./artifact/document.mdw --no-open

Choose the right link

Use a view link for reading, a review capability only when the recipient must decide on a candidate, and a fixed version permalink when the handoff must keep identifying the exact approved revision.