diff --git a/docs/adr/0114-cellular-first-life-publication.md b/docs/adr/0114-cellular-first-life-publication.md new file mode 100644 index 0000000..8686bd3 --- /dev/null +++ b/docs/adr/0114-cellular-first-life-publication.md @@ -0,0 +1,87 @@ +# ADR-0114: First player life in cellular profile 4 + +## Status + +Proposed M11.3d contract; not yet accepted. No implementation or gameplay +constant is authorized by this proposal alone. It resolves the gap between the +empty profile-4 genesis and the 11.3e requirement that a player can enter the +cellular stage. + +## Context + +ADR-0100 requires owner-provisioned primitive genesis to start with no +organisms, and requires life, organism, genome, and event identities to come +from the durable world allocator. ADR-0108 gives cellular state its own +immutable profile and says profile-4 cloning is unsupported until identity and +source-total remapping are specified. `CellularLives::create` can wrap a +profile-3 opening in memory, but the existing owner provisioner creates only +profile-3 genesis and the cellular publisher accepts only profile-4 successors. +There is no supported transition that can turn a profile-3 life into a +profile-4 founder. + +The early 11.3e probe requires a player to spawn, then perceive, steer, seek, +and feed. Directly putting a cell in profile-4 genesis would contradict the +empty-genesis rule and bypass the ordinary world-scoped identity allocator. +Copying a profile-3 checkpoint into profile 4 would violate profile immutability +and the unresolved clone remapping contract. + +## Proposed decision + +- Keep profile-4 genesis empty. Do not seed a founder, import profile-3 lives, + accept client-chosen identities, or infer an opening from defaults. +- Extend the existing reliable v5 new-life request to the profile-4 owner + without changing its wire encoding. The authenticated account and stable + request identity remain authoritative; the host obtains identity allocation, + control generation, finite nursery funding, and the first free provisioned + site from the existing server-side contracts. +- Add a canonical profile-4 birth record to the durable replay evidence. It + binds the predecessor checkpoint, authenticated account/request, allocated + identities, source debit, selected site, derived founder body/reserve, and + construction heat. The values are replay inputs/results, not client claims. +- Publish the birth record, account/life binding, immutable request outcome, + archive update, source debit, heat, and complete profile-4 checkpoint + atomically under the current region lease and account-control generation. + Failed funding, placement, allocation, stale control, or uncertain publication + must leave no acknowledged partial birth. Exact retries return the durable + original result; changed reuse is refused. +- Birth does not simulate elapsed time. The durable commit sequence advances; + biological tick advances only when a normal cellular tick is committed. If + the current publisher/schema cannot represent a same-tick birth commit, extend + its versioned trace and bounds rather than pretending the birth was a tick. +- Recovery replays the birth from its verified predecessor before replaying any + cellular ticks and compares the complete recovered state and action outcome. + The life remains frozen whenever its owner is disconnected, consistent with + the offline-fairness requirement. +- This contract enables the single-region 11.3e probe only. It does not claim + cross-region owner routing, resume, death/re-entry, reproduction, or completion + of M11.2. Those remain separately gated. + +## Alternatives considered + +- **Put a cell directly in profile-4 genesis:** rejected because genesis is + explicitly empty and this bypasses the durable allocator and birth operation. +- **Convert or clone a profile-3 checkpoint:** rejected because region profiles + are immutable and profile-4 cloning/remapping is explicitly unresolved. +- **Let the client supply IDs or a position:** rejected because identity + allocation and placement are server-owned. +- **Advance one simulation tick to record a birth:** rejected because a spawn + operation must not consume biological time or permit offline progression. +- **Add another wire layout for the same request:** not preferred; the accepted + v5 request already carries the authenticated account-scoped new-life + operation. A new layout is justified only if implementation finds a missing + semantic field that cannot be supplied by authoritative server state. + +## Benefits and costs + +The proposal preserves empty genesis, profile immutability, allocator ownership, +finite funding, and exact retry semantics while providing an ordinary player +entry path into the cellular owner. It requires a new canonical birth trace, +profile-4 same-tick publication semantics, server admission wiring, and +concurrent/restart tests before the 11.3e probe can run. + +## Consequences + +Until this proposal is accepted and implemented, `evo-world-clone` must not gain +a shortcut that creates a profile-4 founder, and the M11.3e gate is not +playable. After acceptance, the work belongs to the profile-4 owner/session +path; it must not change the headless simulation boundary or M10 probe behavior. diff --git a/docs/adr/README.md b/docs/adr/README.md index bd4a23d..bcace05 100644 --- a/docs/adr/README.md +++ b/docs/adr/README.md @@ -14,6 +14,7 @@ - [ADR-0111: Durable identity for cellular player inputs](0111-cellular-durable-action-identity.md) - specifies the reliable v7 action identity needed for commit-bound cellular outcomes and exact retries. - [ADR-0112: Durable cellular action input records](0112-cellular-action-ledger-records.md) - specifies canonical retry bytes, persisted result identity and the isolated profile-4 publisher needed before v7 admission. - [ADR-0113: Cellular replay trace](0113-cellular-replay-trace.md) - specifies bounded per-tick life intentions for deterministic profile-4 replay and durable action reconciliation. +- [ADR-0114: First player life in cellular profile 4](0114-cellular-first-life-publication.md) - proposed, not accepted: preserve empty genesis and add an allocator-backed, durable profile-4 birth operation so the 11.3e probe can start through the normal player path. - [ADR-0058: Region durability contract](0058-region-durability-contract.md) - accepted M7.1 full checkpoint batches and explicit state closure; storage implementation follows. diff --git a/docs/engineering/M11_2_DELIVERY_PLAN.md b/docs/engineering/M11_2_DELIVERY_PLAN.md index e8d3fda..b0cf437 100644 --- a/docs/engineering/M11_2_DELIVERY_PLAN.md +++ b/docs/engineering/M11_2_DELIVERY_PLAN.md @@ -142,3 +142,13 @@ Local checks do not close ADR-0097's reference-worker qualification. specify a server-side router. Do not treat a client-provided endpoint as trusted. No deployed world has been provisioned or changed by this work. + +## Profile-4 entry dependency + +M11.2's primitive host provisions profile 3, whose region profile is immutable. +M11.3 cannot use that checkpoint as a cellular opening, and profile 4 must start +empty. The 11.3e player-entry dependency and proposed resolution are recorded +in [ADR-0114](../adr/0114-cellular-first-life-publication.md). Do not treat a +profile-3-to-4 conversion or a manually seeded founder as an implementation +shortcut. Cross-region routing and reconnect-to-owner remain separate open 11.2 +gates. diff --git a/docs/engineering/M11_3_DELIVERY_PLAN.md b/docs/engineering/M11_3_DELIVERY_PLAN.md index 4cd8748..dd2c3a6 100644 --- a/docs/engineering/M11_3_DELIVERY_PLAN.md +++ b/docs/engineering/M11_3_DELIVERY_PLAN.md @@ -283,6 +283,15 @@ scoped change before starting the next segment. candidate with independent trace replay and cover cross-tick action-ID reuse. The service loop, profile-4 genesis tooling, process kill tests and CI execution remain open. +- 11.3d-7e contract conflict: a playable cellular stage needs a player life, but + ADR-0100 requires empty genesis and allocator-issued identities, while + ADR-0108 keeps profile 3 immutable and leaves profile-4 conversion/cloning + unsupported. Do not add a founder-seeding provisioner. Proposed ADR-0114 + resolves this with an allocator-backed profile-4 birth operation using the + existing reliable v5 request, a canonical birth replay record, and an atomic + same-biological-tick checkpoint publication. This remains a proposal; no + profile-4 entry path or 11.3e playtest is available until the contract is + accepted, implemented and qualified. ## Exit boundary