The document identity continues
Publishing with --update keeps the same document identity while advancing its current published version.
Each formal version is immutable
The Version history tab lists numbered versions with stable reader, PDF, social-data, and image resources. A later publication does not change an older version's bytes.
Identity does not grant access
Ordinary works are private even when a person knows the document or version identifier. The author must create a view link for private reading.
Use public official pages only after curation
An administrator can bind a maintained official-work slug to one exact published version. Updating the underlying private work does not silently replace that public page; the administrator must check and publish the new version explicitly.
FAQ
Frequently asked questions
Will an old fixed version redirect to the newest one?
No. Fixed versions remain pinned. The continuing document identity is the surface that advances.
Can I post a private fixed-version URL without a view link?
No. Version identity and access are separate; private reading still requires an active reader capability.
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.