Axiom Weaver

A story is authored once as a structured Story Package and performed into prose on every read. Pick a story to open its author surfaces: the Working Draft and its scene compile view, the World & Discourse inspector, and the run report.

New here? Start with the Author's Guide or the Reader's Guide.

Stories

Start a story →

Read surfaces

• GET /api/stories — every story with a retained package
• GET /api/stories/{storyId}/package — the current Story Package
• GET /api/stories/{storyId}/package/{version} — a retained snapshot
• GET /api/stories/{storyId}/world-model?scene=N — the World Model as of scene N, replayed from the commit log
• GET /api/stories/{storyId}/proposals — the proposals queue: volitional proposals awaiting the author
• GET /api/stories/{storyId}/draft — the Working Draft's scene list, with staleness
• GET /api/stories/{storyId}/inspector?scene=N — both inspector tabs at one scrubber position
• GET /api/stories/{storyId}/run-report — runs aggregated by Scene Card
• GET /api/tellings/{runId}/report — one run's full report

Author surfaces

The four surfaces ADR 0016 settled on, plus the authoring screen ADR 0017 adds. Compiling a scene, resolving a proposal, promoting a run and saving a draft are writes, and a deployment asks for the same BLOB_READ_WRITE_TOKEN every other write surface uses; a local filesystem-backed instance asks for nothing.

• /stories/{storyId} — Working Draft, stale badges, and the scene compile view (diagnostics + proposals queue)
• /stories/{storyId}/inspector — World Model and told-ledger over one scene-index scrubber
• /stories/{storyId}/runs — run report and the manual Baked promotion
• /stories/{storyId}/edit — the Manuscript: metadata, Voice Card, World Model seed, the linter, and publish
• /stories/new — start a story from scratch, or duplicate a retained version of an existing one

Admin

• /admin/load-fixtures — (re)load both fixture Story Packages, from a browser