M12.7: require registered regions in census snapshots
Foundation / checks (deploy) (push) Successful in 58s
Foundation / checks (ecs) (push) Successful in 2m36s
Foundation / checks (network) (push) Successful in 20m56s
Foundation / checks (client) (push) Successful in 22m19s
Foundation / checks (tsan) (push) Successful in 25m18s
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 44m49s
Foundation / checks (postgres) (push) Canceled after 44m54s

This commit is contained in:
dingo
2026-10-18 19:48:23 -04:00
parent 7631f9d2e2
commit 145e6e1445
19 changed files with 605 additions and 46 deletions
+18
View File
@@ -1,5 +1,23 @@
# Project status and next steps
## M12.7a registered-world census coverage - 2026-10-18
Schema 50 now uses the durable authority registry as the required regional set
for consistent census snapshots. Every registered region must have matching
resources and recoverable evidence, including inactive/expired owners. Missing
heads, unsupported profiles, unknown worlds and more than 64 regions fail the
query. Catalog selection and head capture use the same database snapshot, with
complete immutable replay afterward; no duplicate catalog/enrollment write.
Native Release passes **79/79**; registered coverage/enrollment and raw/cohort
migration races, ASan/UBSan TLS/storage faults, Clang analysis and formatting pass.
Complete private persistence/process/backup/DR, schema upgrade, permissions and
checksum qualification passes in **551 s** after correcting a stale schema-history
test expectation. [Evidence and limits](engineering/VALIDATION.md) retain external
branch identity, other viable stores, durable accepted reconciliation records,
client access and the ecology/soak/product gates. This segment accepts no terminal
extinction, deployment or World0 promotion.
## M12.6d consistent scoped census snapshots - 2026-10-18
Scoped census reads now select all declared regional heads from one short
@@ -0,0 +1,67 @@
# ADR-0154: Registered-world coverage for cellular census snapshots
## Status
Accepted for scoped M12.7a, 2026-10-18. Implements database-registered regional
coverage under ADR-0133/0153, not terminal extinction or external branch identity.
## Context and decision
A consistent snapshot of a caller-declared list can still omit an owner. The
existing durable `region_leases` registry is the source of region identity and
frame for all supported provisioning paths. Duplicating it in a separate census
catalog would create another enrollment truth and a failure window.
Schema 50 adds a least-privilege read function listing registered regions of one
world, ordered by region ID, with frame IDs. Read from the registry itself, without
joining/filtering on heads, profile, active holder, expiry, activity or living count.
A missing checkpoint or unsupported region must prevent evidence completion,
not disappear from the required list. Return at most 65 rows: the 65th detects
overflow of the existing 64-region query bound. This is not a selected world size.
No new table/index, registration write or biological codec/rule.
Add `load_registered_cellular_census_snapshot`. In ADR-0153's owned short read-only
repeatable-read transaction, read this registry before selecting any heads. Require
an exact match to the supplied region resources/grants, including frames. Empty
registry means unknown world coverage, not zero life. Over-limit worlds fail;
never truncate/paginate a subset and label it complete. Read every selected head
in the same database snapshot, close the metadata transaction, then use unchanged
exact-cut replay and scoped census validation. Return registry evidence alongside
the exact cuts and census. Existing caller-declared snapshots keep their semantics.
Concurrent enrollment after the registry read belongs to a later snapshot. The
current result covers the registered set as of its captured database view, not
the latest state at return. Uncommitted enrollment is not included. A registered
row without a recoverable head fails the whole result. No fallback or zero filling.
## Alternatives, benefits, costs and risks
Trusting a supplied list cannot prove coverage. Listing only checkpoint-bearing,
cellular, active or unexpired regions hides unavailable or unsupported owners.
A duplicate mutable catalog can disagree with the authority registry. Read the
existing durable registry through its `(world_id, region_id)` primary-key prefix;
the 65-row limit bounds listing work and detects oversized sets explicitly.
The new security-definer read function exposes only region/frame metadata to the
existing trusted runtime group. Fixed search path, PUBLIC revocation and the full
runtime privilege audit remain mandatory. It grants no table access, provisioning,
new client permission or cross-world biological authority. Old schemas fail the
new query instead of falling back to caller-declared coverage.
## Consequences and qualification
Test exact sets, omitted/extra/duplicate resources, unknown worlds, wrong frames,
expired/released holders, missing heads, unsupported profiles and 64/65 bounds.
Race committed and uncommitted enrollment with snapshot capture; current cuts
must retain their selected catalog and later reads must see new enrollment.
Repeat real raw/cohort atomic migration races under registered coverage. Retain
failure cleanup, TLS faults, object verification and no-partial-result behavior.
Run migration/no-op/checksum/permissions, full private persistence regression,
sanitizers, Clang analysis/format and default-build checks. Never alter prior
migration bytes or biological goldens.
This covers registered regions in one connected database view. A rewind can reuse
the world ID; external branch identity is still missing. Outside/unsupported stores,
viable reserves, durable accepted reconciliation records and global freshness remain
M12.7 work. No terminal-extinction outcome, client endpoint, live database,
deployment or World0 action.
+2
View File
@@ -1,5 +1,7 @@
# Architecture decision records
- [ADR-0154: Registered-world census coverage](0154-registered-world-census-coverage.md) - schema 50 uses the existing durable authority registry as the required regional set in a consistent snapshot; omitted/unavailable/over-bound owners fail without a new catalog table or extinction authority.
- [ADR-0153: Consistent scoped cellular census snapshots](0153-consistent-cellular-census-snapshots.md) - short read-only repeatable-read head capture followed by exact immutable replay; atomic pairs cannot straddle a declared-region cut, without claiming world/branch completeness.
- [ADR-0152: Scoped multi-region cellular census queries](0152-scoped-cellular-census-sets.md) - bounded declared coverage, exact boundaries, complete shared-genome equality and disjoint resident identities; no world-completeness or extinction authority.
@@ -1,5 +1,13 @@
# Persistence and region authority
M12.7a/schema 50 adds [registered-world coverage](../../schemas/ecology/registered-world-census-coverage-v1.md).
The existing authority registry supplies every required region/frame, without
activity, expiry, profile or checkpoint filters. The bounded read function and
head selection share one database snapshot; resources must match the entire
registered set. Missing/unusable owners and a 65th region fail the query. There
is no new catalog table or registration write. External branch identity, other
viable stores and accepted global extinction reconciliation remain separate.
M12.6d captures declared regional heads in one short read-only repeatable-read
transaction, closes it, then fully replays each exact immutable cut before
constructing a scoped census. Atomic migration commits cannot split the selected
@@ -29,6 +29,13 @@ when both regions are declared. Durable required-world coverage, outside transfe
and reserve reconciliation, external branch identity and extinction acceptance
remain separate; this is no complete world evidence envelope.
M12.7a's [registered-region coverage](../../schemas/ecology/registered-world-census-coverage-v1.md)
now checks supplied resources against every durable registered region in that
same database view. It includes released/expired, empty, unsupported and
unavailable owners; no missing-as-zero or caller omission can complete the result.
This still lacks external branch identity, other viable-store reconciliation and
a durable accepted global extinction record. It supplies no terminal conclusion.
## Identity and classification
An organism has a permanent identity and terminal death. An immutable genome has
+1 -1
View File
@@ -14,7 +14,7 @@ Commit and push each validated scoped segment separately.
| 12.4 | Owned intervals and durable paired migration/fault qualification implemented in scoped segments through 12.4l | ADR-0143–0149/schema 49; bounded admitted work, source freeze, staged ghost, atomic pair and exact recovery, local TLS and storage faults. Multi-host/orchestrator, linked ecology and integrated stock audits remain open. |
| 12.5 | Blocked on 12.2-12.4 | Finite M6 process fixtures do not qualify coupled persistent cellular/cohort atmosphere/water budgets. |
| 12.6 | Regional queries, replayed history, scoped multi-region queries and consistent database head snapshots implemented (12.6a-d) | ADR-0150–0153; short read-only snapshot capture prevents atomic pairs from straddling declared head sets, with exact immutable replay. Durable world/branch coverage, outside transfer/viability reconciliation, target-host query/index costs and client path remain required. |
| 12.7 | Evidence policy defined; reconciler open | Complete durable world watermark and every viable/in-flight store remain required. |
| 12.7 | Evidence policy and registered-region coverage implemented (12.7a) | ADR-0154/schema 50 requires the durable authority registry in one consistent database cut. External branch identity, other viable/in-flight stores and durable accepted global reconciliation remain required. |
| 12.8 | Not qualified | Actual multi-day integrated ecology/restart/clone evidence remains required. |
| 12.9 | Not accepted | Returning-player product evidence and expansion review remain required; World0 stays separately blocked. |
+11 -2
View File
@@ -27,8 +27,8 @@ or authorize production enablement.
| 12.3 | Dedicated population profile/trace/store/owning host; exact recovery and private PostgreSQL fault tests | Population-specific executable/network fault drills and target-host publication/capacity qualification. |
| 12.4 | Owned intervals; exact transfer/accounting; durable atomic pair/recovery; independent loopback TLS path loss and owner expiry/replacement/heal; local object sync/read-failure matrix | Multi-host/kernel-network, storage-host and orchestrator drills, linked-boundary contracts and integrated ownership/stock audits at scale. |
| 12.5 | Finite cellular contact feeding/decay and separate M6 producer/consumer resource owner | One jointly owned cellular/environment budget, explicit effective depth and source entitlements, versioned water/atmosphere species mapping and producer coefficients, plus closed/open and nutrient-exhaustion comparisons. |
| 12.6 | Retained archive, regional census/lineage queries, replayed history, scoped multi-region queries and consistent database head snapshots (12.6a-d) | Durable world/branch history context and required-region coverage, outside transfer/viability reconciliation, target-host query/index qualification and client permission/presentation; no account power or invented precise statistical ancestry. |
| 12.7 | ADR-0133's viability/unknown semantics | Durable region-set/watermark reconciliation covering every owned representation, suspended/viable stock and migration escrow. Missing/stale regions must prevent terminal extinction. |
| 12.6 | Retained archive, regional census/lineage queries, replayed history, scoped multi-region queries and consistent database head snapshots (12.6a-d); registered coverage follows in 12.7a | External branch history context, retained historical coverage/other viable stores, target-host query/index qualification and client permission/presentation; no account power or invented precise statistical ancestry. |
| 12.7 | Viability/unknown policy; consistent head cuts and durable registered-region coverage (12.7a/schema 50) | External world/branch context, other viable-store/transfer reconciliation and durable accepted global evidence records. Missing/stale/unsupported owners must prevent terminal extinction. |
| 12.8 | Deterministic seed/regime drivers and separate-process exact continuation | Reproducible integrated worlds running for actual days, real restarts/clone comparisons and retained accounting/diversity/cost audits. Accelerated tests cannot supply elapsed days. |
| 12.9 | M11 feedback and current UI review retained | Returning-player samples on the integrated ecology and explicit product/3D readiness decision after soak evidence. No M12 product acceptance or World0 promotion is inferred. |
@@ -121,6 +121,15 @@ The short metadata transaction ends before object I/O and fenced recovery; faile
evidence still returns no partial census. Durable world/branch identity, required
owner coverage, outside transfers and viable-store reconciliation remain open.
M12.7a/schema 50's [registered coverage](../../schemas/ecology/registered-world-census-coverage-v1.md)
now reads the existing durable authority registry before head selection in that
same database snapshot. Every registered region is required, including inactive,
expired, unsupported and unavailable owners. Unknown worlds and a 65th region
fail rather than becoming zero or a truncated complete set. Concurrent later
enrollment belongs to a later cut. No duplicate catalog/enrollment write is added.
External branch identity, other viable stores and durable accepted reconciliation
records remain open; this does not close M12.7 or authorize terminal extinction.
Current expansion readiness: **no-go for M13 integration or World0 promotion**
while these M12 integration/evidence gates remain open. This records the present
engineering evidence, not a substitute for the later maintainer product review.
+11
View File
@@ -1,5 +1,16 @@
# Validation strategy
M12.7a's schema-50 tests require exact authority-registry coverage, including
released/expired holders, unavailable heads and unsupported profiles. Check
omitted/extra/duplicate resources, wrong frames, unknown worlds, integral numeric
IDs across the full u64 range and the 64/65-region bound. Race committed enrollment
after catalog selection, and exclude another connection's uncommitted enrollment.
Registered raw/cohort migration snapshots retain the same catalog and preserve
exact cut/stock evidence across real paired commits. Exercise both snapshot APIs
under TLS BEGIN/COMMIT loss. Qualify checksum-preserving 1..50 upgrades/no-ops,
runtime execute revocation/audit, backup/restore/DR, sanitizers and analysis. No
test can promote registered coverage to terminal extinction or branch identity.
M12.6d's private PostgreSQL snapshot tests publish a real atomic migration from
an independent connection between the first and second captured head reads.
Both selected cuts must remain before the pair; the next snapshot sees both
+77
View File
@@ -1,5 +1,82 @@
# Validation report
## 2026-10-18 - M12.7a registered-world census coverage
[ADR-0154](../adr/0154-registered-world-census-coverage.md)/schema 50 uses the
existing durable authority registry as the required region set. It never filters
on checkpoint availability, profile, activity or lease expiry. A registered query
reads that catalog and all heads in one short read-only repeatable-read snapshot,
requires exact region/frame resource coverage, then fully replays every immutable
cut after metadata completion. Returned catalog evidence remains scoped to that
connected database view, without a terminal-extinction or external branch claim.
Executed locally:
- MSVC **19.44.35217.0** default Release full CTest **79/79 passed**, **13.91 s**.
- GCC 14 Release private population/history/registered-coverage qualification
passed **exit 0, 17 s** (15 s population phase), with final normalized catalog
parsing and full unsigned-64-bit/decimal-integral ID fixtures.
- Clang 19 Linux **ASan/UBSan** final combined registered coverage, history,
migration, TLS and storage fault matrix passed **exit 0, 71 s** (67 s population
phase), without sanitizer reports.
- Explicit clang-tidy 19 covered the shared snapshot/coverage adapter, population
integration tests and migration-history tests; final changed adapter/assertions
were rechecked with no owned warnings. Repository clang-format 19,
`bash -n` for both changed shell scripts and `git diff --check` passed.
The first full frozen-binary attempt exited 1 after **437 s**, at the online
migration test's stale expected schema-49 history. The database correctly reached
50. That assertion now explicitly includes the accepted schema-50 addition;
prior migration bytes and biological goldens are unchanged. The corrected full
persistence/process/backup/DR and SQL rerun passed with **exit 0, 551 s**: C++
integration/process/load/history **435 s**, registered/migration TLS/storage
faults **41 s**, life reservations **4 s**, backup/restore **25 s**, host-loss DR
**8 s**, upgrade **10 s**, migration history **5 s**, runtime permission audit
**11 s**, checksum/future-version rejection **8 s**, plus setup/migration. The
fresh frozen-binary runner recorded its successful completion sentinel. The
permission checks include revoking the new registry read grant and requiring
the effective-privilege audit to reject that configuration.
Real empty registered regions exercise exact coverage, omitted/extra/duplicate
resources, wrong frames, unknown worlds, released/expired holders and the 64/65
bound. The SQL listing retains the overflow sentinel. A numeric-domain fixture
uses decimal-integral IDs/frames and region UINT64_MAX without narrowing; rows
with missing heads fail rather than disappearing. A non-cellular registered
profile fails unsupported before any payload inference. Genesis inclusion tests
do not claim fresh authority from expired/released grants; genesis has no fenced
transition evidence to read.
Independent committed enrollment after catalog selection leaves the earlier cut
unchanged; the next query refuses the now-incomplete supplied list. Another
connection's uncommitted enrollment is excluded. Registered raw/cohort snapshots
also retain identical catalog/old-cut evidence across actual paired commits,
while later snapshots see both new heads and preserve living count/body/reserve.
Both declared and registered APIs fail closed under real loopback TLS request/
reply loss at BEGIN and COMMIT. Caller transaction and exception/cleanup guards
retain their prior behavior. No partial result or missing-as-zero fallback.
Schema 50 is additive: one bounded read function, no new catalog table/index or
registration write. Prior migrations 1..49 remain unchanged. Migration tooling,
rollback-history fixtures, runtime privilege audit, latest-prefix assertions and
unknown-future-version rejection now include 50. No biological rule, payload
format, golden, dependency, authority workflow or client endpoint change.
Limits: registry coverage is for the selected database view, not latest state at
return or an external branch identity. Other viable stores, accepted permanent
reconciliation records and complete global freshness remain open. No deployment-
host query/capacity claim, new TSan, remote CI, multi-host drill or actual multi-day
soak. No live database, deployment or World0 action. Private test clusters stop on
exit and retain their forensic directories.
Logs: `build/m127a-native.log`, `build/m127a-final-postgres-build.log`,
`build/m127a-final-postgres.log`, `build/m127a-final-asan-build.log`,
`build/m127a-final-asan.log`, `build/m127a-tidy.log`,
`build/m127a-final-tidy.log`, `build/m127a-final-format.log`,
`build/m127a-shell-syntax.log`, `build/m127a-full-postgres.log`,
`build/m127a-full-postgres.exit`, `build/m127a-recheck-build.log`,
`build/m127a-recheck-tidy.log`, `build/m127a-recheck-format.log`,
`build/m127a-full-recheck.log`, `build/m127a-full-recheck.exit` (completion only).
## 2026-10-18 - M12.6d consistent scoped census snapshots
[ADR-0153](../adr/0153-consistent-cellular-census-snapshots.md) captures the current