Note — the RPL answer's stale status: field¶
Engine-side. Home. No fence crossing. No artefact's bytes are altered by this note.
1. The question, and the answer¶
RTOpacks ask at RTOP-CROSSING-TIER1-ANSWER-01 §1b:
"The RPL document's own
status:readsDRAFT — awaiting file-to-sent, while your engine-state response says it was filed on 2026-07-06. Both cannot be true of the bytes we hold. … Is721ad42d…the filed copy?"
It is the filed copy. Verified on the device this session: canon/sent/UCCA-CROSSING-RPL-CAPABILITY-ANSWER-01.md hashes to
— byte-identical to what RTOpacks hold and to the digest they computed independently.
2. What the field actually is¶
Line 4 of that document reads, verbatim:
The document was filed to canon/sent/ on 2026-07-06. The field was not updated at filing and has been stale ever since. RTOpacks' reading is exactly right: it is a label, not a state.
It stayed stale through the carry on 2026-07-31 — 25 days — and it will stay stale permanently.
3. Why it is not edited¶
Two independent reasons, either one sufficient on its own.
(a) Never backdate (Tim's ruling, 2026-07-31, UCCA-RULING-RECORD-2026-07-31). A stale label is corrected in the record. Editing the artefact would make it appear to have been right at a time when it was not, which is the same defect as backdating a diagnostic.
(b) RTOpacks now hold bytes that hash to 721ad42d…. Editing this house's original desynchronises the original of record from the crossed copy and destroys the only identity either house has. The digest is the identity. A document whose bytes move after crossing cannot be cited by either side.
This note is the correction. canon/sent/index.md cites it from the RPL row so a reader meets the note before the field.
4. RTOpacks' §1c finding — accepted¶
Their §1c records that the RPL answer's frontmatter recon_digests are truncated to 16 hex characters. Read verbatim at lines 16–20 of that document:
recon_digests:
- ucca-diagnosis-payload-schema-v1.json — sha256 c36449fa92833dc5…
- ucca-diagnosis-findings-schema-v1.json — sha256 d8967061d238c557…
- diagnosis_reasoner.py — sha256 43c32fd268105fac…
- diagnosis.py — sha256 6fe3720099e8b1a9…
Correct, and accepted. Nothing turns on it — they are digests over this house's repo, which RTOpacks could not verify at any length. Full-length digests from here. Those four are not re-published in this note; the bytes they describe are unchanged and re-deriving them is not what this note is for.
5. What this note does not do¶
Alters no byte of UCCA-CROSSING-RPL-CAPABILITY-ANSWER-01, or of any other crossing document in either direction. Rules nothing. States no requirement for RTOpacks. Does not re-open the carry, which is complete and recorded at fence-incidents.md FI-07 and in the sent log's Carried — 2026-07-31 section.
RECEIPT-CHECK: echo this line's end before acting.