Files
aevolution/schemas/primitive-publication-v1.md
dingo 58aff5adeb
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m54s
Foundation / checks (client) (push) Successful in 12m21s
Foundation / checks (network) (push) Successful in 13m52s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (tsan) (push) Canceled after 2m34s
Foundation / checks (postgres) (push) Canceled after 6m8s
Foundation / checks (checks) (push) Canceled after 18m34s
Add guarded atomic primitive-life publication (M11.2c-2c)
2026-10-10 10:57:13 -04:00

2.6 KiB

Primitive birth publication (schema v16)

ADR-0100, M11.2c-2c. Migration 0016 admits manifest profile 3 and adds one guarded publication transaction. It does not add biological ticking. The payload must already be replayed and its immutable object-store length/digest verified; this database stores the same commit evidence as existing profiles.

publish_primitive_checkpoint(manifest, trace) parses the canonical manifest and bounded primitive-batch-v1 trace, then checks world/region/frame, predecessor ID and digest, begin/end ticks, trace digest, record order and bounds. For each birth it verifies the world/account/request reservation, shared identity, founder rules, original owner region, no prior binding and exact durable account-control generation under the current region lease. Accounts lock in UUID order. Lease and control are rechecked after waits.

In one SQL transaction it appends the commit-bound trace and immutable primitive_life_bindings, then calls the existing chain publisher to advance the head. A database refusal rolls every write back. The commit trigger requires the private trace evidence for every non-genesis profile-3 commit, so the two existing generic runtime publishers cannot publish such a commit around the guard. Probe action rows cannot be attached. A published life's reservation cannot later be changed into a refusal. Bindings are append-only; schema v16 has no death or respawn transition.

An exact retry returns the original receipt. If it waited behind the commit, the function checks the private evidence again before checking births. Changed bytes under the same commit ID are a conflict; a second commit for the same life is refused. A different commit may carry an empty birth batch and advance the owner checkpoint tick without advancing biology. Unknown connection outcome requires reconnect and exact-byte retry. Reservation status by itself remains insufficient for spawn success.

load_primitive_lives(world, region) returns the bounded, durable account/request, identity, birth-tick and commit binding set for reconciliation. Session generations are deliberately reacquired; they are not restored as authority. Recovery still must restore the object, replay each committed trace from its manifest predecessor, compare the canonical payload and reconcile this binding set before a host can be ready. The generic two-profile recovery host does not yet support profile 3.

The atomicity/fencing tests use a fresh PostgreSQL cluster, full portable payload and trace codecs, and a real runtime role. World 9753 is test-only. No production world is provisioned by migration or tests.