# Presentation chapter procedure under Eve publication

Decision recorded in the board-polish session on 2026-09-23: Elikem said “Publish per chapter” (board task `presentation-center-eve-redesign:EI.0.21`): a chapter's slide changes are authored as Eve revisions, reviewed independently, published by Elikem, and verified against that publication. This restates the chapter procedure of the Eve V1 presentation redesign for that path. It replaces every step that edits or builds from `docs/presentations/presentation-center/content/*.json` or `catalog-source.json`; those files left the repository on 2026-09-22 (d092109ae62).

## Where things live

- An existing chapter is an Eve presentation document whose legacy path is `docs/presentations/presentation-center/content/<nn>-<guide>.json`. Read it with `./eve docs show <that path>`.
- A new chapter or guide is a new Eve presentation document. When published, `tools/presentations/build-eve-oshun.py` adds it to the catalog (`new_publication_chapters`, `published_catalog`).
- Tracks, reading routes and chapter placement are the catalog document (legacy path `docs/presentations/presentation-center/catalog.json`: `tracks`, `trackOrder`, the `track` on each entry). The builder reads it from the publication (`build-eve-oshun.py:822`), so a track declaration is a revision of that document, not of `catalog-source.json`.
- Briefs, receipts and domain documents are Eve documents.

## The steps of a chapter

1. **Brief and section dividers**: Eve documents, as before.
2. **Slide edits** (cover and close, retitling, notes, per-slide treatments, pinned sources, glossary slides, new slides): revisions of the chapter's Eve document through the content API or the `eve` MCP tools. Read the current revision first and keep the retry identity. Run the edition's validators on the revised document where they accept a file (`tools/presentations/presentation_eve_edition.py`, the chapter budget guard). A slide-edit task closes when its revision is submitted for independent review; its evidence is the document id and revision. It does not wait for publication.
3. **Diagram data** is generated from the repository, as before, and goes into the chapter's Eve document.
4. **Review**: an independent reviewer (never the author) approves the revisions through `./eve reviews` or the `eve` MCP review tools.
5. **Publication**: Elikem publishes the reviewed revisions. The rebuild step waits for this. If a chapter's revisions are reviewed but not yet published, the worker on the rebuild step parks it with `--reason governance`, naming the exact document IDs and revisions that need independent approval or owner publication. A preview does not replace that reviewed publication. Workers do not freeze content, publish, promote UAT, or approve their own revisions.
6. **Rebuild and check**: use the publication ID and manifest hash from the tested Dev release's worker-input receipt, with the worker's own scoped API configuration. Export into a new private directory outside Git with `node tools/eve-content/export-publication.mjs --id <publication.id> --manifest-hash <publication.manifestHash> --directory <work>/bundle --cache <work>/media-cache`. Prepare a separate verified reader with `node tools/eve-content/prepare-publication.mjs --root <checkout> --bundle <work>/bundle --manifest-hash <publication.manifestHash> --directory <work>/reader --lfs-exclusions <input-bundle>/lfs-exclusions.json`. The checkout must contain the publication's pinned commit. Preserve the returned `indexHash` and `contextHash`; set `EVE_PUBLICATION_SOURCE=<work>/reader`, `EVE_PUBLICATION_INDEX_HASH=<indexHash>`, `EVE_PUBLICATION_CONTEXT_HASH=<contextHash>`, `EVE_INPUT_BUNDLE=<release's sealed input bundle>` and `SOURCE_DATE_EPOCH=<recorded epoch>` for each consumer. Request a missing verified bundle from platform operations; do not recapture mutable task or Git state. For publications predating input bundles, use the pinned historical Git commit and the export's `createdAt` epoch as specified in repository AGENTS.md. Run sequentially: `python3 tools/presentations/build-eve-oshun.py --output <work>/presentations`, `python3 tools/render-docs-center.py`, then `node tools/build-assistant-docs-search.mjs --presentations <work>/presentations`. Run presentation freshness `--check` against that output and the applicable targeted Python, Node and browser suites. Open every changed slide in the browser; this is where the tracker's "open the slide in the browser" rule is met. These commands consume an existing publication and do not publish it.
7. **Narration, screenshots, PDF**: render and verify narration from the checked build first; then capture and check screenshots with audio chrome; then export and check the PDF after overflow repairs. Media and captures go to Eve as media, with their provenance. These checks use the same publication and verified reader as the rebuild.
8. **Receipt**: an Eve document naming the publication, the build command and its results, the edition, and the layout counts (table-like share, diagram count, capture count). The chapter's `./eve done` evidence cites the receipt's document id.

The required order for unfinished chapter work is: brief → section dividers → all slide edits → applicable binding and evidence re-review → rebuild → narration → screenshots → PDF → receipt. Once dependency repair is implemented and verified, each stage must wait for all tasks in the preceding stage; optional stages without task rows are skipped. Completed task definitions and additional chapter-specific prerequisites are preserved. Dependency repair under EI.0.21 is still incomplete. The 2026-10-05 live snapshot records 97 chapters with 1,230 missing prerequisite paths; the board must not be described as enforcing this order until a fresh audit reports zero missing paths. The read-only command `node tools/presentations/chapter-order.mjs --out <private-evidence.json>` records exact task versions and verifies prerequisite paths; it neither changes task state nor authorizes publication.

## Phase 0

Section 0.10 (EI.9.01) now creates a content-API revision awaiting review instead of writing files. Section 0.11's verifier (EI.10.01) reads the published revision. Section 9's rule that nothing starts before 0.12 is recorded does not hold chapter work back: Elikem chose to publish per chapter.
