Files
aevolution/docs/engineering/M12_DELIVERY_PLAN.md
T

2.9 KiB

M12.1-12.5 delivery and prerequisite conflicts

Requested scope: ecological identity, population qualification, durable automatic tier transitions, unattended scheduling/migration and environmental coupling. Commit and push each validated scoped segment separately.

Gate status (2026-10-15)

Subset State Evidence or condition for completion
12.1 Engineering evidence policy and explicit deferrals documented ADR-0133, identity/time contract and worked histories; no new game rules or runtime versions.
12.2 Qualification open; automatic tier selection disabled ADR-0041 rejects every tested width. Reproduce failures, then qualify a model against M11 cellular rules with hold-outs and target-host budgets.
12.3 Blocked on 12.2 No accepted population model, deterministic durable conversion sample or profile integrating cellular/cohort state.
12.4 Blocked on 12.2-12.3 Existing cellular worker pauses without sessions/lingering players; bounded unattended recovery and biological migration escrow remain unimplemented.
12.5 Blocked on 12.2-12.4 Finite M6 process fixtures do not qualify coupled persistent cellular/cohort atmosphere/water budgets.

M12's roadmap entry also requires the M11 playable-loop product review. The M11.9 plan records engineering delivery and a first sign-in playtest, but no completed repeated-life results or product acceptance. Beginning policy work does not fabricate that acceptance.

Architectural conflict and resolution

Automatic transitions or regional aggregation now would conflict with ADR-0041 and ECOLOGY_MODEL: the measured model can erase viable populations while exactly conserving inventory. The M4 test-only model is not the M11 spatial cellular model; wrapping its in-memory conversion primitives in persistence would not qualify it. Under the engineering constitution, stop expanding the affected implementation.

Resolve this by retaining the failed baseline and adding a separately versioned candidate experiment that preserves relevant age/reserve/genome variation. Before running it, declare population/biomass/diversity trajectory bounds, extinction criteria, supported cellular states and hold-out seed/regime splits. Compare against the accepted M11 controller, contact, contested intake, budding, death and offline rules. An exact retained-member control can check the instrument but cannot by itself establish useful aggregation or acceptable target-host cost.

Measure bin/interval sensitivity, conversion and full-region costs on the Linux target host, including active fallback capacity and backpressure. Passing the M4 synthetic envelope alone is insufficient. Record M11's product review separately. Only then accept the model/tier ADR and proceed to 12.3, followed by owned durable intervals/escrow in 12.4 and versioned finite resource coupling in 12.5. No World0 deployment or promotion follows from these gates.