Help · Revisions

Publish a new version of an existing OWL Compose work

A new formal version advances the current work without rewriting any earlier immutable version.

업데이트 September 5, 2026제품 문서OWL Compose CLI 0.1.3 and laterOWL Compose Product

Edit the author source

Start from the retained OWX source and frozen inputs. Record why the content changed, especially when correcting a factual or source error.

Rebuild the artifact

ow a2ui check ./artifact/document.owx
ow a2ui fmt ./artifact/document.owx
ow a2ui compile ./artifact/document.owx --output ./artifact/document.json
ow a2ui digest ./artifact/document.json

Target the existing document explicitly

The CLI may also retain artifact-directory binding after a successful publish. Keep the document ID in the package metadata and CI secrets boundary, not in public prose unless the work is already curated for public access.

ow publish ./artifact/document.json --update <document_id>

Verify both current and fixed versions

  1. Open the owner page and confirm the expected version number.
  2. Inspect the current reader preview.
  3. Open the new fixed-version preview.
  4. Confirm an older fixed version is unchanged.
  5. Check whether existing view links still match the intended audience and revoke any that do not.

FAQ

자주 묻는 질문

Does a new version overwrite the earlier one?

No. Each published version remains immutable; the work's current pointer advances to the new version.

When should I use --new-document instead?

Use a new identity when the reader task, owner, subject, or evidence boundary has materially changed.

실제 워크플로 사용

에이전트가 만든 작품을 발표하세요.

CLI를 설치하고 OWX로 작성해 로컬에서 검증한 뒤 비공개 작품으로 게시하세요. 공유할 준비가 되었을 때만 독자 링크를 만듭니다.