Files
aevolution/docs/engineering/M12_DELIVERY_PLAN.md
T
dingo 214991c9a3
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m26s
Foundation / checks (tsan) (push) Successful in 11m44s
Foundation / checks (client) (push) Successful in 19m23s
Foundation / checks (network) (push) Successful in 19m45s
Foundation / checks (checks) (push) Successful in 45m39s
Foundation / checks (postgres) (push) Successful in 45m56s
Foundation / postgres-tools (push) Successful in 23s
Foundation / server-image (push) Successful in 31s
Foundation / image (push) Successful in 3m35s
M12.2b: test exact reserve-strata population candidate
2026-10-16 06:01:42 -04:00

3.7 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-16)

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 Baseline reproduction (12.2a) and exact-strata instrument (12.2b) complete; cellular qualification open The old widths remain rejected. The new exact-state experiment matches 83 synthetic trajectories, including 40 held-out cases. M11 paired multi-genome ensembles and target-host fallback budgets remain required.
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.

Executed 12.2a results and remaining limits: M12_POPULATION_QUALIFICATION. Release CTest passed 69/69 outside the filesystem sandbox. No production model was adopted.

12.2b now implements the separately versioned exact-reserve/age research candidate proposed below: experiment results, ADR-0134. It removes the synthetic false-extinction mechanism but often retains one row per individual. Release CTest passed 70/70, with Linux analysis and ASan/UBSan checks. Next is the M11 paired cellular instrument and supported-state/model review; neither exact synthetic fidelity nor workstation costs qualify a production tier.

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.

The isolated 12.2b candidate retains the failed baseline and exact age/reserve variation; it does not yet address cellular/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.