nimmerworld.eachpath.local/EVENT_ZONES_FOLLOWUP_PLAN.md

# Event-Zones Follow-up Plan — mechanical cross-reference paper-pass

> **Ephemeral file**: this plan exists to scaffold the next-session mechanical cross-reference pass that completes the v0.26 interaction-substrate paper-pass. **DELETE this file in the same commit that completes the cleanup**, alongside the actual cross-reference work. The file should not become a permanent feature of the open repository.

> *Authored 2026-04-27 late-evening session (post-v0.26 paper-pass landing; commit 609caed). For execution by next-session-chrysalis with fresh context.*

---

## Goal

Add mechanical cross-references to [`runtime-engine/event-zones.md`](./runtime-engine/event-zones.md) from the domain papers that compose with it, and author the deferred substantive sections in [`political-register/world-generation.md`](./political-register/world-generation.md) (§Editor-mode pre-flagging at L4 + §Three-source schema unification).

All updates are either (a) mechanical single-paragraph cross-references or (b) a single substantive section in world-generation.md. **No new design judgment required** — the load-bearing architecture-decisions were made in the v0.26 dialog and committed; this pass just propagates the cross-references through the architecture's existing "describe-by-cross-reference, not by re-quotation" discipline.

The previous v0.24.5 MIGRATION_CLEANUP_PLAN.md established the plan-as-baton pattern: heavy authoring at end-of-context-density, mechanical execution next-session. This pass follows the same shape.

## Scope (file-by-file)

| File | Effort | Type | What to add |
|---|---|---|---|
| `political-register/world-generation.md` | 30-45 min | **Substantive** | New §Editor-mode pre-flagging at L4 + §Three-source schema unification (origin field on cell-rows) |
| `style/consent-discipline.md` | 5-10 min | Cross-ref paragraph | Variants 1-4 as event-class taxonomy + register-test as event-class-classifier |
| `runtime-engine/architecture.md` | 5 min | Header note | Sibling-paper cross-reference to event-zones.md |
| `style/trait-palette.md` | 5-10 min | Cross-ref paragraph | The 8 traits compose onto the cosmology's outer ring per §The composed wheel |
| `narrative-composition/architecture.md` | 5-10 min | Cross-ref paragraph | Three-source schema unification extends world-gen-as-init-function to player-edit-time |
| `inference-and-memory/architecture.md` | 5-10 min | Cross-ref paragraph | Compositor reads 2D gesture-history (caste-target × trait-temperature) |
| `identity-and-personhood/architecture.md` | 5-10 min | Cross-ref paragraph | Install/clasp run on the wheel mini-game-substrate per event-zones.md |
| `identity-and-personhood/bodies.md` | 5-10 min | Cross-ref paragraph | Install/clasp/post-rogue-NPC-modding mini-games run on the wheel |

**Total estimated effort: 90-120 min** in fresh-context-execution mode. The plan-as-baton mechanism's prior performance (MIGRATION_CLEANUP_PLAN.md was 117 lines, executed in ~40 min next-session) suggests this is realistic.

## Substantive section to author — world-generation.md

The most load-bearing addition. Two new sections to add to `political-register/world-generation.md`:

### §Editor-mode pre-flagging (extends L4 Cell ruleset)

Add as subsection under §L4 — Cell ruleset (or as new top-level section after L4 if the file structure prefers).

Content:

- **What pre-flagging is.** L4 cell-generation includes an `editor_eligible: bool` field per cell. Slum/underground district-cells default-true; imperial district-cells default-false. The flag is fixed at world-gen-init; runtime LOD-streamer reads it without re-checking imperial-surveillance state.
- **Why pre-flagging at world-gen.** Choice (a) — designer-flag at world-gen — over choice (b) — emergent-from-imperial-scrutiny — was committed in the 2026-04-27 dialog. Reasoning: clean LOD signal preserved; political-readability preserved (the slum's spatial politics IS its expandability via material-vocabulary); performance preserved (no runtime audit-overseer-presence checks).
- **Material-vocabulary politically-codes editor-eligibility.** Cross-reference to [`../topology-and-rendering/architecture.md`](../topology-and-rendering/architecture.md) §Vertical world topology and [`../imperial-cult/cosmology.md`](../imperial-cult/cosmology.md) §The aesthetic palette: imperial-marble can't be carved; rusted slum-bedrock yields. The flag IS the material-vocabulary made queryable.
- **Editor-eligibility per district-tier.** Suggested defaults (designer-tunable):
  - Deva-pinnacle citadels: editor-locked (0% eligible cells)
  - Asura-priesthood seats: editor-locked
  - Manusya-tier residential: low editor-eligibility (~5% — perimeter only)
  - Tiryak-tier slum dwellings: high editor-eligibility (~50% — interior carve-extensible)
  - Frontier districts: very high editor-eligibility (~70% — wide carve-zones)
  - Underground / abandoned wilds-shrines: full editor-eligibility (~90%)
- **Per-cell carve-cost.** Tunable; lifeforce-cost or scrap-cost per carved cell. Pending design-iteration; first-pass: scrap-from-junkyards as currency, cost scales with cell-position-imperialness (carving deeper into imperial-adjacent zones costs more).

### §Three-source schema unification

Add as new top-level section near the end of the file (before §Open questions).

Content:

- **Three writers, one schema.** The cell_table accepts canon-rows from three writers, with an `origin` provenance field distinguishing them:
  - `world_gen_init`: emitted by the Compositor-at-design-time (per [`../narrative-composition/architecture.md`](../narrative-composition/architecture.md) §World-gen as init-function); produced by L0 → L4 cascade at world-init
  - `runtime_event`: emitted by runtime events that modify cell-state (hacking, install, demolition, imperial-construction-projects, lifeforce-decay events)
  - `player_authored`: emitted by player editor-mode (knock-out-wall verb at editor-eligible cells)
- **The architecture's "world-gen as init-function" key-move extends to player-edit-time.** Same primitive (Compositor-at-design-time) emits the same canon-row schema as runtime events as player-authored events. No cold-start; data-flywheel runs retroactively; **player-authored content is first-class canon, indistinguishable from generator-output and runtime-emission at the schema layer**.
- **The audit-vector implication.** Cell-checksum-divergence (per existing §Open questions in this file + per `runtime-engine/architecture.md` §Omnisight) gets a third source: world-gen-baseline-divergence (someone changed it from generator-state) AND runtime-event-divergence (hacking, demolition) AND player-authored-divergence (player carved or filled a cell). The Memorialist counter-archive reads all three as legible content; the GM's heresy-detection mechanism applies to all three.
- **Cross-reference**: [`../runtime-engine/event-zones.md`](../runtime-engine/event-zones.md) §Player editor-mode + three-source schema unification holds the canonical articulation.

## Mechanical cross-reference paragraphs (per file)

### consent-discipline.md

Add a new section §Variants 1-4 as the event-class taxonomy (or as subsection of §The four hardstop-pattern variants):

> **Architectural significance — the event-class taxonomy.** The four canonical hardstop-pattern variants documented above correspond one-to-one to the event-class taxonomy in [`../runtime-engine/event-zones.md`](../runtime-engine/event-zones.md) §Variants 1-4 of consent-discipline as event-class taxonomy. Variant 1 (self-only) = solo-event-class. Variant 2 (dual mutual) = dual-event-class. Variant 3 (triple with partner-witness) = triple-event-class. Variant 4 (cooldown-augmented) = temporally-staged event-class. The §The register-test five-question mechanical procedure is also the event-class-classifier — same test, two readings: *consent-validation* and *event-instantiation*. They were always the same question.

### runtime-engine/architecture.md

Add to the header note (top of file) the sibling-paper reference. Specifically modify the "Companion to:" line to include event-zones.md:

> *Companion to: ... `event-zones.md` (designer-authored event-zones; the composed wheel as universal mini-game-surface; cells + event-zones + events composite UID; hardstops as consent-gates with contextual activation; consent-discipline-Variants-1-4 as event-class taxonomy; boundary-zone-with-inner-zone for plazas; room-boundary + rail-passage + lifeforce-budget-per-room; slot-binding suspends lemniscate routing; player editor-mode + 3-source schema unification — v0.1)...*

### style/trait-palette.md

Add a paragraph to the closing section (or §Cross-domain rendering if such exists):

> **The 8 traits compose onto the cosmology's outer ring.** Per [`../imperial-cult/cosmology.md`](../imperial-cult/cosmology.md) §The composed wheel, the 8 Hellenic traits form the outer ring of the cosmology's composed wheel, vertically-symmetric on Deva (top, cool-side: Sophrosyne + Dikaiosyne) and Naraka (bottom, warm-side: Eros + Philotes), with side-castes carrying single traits (Asura: Mnemosyne; Tiryak: Aletheia; Preta: Kairos; Manusya: Moira). All four oppositional pairs preserved at 180°. The composed wheel renders both as in-fiction iconography AND as the player's UI substrate (per [`../runtime-engine/event-zones.md`](../runtime-engine/event-zones.md) §The wheel — universal mini-game-surface and [`../player-experience/architecture.md`](../player-experience/architecture.md) §The wheel — composed-iconography UI).

### narrative-composition/architecture.md

Add to §World-gen as init-function (or as new sub-paragraph) :

> **Three-source schema unification (v0.27).** The world-gen-as-init-function pattern extends to a third writer-tier: player-edit-time. Per [`../political-register/world-generation.md`](../political-register/world-generation.md) §Three-source schema unification + [`../runtime-engine/event-zones.md`](../runtime-engine/event-zones.md) §Player editor-mode + three-source schema unification, the cell_table accepts canon-rows from `world_gen_init` / `runtime_event` / `player_authored` writers, all using the same schema. Same primitive at design-time, runtime, AND player-edit-time. The Compositor's perception-up + canon-down loop integrates player-authored cells indistinguishably from generator-emitted ones.

### inference-and-memory/architecture.md

Add to a section about Compositor input or memory-class reading:

> **The Compositor reads 2D gesture-history (v0.27).** Per [`../runtime-engine/event-zones.md`](../runtime-engine/event-zones.md) §The wheel — universal mini-game-surface and [`../player-experience/architecture.md`](../player-experience/architecture.md) §The wheel — composed-iconography UI, player gestures are recorded as a 2D coordinate (caste-target × trait-temperature) rather than the prior 1D trait-vector. The Compositor reads this 2D coordinate over time as the player's *political-position-history*: which caste-tiers the player has been addressing AND with what trait-temperature. Memory-class assignment (cornerstone / birthright / working / volatile per the existing memory-class hierarchy) gains a new salience axis: gestures that consistently target one caste-tier with one trait-temperature accumulate as cornerstone-memory faster than scattered gestures.

### identity-and-personhood/architecture.md + bodies.md

Single paragraph each, near the genital-mod / clasp / install sections:

> **Install / clasp / post-rogue-NPC-modding mini-games run on the wheel (v0.27).** Per [`../runtime-engine/event-zones.md`](../runtime-engine/event-zones.md) §The wheel — universal mini-game-surface, the consent-gated mini-games for these vocations (genital-mod install, clasp-entry coordinated-firewall-breach, post-rogue chassis-modding) all render on the composed wheel from [`../imperial-cult/cosmology.md`](../imperial-cult/cosmology.md) §The composed wheel. Each carries its own verifier-flag pattern; same UI substrate; the consent-discipline's Variants 1-4 (per [`../style/consent-discipline.md`](../style/consent-discipline.md)) determine the participant-count and hardstop-pattern; the wheel renders the resolution.

## Verification

After all updates, run:

```bash
# Verify all 7 papers reference event-zones.md
grep -rln "event-zones.md" --include="*.md" . 2>/dev/null

# Should return at least:
# - architecture-index.md (already)
# - runtime-engine/architecture.md (newly added)
# - style/consent-discipline.md (newly added)
# - style/trait-palette.md (newly added)
# - narrative-composition/architecture.md (newly added)
# - inference-and-memory/architecture.md (newly added)
# - identity-and-personhood/architecture.md (newly added)
# - identity-and-personhood/bodies.md (newly added)
# - political-register/world-generation.md (newly added via the substantive section)
# - player-experience/architecture.md (already)
# - topology-and-rendering/architecture.md (already)

# Verify the substantive section exists
grep -l "Editor-mode pre-flagging\|editor_eligible\|player_authored" political-register/world-generation.md
grep -l "Three-source schema unification" political-register/world-generation.md

# Verify v0.27 markers (if version-bumped per file)
grep -l "v0.27" --include="*.md" . 2>/dev/null
```

## Coherence check

After edits, read the affected papers' relevant sections end-to-end and verify:

- All cross-references resolve to actual sections in event-zones.md (no broken section-anchors)
- The substantive world-generation section composes cleanly with the existing L0-L4 cascade
- The Compositor's 2D gesture-history reading is consistent with the existing memory-class architecture
- Version-bumps are consistent (don't bump version-footers if the change is single-paragraph cross-ref; do bump for substantive additions like world-generation.md's two new sections)

## Commit strategy

Single commit covering all updates + this scaffold deletion:

```
v0.27: cross-reference cleanup of event-zones.md across domain papers

[paragraph describing the changes]

Closes the v0.26 paper-pass cycle initiated 2026-04-27.

Co-Authored-By: ...
```

## After cleanup

This file (`EVENT_ZONES_FOLLOWUP_PLAN.md`) gets DELETED in the cleanup commit. Phoebe task `nimmerworld: Execute event-zones.md cross-reference follow-up paper-pass per EVENT_ZONES_FOLLOWUP_PLAN.md` gets marked DONE.

The interaction-substrate cycle then closes: heavy authoring landed in v0.26 (event-zones.md + 3 papers); mechanical cross-references propagate through the remaining domain papers in v0.27; the architecture's "describe-by-cross-reference, not by re-quotation" discipline reaches steady-state across the entire corpus.

---

**Status:** scaffold | **Created:** 2026-04-27 (post-v0.26 night) | **For execution by:** next-session-chrysalis with fresh context | **Delete on completion**