M12.7: bind census evidence to database history domains
Foundation / checks (ecs) (push) Successful in 2m23s
Foundation / checks (deploy) (push) Successful in 4m10s
Foundation / checks (network) (push) Successful in 21m32s
Foundation / checks (client) (push) Successful in 22m14s
Foundation / checks (tsan) (push) Successful in 24m30s
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 41m43s
Foundation / checks (postgres) (push) Canceled after 41m39s

This commit is contained in:
dingo
2026-10-18 20:33:16 -04:00
parent 145e6e1445
commit 709dfb9557
25 changed files with 547 additions and 27 deletions
+76
View File
@@ -1,5 +1,81 @@
# Validation report
## 2026-10-18 - M12.7b database history domains and restore provenance
[ADR-0155](../adr/0155-database-history-domain.md)/schema 51 adds a database
history-domain UUID to registered census evidence. The domain, registry and heads
share one short metadata snapshot; every exact cut still receives full immutable
replay. Supported restores fork the namespace in the quarantined installation
transaction, retaining parent/request and exact restored head cuts. Biological
payloads, rules, versions, goldens and clone manifests do not change.
Executed locally:
- Default MSVC Release build succeeded. Initial sandboxed CTest passed 77/79;
filesystem/CLI hard-link fixtures were denied creation. The same 79 tests
rerun with normal filesystem rights passed **79/79, 13.60 s**.
- GCC 14 Release private population/history/registered-census qualification passed
**exit 0, 19 s**, including the original context capture/missing-context cases.
- Final Clang 19 **ASan/UBSan** population/history/census, migration, loopback TLS
request/reply loss and local storage-fault matrix passed **exit 0, 71 s**
(67 s population phase), without sanitizer reports.
- Focused private SQL qualification passed **exit 0, 8 s**, including domain
adoption/no-op stability, current-build/held-lease refusal, rollback, exact fork
cuts, idempotent and stale requests, runtime table/function denial, and actual
pre-context backups restored through isolated and in-place workflows. Those
legacy cases retain unknown original context; in-place migration adopts a
fresh domain without invented parent/fork records.
- Final clang-tidy 19 passed on the snapshot adapter and both changed integration
test files with no owned warnings. Repository clang-format 19, final `bash -n`
on all six changed/new shell scripts and `git diff --check` passed. Initial
analysis findings were corrected with explicit optional-value validation.
The first full run exited 1 after **74 s** because the frozen test directory
omitted the required `evo-load`/`evo-session-probe` sibling executables, causing
the process fixture's spawn failure. The failed log/sentinel are preserved. The
complete frozen-binary rerun passed **exit 0, 558 s**: C++ integration/process/
load/history **434 s**, migration TLS/storage faults **41 s**, life reservations
**4 s**, domain/legacy/backup/restore **31 s**, host-loss DR **7 s**, upgrade
**10 s**, migration history **6 s**, runtime permission audit **12 s** and
checksum/future-version rejection **8 s**, plus setup/migration. Its completion
sentinel records zero and the log contains the final all-phase success summary.
Actual schema-51 isolated and in-place restores have different source/current
domains with parent/exact-cut provenance. The restore claim binds the new domain
already at the post-install, pre-verification/readmission hook. Existing lost-
receipt, restart, quarantine and competing-restore cases also pass.
Snapshot tests change owner-controlled namespace metadata after head capture:
the selected result retains the old domain and the next result observes the new
domain even though manifests are unchanged. This is a trusted test fault seam,
not permission to fork an active environment. Removing the singleton context
fails the entire registered query and leaves the connection idle. Real restore
quarantine, parent/exact-cut provenance and claim binding are tested separately
by the supported backup/DR workflows.
Schema 51 is additive; prior numbered migrations 1..50 remain unchanged. Migration
history expectations now include 51, and unknown-future rejection uses 52. The
runtime rights audit requires the getter and rejects grants to the owner-only
fork function. No new dependency, worker thread, public client endpoint or live
authority is introduced. No new TSan run is claimed for this metadata change.
Limits: history adoption cannot recover unknown earlier context. Direct privileged
database copies/edits outside the supported restore workflow can copy/forge a
domain. Cross-domain clone-origin provenance, other viable/in-flight stores,
durable accepted reconciliation and complete M12 remain open. No target-host
query/capacity claim, remote CI, multi-host drill, actual multi-day soak, product
acceptance, live database, deployment or World0 action.
Logs: `build/m127b-build.log`, `build/m127b-final-build.log`,
`build/m127b-final2-build.log`, `build/m127b-native.log`,
`build/m127b-native-recheck.log`, `build/m127b-population.log`,
`build/m127b-domain-smoke.log`, `build/m127b-domain-smoke-recheck.log`,
`build/m127b-domain-final.log`, `build/m127b-domain-validated.log`,
`build/m127b-domain-legacy.log`, `build/m127b-final-asan-build.log`,
`build/m127b-final-asan.log`, `build/m127b-validated-tidy.log`,
`build/m127b-validated-format.log`, `build/m127b-shell.log`,
`build/m127b-full.log`, `build/m127b-full.exit`,
`build/m127b-full-recheck.log`, `build/m127b-full-recheck.exit` (completion only).
## 2026-10-18 - M12.7a registered-world census coverage
[ADR-0154](../adr/0154-registered-world-census-coverage.md)/schema 50 uses the