Stories & publishing
The current story lifecycle from evidence-bound draft to Core-owned publication bundle.
Current product shape
Stories live in the Work stage. The old canvas/world language is replaced by a smaller story path: evidence, validation, reader, authoring, publication, and verifier output.
Lifecycle
Draft
Story body and evidence are still being assembled. No release truth is implied.
Review
Claims and evidence are checked through human/Core review paths.
Ready
Required review and evidence checks are satisfied for the selected release path.
Published
Core produced a publication bundle and verifier-readable output.
Archived
Story is no longer active, but audit evidence remains inspectable.
Authoring contract
- Use the documented story editor controls only: body text, one heading level, quote, links, claim references, and evidence citations.
- Unsupported rich-text structures are blocked or stripped rather than silently serialized.
- Story body resolution is canonical; screens must not invent a fallback body and call it Core-backed.
- Publishing is Core-owned. The browser can request, display, and verify; it cannot mint publication truth.
Publication gate
Release readiness is not a visual badge alone. It depends on evidence binding, review state, Core bundle production, and verifier behavior. Trusted L2 additionally depends on active production signer trust.