M12.4: admit and replay durable boundary-accounting upgrades
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m23s
Foundation / checks (network) (push) Successful in 21m4s
Foundation / checks (client) (push) Successful in 22m15s
Foundation / checks (tsan) (push) Successful in 23m3s
Foundation / checks (postgres) (push) Successful in 51m33s
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 55m18s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m23s
Foundation / checks (network) (push) Successful in 21m4s
Foundation / checks (client) (push) Successful in 22m15s
Foundation / checks (tsan) (push) Successful in 23m3s
Foundation / checks (postgres) (push) Successful in 51m33s
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 55m18s
This commit is contained in:
@@ -1,5 +1,20 @@
|
||||
# Project status and next steps
|
||||
|
||||
## M12.4g durable accounting upgrade - 2026-10-18
|
||||
|
||||
ADR-0146/schema 46 extends the immutable version-upgrade journal to same-profile
|
||||
bundle-9 to 10 upgrades. Full source/result replay protects biology and cohort
|
||||
policy/membership/sequence; pending intervals and current lease/head fences remain
|
||||
enforced. Batch 2 is admitted only under bundle 10, and representation changes
|
||||
preserve either tuple. No worker upgrades automatically.
|
||||
|
||||
Native Release passes 78/78; Clang analysis/format and ASan/UBSan upgrade checks
|
||||
pass. The complete private PostgreSQL/process/backup/DR/upgrade/permission/history
|
||||
suite passes in 503 s. [Evidence and limits](engineering/VALIDATION.md) retain the
|
||||
next M12.4 work: durable paired biological escrow, source freeze, destination
|
||||
activation and linked-boundary contracts. All of M12 remains in progress; no
|
||||
deployment or live region changed.
|
||||
|
||||
## M12.4f explicit portable accounting upgrade - 2026-10-17
|
||||
|
||||
ADR-0145 declares checkpoint bundle 10 for owner 7/population envelope 2, with an
|
||||
|
||||
@@ -0,0 +1,56 @@
|
||||
# ADR-0146: Durable boundary-accounting upgrade admission
|
||||
|
||||
## Status
|
||||
|
||||
Accepted for scoped M12.4g implementation, 2026-10-17; locally qualified
|
||||
2026-10-18, including the full private persistence suite. See
|
||||
[validation](../engineering/VALIDATION.md). No deployment, automatic upgrade or
|
||||
World0 change. Paired biological escrow remains open.
|
||||
|
||||
## Decision
|
||||
|
||||
Admit ADR-0145's bundle 10 through SQL schema 46. Extend the existing immutable
|
||||
`cellular_profile_migrations` journal: it already retains both sequences, commits,
|
||||
manifest/payload digests and exact version tuples. A new table or independent
|
||||
publication service would duplicate that authority. Old upgrade meanings remain.
|
||||
|
||||
Only an explicit bundle-9 to 10, same-profile (4 or 5), same-tick upgrade may
|
||||
change the tuple. The existing fenced version-migration publisher verifies the
|
||||
exact current head, lease/frame and retained build, inserts the complete upgrade
|
||||
evidence and result, and advances the head in one transaction. An unsettled
|
||||
population interval blocks a new upgrade. Exact retries return their original
|
||||
receipt under current authority; changed bytes conflict. Unknown outcomes retain
|
||||
the exact prepared request. An explicit adapter verifies source SHA-256, derives
|
||||
the complete upgrade, uploads and reads back its object before publication.
|
||||
|
||||
Recovery under a fresh current lease verifies the immutable journal, both complete
|
||||
manifests and objects, rederives the exact upgrade, and requires byte equality.
|
||||
No fallback genesis, older head, opening-stock reset or version reinterpretation
|
||||
is allowed. Version upgrades and profile changes retain distinct journals. A
|
||||
no-tick recovery selects the recorded operation, never assumes its kind solely
|
||||
from the target bundle.
|
||||
|
||||
For bundle 10, population profile 5 requires envelope 2/batch 2. Retained bundle
|
||||
9 continues to require envelope 1/batch 1. Profile 4's unchanged trace 3 carries
|
||||
the same rules-8 inputs. Representation transitions preserve the tuple. Interval
|
||||
admission/settlement, pending player-choice guards and materialization before
|
||||
player operations retain their existing requirements. Generic publication cannot
|
||||
change versions or bypass dedicated evidence. No worker automatically upgrades.
|
||||
|
||||
This admits the accounting format only. It does not admit paired migration trace
|
||||
1, publish two heads, freeze a source, activate a destination ghost, choose an atlas
|
||||
or resolve multigeneration growth/environment/census gates.
|
||||
|
||||
## Alternatives and qualification
|
||||
|
||||
Reusing representation-transition evidence for a same-profile version change
|
||||
would erase the distinction needed by recovery. Fresh provisioning would lose
|
||||
the retained opening history. Keep the existing version-upgrade journal and
|
||||
extend its exact supported pair instead.
|
||||
|
||||
Require both profiles, full-state replay/continuation, retained-format refusal,
|
||||
pending interval refusal, stale/current leases, duplicate/conflicting requests,
|
||||
ambiguous outcomes, publisher process loss, missing/corrupt objects, migration
|
||||
rollback/history checks and least-privilege audits on private PostgreSQL. Portable
|
||||
success alone is insufficient. Actual paired escrow and production costs remain
|
||||
separate gates.
|
||||
@@ -1,5 +1,7 @@
|
||||
# Architecture decision records
|
||||
|
||||
- [ADR-0146: Durable boundary-accounting upgrade admission](0146-durable-boundary-accounting-upgrade.md) - schema 46 extends immutable version-upgrade evidence to same-profile bundle 9->10, full upgrade replay, population batch 2 and preserved representation/interval guards; paired migration escrow remains open.
|
||||
|
||||
- [ADR-0145: Explicit boundary-accounting checkpoint upgrade](0145-boundary-accounting-checkpoint-upgrade.md) - portable bundle 10, exact no-tick retained-source upgrade and representation-preserving continuation; SQL admission and durable upgrade evidence remain open.
|
||||
|
||||
- [ADR-0138: Current cellular population reference instrument](0138-cellular-population-reference-instrument.md) - M12.2c headless rules-8 control, encoded replay partitions and offline closure; no aggregation qualification.
|
||||
|
||||
@@ -1,11 +1,14 @@
|
||||
# Persistence and region authority
|
||||
|
||||
M12.4f defines portable cellular bundle 10 for owner-7 boundary accounting, with
|
||||
an explicit same-profile, no-tick bundle-9 upgrade candidate. Profile transitions
|
||||
preserve either tuple. Portable reader support grants no publication authority;
|
||||
schema 45 still refuses bundle 10 and no worker selects it. Dedicated fenced
|
||||
upgrade evidence/recovery and atomic paired transfer publication remain required.
|
||||
See [ADR-0145](../adr/0145-boundary-accounting-checkpoint-upgrade.md).
|
||||
M12.4f defines cellular bundle 10 for owner-7 boundary accounting, with an explicit
|
||||
same-profile, no-tick bundle-9 upgrade. M12.4g/schema 46 admits it through the
|
||||
existing immutable version-upgrade journal and lease/head fence. Recovery
|
||||
rederives the complete source/target transformation. Profile transitions preserve
|
||||
either tuple; bundle 9 requires population batch 1 and bundle 10 requires batch 2.
|
||||
Portable reader support grants no publication authority and no worker selects an
|
||||
upgrade automatically. Atomic paired transfer publication remains required.
|
||||
See [ADR-0145](../adr/0145-boundary-accounting-checkpoint-upgrade.md) and
|
||||
[ADR-0146](../adr/0146-durable-boundary-accounting-upgrade.md).
|
||||
|
||||
M7.1 now scopes the first implementation in [ADR-0058](../adr/0058-region-durability-contract.md)
|
||||
and [REGION_DURABILITY.md](REGION_DURABILITY.md): full checkpoint batches, not
|
||||
|
||||
@@ -97,3 +97,26 @@ confusion is refused in both directions. Portable reader support does not imply
|
||||
database admission: schema 45 and the population prepared validator still reject
|
||||
the tuple. Dedicated upgrade publication/evidence/recovery is the next segment;
|
||||
paired escrow, geometry and remaining biological gates stay open.
|
||||
|
||||
## M12.4g durable accounting upgrade admission
|
||||
|
||||
[ADR-0146](../adr/0146-durable-boundary-accounting-upgrade.md)/schema 46 extends
|
||||
the existing immutable version-upgrade journal to an explicit same-profile
|
||||
bundle-9 to 10 publication. Both profiles retain complete source/result manifests,
|
||||
payload digests and exact version tuples under the current lease and head fence.
|
||||
An unsettled population interval blocks a new upgrade. The adapter restores the
|
||||
verified source, derives the exact candidate, uploads/reads back its object and
|
||||
retains the same prepared bytes after ambiguity. No worker upgrades automatically.
|
||||
|
||||
Recovery selects the recorded no-tick operation: a version upgrade is rederived
|
||||
from its full retained source; a representation change uses its separate journal.
|
||||
Both require full byte equality. Matching aggregate inventory cannot admit a
|
||||
different cohort policy or membership. Bundle 10 requires envelope/batch 2;
|
||||
bundle 9 retains envelope/batch 1. Raw biological trace 3 and rules 8 are unchanged.
|
||||
Representation changes preserve either tuple and interval/player-operation
|
||||
guards remain in place.
|
||||
|
||||
This admits the accounting format and its ordinary continuation. Paired migration
|
||||
trace 1 still has no SQL publisher, source freeze, staged ghost or activation
|
||||
rights. Durable two-head escrow, abort/partition/duplicate settlement, linked
|
||||
geometry and ecology remain open. No deployment, live upgrade or golden changed.
|
||||
|
||||
@@ -56,8 +56,11 @@ cross-version replay is refused and a new process reproduces a post-transfer
|
||||
by bundle 9 and schema 45.
|
||||
ADR-0145 now defines the portable bundle-10 declaration and explicit same-profile,
|
||||
no-tick source upgrade, with complete payload preservation and no new genesis.
|
||||
SQL admission, immutable upgrade evidence and replayed recovery remain required
|
||||
before those candidates can become durable region heads.
|
||||
ADR-0146/schema 46 supplies SQL admission through the existing immutable
|
||||
version-upgrade evidence and complete replayed recovery. Both profile upgrades,
|
||||
population batch 2 and bundle-preserving profile changes are explicit; no worker
|
||||
upgrades automatically. This format admission does not publish a migration pair
|
||||
or close source-freeze/destination-activation and escrow qualification.
|
||||
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
|
||||
|
||||
@@ -10,6 +10,16 @@ continue refusing these portable candidates through schema 45 and existing
|
||||
prepared/generic publication paths without advancing the head. Durable admission
|
||||
and upgrade crash/retry recovery remain separate gates.
|
||||
|
||||
M12.4g's private PostgreSQL suite upgrades raw/profile-5 bundle-9 sources using
|
||||
schema 46. It rehearses raw upgrade/trace-3 continuation and rollback, retains a
|
||||
nonempty cohort, refuses pending-interval upgrades and wrong publication paths,
|
||||
and recovers after a pre-transaction SIGKILL and an ambiguous exact retry. Changed
|
||||
requests and stale writers fail. Missing/corrupt objects quarantine; a canonical
|
||||
but unequal cohort with matching biological totals fails full upgrade replay.
|
||||
Batch-1/2 cross-binding is refused in both directions. The process-loss and
|
||||
host-recreation/materialization matrix also runs with batch 2. Full historical
|
||||
migration/backup/DR/permission regression remains required for schema admission.
|
||||
|
||||
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
|
||||
|
||||
@@ -1,5 +1,51 @@
|
||||
# Validation report
|
||||
|
||||
## 2026-10-18 - M12.4g durable boundary-accounting upgrade
|
||||
|
||||
ADR-0146/schema 46 admits the explicit same-profile bundle-9 to 10 upgrade through
|
||||
the existing immutable version-upgrade journal. Recovery rederives the complete
|
||||
source/result transformation; representation changes retain separate evidence.
|
||||
Both profiles preserve their exact tuple through ordinary continuation; bundle
|
||||
10 requires population batch 2 while bundle 9 retains batch 1. No worker performs
|
||||
an automatic upgrade. Biology/rules 8, goldens, dependencies and live state are
|
||||
unchanged.
|
||||
|
||||
Executed locally:
|
||||
|
||||
- Native MSVC Release **78/78 passed**, 12.30 s.
|
||||
- Actual GCC 14 optional server/PostgreSQL targets rebuilt; final focused private
|
||||
PostgreSQL population/upgrade suite passed, 6 s total.
|
||||
- Linux Clang 19 ASan/UBSan final private population/upgrade suite passed, 26 s
|
||||
total (22 s test phase), with no reports.
|
||||
- Explicit clang-tidy 19 on both affected adapters and both PostgreSQL test
|
||||
sources passed, with no owned warnings. Repository clang-format 19 and shell
|
||||
syntax checks passed.
|
||||
- Complete frozen-binary private PostgreSQL qualification passed with **exit 0**,
|
||||
**503 s**: C++ integration/process/load/history (423 s), life reservations,
|
||||
backup, DR, upgrade, migration history/rollback, runtime permission audit and
|
||||
checksum/future-version rejection. Earlier interrupted runs are not counted.
|
||||
|
||||
New cases exercise raw upgrade/trace-3 continuation and rollback, nonempty cohort
|
||||
policy/sequence retention, pending-interval refusal, wrong publication paths,
|
||||
pre-transaction SIGKILL, ambiguous exact retry, conflicting bytes and stale
|
||||
writers. Missing/corrupt objects quarantine. A canonical cohort object with equal
|
||||
biological totals but different policy/membership fails complete upgrade replay.
|
||||
Batch-1/2 cross-binding is refused in both directions. The publication process
|
||||
kill and actual host-recreation/materialization matrix also runs with batch 2.
|
||||
|
||||
An initial new-migration CASE expression failed parsing and was corrected before
|
||||
the successful runs. The first full fixture omitted sibling load/session-probe
|
||||
tools; a corrected run was then interrupted by a hangup. The final detached run
|
||||
used every required frozen sibling executable and recorded its completion code.
|
||||
|
||||
Limits: these backup/DR/clone checks retain their existing supported fixtures;
|
||||
they do not qualify cellular cloning or a new world-wide migration cut. Paired
|
||||
biological transfer trace 1 remains unadmitted; no durable source freeze, staged
|
||||
ghost activation, two-head escrow, linked atlas/environment or multi-generation/
|
||||
elapsed-day ecological claim follows. No live database, World0 or deployment was
|
||||
touched. Remote CI/container confirmation of the earlier build-runner repair
|
||||
remains separate; `Build_Errors.txt` and unrelated local work remain untracked.
|
||||
|
||||
## 2026-10-17 - M12.4f portable boundary-accounting checkpoint upgrade
|
||||
|
||||
ADR-0145 adds portable bundle 10, explicit bundle-9 no-tick upgrade candidates
|
||||
|
||||
Reference in New Issue
Block a user