Accept profile-4 first-life path
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 4s
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 4s
This commit is contained in:
@@ -2,10 +2,11 @@
|
||||
|
||||
## 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.
|
||||
Accepted M11.3 engineering direction under the maintainer's standing
|
||||
authorization to proceed with recommendations and revisit decisions after
|
||||
implementation. It adds no gameplay constant. Implementation, PostgreSQL
|
||||
qualification and CI remain open. This resolves the gap between empty profile-4
|
||||
genesis and the 11.3e requirement that a player can enter the cellular stage.
|
||||
|
||||
## Context
|
||||
|
||||
@@ -25,7 +26,7 @@ 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
|
||||
## 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.
|
||||
@@ -34,24 +35,29 @@ and the unresolved clone remapping contract.
|
||||
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.
|
||||
- Extend the profile-4 per-tick replay trace with a bounded birth set after the
|
||||
tick's existing-life intentions. Each record binds the authenticated account,
|
||||
stable v5 request ID, durable control generation and allocator-issued life
|
||||
identity. Organism, genome and event identities use that same reserved value
|
||||
in their distinct namespaces, as in the existing primitive-life path. Source,
|
||||
site, body, reserve and construction heat are re-derived by deterministic
|
||||
replay from the committed predecessor and are 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.
|
||||
- Birth is applied after the existing lives' normal tick. It shares that tick's
|
||||
checkpoint commit, is born at its end tick, and first acts on the following
|
||||
tick. When the region is empty, the first empty tick creates the first life;
|
||||
no organism advances or accrues offline time. Do not add a second birth-only
|
||||
tick or use spawn to progress an existing life.
|
||||
- Recovery replays each tick's existing-life intentions, then its canonically
|
||||
ordered births, and compares the complete recovered state and durable request
|
||||
outcomes. For the first single-player probe, the scheduler does not advance
|
||||
the region while its only living player's session is absent. Multi-life
|
||||
disconnect behavior remains governed by later M11 gates.
|
||||
- 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.
|
||||
@@ -64,8 +70,9 @@ and the unresolved clone remapping contract.
|
||||
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.
|
||||
- **Run birth as a separate biological tick:** rejected because a new life must
|
||||
not make existing lives lose an action opportunity or receive hidden offline
|
||||
progress.
|
||||
- **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
|
||||
@@ -73,15 +80,15 @@ and the unresolved clone remapping contract.
|
||||
|
||||
## 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.
|
||||
The direction 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 an extended
|
||||
canonical birth trace, atomic life-binding publication, 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.
|
||||
`evo-world-clone` creates empty profile-4 genesis only. The M11.3e gate remains
|
||||
unplayable until this birth operation and the tick/view path are implemented and
|
||||
qualified. The work belongs to the profile-4 owner/session path; it must not
|
||||
change the headless simulation boundary or M10 probe behavior.
|
||||
|
||||
+1
-1
@@ -14,7 +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-0114: First player life in cellular profile 4](0114-cellular-first-life-publication.md) - accepted M11.3 engineering direction: 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.
|
||||
|
||||
|
||||
@@ -283,15 +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
|
||||
- 11.3d-7e contract resolution: 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.
|
||||
unsupported. ADR-0114 now directs an allocator-backed profile-4 birth using
|
||||
the existing reliable v5 request. Its canonical birth record follows the
|
||||
existing-life inputs at the end of a normal tick and publishes with that
|
||||
checkpoint; this does not seed genesis or add a birth-only tick. The durable
|
||||
birth trace, publisher, recovery, host, session and restart tests remain open;
|
||||
11.3e is not playable yet.
|
||||
- 11.3d-7f: the owner persistence API and `evo-world-clone provision
|
||||
--opening cellular-v1` now create only an empty profile-4 genesis. The CLI
|
||||
requires explicit arena dimensions, temperature, nursery funding, ordered
|
||||
|
||||
Reference in New Issue
Block a user