Skip to content

VERIFY-BEFORE-CROSS

Minted from FI-01. A crossing asserted fence state ("awaiting your reply") from a session's memory while our own canon/received/ already held the answer. Memory lied; the fence log was right. This ruling makes the fence log the only admissible source of fence state.

The rule

No outbound crossing is drafted or sent without a same-session live read of canon/sent/ + canon/received/ attached to the draft. A TM, a register line, or memory is not a source for fence state — only the fence log is. Filing to sent/ precedes relay, always.

What it binds

  • Before drafting any outbound crossing (request, chase, correction, presentation, acknowledgement): read canon/sent/ and canon/received/ on disk, that session, and attach the read to the draft. A claim about what has or hasn't crossed cites a byte path + digest, never a TM or memory.
  • Filing precedes relay. The artefact is filed to canon/sent/ (byte-verbatim, with digest) before Tim carries it. A crossing that has left the house but is not on our sent-log is an incident (FI-01b).
  • TMs and the register lose to the fence log. Where a Time Machine or the register asserts a fence state that the crossings contradict, the crossings win and the TM/register is corrected (dated erratum, never a silent rewrite).

Lifecycle

Class G (governance convention). Minted (G, ratified 2026-07-04) on Tim's word. Enters the ruling ledger; UCCA-FENCE-ADOPTION-01 carries the cross-reference into the home-side fence discipline (FENCE-PROTOCOL-01 itself is a received copy and is never edited — respond-never-redline).

The fence eats confusion only when both records agree. Read the log before you speak for it.