Several independent proposals from the same frozen source may land side by side for human judgment.
scribectl
canonical fiction pipeline / system map
interactive
Vault → pack → draft → verdict → canon
Fiction without quiet canon rot.
scribectl separates authored intent, ratified truth, and agent proposals. The machine assembles evidence and preserves receipts; the writer decides what is true in the world.
state is derived
packs are frozen
canon is ratified
01 / responsibility boundaries
Who may do what?
Select a system component. The boundaries are the architecture: where state lives, who may write, and where decision authority remains.
02 / two canonical pipelines
One gate, different raw material.
The production pipeline creates a scene from existing canon. The worldbuilding pipeline mines sources for new claims. Both terminate at the same writer-owned verdict inbox.
03 / artifact map
Every file has a trust class.
Filter artifacts by authority and inspect a card. The critical distinction is between canon, frozen, quarantined, gate-controlled, and merely derived information.
04 / contract layers
Intent becomes executable without becoming canon.
The template set defines the project shape for the engine. The scene card defines the content objective. The per-card contract bounds exactly one agent run.
05 / Fertile Flames
A new world, its first canonical pass.
Walk through seven stages. The example shows how unresolved canon blocks a fill, how the hash acts as a receipt, and the exact point where a proposal may become true.
Volcanic City-State Battling Demons and Mist
06 / iteration boundaries
The loop grows sideways, not inward.
scribectl permits new source material, independent fill variants, and new review passes. It does not permit an agent to revise its own output autonomously from another agent's feedback.
A review reports. The writer decides, reworks the draft, and requests another bounded pass if needed.
Only a checkbox verdict and ratify --sweep move a claim from quarantine into a ratified node and ledger.