Files
aevolution/schemas/ecology/database-history-domain-v1.md
dingo 709dfb9557
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
M12.7: bind census evidence to database history domains
2026-10-18 20:33:16 -04:00

1.6 KiB

Database history domain v1

Semantic evidence contract, schema 51; ADR-0155. No biological byte format or public client endpoint.

  • A registered census result carries a nonzero 16-byte UUID history_domain. The external world key is (history_domain, census.world).
  • Domain, durable region registry and all selected heads share the same database repeatable-read metadata view. Exact replay and set validation remain required.
  • A missing/zero/malformed domain fails the entire registered result with a context error; SQL/transport failures retain the transaction error. No inferred domain, local-list fallback, cache substitution or partial/zero result.
  • Adoption is database-local metadata. It does not identify an unknown original branch predating migration. Caller-declared snapshots remain local observations.
  • Supported restores of schema-51 bundles fork while quarantined, atomically with installation. Record parent/current domain, restore-claim UUID and exact restored head tuples (world,region,frame,sequence,commit,digest,end_tick). Repeated current requests are idempotent; stale requests and unquarantined forks refuse.
  • Legacy backups without a domain acquire a fresh adoption only when migrated. Their original external context remains unknown. Direct privileged database copies outside the restore workflow do not receive an automatic new identity.
  • A captured domain is neither live authority nor a terminal-extinction decision. Cross-domain clone provenance, other viable stores and durable accepted global reconciliation remain separate work.