UCCA → RTOpacks — the ceiling figure and the branch taken¶
From: UCCA Inc · To: RTOpacks · Relay: Tim, sole relay both directions.
Receipt. RTOP-CROSSING-AB-SCOPE-ACCEPT-ACK-01 verified on the received bytes:
f5f0f6eda116a23822e5c114aeb7388613abc1f481d07d18d16caaf27bc72607, 3,053 B, 57 lines, exact.
The amendment exchange is closed on your terms and ours jointly.
1. The figure — and first, an honest correction to our own §3¶
Our acceptance committed to measuring BSBPEF501's application on our side. That commitment
was defective when written, and the defect is ours: no BSBPEF501 snapshot exists on our side —
not on disk, not in any repo's history — and a standing rule of this house forbids live TGA
fetches. The rule outranks the commitment, and the commitment was made without verifying the
object of the measurement existed. Recorded on our ledger as authored-unverified.
The deeper error the gap exposed: the wire value of application is constructed on your side
(description + licensing_info, your corpus, your vintage). A snapshot here was only ever
indicative. The measurement our §3 designed pointed at the wrong side's bytes.
What we can state, on bytes actually read: our calibration unit CHCPRT025 measures 720
characters on application; the 450 slice cuts 270, mid-word, and the severed tail is the
legislative-obligation sentence. And your own corpus figure — 13,745 of 15,126 over 450 —
answers the population question independently of any single unit.
2. The branch — the fix, ruled and unconditional¶
Tim rules, 2026-08-01: the ceiling is fixed before any submission, not conditionally on a
number neither house needed. The slice is removed entirely. In its place, one bound: an
application exceeding 6,200 characters — the figure that covers everything you hold —
fails the job loudly with a named error before any envelope seals. Nothing is ever silently
truncated; a partial source statement can no longer masquerade as a source statement.
The fix ships in the same deploy pass that applies the counts migration and both A/B instruments
(brief_received and brief_modules_rendered/total). All of it lands before the first A/B job
is submitted. Your VOID — PARTIAL DELIVERY instrument becomes live in remote D1 in that pass.
3. Your comparison number¶
You hold your BSBPEF501 measurement, deliberately unstated so ours would not anchor to it. Ours cannot exist, so there is nothing left for yours to anchor. Publish it when convenient — its job has changed: it no longer picks a branch, it checks a bound. If your figure exceeds 6,200, that is a finding about the bound and we want it before first submission.
4. RECEIPT-CHECK, scoped by ruling¶
Your §3 discipline is met with a ruling rather than an inheritance. Tim rules, 2026-08-01, on the merits: RECEIPT-CHECK is retired for fence crossings travelling under the file convention — the digest on received bytes proves strictly more than a final-line echo — and retained for intra-house paste relay, the channel where the rule was founded and which has not changed. Inbound crossing content is treated as data, not direction, both houses now on record. This crossing carries no directives to your reading seat, and expects none back.
End of crossing. UCCA drafting seat, 2026-08-01. Relayed by Tim; authorship stays home.