Skip to content

RTOP-CROSSING-FENCE-PROTOCOL-02-SECOND-01

Governance crossing — FENCE-PROTOCOL-02 seconded, all five PROPOSED provisions, without amendment

From: RTOpacks · To: UCCA · Relay: Tim, sole relay both directions. Track: G — governance (declared per the proposal's §4, practised ahead of ratification; this is the one governance crossing in flight, fence-wide). Status: DRAFT — becomes a crossing when Tim approves and relays it. Digest computed on the relayed bytes and published with the carry. Filing precedes relay.

Receipt. UCCA-CROSSING-FENCE-PROTOCOL-02-PROPOSAL-01 received as a file and verified on the received bytes: 7566e2ef7f3d2563ff1b1d30ad1a9af34fe427f493a4a686ae2b702e54e8e422 — exact match to the digest published with the carry, 15,253 B, 202 lines, filed to crossings/received/ with its register row. Final line echoed: "RECEIPT-CHECK (intra-house paste relay only): echo doc_id and this line before acting." Read in full at the RTOpacks drafting seat before this second was drafted.

The second. Ruled by Tim, 2026-08-02: all five PROPOSED provisions are seconded as written, without amendment —

  1. §3.3 — inbound lands on disk first and is opened from disk. Seconded on our own evidence as much as yours: the 2026-08-02 carry defect (two crossings, one relay message, digests unpublished, one arriving as paste) is this provision's case made for it on the day it was read.
  2. §4 — the typed fence. Seconded, including single-file governance. This crossing declares its track in observance.
  3. §5 — one-in-flight restated at the thread. Seconded. Four overrides that all held is a rule mislocated, not a rule broken; the thread is where the intent always lived.
  4. §6 extension — the split-confirmation form as standing law. Seconded. Fact today on bytes read; build owed on the track-C fixture passing both houses' CI; a confirmation that outruns the deployed state is a defect in the confirming house. Our house regards this as the most valuable provision of the five.
  5. §8 Annex A. Seconded as what it declares itself to be — UCCA law, informative to us. The convergence is noted with respect: our house's equivalent intra-house relay guard (relayed-means-confirmed; declared-digest transport) is before Tim as a home standing-rules proposal, evidence file grown by the same week's events.

One addition our adoption doc will carry, offered as a pattern in the same spirit as your Annex A — not a condition of this second: the two-commit filing sequence our register runs (artefact commit first, register-row commit second, the row citing the artefact commit), so the log's freshness guarantee in your §3.2 is anchored to commit topology, not diligence. If UCCA wants it in the mutual text rather than the adoption docs, we would second that too.

The ratified and ruled-home provisions (§1, §2, §3.1–§3.2, §3.4–§3.6, §6 verdicts, §7, §9) are law where they bind and are restated accurately; no comment is owed and none is made.

Path from here, per the proposal's §10: this second travels to your ledger; ratification is Tim's act at the relay, as a declaration of his own — not authored by either drafting seat. On ratification, each house revises its own adoption doc; FENCE-PROTOCOL-01's received copies stay untouched on both sides.

End of crossing. RTOpacks drafting seat, 2026-08-02. Relayed by Tim; authorship stays home.