OWX is the authoring truth
OWX is constrained XML-based markup for document structure, typed data, presentation, evidence references, and package-local assets. Unsupported tags, scripts, paths, and attributes fail closed.
Compilation creates the delivery artifact
The compiler materializes supported views and presentation intent into one schema-validated Render Document JSON file.
ow a2ui check ./artifact/document.owx
ow a2ui compile ./artifact/document.owx --output ./artifact/document.jsonDigest checks deterministic identity
Equivalent source and frozen inputs produce a verifiable artifact identity. A changed source or asset produces a different result.
ow a2ui digest ./artifact/document.jsonNeither layer is arbitrary web code
OWX is not Markdown with another extension, raw HTML, Bootstrap, or JavaScript. Render Document JSON is not a place to inject scripts or hand-patch the compiler output.
FAQ
Frequently asked questions
Can a person edit an OWX file?
Yes. It is text and remains the editable source, although Agents are the primary authoring interface.
Can OWL Compose publish the OWX file directly?
No. Run the local compiler and publish the resulting Render Document JSON artifact.
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.