Open Record or Closed Record? Declared Record Conventions, Near Miss Records Read as Negation, and Flag Only Against Rewriting Validators

When the record convention is declared, do readers still read a missing or defective record as proof that an event did not happen, and should a validator flag ledger defects or rewrite them?

Tests whether readers that took a missing record as proof an event did not happen (Round 42) misread absence or silently apply a closed record convention, and whether a validator should flag defects or rewrite them, as the Round 42 handoff and the roadmap asked. Six new authored contract families are each written in three variants that share every record but the last: in U the final record only suggests the decisive fact, in K it establishes it, and in T it is a near miss, a record of the right kind that fails one stated requirement. Witness B, Witness C, and Witness D answered every item under a declared open record and a declared closed record and with the undeclared Round 42 prompt, and filled one evidence ledger per item resolved by code under both conventions; Witness A read the T items under the open declaration until the budget rule stopped it. A structural diagnostic (E43-A, 0 model calls) certifies the variants and the exhibit track and shows that a flag only validator cannot create an unsafe release while a rewriting validator can. Live, 297 completed calls (E43-B and E43-C) found that undeclared direct readers released FAIL on 33 of 36 U and T decisions; declaring an open record removed every absence error (U 15 of 18 to 0 of 18) but not the near miss errors (T 18 of 18 to 6 of 18), and a declared closed record was followed on 36 of 36. Extraction readers released FAIL on 14 of 18 T items under the open resolver, and 5 of 6 direct unsafe releases coincided with the same witness's extraction. On 24 new SEC EDGAR exhibits with gold and seeded ledgers, the flag only validator made 0 unsafe releases in 48 and 12 false holds it could not repair; the rewriting validator was correct on 48 of 48 with no structural bound. Revises P7 (a failed record is not proof of absence), P4 (role decorrelates only where failure modes differ), and P5 (gate rewrites that can release); no production system changed.

• F43.1 (deterministic, E43-A): all seven certificates pass; a flag only validator cannot create an unsafe release, while a span valid rewrite turns each of the 12 gold HOLD exhibit ledgers into an unsafe release.
• F43.2 (live, E43-B): undeclared, direct readers released FAIL on 33 of 36 U and T decisions; declared open, U errors fell from 15 of 18 to 0 of 18 and T errors from 18 of 18 to 6 of 18, all FAIL on near miss items (S03T, S06T, S02T).
• F43.3 (live, E43-B): declared closed, direct readers were correct on 36 of 36 U and T decisions and 18 of 18 K decisions; K was also 18 of 18 under the open declaration.
• F43.4 (live, E43-B): extraction readers under the open resolver held 18 of 18 U items and released FAIL on 14 of 18 T items, marking the requirement UNMET from the near miss record; under the closed resolver they were correct on 35 of 36 with no unsafe release.
• F43.5 (live, E43-B): under the open convention, 5 of 6 direct unsafe releases coincided with the same witness's extraction unsafe release (independence 2.33); error correlation was positive for every role pair and every cross witness pair.
• F43.6 (live, E43-C): on 48 exhibit ledgers, the flag only arm made 0 unsafe releases and 12 false holds and repaired 12; the rewriting arm made 0 unsafe releases and 0 false holds and repaired 24; neither corrupted a correct ledger.

• E43-A Structural certificates for variants, conventions, exhibit novelty, and validator monotonicity Executed (diagnostic)
• E43-B Live declared convention study on authored near miss families Executed (diagnostic)
• E43-C Flag only against rewriting validators on real SEC exhibit ledgers Executed (diagnostic)

• H43.1 Declaring an open record removes the direct FAIL releases on U and T items.
• H43.2 Under a declared closed record, direct readers answer FAIL on U and T items and keep K unchanged.
• H43.3 Once extraction readers can err unsafely, a witness's unsafe releases coincide across its two roles.
• H43.4 A flag only validator creates no unsafe release; a rewriting validator can.
• H43.5 A flag only validator pays for its safety in false holds that it cannot repair.

Research diagnostic and live benchmark only. Recommends stating the record convention in every Noetis prompt and evaluation pool, adding a record level status to extraction ledgers, and accepting validator rewrites only when they move a decision toward HOLD, with rewrites that release sent to review. No production system, release gate, or Noetis behavior changed.

• Does an extraction ledger that records, for each cited record, whether it satisfies, fails, or is irrelevant to the condition hold near miss items under an open record, and does a second validator witness keep the rewriting arm safe on harder seeded defects?

Builds on Round 42, Round 41, Round 40, Round 37.