The Claim Status Packet is a schema specification, unimplemented, addressing a defect class the archive had already ruled on once. Deposit counts hand-maintained across the fleet drifted to 57 percent of true before being bound to a single source; the repair was a binding, not more careful editing. The same class recurred inside a specification batch, where a document's version diverged from its own machine-readable layer three times, and a single status string was hand-maintained in six separate locations. Corrections logged as sweep residue were largely those copies disagreeing: recorded as editing failures, they were a schema failure.
The packet separates five objects that earlier drafts conflated: claim and typed state, relations, provenance of transitions, bindings, and policy. State is typed rather than scalar — what was asserted, by whom, with what verification, at what scope — because a single status field conflates dimensions that fail independently and lets one word become a universal solvent. The packet points at a claim by anchor and hash rather than restating it: a restated proposition becomes a second textual authority whose wording drifts from the document it describes.
Relations do not copy state. They license specified transitions on specified dimensions, and most license nothing. That is what prevents a candidate interpretation from attenuating the observation it interprets — not because claim kinds are sealed, but because the interprets relation transmits nothing. Rank survives only as a default where no relation is declared, and the default is silence rather than hierarchy. Path licensing requires every edge to license the same dimension in the same direction, since mixed-dimension paths compose into nothing.
The architecture is generate facts and lint argument. Mechanical facts — version, dates, status enums, inclusion flags — are projected from the packet at build time, while claims, interpretations and scope-sensitive sentences remain authored. An earlier draft specified a checker over hand-maintained copies and described it as a single-source binding; that improved six unaudited copies to six copies plus a linter, which is not the repair.
The attenuation metric is unsupported attenuation rather than raw weakening. Early drafts overclaim and editorial narrowing is the work, so a healthy pipeline weakens often; what matters is weakening with no evidence, scope or proposition change on the claim and no relation licensing propagation from whatever triggered it. Named vulnerabilities include layer smuggling, undeclared surfaces, cleanliness relocating rather than removing complexity, false harmony, and claim-identity smuggling. No generator and no checker exist, no document carries a generated packet, and no anchors have been inserted.