PUBLISHED under R67 (condition T-B) — NOT house-adjudicated. Build S371a. What PUBLISHED means here (R72): two non-drafting AI lanes (gemini + grok) read this record's anchor citation on different objects and agreed it SUPPORTS the record's statement; no citation on the record is disputed as support; its machine certificate is current. What it does not mean: no person has signed off on this record (adjudication: NOT_ADJUDICATED), the drafting lane's own reads count for nothing, and 2 of 2 unblocked uses were REVIEWED — the rest were read by one lane or none. Every label shown is the label as printed in the suite of record (Rev33.1_S369 (PDF sha256 b64ddcd9e16a6dcd…)); no house tier is assigned. The state is recomputed from the uses on every build and is withdrawn if they stop justifying it. Receipt: condition R67-TB · anchor SU-2640605907bafc30b6b5684f · master 627e728c4b819013 · S339.

LIB2-263 · Retired depth-exclusion inference from commuting charge and mass

class RETIREDmath status (as printed) —attachment (as printed) —scorecard tier word (as printed) none printedhouse tier not yet assignedreview state PUBLISHEDentry version 7

Statement

The earlier depth-exclusion cut treated commutation of the mass and electromagnetic charge operators as forbidding depth sourcing.

Scope

domain	The former exclusion of depth sourcing, not the distinction between the two finite clock labels.

What this does not show. Withdrawing the cut does not identify the two clock labels or select depth or order as the physical source.

Sources in the suite of record

Key — use ≠ record. A review state printed on a source use below names that use — one citation of the suite, read by the lane named in its warrant — not this record. The record's own review state is the one in the table above and is unchanged by any use-level state; a use may be LANE_PROPOSED or REVIEWED while the record it sits on remains IN_REVIEW (R45, R49).

Quotes are verbatim from the sha-pinned text extraction of the Rev33.1 PDF (A1584 §2.2, S309): mathematical typography — radicals, exponents, ≅ — can appear displaced in the extracted line. The PDF page is authoritative; the quote is what the machine gate matched.

Appendix S, §7, Casualty #7: depth-exclusion cut — PDF p.307 (bytes of record)
review state: REVIEWED · role SUPPORTS · warrant: gemini read SUITE_TEXT_EXTRACT → SUPPORTS · grok read THE_RECORD → SUPPORTS

the depth-exclusion cut retired ([M, Qem ] = 0 forbids identifying the two Z4 labels but not depth sourcing).

Appendix S, §5, Excluding depth would not select order — PDF p.305 (bytes of record)
review state: REVIEWED · role CONTEXT · warrant: gemini read SUITE_TEXT_EXTRACT → CONTEXT · grok read THE_RECORD → CONTEXT

Killing the depth ray does not select order (s and o alone span E); the root-line conditions are full coefficient hyperplanes, not coordinate rays.

Evidence (availability is not outcome)

kind	reference	line / key	availability	note
registry	Appendix S casualty #7 p.291; Appendix X casualty summary p.339	—	shipped	The suite retires the depth-exclusion cut and distinguishes label identification from sourcing. No charge or depth operator is evaluated in this round.

What was said, and what retired it

historical statement	The commutator [M,Qem] = 0 excludes depth sourcing.
where it stood	Earlier depth-exclusion cut, casualty #7 in Appendix S p.291 and Appendix X p.339
retiring decision	S244–S245 depth-exclusion correction; Appendix S casualty #7 p.291
what the suite prints now	the depth-exclusion cut retired ([M, Qem ] = 0 forbids identifying the two Z4 labels but not depth sourcing). PDF p.291 (bytes of record)
why retired	scientific_supersession — from the record's own words: `RESULT_CHANGED` → "correction"

A successor is linked, never "derived from" the retired statement (charter §10.10).

Typed links

type	target	licensed by
`related_to` (never evidential)	LIB2-029 The conditional selector for occupied golden mass-ladder rungs	—

Why this record is PUBLISHED (R67, condition T-B)

states a predicate	yes
uses on the record · unblocked	2 · 2
uses any lane has read	2 of 2
REVIEWED SUPPORTS use on the predicate, read by two non-drafting lanes	yes (1)
a SUPPORTS use on the predicate is DISPUTED	no
machine certificate current	yes

Machine certificate (R68)

state MACHINE_CHECKS_PASSED

policy sgtoe-clearance-policy-1.0-RATIFIED · sha16 ef7d6e7690514311

bound to master aad7a3ec6ce3b510 (the master the checks ran on; issued 2026-09-26T05:06Z)

checks

check	result	reason
`schema_valid`	PASS	exercised
`basis_current`	PASS	exercised
`quote_located`	PASS	exercised
`labels_literal`	N/A	class RETIRED not governed by the source_labels rule
`edges_resolved`	PASS	exercised
`bindings_valid`	PASS	exercised

A certificate says the record is well-formed, current, quote-on-page, label-literal, edge-resolved and binding-consistent on the bytes it was issued on. It is not a review, and it goes STALE the moment the master moves under it (R68). It is one conjunct of the PUBLISHED condition (R67), never the whole of it.

History

March library (v1) antecedents	no legacy antecedent identified
candidate ids (frozen list S304)	C2-068

Drafting-lane note

C2-068 is the nearest occupation/depth candidate. G-033 is related navigation, not a claim that the rung selector proves the missing source assignment. The exact old exclusion formula beyond the commutator is not reconstructed.

Receipt

round D1253 · parsed 2026-09-06T00:06Z · machine gates passed: CONTRACT, G1-quote-on-page, G2-numerals-declared, G4-ids-resolve, DAG-acyclic · content sha256 fdc876ff500e95fdae6beff7b6ece1b5ed9d22253dbe0715b2ad7a647fc00e5c

Review this entry

Reviewer verdict line (one per entry, as text): LIB2-263 | PASS or FAIL(G1–G8) or NOT RUN | quote | PDF page | one sentence. G1 source supports the exact scoped assertion · G2 evidence class fits (numbers ≡ digit source) · G3 labels as printed, not converted · G4 comparison typed · G6 public scope · G7 history real · G8 caution present and true. Machine surfaces: index.json · capsule.md.

Generated from library_v2.jsonl. Declared volatile fields (R36): BUILD_STAMP.
BUILD_STAMP S371a · 2026-09-26T22:53Z · master 01d1a5873ede42f5 · cut 9dcc6ce9a8ee3e02