Complete M7.5 durable batch outcomes and commit resolution

ADR-0063: manifest v2 (360 bytes) binds a per-tick validation trace
object and a canonical decision block by SHA-256. Publication replays the
trace from the committed predecessor's verified payload and requires
every report and the candidate bytes, derives deaths deterministically,
uploads payload and trace with verified read-back, then sends manifest
and decisions to one fenced statement. RegionBatch seals at a terminal
transition or 64 ticks and refuses ticks until durable confirmation.

Schema v5 records the checkpoint, its decisions and outbox rows
atomically; a unique index keeps one terminal outcome per actor
(EVL08), triggers make commits/decisions immutable (EVL09), an exact
retry of a committed ID returns the original receipt, changed bytes
conflict, and read-only resolve_region_commit answers committed/absent/
conflict. Outbox pending/acknowledge give idempotent at-least-once
delivery. Recovery reconciles durable deaths with restored lifecycle
(and archive deaths for the lineage profile).

Validated: Windows CTest 58/58; Linux GCC Debug/Release, clang-tidy and
ASan/UBSan CTest 58/58 each; PostgreSQL suites Release, analysis, ASan
(lost response, committed-after-timeout, terminated orphan retry,
changed bytes, repeated/partial/reordered decisions, gap, outbox
redelivery, history quarantine); five mutations each caught. No
Docker/Gitea CI, process kill, broker or deployment.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-09-28 17:30:30 -04:00
co-authored by Claude Opus 5.5
parent a2c4543df2
commit dd7e8028b0
27 changed files with 2075 additions and 216 deletions
+24
View File
@@ -812,3 +812,27 @@ and ASan/UBSan CTest each ran 57/57. The PostgreSQL suites passed 2/2/5 times.
Next: M7.5 durable decisions, history and outbox rows, and commit-ID resolution.
Retained ancestry still needs M7.5 history and M7.7/M7.9 kill-recovery evidence.
## M7.5 durable batch outcomes (2026-09-28)
ADR-0063 introduces manifest v2, which binds a per-tick validation trace object
and a decision block.
- Staging replays the trace from the committed predecessor's verified payload and
must reproduce every report and the candidate bytes.
- `RegionBatch` seals at a death or at 64 ticks and refuses ticks until the commit
is confirmed.
- Schema v5 records each checkpoint, its deaths and their outbox rows in one
statement:
- one terminal outcome per actor;
- committed history is immutable;
- exact retries return the original receipt;
- read-only resolution answers committed, absent or conflict.
- Recovery reconciles durable deaths with the restored lifecycle.
Real-PostgreSQL tests cover a lost response, a timeout that later committed, a
terminated orphan that was retried, changed bytes, repeated or partial or
reordered decisions, gaps, outbox redelivery, and history disagreement. Five
mutations were each caught. Windows and Linux ran 58/58; PostgreSQL suites passed
under Release, analysis and ASan.
Next: M7.6 region host. No host, broker, deployment or process-kill test exists yet.