M12.4: retain read-only destination migration stages
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m25s
Foundation / checks (network) (push) Successful in 20m44s
Foundation / checks (client) (push) Successful in 21m57s
Foundation / checks (tsan) (push) Successful in 22m46s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 30m2s
Foundation / checks (postgres) (push) Canceled after 29m56s

This commit is contained in:
dingo
2026-10-18 09:32:50 -04:00
parent c625a4cb68
commit 0515702964
21 changed files with 1023 additions and 21 deletions
@@ -140,3 +140,26 @@ and canonically encoded false member/material declarations fail complete replay.
See [the contract](../../schemas/ecology/cellular-migration-freeze-v1.md).
Destination staging, atomic paired head publication, commit/abort races and
activation remain the next segment; no route or automatic migration is enabled.
## M12.4i durable read-only destination staging
ADR-0148/schema 48 freezes the destination at its exact captured head under
current destination authority and ordered endpoint locks. The adapter restores
both cuts, replays the retained trace, copies the source capsule into the
destination namespace and uploads/reads back the derived destination ghost.
Its exact digest/length is immutable retry evidence, not an ownership receipt.
Recovery uses those local objects and compares the complete rederived ghost.
Neither biological head moves, and the source still owns all outgoing stock.
Both local migration roles are exclusive and block new publication, profile
changes, intervals and player reservations. Unknown staging retains exact bytes;
the owning destination pauses readiness/advancement through worker replacement.
Source abort serializes with staging and releases both pointers atomically.
Aborted-stage retries return their old outcome and never reopen a pause.
Missing/corrupt evidence and real but semantically false objects fail closed.
See [the staging contract](../../schemas/ecology/cellular-migration-stage-v1.md).
Atomic paired publication/common receipt, commit/abort races, recovery/activation
and linked ecology remain subsequent work. The ghost cannot run biology or
contribute owned census/extinction stock. No biological format, rule, route,
automatic movement, live region or deployment changes.
+6 -3
View File
@@ -64,9 +64,12 @@ or close source-freeze/destination-activation and escrow qualification.
ADR-0147/schema 47 now adds durable source preparation/freeze, retained replay
capsules, explicit abort and host pause/recovery. Source stock remains owned at
its exact head through worker replacement; no timeout or drain releases it.
Destination staging, atomic paired commit, commit/abort races and activation
remain open. The destination head is only checked optimistically at preparation
and must be rechecked before any future stage/commit.
ADR-0148/schema 48 now supplies destination-authorized staging at its exact
captured head, verified read-only ghost/capsule retention and full destination
recovery. Both endpoints stay paused; explicit source abort atomically releases
both pointers and races safely with staging. Atomic paired commit, its common
receipt, commit/abort races and activation remain open. Preparation remains an
optimistic destination observation; first staging rechecks both captured heads.
The transfer tests also expose the current rules-8 maturation gap: buds retain
their subadult realization while reproduction requires a fully realized parent.
Finite extra food alone does not close repeated wildlife generations. A versioned
+13
View File
@@ -32,6 +32,19 @@ the C++ decoder. The metric has one fixed unlabelled series and remains bounded.
These are preparation/abort checks, not proof of destination activation or atomic
paired publication; full historical persistence regression is also required.
M12.4i's private staging matrix covers both bundle-10 representations and actual
player-origin wildlife. It requires unchanged biological heads, complete ghost
replay, exact/conflicting retries, refusal of moved destination heads and pending
intervals, publication/profile/life-reservation guards and exclusive endpoint
roles. Stale destination epochs fail; replacement retains the read-only ghost.
Missing source capsules, missing/same-length corrupt ghosts and valid but false
ghost objects fail recovery. Real lock-timeout ambiguity, SIGKILL before/after
stage commit and independent-connection stage/abort races preserve one outcome.
The owning destination host retains exact uncertain work across restart and
resumes only its original biology after confirmed source abort. Full schema,
permission, backup/DR and historical regression remain required. These tests do
not qualify paired commit, destination activation or linked ecological movement.
Tests defend contracts, not directory coverage. All checks remain active in
Release builds. Current proof has no actual network, biology or distributed
recovery, so those categories below are milestone gates rather than passing
+48
View File
@@ -1,5 +1,53 @@
# Validation report
## 2026-10-18 - M12.4i durable read-only destination staging
ADR-0148/schema 48 retains a destination-authorized staging record and bounded
pending pointer at the exact captured head. The adapter verifies both cuts,
replays the trace and retains a source capsule plus verified destination ghost
in the destination namespace. The source owns all outgoing stock; neither head
moves. Source abort releases both pending pointers atomically, and exact stage
retries retain their original outcome. Both migration roles are exclusive.
Executed locally:
- Native MSVC Release **78/78 passed**, 12.62 s.
- Actual GCC 14 optional server/persistence targets rebuilt; final private
PostgreSQL population/staging suite passed, **11 s** (8 s test phase).
- Linux Clang 19 ASan/UBSan private population/staging suite passed, **33 s**
(30 s test phase), with no sanitizer reports.
- Explicit clang-tidy 19 on the adapter, owning host and PostgreSQL population
tests passed with no owned warnings. Repository clang-format 19 and both
changed shell scripts' syntax checks passed.
- Complete frozen-binary private PostgreSQL qualification passed with **exit 0**,
**501 s**: C++ integration/process/load/history (426 s), life reservations,
backup/restore, host-loss DR, upgrade, migration history/rollback, runtime
permission audit and checksum/future-version rejection. The detached runner
recorded its completion code.
Both representations use real funded player-origin wildlife and unchanged cuts.
Cases cover exact/conflicting retries, a moved destination, pending destination
intervals, source/destination role exclusivity, blocked publication/profile/life
reservations and stale destination authority. Replacement epochs retain staging.
Missing source capsules, missing and same-length corrupt ghosts fail strong
binding. An existing valid object with false destination biology fails complete
replay. Real lock-timeout ambiguity retains exact requests; SIGKILL before/after
stage commit leaves absence/a retained pause respectively. Independent database
connections race stage against source abort without stranded destination work.
The owning destination host pauses on unknown staging, survives drain/recreation
without adopting the ghost and resumes its identical original state after source
abort. The existing fixed freeze metric covers either role without new labels.
Limits: this is staging evidence, not a migration result or activation receipt.
Atomic paired publication, its common immutable outcome, commit/abort races and
recovery/activation remain open. Backup retains all immutable namespace objects;
existing backup/DR fixtures do not qualify cellular cloning or a new cellular
restore procedure. No elapsed-day, linked-geometry or multigeneration claim
follows. No live database, World0, deployment, dependency, biological rule, format
or golden changed. The earlier captured `Build_Errors.txt` and unrelated local
work remain untracked; remote CI confirmation of the previous runner repair
remains separate.
## 2026-10-18 - M12.4h durable migration source freeze and explicit abort
ADR-0147/schema 47 retains exact source-authorized preparation, both predecessor