Add corpus coverage ledger

notes/documentation-inventory.md

@@ -38,6 +38,8 @@ not slowly melt into one cursed binder.
   format.
 - `docs/architecture/aetheria-lore-grounding-architecture.md`: Aetheria
   historical, future-branch, and procedural grounding boundaries.
+- `docs/architecture/corpus-coverage-ledger.md`: corpus coverage ledger
+  contract and status-report shape.
 - `docs/architecture/technology-item-manifest-plan.md`: item, assembly,
   supply-chain, trade-good, and blueprint data target.
 - `docs/architecture/training-plan.md`: trainable organs, datasets, gates, and
@@ -76,6 +78,8 @@ not slowly melt into one cursed binder.
 - `state/evidence.jsonl`: distilled current evidence ledger.
 - `state/evidence.archive.jsonl`: archival evidence ledger.
 - `state/branches.json`: branch ledger.
+- `state/corpus-coverage.json`: machine-readable coverage ledger for accepted,
+  draft, planned, rejected, and superseded Aetheria fixtures.
 - `state/scratch.md`: disposable one-subgoal scratch surface.
 
 ## Maintenance Rule

notes/fresh-workspace-handoff.md

@@ -56,6 +56,8 @@ The active path is a source-grounded branching-scene data loop:
 - Responder packet schema: `schemas/responder-packet.schema.json`
 - Responder output schema: `schemas/responder-output.schema.json`
 - Prompt folder: `prompts/`
+- Corpus coverage ledger: `state/corpus-coverage.json`
+- Corpus coverage command: `npm run coverage:status`
 - Sandboxed responder prompt template: `prompts/sandboxed-responder-packet.md`
 - Research sanity responder prompt template: `prompts/research-sanity-responder.md`
 - Narrative quality reviewer prompt: `prompts/narrative-quality-reviewer.md`
@@ -135,8 +137,9 @@ steering surfaces unless the user explicitly asks for archaeology.
 
 ## Current Next Action
 
-Add the corpus coverage ledger seam or choose the next Aetheria fixture from the
-100-150 broad coverage target.
+Use the corpus coverage ledger to choose the next Aetheria fixture from the
+100-150 broad coverage target. Current coverage begins with Pallas Species
+Strikes as the first accepted-as-draft row.
 
 ## Warnings
 

notes/ghostlight-current-system-map.md

@@ -18,6 +18,7 @@ validated artifact seams for producing reviewed training data.
 - `state/map.yaml`: canonical mission, boundaries, live architecture, next action.
 - `state/evidence.jsonl`: distilled belief-changing evidence only.
 - `state/evidence.archive.jsonl`: older evidence preserved for archaeology.
+- `state/corpus-coverage.json`: accepted/planned fixture coverage ledger.
 - `notes/fresh-workspace-handoff.md`: compact re-entry packet.
 - `notes/ghostlight-implementation-plan.md`: near-term implementation sequence.
 - `docs/architecture/`: detailed contracts and rationale.
@@ -79,6 +80,7 @@ the room.
 - Ink branch contract: `docs/architecture/ink-branching-scenes.md`
 - Illustrated IF visual pipeline: `docs/architecture/illustrated-if-visual-pipeline.md`
 - Training stages and corpus gates: `docs/architecture/training-plan.md`
+- Corpus coverage ledger: `docs/architecture/corpus-coverage-ledger.md`
 
 ## Current Live Example
 
@@ -118,7 +120,7 @@ paths as active state surfaces.
 - Full scene/event loop implementation
 - Culture prior engine
 - Automatic promotion of branch outcomes into canonical state
-- Corpus coverage ledger
+- Corpus coverage ledger expansion beyond the initial Pallas row
 
 ## Current North Star
 
@@ -129,3 +131,6 @@ receipts, branch compiler artifacts, IF review findings, visual scene plans, and
 clear branch consequences. The samples should also train tonal control: a
 fixture needs an intentional prose mode and enough ordinary life for consequence
 to matter.
+
+Use `npm run coverage:status` before choosing new fixtures so the corpus grows
+by coverage need instead of proximity to the nearest interesting disaster.

notes/ghostlight-implementation-plan.md

@@ -42,7 +42,7 @@ not carry live next-action lists.
    - Preserve the lessons it established: ordinary-life onboarding, branch-and-fold discipline, material state variables, source-backed lore elaboration, visual segmentation, scene-set need for illustrated replay, and review before acceptance.
 
 4. Generalize the loop.
-   - Add the corpus coverage ledger seam so future fixtures can be tracked by faction, movement, flashpoint, tonal mode, training target, review status, and cultural collisions.
+   - Use the corpus coverage ledger so future fixtures can be tracked by faction, movement, flashpoint, tonal mode, training target, review status, and cultural collisions.
    - Select the next Aetheria fixture from the 100-150 broad coverage target.
    - Add more historical grounded fixtures from AetheriaLore.
    - Add future-branch Elysium fixtures with branch lineage and constraint labels.