# ADR-0174: Durable cellular environment profile ## Status and scope Accepted M12.5c durable admission, 2026-10-19. Extends ADR-0142/0143 (population profile and owned intervals), ADR-0172 (joint owner) and ADR-0173 (joint batch). Schema 56. No automatic selection, worker scheduling, census/migration support, default/DEV opening, live upgrade or World0 operation. ## Decision **Checkpoint profile 6** (`cellular_environment_v1`, history profile 6) stores the complete joint envelope `AEVOCEN1`. It nests population envelope 2 only (owner 7 with rules 8 or 9: cellular bundles 10 and 11). Bundle 12 retained-plan populations stay outside until their own durable population admission exists. **Entry is explicit, no-tick and one-way.** `migrate_population_to_environment` takes a committed profile-5 head under the current lease, restores its population, wraps it with the declared environment and requires the nested population bytes to equal the source exactly. SQL binds the source commit, manifest digest and payload digest in `environment_profile_transitions`; the bundle, frame, tick quantum and tick are unchanged and a pending player mutation or interval blocks it. There is no reverse transition: unwrapping would discard environment state that has no other owner. Re-entering profile 5 needs a separately versioned decision. **Publication** of a joint interval or whole-group conversion replays the batch from the committed predecessor before upload and requires the candidate bytes exactly. `publish_environment_checkpoint` validates the joint trace structurally, including the complete nested population batch contract bound to the same identity, predecessor and ticks, and records per-commit totals of imported energy/C/N/P/other and radiated heat. Intervals require schema 45's owned admission: admission now accepts profiles 5 and 6 and the same pending pointer and settlement journal apply. A conversion cannot overtake a pending interval. Exact retries return the original receipt; a reused identity with other bytes conflicts. **Recovery** loads the head, its immutable evidence and its predecessor, then either verifies the transition's byte-identical nesting or replays the joint trace and requires the stored payload exactly. SQL flow totals are audit evidence only; a structurally valid but forged trace that reaches the database through the low-level publisher is refused on recovery, not trusted. Every profile-6 commit requires its evidence: a trigger refuses the generic, raw and population publishers. History/census/migration readers refuse profile 6 explicitly until 12.5d integrates them; the region host does not select it. ## Consequences and qualification Joint ownership now survives process and worker replacement with exact replay, retries and fenced authority, without changing any profile-4/5 byte or rule. The nested ledger's flows remain complete; recorded environmental totals separate them from migration flows for audit. Required evidence: durable bundle 9 -> 10 -> 11, profile 4 -> 5 -> 6, transition retry/conflict/resolution, unadmitted interval refusal, owned interval with matching SQL totals, conversion blocked by a pending interval, settled conversion, cohort interval, bypass-publisher refusal, forged-flow recovery refusal, the upgrade chain and legacy history-domain reconstruction. Executable/network fault drills, census and migration integration, producers and target-host qualification remain open.