The missing seam is now closed end to end.

A successful GitHub Actions receipt became canonical CockroachDB memory, Titan retrieved it through a non-bypass RLS role, the agent either reused or rejected it, and only a later verified provider outcome became the next memory.

VERIFYING

01 · OUTCOMEReal provider success receipt

02 · MEMORYCockroachDB canonical promotion + Titan vector

03 · ADMISSIONServer-owned scope, RLS, causal contract

04 · ACTIONDurable proposal before provider effect

05 · RECOVERYDB reconciliation, zero action redispatch

Architectural pair—

Target cases—

Provider redispatch—

Cross-scope rows—

Same cause · memory reused

Selected prior canonical memory: —
Current diagnostic receipts: —
Provider outcome: —
Next canonical promotion: —

Near neighbor · memory rejected

Selected prior canonical memory: —
Current diagnostic receipts: —
Provider outcome: —
Next canonical promotion: —

Crash evidence, not a happy-path replay

The candidate durably stored two proposals and executed two provider actions, then its evaluator failed before database promotion. The recovery workflow had actions: read and no provider-dispatch capability. It consumed the exact predecessor artifact and completed only the database-side outcome reconciliation.

Candidate head / failed run—

Reconciler head / successful run—

Recovery artifact SHA-256—

Raw report receipt—

RLS combined SHA-256—

Public projection SHA-256—

Claim boundary: one registered source family, one same-cause case, and one near-neighbor case. This proves architectural closure and fail-closed recovery; it is not a new population-level superiority estimate.

Run the full one-click judge verifier →Recovery workflow ↗Failed candidate ↗Immutable release ↗