feat(persistence): admit durable funded maturation upgrades
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (ecs) (push) Successful in 2m24s
Foundation / checks (network) (push) Successful in 20m40s
Foundation / checks (client) (push) Successful in 21m57s
Foundation / checks (tsan) (push) Successful in 26m32s
Foundation / checks (postgres) (push) Successful in 1h3m17s
Foundation / checks (checks) (push) Successful in 1h14m29s
Foundation / postgres-tools (push) Successful in 34s
Foundation / server-image (push) Successful in 4m6s
Foundation / image (push) Successful in 4m52s

This commit is contained in:
dingo
2026-10-19 06:23:51 -04:00
parent a5307c768b
commit 463b091056
25 changed files with 799 additions and 74 deletions
+18
View File
@@ -1,5 +1,23 @@
# Project status and next steps
## Durable funded cellular maturation - 2026-10-19
[ADR-0158](adr/0158-durable-cellular-maturation.md)/schema 53 admits explicit
bundle-10 -> 11 maturation upgrades in either raw or population profile, using
the existing immutable version journal and current head/lease fence. Recovery
rederives full state, and upgraded hosts retain exact growth through publication,
replacement, interval settlement and representation changes. No automatic upgrade
or default/DEV provisioning change.
Native Release passes **81/81**. Private Release and ASan/UBSan upgrade/fault
matrices, including prepared-handoff refusal with no partial journal evidence,
and final analysis/formatting pass. Detailed evidence and limits are recorded in
[validation](engineering/VALIDATION.md). The full private persistence/process,
backup/DR, migration-history and permission qualification reports **exit 0, 563 s**.
Rules-9 migration/census, autonomous
generations, shared environmental budgets, target-host cost, actual days and
product gates remain open; this is not completion of M12.
## Portable M12 funded maturation prerequisite - 2026-10-18
[ADR-0157](adr/0157-funded-cellular-maturation.md) adds opt-in rules-9 funded
@@ -63,3 +63,7 @@ Rules-9 durable checkpoint admission, migration, registered census, environmenta
coupling and client presentation require their own contract/qualification. Current
durable bundle allowlists continue to reject this rule. No actual-days soak,
deployment, World0 operation, extinction or M12 completion is inferred.
ADR-0158/schema 53 subsequently admits explicit durable bundle-10 -> 11 upgrades.
The maturation rule above is unchanged; migration/census and ecological/product
qualification remain separate gates.
@@ -0,0 +1,52 @@
# ADR-0158: Durable admission of funded cellular maturation
## Status
Accepted for the scoped M12 maturation durability gate, 2026-10-19. Extends
ADR-0146/0157. No deployment, automatic upgrade, balance acceptance or World0 change.
## Decision
Admit cellular bundle 11 `{9,7,2,1,1,4,3,2,1}` through schema 53. Reuse the
immutable `cellular_profile_migrations` journal and current lease/head fence.
Only explicit bundle 10 -> 11, same-profile (4 or 5), same-tick upgrades are
allowed. Preserve all stocks, organisms, genomes, growth, presence, boundary
flows, archive, policy, cohort membership and conversion sequence. No new genesis,
skipped prerequisite, downgrade or independently published upgrade record.
The adapter verifies both predecessor bindings, derives and reads back the full
candidate object, then atomically records evidence/result/head. Pending intervals
and biological handoffs prevent a new upgrade. Exact retries retain original
bytes/receipt under current authority; changed bytes conflict. An uncertain
transaction retains the exact prepared request. Recovery verifies both complete
manifests/objects and the journal and rederives the recorded operation, selected
from the exact source/target tuple. No fallback to older biology or fresh genesis.
Both raw trace 3 and population envelope/batch 2 keep their existing layouts.
The bound predecessor's rules select funded maturation. Representation changes
preserve the tuple. Parser-local SQL normalization can reuse the existing shape
checks, after checking real trace binding; stored bytes, strong digests and retry
identity always retain bundle 11. Legacy parser/publisher helpers remain private.
Keep all original version meanings and migration checksums. Existing freeze,
interval, player-choice, permanent-death and dedicated-publication guards remain.
No worker upgrades automatically, and DEV/default provisioning stays rules 8.
An explicitly upgraded host can recover and continue either representation.
Biological migration still accepts bundle 10 only. Rules-9 census queries return
unsupported until separately qualified; a missing projection is never zero life
or evidence of extinction.
## Alternatives and qualification
A fresh opening loses funded ancestry and stock history. Reusing profile-change
evidence obscures a biological-rules change. A separate journal duplicates the
existing atomic authority. Extend its exact pair and replay dispatch instead.
Require both profiles, real juvenile growth after upgrade, exact continuation and
profile conversion, stale/current leases, retries/conflicts, pending-work refusal,
ambiguous outcomes/process loss, missing/corrupt/false source or result objects,
rollback, retained history and runtime privilege audits on private PostgreSQL.
Run portable Release, sanitizers, analysis and the full persistence/backup/DR
matrix. This qualifies the retained biological rule and its storage path, not
autonomous multi-generation ecology, linked environmental budgets, actual days,
deployment-host costs, product readiness or M12 completion.
@@ -1,5 +1,13 @@
# Persistence and region authority
ADR-0158/schema 53 admits the explicit same-profile bundle-10 -> 11 maturation
upgrade through the existing immutable version journal and lease/head fence.
Recovery rederives the complete retained transformation; raw trace 3 and population
batch 2 keep their layouts. Profile changes preserve the tuple. No new genesis,
automatic upgrade or default change. Biological migration and registered census
for rules 9 remain unsupported; an unavailable owner projection cannot become
zero life. See [the upgrade contract](../../schemas/cellular-maturation-upgrade.md).
M12.7c/schema 52 adds [pending migration evidence](../../schemas/ecology/census-pending-migrations-v1.md)
to registered snapshots. Pending source/destination pointers, namespace, registry
and heads share one metadata view. Exact captured capsules/ghosts are fully
+6
View File
@@ -111,6 +111,12 @@ because the existing quarter-yield rounds down; finite nutrient motes/contact an
space still matter. Durable rules-9 publication/migration/census, linked resources,
automatic wildlife robustness, balance and actual-days qualification remain open.
ADR-0158/schema 53 now adds explicit durable bundle-10 -> 11 maturation admission,
using the existing immutable version journal and exact same-profile recovery.
Raw/cohort publication and representation changes preserve the retained rule.
This does not enable rules-9 biological migration/census, autonomous sustainability,
joint environmental budgets or actual-days qualification.
M12.6a's [regional census projection](../../schemas/ecology/regional-cellular-census-v1.md)
independently implements local current-genome and descendant-closure queries.
It keeps suspended stock and retained zero-carrier ancestry, separates exact cohort
+81
View File
@@ -1,5 +1,86 @@
# Validation report
## 2026-10-19 - Durable funded cellular maturation
[ADR-0158](../adr/0158-durable-cellular-maturation.md)/schema 53 admits bundle 11
through an explicit same-profile, same-tick bundle-10 upgrade. The existing
immutable version journal, fenced head transaction and exact source/target
recovery are reused. Raw trace 3 and population envelope/batch 2 keep their
layouts; no default, DEV provisioning, old golden or numbered migration changes.
The host can continue an explicitly upgraded owner in either representation.
Executed locally:
- MSVC default Release full CTest **81/81 passed, 17.72 s**, with NDEBUG.
- GCC 14 Release maturation/process/manifest contracts **3/3 passed, 1.59 s**.
- Private PostgreSQL raw/population upgrade, publication/history/migration/census
regression and host fault matrix **exit 0, 19 s** (17 s population). The final
raw/cohort pending-handoff upgrade refusal and journal-rollback assertions pass
in a separate complete matrix rerun, also **exit 0, 19 s**.
- Clang 19 ASan/UBSan manifest contracts and complete affected private matrix
passed **exit 0, 55 s** (53 s population), without sanitizer reports. The final
pending-handoff guard rerun passed **exit 0, 56 s** (54 s population), without
reports. These runs use private Unix-socket databases; the full qualification
separately runs the existing loopback TLS migration/storage matrix.
- The full frozen-executable private persistence/process/backup/DR and SQL suite
reported **exit 0, 563 s**: C++ integration/process/load/history **435 s**, TLS
migration/storage faults **44 s**, life reservations **3 s**, backup/restore
**31 s**, host-loss DR **8 s**, upgrade **10 s**, migration history **5 s**,
effective runtime permissions **14 s**, checksum/future refusal **8 s**, plus
setup/migration. It includes schema-53 admission and legacy pre-context restore.
The later test-only pending-handoff assertions passed the separate final
Release/ASan matrices above; no implementation changed after freezing.
- clang-tidy 19 passed on the three changed persistence sources, cellular host,
both checkpoint/publication tests and schema-migration integration tests. The
final pending-handoff assertions passed a separate recheck. Repository
clang-format 19, changed-script `bash -n` and `git diff --check` pass.
The inline outer WSL launcher mishandled its status variable after the full suite
finished and left an empty completion file. The original log contains both the
all-phase success marker and the suite's own `timing (exit 0)` trap. A separate
successful verifier checked that complete final summary, every expected phase
and the exact 563-second total before recording the zero completion result. The
outer runner is now a saved shell file for future use; the original log was
preserved and unchanged tests were not repeated solely for that capture error.
Both profile-4 and profile-5 candidates preserve complete state, policy, cohort
tags and conversion history. Ordinary raw continuation, batch-2 growth and
representation transitions retain bundle 11. A real, player-origin juvenile
increases its realized growth in a funded 64-tick interval, publishes under its
durable admission and recovers byte-identically. Host replacement restores the
upgraded population, settles retained admitted work with no fresh tick debt,
and materializes before returning-player lookup. No biological rule was changed
to manufacture this evidence.
The reused fault matrix covers source-object absence/corruption, a valid but
unequal conserved target, pre-transaction publisher kill, uncertain transaction
retaining exact prepared bytes, duplicate/conflicting requests, ordinary publisher
process loss and exact owner replacement. The maturation cases additionally
reject stale upgrade authority, SQL-level skipped prerequisites and downgrades.
Pending intervals block upgrades. Both raw and cohort prepared handoffs also
block them: the head stays unchanged and no partial upgrade journal row remains.
Pure manifests reject repeated/skipped operations, incompatible tuples and genesis;
rules-8 manifests still reject rules-9 payloads, and unknown rules remain unsupported.
The first private run exposed best-effort shutdown in a deliberately uncertain
host fixture: the next test could not immediately acquire its lease. The fixture
now confirms release through an independent connection before handing authority
to the next test. Another new positive growth test initially omitted its required
durable interval admission and correctly failed EVL18; adding the real admission
made the complete path pass. Neither fix relaxes runtime ownership/admission.
Schema 53 adds no state table and preserves all previous migration bytes. Runtime
can execute only the existing fenced entry points; newly retained parser/publisher
helpers remain private. The legacy history-domain backup fixture restores the
exact pre-53 function definitions/grants before making its pre-context backup.
Biological migration remains bundle 10 only. Rules-9 census is unsupported until
separately qualified, preventing a complete census rather than producing zero
life. Autonomous generations, linked environmental stocks, deployment-host cost,
actual days and product readiness remain open. No live database, deployment or
World0 operation occurred. TSan was not rerun: no shared-memory ownership or
scheduler concurrency changed.
## 2026-10-18 - Portable M12 funded maturation prerequisite
[ADR-0157](../adr/0157-funded-cellular-maturation.md) adds an explicit detached