Supported direct inputs
Both inputs must come from the current OWL Compose compiler workflow and pass local validation.
ow publish ./artifact/document.json
ow publish ./artifact/document.multilingual.jsonUnsupported direct inputs
- Raw .owx source
- Markdown or .md files
- Standalone HTML
- Directories or stdin
- JSON-LD or arbitrary JSON
- Web applications with runtime services
Use source material without pretending it is an import
An Agent may use Markdown, a repository, a PDF, a spreadsheet, or public data as source material for a new OWX work. The result must still be authored through supported nodes and compiled locally.
Choose another host when bytes must remain unchanged
Use an HTML or static artifact host when the job is to serve an existing webpage unchanged. Use an application platform when the output depends on a server, database, or client runtime outside the document contract.
OWL Compose does not promise lossless conversion of arbitrary Markdown, HTML, or application bundles.
FAQ
Frequently asked questions
Can I publish a Markdown plan directly?
No. Use it as source material, author the work in OWX, compile it, and publish the resulting JSON.
Why is arbitrary JSON rejected?
Hosted publishing accepts one versioned Render Document schema so validation, storage, and rendering share the same structural truth.
Use the real workflow
Publish what your agent creates.
Install the CLI, author in OWX, validate locally, and publish a private work. Create a reader link only when you are ready to share.