What a shared Agent chat preserves
- Prompt and response sequence
- Discarded alternatives and debugging context
- Tool calls or intermediate reasoning exposed by that platform
- The ability to inspect or continue the original collaboration when supported
What an OpenWiki publication preserves
- The selected reader-facing result
- Typed facts, structure, and presentation intent
- One canonical identity and immutable formal revisions
- Feedback and human decision state
- An Agent-readable .mdw package
Privacy tradeoff
Session history can contain credentials, internal paths, personal notes, and unrelated messages. A separate document reduces exposure only when the author actively excludes that context and inspects the final artifact.
Use links with the right authority
Send the view link for reading, a version permalink for citation, and the review capability only to the approver. The separate artifact boundary does not make every capability public.
FAQ
Frequently asked questions
Can a reader see how the Agent produced an OpenWiki document?
Not from the publication alone. It contains the selected work product and evidence, not the complete generation session.
When is sharing the Agent chat better?
Use the chat when a collaborator must debug prompts, inspect session context, or continue the same conversation and disclosure is acceptable.
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.