Planning Docs

Compact XML-style planning index for the books section.

Planning Docs

Planning Index

PageRecord SetPurpose
Statestate-recordsCurrent phase, owner, next queue, and working references.
Task Registrytask-recordsOrdered work items with status, dependencies, and verification commands.
Errors and Attemptsattempt-recordsFailures, corrections, and still-open problem tracks.
Decisionsdecision-recordsAccepted section decisions and their consequences.

Book: Mordred's Tale

PageRecord SetPurpose
Mordred's Tale — Outlinemordreds-tale-outlineFull narrative arc, chapter beats, path to completed first draft.
Mordred's Tale — Statemordreds-tale-stateNarrative fronts, manuscript position, next writing queue.
Mordred's Tale — Task Registrymordreds-tale-tasksWriting and story tasks (draft to completion first; polish phase later).
Mordred's Tale — Decisionsmordreds-tale-decisionsStory and writing decisions (style, timeline, POV).

Section Scope

FieldValue
sectionbooks
sourcerepo-authored books under books/<slug>/
deliveryEPUB output, manifest generation, and reading surfaces
coverageplanning notes that affect publishing, editions, or reading UX

Record Rules

FieldRule
priorityPlanning pages sort before general books docs.
shapeUse fixed fields, short values, and explicit ids instead of prose blocks.
update-triggerChange these records before or with any books workflow change.
follow-on-docsReader and implementation docs come after the planning stack.
agent-loopFollow AGENTS.md: read planning state, pick one books task, implement, verify, then update planning records.
book-planningPer-book planning (e.g. Mordred's Tale) uses the same compact schema: state, task registry, decisions. Update book state and tasks when drafting or revising manuscript.