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 4 of 4 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-a19af16fae58a8c38c60bab2 · master 627e728c4b819013 · S339.

LIB2-264 · Withdrawn claim that the promotion functional was constructed and run

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

Statement

The earlier promotion-gate account said its canonical test functional was constructed and its zero set house-verified at the required operator tier.

Parts of the statement (2)

Each part is a clause of the statement above, cut so that one part makes one claim. A reader naming the clause a quote supports can name the part.

p1 · The earlier promotion-gate account said its canonical test functional was constructed (one claim)
p2 · its zero set house-verified at the required operator tier. (one claim)

Scope

domain	The overstated construction and operator-tier verification of the promotion gate, not the narrower executable recovery map or scalar-tier zero-set result.

What this does not show. The correction does not deny the executable recovery map or the qualified scalar zero-set computation, and does not assert that the gate cannot be executed.

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 X, §3.3, Promotion-gate construction correction — PDF p.368 (bytes of record)
review state: REVIEWED · role SUPPORTS · warrant: gemini read SUITE_TEXT_EXTRACT → SUPPORTS · grok read THE_RECORD → SUPPORTS

Correction to the Rev28 wording, which said the canonical test functional Spromo “is constructed” and its zero set “house-verified”.

Appendix X, §3.3, Functional specified rather than built — PDF p.368 (bytes of record)
review state: REVIEWED · role CONTEXT · warrant: gemini read SUITE_TEXT_EXTRACT → CONTEXT · grok read THE_RECORD → CONTEXT

the functional is specified, not built, and no run of it exists.

Appendix X, §3.3, Scalar-tier result retained — PDF p.368 (bytes of record)
review state: REVIEWED · role CONTEXT · warrant: gemini read SUITE_TEXT_EXTRACT → CONTEXT · grok read THE_RECORD → CONTEXT

That zero-set result stands — at scalar tier, with Ĥ = H4 , the qualifier carried at s954:9 and dropped in transmission to the paper; it is restored here.

Appendix X, §3.3, No impossibility-of-execution claim — PDF p.368 (bytes of record)
review state: REVIEWED · role CONTEXT · warrant: gemini read SUITE_TEXT_EXTRACT → CONTEXT · grok read THE_RECORD → CONTEXT

The stronger reviewer formulation — that the gate “is not an executable object” — is too strong, is not adopted, and should not be repeated.

Evidence (availability is not outcome)

kind	reference	line / key	availability	note
registry	Rev29 promotion-gate correction; Appendix X §3.3 p.347; s953/s954 locators	—	shipped	The suite reports an AST audit and distinguishes the uninstantiated functional from the built recovery map and scalar-tier result. No audit or scientific kernel is run here.

What was said, and what retired it

historical statement	The canonical test functional Spromo “is constructed” and its zero set is “house-verified”, without retaining the scalar-tier qualifier.
where it stood	Rev28 promotion-gate wording, corrected in Appendix X §3.3 p.347
retiring decision	Rev29 promotion-gate correction, carried in Appendix X §3.3 p.347; AST audit and restored s954:9 qualifier
what the suite prints now	the functional is specified, not built, and no run of it exists. PDF p.347 (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-174 The record-quotient observation composite is unique under its seven premises	—
`related_to` (never evidential)	LIB2-005 Joint basepoint and microscopic observation-map construction	—

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

states a predicate	yes
uses on the record · unblocked	4 · 4
uses any lane has read	4 of 4
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
Track-2 claim ids	D-OBS-01, F-FAITH-01 — cross-reference; the Track 1 / Track 2 join sets each one against what the sealed suite prints for this record. Where they differ, the suite is the record.
serials	s953 s954
candidate ids (frozen list S304)	C2-067 C2-088

Drafting-lane note

C2-067/C2-088 are the nearest microscopic-output candidates. The historical construction claim and the retained lower-tier computation are kept distinct. This is not a claim that OMOS was never built; OMOS is the separate record-quotient object G-178.

Receipt

round D1253 · parsed 2026-09-06T00:06Z · machine gates passed: CONTRACT, G1-quote-on-page (LOCATED, NOT SUPPORTED — this record's own note below says the cited source does not carry its statement; G1 tests where a quote IS, not whether it supports the claim), G2-numerals-declared, G4-ids-resolve, DAG-acyclic · content sha256 5f0b021acdfea48650ea83edf2dd306ccce912d45f1519ec241af43bdc224dc1

Review this entry

Reviewer verdict line (one per entry, as text): LIB2-264 | 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