feat(persistence): admit durable retained offspring plans
Foundation / checks (tsan) (push) Canceled after 0s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (client) (push) Canceled after 1m11s
Foundation / checks (checks) (push) Canceled after 1m13s
Foundation / checks (postgres) (push) Canceled after 1m8s
Foundation / checks (ecs) (push) Canceled after 1m13s
Foundation / checks (network) (push) Canceled after 1m14s
Foundation / checks (deploy) (push) Canceled after 1m18s

This commit is contained in:
dingo
2026-10-19 15:04:30 -04:00
parent 39509ecd40
commit c60cdf8e19
20 changed files with 850 additions and 46 deletions
+15
View File
@@ -1,5 +1,20 @@
# Project status and next steps
## Durable retained offspring plans - 2026-10-19
[ADR-0168](adr/0168-durable-retained-plan-admission.md)/schema 55 adds explicit
raw bundle-11 -> 12 fenced upgrades, trace-4 publication, earned plan selections
and repeated funded births. Recovery rederives the full upgrade from retained
source objects and replays subsequent choices/births exactly. Ambiguous retries,
stale writers, rollback, pending choices and missing/corrupt/false evidence are
covered. No default or DEV opening opts into this version automatically.
[Validation](engineering/VALIDATION.md) records executed checks. Population and
migration support, census plan semantics, control succession, retained NPC
behavior, client choice UI and the remaining M12 operational/ecology/product
gates remain open. Delivery follows Git Actions -> Harbor -> ArgoCD -> Kubernetes
using the checked-in `deploy/` manifests.
## Portable retained-plan checkpoint upgrade - 2026-10-19
[ADR-0167](adr/0167-retained-plan-checkpoint-upgrade.md) defines raw-only bundle
@@ -0,0 +1,57 @@
# ADR-0168: Durable raw retained-plan admission
## Status and scope
Accepted scoped persistence segment of ADR-0163/0165-0167, 2026-10-19. Raw
profile 4 only. No automatic upgrade, default/DEV change, population conversion,
migration/census qualification, control succession or client-choice UI.
## Decision
Schema 55 admits exactly raw bundle 12 with trace 4 through the existing fenced
cellular publisher. Only explicit raw bundle 11 -> 12 no-tick upgrades use the
immutable cellular profile/version journal. Verify both source bindings, derive
the complete owner upgrade and read back the target object before publishing.
Journal evidence, result commit and head move remain one transaction under the
current lease/exact head. Pending intervals/handoffs prevent new upgrades.
Retain original manifests, traces, input blocks and digests. SQL may normalize
parser-local copies of the tuple/trace layout only after verifying the actual
trace length/SHA-256 and exact owner/trace version pairing. Stored bytes, retry
identity and authority checks always use the actual bundle-12/trace-4 evidence.
Legacy helpers remain private. No new runtime privilege or provisioning path.
Mutation outcomes are derived by complete C++ replay and bound atomically to the
existing allocator reservation and action block. For this editing mode only,
admit result 4 (offspring plan applied), 3 (declined) or 1 (life died); reject
in-life applied/funding result meanings. A decline must match operator zero;
successful plan selection must match a nonzero operator. Old result domains and
old trace/tuple meanings remain unchanged. Recovery loads the exact actions,
replays the complete checkpoint, and compares every result and all target bytes.
Upgrade recovery verifies the immutable source/target manifests and objects,
journal versions/digests and exact retained transformation using the original
writer fields under current recovery authority. Missing, corrupt or biologically
false evidence fails closed without an older-head fallback. Exact retries retain
original bytes/receipt; changed retries conflict and stale writers remain fenced.
Bundle 12 remains raw-only. Population/census/migration adapters must refuse it,
and unsupported evidence cannot become zero life or terminal extinction. A
recovered raw owner may continue authoritative biology; no worker opts into the
upgrade automatically. NPC behavior retention, birth-time one-way control and
their presentation remain separate contracts.
## Alternatives, consequences and qualification
New genesis would discard ancestry/stock history; a second upgrade journal would
duplicate authority. Broadly admitting every revision bundle would mix two
mutation meanings. Use the existing journal and an exact tuple/trace/result set.
Risks include parser normalization bypassing strong bindings, wrong result
meanings and partial history after ambiguous publication. Require private SQL
tests for the upgrade, exact recovery/continuation, earned plan selections and
repeated funded births, stale/current leases, exact/conflicting retries, rollback,
pending work, missing/corrupt/false objects and replacement recovery. Run the full
persistence/backup/DR/upgrade and privilege/checksum matrix plus appropriate
portable, analysis and sanitizer checks. This is not M12 completion or a product
acceptance decision.
+2
View File
@@ -1,5 +1,7 @@
# Architecture decision records
- [ADR-0168: Durable raw retained-plan admission](0168-durable-retained-plan-admission.md) - schema 55, explicit raw bundle-11 -> 12 fenced upgrades and trace-4 mutation/birth publication with exact recovery; no automatic opening or population admission.
- [ADR-0167: Explicit retained-plan checkpoint upgrade](0167-retained-plan-checkpoint-upgrade.md) - portable raw-only bundle 12 and exact no-tick bundle-11 source transformation; SQL/durable admission and population support remain separate.
- [ADR-0166: Retained-plan replay traces](0166-retained-plan-replay-traces.md) - explicit raw trace 4 for owner 8/rules 10, inherited-offer action matching and complete-result replay; durable admission remains separate.
+12 -3
View File
@@ -20,11 +20,20 @@ retained plans and earned selections, unchanged expressed parents and repeated
funded births. [ADR-0166](../adr/0166-retained-plan-replay-traces.md) adds portable
raw trace-4 replay, action matching and exact process restart. Existing same-genome
behavior remains. [ADR-0167](../adr/0167-retained-plan-checkpoint-upgrade.md) defines
the portable raw checkpoint tuple and exact retained-source upgrade. Durable
plan/trace/bundle admission,
population/migration/census admission, the in-life expression catalog, authority
the portable raw checkpoint tuple and exact retained-source upgrade.
[ADR-0168](../adr/0168-durable-retained-plan-admission.md) adds schema 55,
explicit fenced raw admission, plan selections and repeated funded births with
complete source/target recovery. Population/migration/census admission, the
in-life expression catalog, authority
handoff and NPC/UI integration are still required.
Delivery follows the maintainer-confirmed Git Actions -> Harbor -> ArgoCD ->
Kubernetes flow using `deploy/`. DEV qualification belongs in `evolution-dev`
on worker nodes, using the existing PostgreSQL server/network endpoints and
isolated test data. A successful local check or Git push alone is not evidence
that a target-host fault drill or deployed workload passed. Direct workstation
Kubernetes access is not a prerequisite for this delivery flow.
## Persistence boundary resolved by 12.3b
ADR-0142 adds dedicated profile 5, population trace 1 and schema 44; raw profile 4
+56
View File
@@ -1,5 +1,61 @@
# Validation report
## 2026-10-19 - Durable raw retained-plan admission
[ADR-0168](../adr/0168-durable-retained-plan-admission.md)/schema 55 adds the
explicit raw bundle-11 -> 12 upgrade and trace-4 durable publisher/recovery.
Complete retained source and target bytes are independently bound, restored and
compared. A valid equal-stock but different-position upgrade fails recovery;
metadata checks alone never establish the biological transformation. SQL
parser-local normalization first verifies the actual trace length/SHA-256 and
version; retained evidence and retry identity use the original bytes.
Executed locally before the following census segment:
- MSVC 19.44 Release full CTest **89/89, 22.93 s**; GCC 14.2 Release **89/89,
17.58 s**, with NDEBUG.
- Clang 19.1/clang-tidy 19 persistence build and private population/fault suite
passed **56 s total**, including retained plans and existing raw/cohort,
interval, migration and registered-census controls.
- Clang 19.1 ASan/UBSan persistence build and the same private suite passed
**111 s total**, without sanitizer reports.
- GCC 14.2 full private schema-55 matrix passed **624 s total**: complete
integration suite (454 s), network partitions (82 s), reservation concurrency,
backup/history-domain/restore, disaster recovery, upgrade rehearsal, migration
history, runtime privileges and checksum drift. No shared database was used.
- Repository clang-format 19 and staged/working diff checks passed. No golden
was replaced. The exact staged deployment policy passes: 75 objects in 74
files, 138 rendered objects in 17 overlays, zero failures.
The refreshed DEV session window expires **2026-10-19 23:04:00 UTC**. Pipeline
build/deployment success and live reachability are not inferred from this push.
The real finite-food fixture follows the required earlier version upgrades,
preserves suspended lives, selects an earned plan without changing the parent's
expressed genome, publishes result 4 and produces at least two funded children
with that plan. Complete recovery under a replacement lease preserves the
family. Tests refuse skipped/repeated upgrades, population conversion, pending
mutation work, stale/current conflicting retries, wrong result meanings,
trace-3/owner-8 pairing and altered traces with the original digest. A triggered
result-insert failure rolls back journal/head; process loss before publication,
an ambiguous timed request, exact duplicate retry, source loss/corruption and
biologically false source transformation retain their explicit failure behavior.
An earlier full run used an old test binary missing the new migration-checksum
argument and failed its upgrade rehearsal. The test was corrected and rebuilt.
The next full run was canceled at the maintainer's stop request; its shell trap
printed an exit-0 timing summary before reporting the child hangup. That summary
is **not** a completed test pass. Only the subsequent uninterrupted run counts.
All database tests use disposable local clusters, not the shared DEV server.
The maintainer confirms delivery through Git Actions, Harbor, ArgoCD and
Kubernetes, with workloads in `evolution-dev` on workers and the existing
PostgreSQL/network/URLs. This workstation has no configured Kubernetes context;
direct access is not required for that delivery flow. No target-host performance,
multi-host failure, deployed reachability, actual-days ecology, product/UI,
TSan or World0 evidence is inferred from local tests or a Git push. Default
biology and player control behavior remain unchanged; M12 is still in progress.
## 2026-10-19 - Portable retained-plan checkpoint upgrade
[ADR-0167](../adr/0167-retained-plan-checkpoint-upgrade.md) adds raw-only bundle