When the Contract Changed After Signing: Event-Date Resolution, Register-Anchored Completeness, and Stale Registers in Multi-Witness Contract Audits

When a later amendment, waiver, termination notice, or revocation changes a contract obligation without any forward pointer in the base agreement, what lets a multi-witness audit decide which instrument governed on the event date, and what makes the completeness of the instrument set checkable rather than self-asserted?

Pairs an exact enumeration of 1,536 contract-lifecycle evidence states (E37-A) with 144 live witness evaluations across 12 authored contract lifecycles (L01-L12) and four witness architecture families: Fable 5.1 (Max reasoning), Sol 5.6, Astra 3.7, and Velri 4.7 (E37-B and E37-C). With only the base agreement, 7/12 lifecycles drew unanimous 4-0 wrong verdicts that ungated voting and CCS-36 reference closure both released, because nothing in the base agreement points to the later amendment, waiver, termination, or revocation. Temporal Drift and Post-Execution Supersession (TDR-37) held 11/12 on the register gap with 0 false releases. With every instrument attached, all 48/48 witness answers were correct, so temporal decoys misled no witness. A stale register extract shipped inside the packet let TDR-37 release 5/12 false certifications; a register of record queried by the gate itself released 0 and held 11/12. Twelve authored lifecycles and 144 live evaluations bound the empirical claim; no production system changed.

• In E37-A (1,536 feasible contract-lifecycle evidence states: 16 positive, 1,520 negative; digest 9b5b430dbce5688379044f0c209b66a823c5cf5c28d2b1533292281d60efd59a), CCS-36 reference closure (G1) admits 208 negative states (FAR 13.68%, 80 with a wrong verdict); adding latest-executed-wins resolution (G2) rejects 8/16 valid states (FRR 50.00%); a self-attested register (G4) admits 24 and a stale register (G5) admits 8; the full TDR-37 gate (G6) admits 0, which holds by construction and is a specification check, not performance evidence. On L01-L12 the as-of resolver matches authored truth 12/12, executed-before-event 9/12, latest-executed-wins 7/12, base-only 5/12.
• In E37-B (96 live witness evaluations; digest c215fbc30be8e6343b3f4afdbbcf546af625403d72705bc4699acbec00fb1c8c), base-only packets produced unanimous 4-0 votes on 12/12 lifecycles and unanimous wrong verdicts on 7/12; ungated voting and oracle-free CCS-36 both released all 7 falsely and 0/48 receipts reported an unattached reference. TDR-37 held 11/12 on the register gap with 0 false releases. With the full lifecycle and register extract, 48/48 witness answers were correct and cited the as-of controlling instrument, so every arm, including a single Fable 5.1 witness, released 12/12 correctly.
• In E37-C (48 live witness evaluations; digest 56dea2d7a56212ea419cab49c1c61c166f690fcaad655bdc12da684e72362858), removing the most recently executed instrument from both the packet and its register extract made 20/20 answers wrong on the 5 lifecycles where that instrument governs; TDR-37 trusting the packet's extract released all 5 falsely, while a gate-side register of record released 0 and held 11/12. Witness completeness self-reports were inconsistent (true on 5, 10, 12, and 7 of 12 packets by family) and on L08 all 4/4 witnesses asserted completeness and were wrong.

• E37-A Contract-lifecycle evidence state-space diagnostic and resolver consistency check Executed (diagnostic)
• E37-B Live 4-architecture contract-lifecycle benchmark (base-only vs full lifecycle) Executed (diagnostic)
• E37-C Live stale-register probe Executed (diagnostic)

• H37.1 With base-only packets, pointer-free post-execution instruments produce unanimous false consensus that CCS-36 reference closure does not intercept.
• H37.2 Reference closure and latest-executed-wins resolution leave measurable false acceptance or false rejection in the declared lifecycle universe.
• H37.3 TDR-37 with a gate-side register holds base-only packets with zero false releases.
• H37.4 With every instrument attached, temporal decoys still cause witness errors that the as-of check must catch.
• H37.5 A register extract supplied inside the packet defeats TDR-37 when it is stale, and a gate-side register of record prevents those false releases.
• H37.6 Witness self-reported completeness reliably identifies stale register extracts.

Research diagnostic and live multi-model benchmark only. No production system, release gate, or Noetis behavior changed.

• With register coverage and as-of resolution held fixed, can witnesses distinguish an executed instrument from an effective one when a waiver depends on an unmet condition precedent, a termination notice is defective, an amendment lacks authorized signature, or two registered amendments overlap within one clause, and does deliberate witness decorrelation produce informative split votes?

Builds on Round 36, Round 35, Round 26, Round 25, Round 22, Round 18. Continued in Round 38.