Document cellular profile-4 first-life contract
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s

This commit is contained in:
dingo
2026-10-10 23:51:34 -04:00
parent 82bef03138
commit 140687da97
4 changed files with 107 additions and 0 deletions
+10
View File
@@ -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.
+9
View File
@@ -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