Choose an HTML artifact host when fidelity is the contract
- The source is already a standalone HTML file.
- Custom CSS, SVG, or client-side interaction must remain intact.
- The artifact is a prototype or visual exploration.
- You accept the security and maintenance responsibilities of arbitrary HTML.
Choose OpenWiki when governance is the contract
- The work product is a report, plan, specification, guide, or data narrative.
- A candidate needs human feedback or an explicit decision.
- One canonical identity must coexist with immutable formal revisions.
- Another Agent needs a typed package rather than scraped HTML.
Important input difference
OpenWiki Hosted does not accept raw HTML. It cannot be used as a drop-in replacement for a standalone HTML file host. A separate typed .mdw authoring step changes the artifact and should be described honestly.
A two-artifact workflow can be valid
A team can keep a rich HTML prototype for visual exploration and publish a typed OpenWiki decision document that records scope, evidence, tradeoffs, and approval. Link the artifacts explicitly without pretending they are the same file.
FAQ
Frequently asked questions
Is OpenWiki an HTML hosting service?
No. OpenWiki Hosted publishes validated .mdw documents and does not accept arbitrary HTML uploads.
Can I use both an HTML prototype and OpenWiki in one workflow?
Yes. Use the prototype for visual fidelity and a separate typed OpenWiki document for governed decisions, revisions, and 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.