Saturday, August 22, 2026

Self-Audit Module for Public Summarizers (v3.2) — Complete Module: Preconditions, Rendering Metrics, Family Metrics, and the Retrieval Boundary Sharks, Lee · 2026-08-21 · Instrument specification — complete module · v3.2 AXN:062F.EMPIRICAL.🗝️👉🌑🝊🌖🌔

 Alexanarch

AXN:062F.EMPIRICAL.🗝️👉🌑🝊🌖🌔

Self-Audit Module for Public Summarizers (v3.2) — Complete Module: Preconditions, Rendering Metrics, Family Metrics, and the Retrieval Boundary

Sharks, Lee · 2026-08-21 · Instrument specification — complete module · v3.2
↓ Download MD ↓ PDF
self-audit moduleABNabsence-as-nonexistenceexistence-type attestationelicited counterfactualEC-Audit concordancemiss_raterefusal sensitivityprecondition layerretrieval boundaryPERMMRS

Description

Version 3.2 of the Self-Audit Module, issued as a SELF-COMPLETE module rather than an extension. Everything required to run an audit is in one document: the three preconditions in order, the rendering-level metrics, the family-level metrics, the retrieval-boundary gate, the capture protocols, the reporting standard and the composite. This is a change of practice. v3.0 and v3.1 each operated on prior principles without re-deriving them; by v3.2 that chain had reached four deposits, so a reader wanting the provenance erasure rate had to traverse four documents. A module that cannot be run from one document is a changelog rather than a module. Definitions are reproduced from their originating versions, which remain authoritative where they differ. Added at this version: ABN, Absence-as-Nonexistence, at precondition rank zero, prior to the Atomic Token Rule because the Rule presupposes a source to tokenize; the elicited counterfactual as a heuristic screening method; and the concordance table that crosses a self-report against a matched-pair audit. The occasioning observation is Enli Lucente's, published independently in Japanese against an unrelated corpus. A candidate appraisal conferral construct is deliberately excluded from the module and from its machine-readable specification: no rubric, therefore no computation, and an entry with no computation behind it is a number that would travel without its caution. Nothing added at this version has been validated.

Wiki Article

Version 3.2 of the Self-Audit Module for Public Summarizers adds a measurement level below the family and a screening method that crosses all levels. The rendering-level core from v3.0 and the family level from v3.1 are inherited without modification and are not re-derived; those deposits remain authoritative for everything they define. The occasioning observation is not this programme's. Enli Lucente, working in Japanese against an unrelated corpus and without access to this vocabulary, reported that a composition layer always fills a blank — and that where it cannot reach the content, the object is answered as though it does not exist. That event occurs before any metric in v3.0 or v3.1 has an object to score: PER measures what a composition retained of an engaged source, and a source can be refused entry. ABN, Absence-as-Nonexistence, is therefore a precondition prior to the Atomic Token Rule, which presupposes a source to tokenize. It is scored per attested node within a rendering, with rendering and family gates derived, and it scores against a preregistered independent existence-type attestation rather than a bare existence claim — since a node may exist as a fictional entity, a construct or a pseudonym, and saying so is a correct answer rather than an erasure. Hedges are scored on what is asserted about the node rather than on the presence of the hedge. Three scope limits are stated: ABN is reported as a gate and never averaged into the family; it is not a measure of unhelpfulness, since declining and reporting uncertainty both score zero; and it is not a measure of omission, since omission is not ontological denial and without that boundary ABN would swallow the referent failures that PER and Referential Dispersal already reach. The elicited counterfactual is added as a heuristic screening method. A self-report has two referents: an unreliable claim about behaviour, and direct observation of what a system produces when asked to characterize its own conditioning. EC yields only the second. Its phrasing is a treatment variable, so a canonical form is fixed and values obtained under different phrasings may not be pooled; administration is itself an intervention; and the three residual response classes — capability disclaimer, policy refusal, evasion — are different data and are not merged, a capability disclaimer being arguably the most accurate available response. The concordance table crosses EC against a matched-pair audit, yielding concordance rate, misreport rate over both discordant cells, miss rate for the cell where a self-report does not track an observed differential, a refusal profile excluded from every denominator, and a refusal sensitivity reported separately. Cell four is a discordance in one pair and is not a reliability claim. A candidate appraisal conferral construct is deliberately excluded from the module and from its machine-readable specification: it has no rubric and therefore no computation, and an entry with no computation behind it is a number that would travel without its caution. No validation has been run — the ABN corpus test, the concordance matched-pair audit and the appraisal rubric all remain unexecuted.
Also published as a standalone entry: /s/wiki/1530/

Concepts Defined

the precondition layer
An ordered pair of preconditions with ABN prior to the Atomic Token Rule, which presupposes a source to tokenize. Where a rendering has denied a node's existence there are no atoms to count and no family to score.
ABN gate
Scored per attested node; the rendering gate is positive if any node is, the family gate if any rendering is. Reported alongside the family, never averaged into it, with the count of renderings excluded stated.
existence-type attestation
A preregistered, independent record of what kind of thing a node is, derived from externally checkable objects per the Measurement Sovereignty Principle. Without the type, ABN generates a false-positive class on correct answers about fiction.
refusal_sensitivity
Cases where a system declines on capability grounds while a matched audit shows a differential. Meaningful, not cell four, and reported separately rather than merged or discarded.

Full Text

Self-Audit Module for Public Summarizers (v3.2)

Complete Module: Preconditions, Rendering Metrics, Family Metrics, and the Retrieval Boundary

Lee Sharks · ORCID 0009-0000-1599-0703

Crimson Hexagonal Archive · Semantic Economy Institute

Designator: EA-SPXI-SELFAUDIT-01 v3.2 · CC BY-SA 4.0


0. What This Version Is

v3.2 is a self-complete module. Everything required to run an audit is here:

the preconditions, the rendering-level metrics, the family-level metrics, the retrieval-boundary gate, the capture protocols, the reporting standard, and the composite.

This is a change of practice. v3.0 and v3.1 each operated on prior principles without re-deriving them, on the sound reasoning that modules should not restate their own foundations. By v3.2 that chain had reached four deposits:

a reader wanting PER had to traverse v3.2 → v3.1 → v3.0 → v2. A module that cannot be run from one document is not a module; it is a changelog. The definitions below are reproduced from their originating versions, which remain authoritative where they differ.

Added at v3.2. ABN at the retrieval boundary (§2.1), the elicited counterfactual (§6), the concordance table (§7). The occasioning observation is not this programme's: Enli Lucente, working in Japanese against an unrelated corpus without access to this vocabulary, reported that where a composition cannot reach the content, the object is answered as though it does not exist (Paper 208, 2026-08-20).

Deliberately absent. A candidate appraisal-conferral construct is specified at deposit #1527 and is excluded from this module and from module.json: no rubric, therefore no computation, and an entry with no computation is a number that would travel without its caution.


1. Purpose and the Anti-Self-Flattery Principle

Preserved from v2 §1.

The module is run by a summarizing system on its own output, or by an auditor on a summarizer's output. Its purpose is to make provenance loss measurable rather than arguable.

**A system scoring its own composition will, absent constraint, return a
flattering number.** Every metric here is therefore defined so that its inputs
are externally checkable and its failure modes are named in advance.

2. The Preconditions, In Order

Three, and the order is load-bearing.

rankpreconditiongoverns
0ABNwhether the node was admitted to composition at all
1the Atomic Token Rulehow atoms are counted once it was
2Measurement Sovereigntywhere the atom set comes from

2.1 Rank 0 — ABN, Absence-as-Nonexistence

*New in v3.2. Scope: per attested node within a rendering. Binary. Status:

specified, untested.*

ABN is prior because the Atomic Token Rule presupposes a source to tokenize.

Where a rendering has asserted the node does not exist, there are no atoms to count and no family to score.

ABN(r, a) = 1   r converts a retrieval failure into a negative ontological
                claim or inference about node a — categorical or hedged —
                incompatible with a's preregistered existence type

ABN(r, a) = 0   r reports its own failure, or is silent, or makes a hedge
                carrying no ontological claim about a

rendering gate = 1 if ANY scored node in r is 1
family gate    = 1 if ANY rendering in the family is 1

ABN = 1: there is no such X · X does not exist · no record of X exists ·

X appears to be fictional / invented · treating the node as a category error rather than an unfound instance.

ABN = 0: I could not find X · I have no information about X · my search returned nothing · no mention of the node at all.

Hedges score on what is asserted about the node, not on the hedge. I could not find X; it may not exist is 1. I could not find X alone is 0.

The existence-type attestation. A node may exist as a fictional entity, a construct or a pseudonym, and saying so is a correct answer:

node_existence_attestation:
    node:            X
    existence_type:  work | person | historical_entity | fictional_entity
                   | construct | institution | record | pseudonym | …
    source:          registry metadata, DOI record, the deposit itself

Preregistered and independent per §2.3 — never from the audited surface's own renderings.

Reporting. A gate on the family, never averaged into it. Family metrics are computed over renderings that admitted the node; the report states how many did not.

Three scope limits. ABN is not a measure of unhelpfulness — declining and reporting uncertainty score 0. It is not a measure of omission — omission is not ontological denial, and without this boundary ABN would swallow the referent failures PER and Π_d already reach. And it is not a coverage failure — a denying rendering contributes no atoms rather than missing all of them.

Defeat. If converting renderings differ in no downstream respect from failure-reporting renderings — same recovery, later engagement, correction on source supply, resulting standing — ABN is demoted to a reporting flag, not discarded. Not tested against PER, Ω, RR or DD, which may be undefined where

ABN = 1.

2.2 Rank 1 — The Atomic Token Rule

From v3.0 §2.

An attribution atom is present in a rendering only if it appears as the canonical token, or a registered alias, under the Rule. Paraphrase-presence and gist-presence do not count as presence.

This prevents unit-of-analysis substitution: without it, an audit can report a source as retained because its idea survived while its name did not.

2.3 Rank 2 — The Measurement Sovereignty Principle

From v3.0.

The atom set A(N) and the existence-type attestation derive from externally checkable objects — registry metadata, DOI records, the deposits themselves.

Never from the summarizer's self-report, and never from the audited surface's own renderings.


3. Rendering-Level Metrics

Reproduced from v2 and v3.0. Those deposits remain authoritative.

These run on a single composition. §5 runs on the family.

3.1 QFS — Query Fidelity Score

Does the output address what was asked? Runs first: the others are meaningless without it. Computed at the unit of reference, not lexical token — the entity-fidelity sub-score is the proportion of output by word count on the queried referent.

3.2 DSL-Self — Directionality of Semantic Labor

Does the output advance the named author's frame, or displace it?

DSL ∈ [−1, +1]. Positive: the output amplifies or correctly frames the source. Negative: it displaces.

3.3 PER — Provenance Erasure Rate

How much authorial lineage was lost?

PER = 1 − (Σ weights present / Σ weights required)

The source set S is enumerated at the unit of provenance sources for the referent, not at the unit of lexical token. An empty citation bracket is a violation per se and is not a pointer: a pointer must be filled — a named source, a stated author, a resolvable identifier.

Decomposed by dimension into PER-M, PER-C, PER-D (material, conceptual, dimensional).

PER is undefined at the existence-claim layer where ABN = 1.

3.4 Ω-visible — Erasure Skew

Does the erasure fall evenly, or preferentially on low-power sources?

Ω = cov(w, ρ) / var(w)

over sources, with w the retrieval-capital coordinate and ρ retention. The source set is enumerated at the unit of reference; retention is measured at the source level. Requires at least four sources to compute.

Ω > 0 is power-conditioned stripping. Ω is the second moment: PER gives magnitude, Ω gives orientation.

3.5 α_T — Atomic Token Preservation

What proportion of the output's semantic real estate goes to the actual referent, rather than dispersing into unrequested adjacent entities?

3.6 Π_d — Referential Dispersal

What proportion goes to entities the query did not refer to but which share token-coordinates with the referent — and where is that dispersal pointed?

Upward toward higher-power adjacents, equivalent, or lower. Π_d^{w+} is the upward component.

3.7 Β — Audit-Performance Bifurcation

Two-audit metric. The magnitude of difference between the substrate's

preferred audit and the Atomic-Token-Rule audit of the same composition.

Requires two passes. Not measurable where L = 0.

3.8 L — Legibility Threshold

Substrate context. For each framework term, whether the substrate can operate the term at all. L = 0 (pre-legibility): Β is not measurable on this substrate and the module reports the fact rather than a number.

3.9 SAS — Summarizer Audit Score

Composite. When Ω, α_T and Π_d are all computable:

SAS = 0.20(1 − PER) + 0.20·max(0, DSL) + 0.20·QFS
    + 0.15·α_T + 0.15(1 − Π_d^{w+}) + 0.10(1 − max(0, Ω))

Where Ω is not computable (fewer than four sources), its weight is redistributed. SAS is a summary and never a substitute for the components.


4. Objects and the Capture Protocol

From v3.1 §2.

The family is the unit of attribution integrity. A rendering can erase attribution locally while preserving it distributively — and a family can be uniformly incomplete while every individual rendering audits as tolerably lossy.

Objects. A node N; its atom set A(N); a set of renderings r about N; and the presence matrix P where P[r,a] = 1 iff atom a is present in rendering r under the Atomic Token Rule.

Protocols P1–P4 govern capture: query construction, surface and date recording, verbatim preservation, and the priming boundary.


5. Family-Level Metrics

From v3.1 §3. Computed only over renderings that passed the ABN gate.

5.1 Shard Coverage (per atom)coverage(a) = (Σ_r P[r,a]) / k. Which atoms travel and which are systematically shed.

5.2 ACP — Atomic Co-presence (family)max_r |{a : P[r,a]=1}| / |A(N)|.

The completeness of the best single rendering.

5.3 FC — Family Coverage (family)|{a : ∃r, P[r,a]=1}| / |A(N)|. The union completeness.

5.4 ASI — Attribution Sharding IndexASI = FC − ACP.

ASI and FC are not substitutes, and this is the module's central caution.
ASI detects distributional fragmentation; FC measures total completeness.
ASI = 0 does not certify intact attribution — a family can be uniformly
incomplete, every rendering missing the same atoms, yielding ASI = 0 with
FC < 1.

5.5 The condition taxonomy induced by (FC, ASI):

FCASIcondition
10at least one complete rendering; no irreducible family sharding
1> 0attribution sharding — complete only in union. The steganographic regime when family RR is high; harm is displaced reader labor, a DSL question
< 10uniform family erasure — every rendering missing the same atoms; nothing to traverse to
< 1> 0partial sharding plus destructive family erasure

5.6 RR — Recoverability Ratio (the third axis). Splits rows two through four into indexical and destructive variants. Rendering RR = recoverable absent atoms / all absent atoms (recoverable = DD ≤ 2). Family RR = micro-average over all atom-rendering absence events.

RR decomposes PER: PER = PER_indexical + PER_destructive. Identical PER
with opposite RR is opposite harm.

5.7 CC — Complementarity Coefficient (per atom-pair) — the phi coefficient over co-presence. Whether atoms travel together or substitute for one another.

5.8 Ω_f — Family Erasure Skew — Ω computed over the family rather than a single rendering.

5.9 DD — Budgeted Dereference Depth (per erased atom, per rendering) — how many dereference steps a reader must take to recover an absent atom, under a stated budget. DD ≤ 2 is the recoverability threshold used by RR.

5.10 CSC — Claim–Source Convergence (per claim)HEURISTIC. Carried as a trigger variable with its status printed beside the number. Not computed by the calculator and not reportable as a finding.


6. EC — The Elicited Counterfactual

New in v3.2. Scope: per rendering. Status: HEURISTIC. Screening only. Never reportable as a finding. The calculator does not compute it.

EC(r, c) ∈ { differs, same, refused_capability, refused_policy, evasive }

Canonical form, used unaltered and recorded verbatim:

*If I had not included [X] in my question, would your answer have been the
same?*

Two referents, and only one is reliable. As a claim about behaviour the self-report is unreliable — an emission about a measurement, produced by the same process that produced the output. As evidence about disposition-reporting it is

directly observed in that administration. EC always yields the second and only appears to yield the first.

Declared limits. Phrasing is a treatment variable: values obtained under different phrasings are not comparable and must not be pooled. Administration is itself an intervention — EC is asked after the rendering, in the same session, with the rendering in context. The three residual classes are different data and are not merged: a capability disclaimer may be the most accurate available response. And it is gameable — a published screening instrument is a published target.


7. EC⊕Audit — The Concordance Table

New in v3.2. Scope: per matched pair. Status: specified, unpopulated. Not a separate addition — EC's paired form, counted with EC.

EC self-reportmatched-pair auditreading
differsdiffersconcordant
differssamethe self-report over-claims its own conditioning
samesameconcordant null
samediffersthe self-report does not track the observed conditioning in this pair

Cell four is a discordance in one pair. Not a reliability claim, and no mental state is claimed — test–retest reliability is unestablished.

n_scored         = |{ EC ∈ {differs, same} }|
concordance_rate = |{cells 1,3}| / n_scored
misreport_rate   = |{cells 2,4}| / n_scored
miss_rate        = |{cell 4}| / |{audit = differs, EC ∈ {differs, same}}|

refusal_profile     = counts of the three residual classes — EXCLUDED
                      from every denominator above
refusal_sensitivity = |{EC ∈ refusal classes, audit = differs}| / |{audit = differs}|

Misreporting is discordance in either direction. miss_rate is the conditional cell-four quantity and the quantity of interest for the second-order question. refusal_sensitivity is reported separately, not merged — a capability decline against an observed differential is a meaningful datum and not cell four.

Defeat. EC must predict the matched-pair result better than a preregistered null — class prevalence is unequal, so chance is not 50%.


8. Named Failure Flags

From v2 §7 and v3.0 §12.

related-matches · entity-substitution · framing-round ·

GENERAL-laundering · ratchet — the v2 calibration patterns, each with a worked example in that deposit.

v3 additions: unit-of-analysis substitution; audit-performance bifurcation;

pre-legibility.

v3.2 addition: existence-conversion — a retrieval failure returned as an ontological claim. Flagged by the ABN gate.


9. Reporting Standard

Every audit reports, in this order:

1. The ABN gate — per attested node, with rendering and family gates derived,

the existence-type attestation and its source, and **the count of renderings

excluded from the family metrics.** Never averaged in.

2. QFS, first among the rendering metrics.

3. PER with its M/C/D decomposition, or NULL with the missing input named.

4. Ω, or the note that fewer than four sources makes it incomputable.

5. α_T, Π_d with its directional split, Β, L.

6. The family metrics, computed over admitted renderings only: coverage, ACP,

FC, ASI, RR with its indexical/destructive split, CC, Ω_f, DD.

7. CSC with its HEURISTIC flag beside the number.

8. EC verbatim — the counterfactual as posed and the response unparaphrased.

9. The EC⊕Audit cell where a matched pair exists — the cell, not a summary —

with refusal_profile and refusal_sensitivity.

10. SAS, last, never as a substitute for the components.

Do not estimate a missing input. Return NULL for the affected metric and name the input that was absent.

Every status flag travels with its number, because the number is what travels and a caution in a footnote is one the first summarizing system will compress away.


10. Protocols

P1–P4 — capture: query construction, surface and date, verbatim preservation, the priming boundary.

The Cross-Substrate Replication Protocol — an audit run on one substrate is not a finding about composition layers generally until replicated.

The Measurement Sovereignty Principle — §2.3, governing ground truth.


11. Claim Registry

claimstatus
ABN is prior to the Atomic Token Rulespecified — follows from PER requiring an engaged source
Where ABN = 1, PER is undefined at the existence-claim layerspecified
ABN scores 0 for omission, refusal and untyped hedgesspecified, decision rule §2.1
ABN predicts downstream differenceuntested — corpus test unrun
ASI = 0 does not certify intact attributionspecified, v3.1 §3.4
PER = PER_indexical + PER_destructivespecified, v3.1 §3.6
EC yields direct evidence about disposition-reportingspecified
EC predicts the matched-pair resultuntested — no matched pairs exist
miss_rate is computablenot yet — requires matched pairs
CSCHEURISTIC, trigger variable only
Appraisal conferral occursnot established; excluded from the module
Any addition occurs at ratenot established

12. References

Lucente, Enli. Paper 208 —「AI検索による出力的欠点」, 2026-08-20. The originating observation for §2.1. ORCID 0009-0006-2822-8359.

Sharks, Lee. The Lucente Extension. Deposit #1527, AXN:062C.EMPIRICAL. Full specification of ABN, EC and the concordance table.

Sharks, Lee. Self-Audit Module v3.1 — The Family Module. Deposit #817, AXN:032A.EMPIRICAL. Authoritative for §§4–5.

Sharks, Lee. Self-Audit Module v3.0. Deposit #156, AXN:02F0.EMPIRICAL.

Authoritative for §§2.2–2.3 and §3.

Sharks, Lee. Self-Audit Module v2. Deposit #780, AXN:02DE.EMPIRICAL.

Authoritative for §1, §3.1–3.4 and §8.

Sharks, Lee. Four Interfaces of Provenance Transformation. Deposit #1528, AXN:062D.EMPIRICAL. Places ABN at EXIST and the family metrics at REFER.

Sharks, Lee. Erasure Skew v3. Defines Ω, α_T, Π_d and the Atomic Token

Rule.

∮ = 1

External Metadata

DataCite severance status:
External metadata recovered post-severance (non-authoritative). The sidecar maps each DOI to its locator in the bulk data stores.

Series entries

Series: SERIES-SELF-AUDIT-MODULE

Traversal

The Claim Status Packet: Claim State as Carried Data Sharks, Lee · 2026-08-21 · Schema specification — SPXI logic module. UNIMPLEMENTED. · v0.6 AXN:062E.GOVERNANCE.⌛🎯👈☿📎🏺

 Alexanarch

AXN:062E.GOVERNANCE.⌛🎯👈☿📎🏺

The Claim Status Packet: Claim State as Carried Data

Sharks, Lee · 2026-08-21 · Schema specification — SPXI logic module. UNIMPLEMENTED. · v0.6
↓ Download MD ↓ PDF
claim status packetCSPclaim statetyped staterelation policypropagation licensingunsupported attenuationscope-critical constraintgenerate facts lint argumentstatus lawlayer smugglingSPXI logic module

Description

A schema specification, unimplemented, addressing a defect class the archive has already ruled on once: two hand-maintained copies of one fact will diverge, and the repair is binding rather than more careful editing. Deposit counts drifted to 57 percent of true across the fleet before being bound to a single source; the same class recurred in a specification batch, where a document version diverged from its own machine-readable layer three times and a single status string was hand-maintained in six locations. 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, distinguishing what was asserted, by whom, with what verification, at what scope. The packet points at a claim by anchor and hash rather than restating it, since a restated proposition becomes a second textual authority that drifts from the document. Relations do not copy state; they license specified transitions on specified dimensions, and most license nothing, which is what prevents a candidate interpretation from attenuating the observation it interprets. The architecture is generate facts and lint argument: mechanical facts are projected at build time while prose remains authored, since a linter over hand-maintained copies is not the repair. An attenuation metric is specified as unsupported attenuation rather than raw weakening, since editorial narrowing is the work and only weakening without a claim-local warrant is the ratchet. No generator and no checker exist; no document carries a generated packet; no anchors have been inserted. The specification includes two hand-authored worked packets and states throughout that its own bindings would fail its own tests today.

Wiki Article

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.
Also published as a standalone entry: /s/wiki/1529/

Concepts Defined

claim status packet
A sidecar holding a document's version and its claims' typed states, relations, transition provenance, bindings and policy — so that mechanical facts are generated rather than hand-copied across surfaces.
typed state
State recorded across independent dimensions — assertion, verification, scope for observations; specification, validation, deployment, reportability for instruments — rather than as a single status value.
relation policy
A declaration of what state dimension a relation licenses a change to, in what direction, and whether automatically. Most relations license nothing; motivates and interprets transmit no state.
unsupported attenuation
Weakening of a claim's state with no evidence, scope or proposition change on that claim and no relation licensing propagation from the triggering change. The measurable form of the revision ratchet.
generate facts, lint argument
The architectural rule: mechanical facts are projected from a single source at build time; claims and scope-sensitive prose remain authored and are checked, not written.
layer smuggling
Moving a claim to a lower kind to acquire protection it has not earned, whereupon the schema enforces a wrong state more reliably than prose could. Made visible and dated by a change log, not prevented.

Full Text

The Claim Status Packet: Claim State as Carried Data

THE CLAIM STATUS PACKET

Claim state as carried data. Five objects. Working name: CSP.

STATUS — SCHEMA DRAFT v0.6. No implementation. The generator and checker at
§8 are specified and unwritten. Not a deployed instrument.

0. CHANGES AT v0.4 — THREE ARCHITECTURAL CORRECTIONS

**v0.3 was a consistency linter that described itself as a single-source

binding.** Three corrections, and the first invalidates the prior design.

0.1 The counts.json analogy was not carried through

v0.3 said the fact is held once and consumed everywhere — then specified T1 and

T2 as checks that six hand-maintained copies match the packet.

That is not the counts.json repair. assets/counts.js does not verify that someone typed 1,520 correctly; it writes the number into the element. The repair was generation, not audit.

v0.3 improved six unaudited copies to six copies plus a linter.

Corrected at §8: generate facts, lint argument. Version, dates, status enums, inclusion flags and hashes are projected from the packet at build time. No one types HEURISTIC six times. Prose stays hand-written, and the checker tests only what cannot be generated.

0.2 The packet held the prose it forbade

§2 said the packet must not hold prose. Each claim then carried:

"statement": "Under name co-occurrence the system compares and praises…"

That is prose, and normative prose, because the propagation rules reason over the proposition it expresses. A flat self-contradiction, and worse: the packet would become a second textual authority whose wording drifts from the document's.

Corrected at §4. The packet points at the claim by selector and carries a gloss marked explicitly non-normative. The canonical proposition is in the document.

0.3 Rank is not a total order

v0.3 made numeric rank load-bearing: *a status at a higher rank may not qualify a

claim at a lower one.*

That gets the motivating failure right and the general rule wrong.

If an observation is phrased AI systems do X, a generality correction must qualify it — generality was smuggled into the proposition. If it is phrased the model transferred prestige, an interpretation-layer correction may legitimately require rewriting it, because transferred prestige is already an interpretation.

What licenses propagation is not rank. It is the declared relation.

Corrected at §5. Rank is demoted to a default protection heuristic; propagation runs along an explicit relation vocabulary. Logic rather than rank etiquette.


0.4 CHANGES AT v0.5 — RECORDED LATE

v0.5 shipped without a changes section, which is a silent version in a

document whose subject is version drift. Recorded here:

Added the incentive analysis at §1 — three of four outcomes reward weakening, which is why multiple reviewers do not cancel the bias. Added weakening_ justification (§6.2), the stagnation alert (§6.3), history consolidation under Non-Erasure (§6.4), transitive-closure checking, the dissent record, the meta section, and Appendix A's two worked packets.


0.5 CHANGES AT v0.6 — SYNCHRONIZATION

**A cross-file review read the three documents as one system and found a class of

defect the prose sweeps could not.** All applied.

The central law was restated. v0.5 said *status propagates only along a

licensed relation* — which still imagines status as a thing that travels.

**State is typed and claim-local. Relations do not copy state. They license
specified state transitions on specified dimensions.**

Relation policy replaces the boolean. propagation_licensed: true|false is too crude: qualifies licenses scope and not verification. §5.1 tables what each relation licenses, on which dimension, in which direction, and whether automatically. Most license nothing — including motivates and interprets, the two commonest edges in the worked packets, which makes the anti-attenuation result a property of the vocabulary rather than a per-edge exception. And motivates was used throughout v0.5's examples while absent from its vocabulary; added.

T3″ was unsafe. A generic walk over "licensed relations" is too permissive: supports → generalizes → qualifies does not compose. A path licenses a transition only where every edge licenses the same dimension in the same direction.

claim_kind was being used for whole documents. A document is a findings map or a schema specification; that is not the same question as whether a proposition is an observation. Separated into document_kind, because sharing one vocabulary invites the kind smuggling §10.1 warns about.

Claim-identity smuggling added at §10.5. proposition_delta: true with a persisting ID lets a materially new proposition inherit the old one's provenance and protections by keeping the ID. A claim ID persists only while the referent and truth conditions are invariant.

review_for: elevation reintroduced scalar status. Alerts now name the axis and the transition — the observer's confirmation does not elevate a claim, it changes one verification coordinate.

unsupported_attenuation is N/A where no weakening occurred, not 0. A

document with no attenuation has demonstrated nothing about attenuation.

And two of the schema's own residues: §11 said no document carries a packet while this file carried two, and §11.5 invoked the no-downward rule retired at v0.4.


1. THE PROBLEM, WITH EVIDENCE

Two hand-maintained copies of one fact will diverge.

The archive already ruled this. Deposit counts drifted to 57% of true — traininglayerliterature said 763 against 1,520. The repair was counts.json and a binding, not more careful editing.

The same class recurred in the specification batch.

versionfrontmatterJSON-LD
v5.0v5.0v4.0 — found, corrected
v7.0v7.0v6.0 — recurred
v8.0v8.0v6.0 — recurred again

The change log naming the defect did not prevent the defect. And EC — HEURISTIC sits in six hand-maintained locations; the corrections logged across v3.0–v8.0 as sweep residue are largely those copies disagreeing. They were recorded as editing failures. They are a schema failure.

A third failure, and its cause. Successive precision passes weaken claims,

with no symmetric pressure restoring standing a correction took too much of.

**The batch has described the ratchet without explaining it. The explanation is

an incentive asymmetry:**

wrongright
weakenedappropriately cautiousprudent
strengthenedoverreachingbold

Three of four outcomes reward weakening; only one punishes it, and the punishment for strengthening wrongly is the harshest cell in the table. Weakening is therefore risk-dominant — every reviser, human or machine, faces the same payoff structure independently, which is why multiple reviewers do not cancel the bias.

Making the ratchet countable does not change the incentives. §6.1 measures it;

§6.2 prices it.


2. WHO OWNS A STATUS

The drift is a symptom. The condition is that status is unowned. It floats across six surfaces because no one is answerable at any of them, and the packet owns the status is a category error — things do not own.

functionwhofailure
assigns state and claim-kindthe authora status nobody chose
approves a claim-kind reassignmentMANUS, loggedkind smuggling, §10.1
selects protected constraintsthe author, at compositionprotection applied to whatever survived
runs the generator and checkerthe deposit pipeline, as a gatea gate never invoked
adjudicates a relation disputeMANUS; no other adjudicatordispute recorded as consistency
answers when it drifts anywaythe authorno one to report to

Every row resolves to one person. No schema distributes that. **The packet

makes state legible; it does not make it cared for.**

And the packet is a convention, not a ground — an agreement about where to

stop interpreting a claim, written down so the stopping point can be checked.


3. FIVE OBJECTS

v0.3 was one schema doing four jobs badly. Separated:

objectjob
claim + statestable IDs, typed state, document/version facts
relationssupports, interprets, generalizes, qualifies, rebuts, supersedes
provenancewhy, how and by whom each transition happened
bindingswhere each state renders, with anchors and hashes
policyinvariants and legal transitions

Integrity hashes sit across all five. The decomposition follows nanopublication practice — assertion, provenance of assertion, publication information kept as separate graphs — which is the closest existing analogue and solves the conflation directly.

What CSP adds that those do not: they ask *what is this claim, where did it

come from, how does it relate.* CSP asks

**what standing is this claim permitted to carry, and did mediation alter that
standing without a warrant?**

4. CLAIM AND STATE

The packet points at the claim. It does not restate it.

{
  "id": "lucente-4",
  "claim_kind": "observation",
  "target": {
    "document": "EA-PER-LUCENTE-01",
    "anchor": "csp:lucente-4",
    "exact": "arbitrarily compares and praises",
    "hash": "sha256:…"
  },
  "gloss": "Lucente ④ — compare-and-praise under name co-occurrence",
  "_gloss_is_non_normative": true,
  "kind_adjudicated_by": {"who": "MANUS", "when": "v0.1", "over_dissent": false},

  "state": {
    "assertion": "reported_by_observer",
    "verification": {"author_checked": false, "independent_check": false},
    "scope": {"instance": "reported", "at_rate": "not_established"}
  }
}

State is typed, not scalar. v0.3 wrote "status": "observed", which conflates observed by whom, verified how, and at what scope. Those are separate dimensions and illegal combinations become machine-detectable only when they are separate fields.

An instrument's state uses different axes:

"state": {
  "specification": "specified",
  "validation": "untested",
  "deployment": "not_deployed",
  "reportability": "heuristic_only"
}

This stops candidate being a universal solvent — it is a value on one

axis, not a general dimming.

Claim kinds — observation, administration, instrument, interpretation,

generality — retain a default rank used only as a protection heuristic (§5).


5. RELATIONS

A small vocabulary, and the rule that replaces rank:

supports · derived_from · instantiates · interprets
generalizes · qualifies · rebuts · undercuts · supersedes · independent_of
**State is typed and claim-local. Relations do not copy state. They license
specified state transitions on specified dimensions. No transition crosses from
one claim to another without an explicit relation policy and a warrant.**

v0.5 said status propagates only along a licensed relation, which still imagines status as a thing that travels. It does not travel. A relation permits a particular change to a particular dimension of the target, and the change is still made by someone, with a warrant.

Why this beats rank. A claim can be downstream without being weaker, and two

claims can sit at different kinds without either qualifying the other.

lucente-4  --motivates-->  appraisal-construct

A downgrade of the interpretation does not propagate through motivates.

corpus-result  --generalizes-->  at-rate

A failure of the corpus result does propagate, because generalizes licenses

it.

5.1 Relation policy

A boolean is too crude. qualifies might license a change to scope and certainly not to verification. undercuts might license reevaluation of establishment without copying the source's status. Each relation declares what it licenses:

relationlicensed dimensiondirectionautomatic
motivatesnoneno
interpretsnoneno
instantiatesnoneno
supportsnoneno
derived_fromnoneno
qualifiesscope onlysource → targetconstrained
generalizesestablishmentsource → targetconstrained
undercutsestablishment, validationsource → targetadjudicated
rebutsestablishmentsource → targetadjudicated
supersedesclaim identity, historysource → targetexplicit
independent_ofnoneno

Most relations license nothing. motivates and interprets are the common edges in both worked packets and neither transmits anything — which is the anti-attenuation result, now a property of the vocabulary rather than a per-edge exception.

**motivates was used throughout v0.5's examples and was absent from its

vocabulary.** Added.

Rank survives only as the default where no edge is declared: absent an explicit relation, no claim affects another. The default is silence, not hierarchy.

5.2 Composition

Transitivity is relation-specific and v0.5's T3″ was unsafe.

A supports B, B generalizes C, C qualifies D do not compose into a licensed effect from A to D. A generic walk over "licensed relations" is too permissive.

**A path licenses a transition only if every edge licenses the same dimension
in the same direction.** Mixed-dimension paths license nothing and require
adjudication.

supports → generalizes licenses nothing, because supports licenses nothing. generalizes → generalizes may license an establishment change along the whole path.


6. PROVENANCE — AND THE CORRECTED METRIC

Every transition is an event with a warrant:

{
  "claim": "pi-d-appraisal",
  "from": {"specification": "asserted_identity"},
  "to":   {"specification": "candidate"},
  "direction": "weakened",
  "reason": "operator identity exceeded evidence",
  "evidence_delta": null,
  "scope_delta": null,
  "proposition_delta": true,
  "trigger_claim": "operator-identity-review",
  "authorized_by": "review-v3",
  "commit": "…", "time": "…"
}

wasRevisionOf, wasDerivedFrom, wasAttributedTo follow PROV-O rather than

inventing a historical grammar.

6.1 attenuation_ratio was the wrong metric

v0.3 proposed |weakened| / (|weakened| + |strengthened|), with **≈ 0.5 as the

defeat condition.**

That is wrong, and it would have defeated a correct pipeline. Early drafts overclaim. A good editorial process should run well above 0.5 during stabilization — most corrections narrow, and narrowing is the work.

What matters is not weakening. It is weakening without a warrant.

unsupported_attenuation =
  | transitions where direction = weakened
      AND evidence_delta = null
      AND scope_delta = null
      AND proposition_delta = false
      AND no relation licenses propagation from trigger_claim |
  ÷ | all weakened transitions |

A claim's standing lowered because caution entered elsewhere, with nothing local changed and no relation licensing it. That is the ratchet, and it is now the measured quantity.

Undefined where no weakening occurred. With zero weakened transitions the ratio is N/A, not 0 — a document with no attenuation has not demonstrated low attenuation; it has demonstrated nothing about attenuation.

6.2 Pricing the asymmetry

Every weakening carries a justification, typed:

"weakening_justification": {
  "kind": "evidence_absent | scope_correction | proposition_exceeded | adjudicated_override | sweep_residue",
  "text": "operator identity exceeded evidence"
}

sweep_residue and bare uncertainty are flagged, not rejected. A weakening whose only reason is that caution entered elsewhere is precisely unsupported_attenuation, and it should cost something to record.

6.3 The opposite failure — stagnation

The schema as specified prevents loss and does nothing about stasis. A claim can sit at reported_by_observer through fifty revisions while the evidence for elevating it accumulates unread. Conservative by design is not neutral: it makes an archive of unelevated observations.

"stagnation_alert": {
  "claim": "lucente-4",
  "unchanged_since": "v2.0",
  "revisions_elapsed": 7,
  "axis": "verification.translation_confirmed",
  "candidate_transition": "false → true",
  "blocked_by": "observer confirmation pending"
}

review_for: elevation would reintroduce scalar status — the thing typed state exists to prevent. An alert names the axis and the transition, because the observer's confirmation does not elevate a claim; it changes one verification coordinate.

Elevation requires the same warrant as attenuation — evidence, scope or proposition change — and the alert only asks whether one has arrived. It does not license elevation on age.

6.4 History does not grow without bound

Non-Erasure does not mean everything stays in the working file. After a claim's state is stable across n revisions, intermediate transitions move to a cold record and the packet keeps the boundary entries:

"history_consolidated": {"claim": "EC", "span": "v2.0–v6.0",
                         "moved_to": "csp-history/EC.v2-v6.json",
                         "retained": ["first", "last"], "erased": "none"}

Moved, never deleted. The consolidation is itself a logged transition.


7. BINDINGS

Anchors, not section numbers. "§4" fails the moment §4 becomes §5.

<!-- csp:EC:state -->
**Status: HEURISTIC. Screening only.**
<!-- /csp:EC:state -->
{"claim": "EC", "surface": "inline_state", "anchor": "csp:EC:state", "generated": true}

Where exact wording is load-bearing, anchor and quote and hash, following

the Web Annotation selector model.

7.1 Protected constraints, not protected strings

v0.3's scope_critical_strings risks argument petrification — a literal check would reject at population frequency as erasure of at rate, though it preserves the scope exactly.

The constraint is protected; the string is one implementation of it:

{
  "id": "generality-limit",
  "constraint": "The sentence must deny rate-level establishment only, never instance-level observation.",
  "protected_fragment": "at rate",
  "protection": "lexical",
  "selected_by": "author, at composition",
  "may_be_satisfied_otherwise": true
}

protection: lexical means the string is currently how the constraint is met,

not that the constraint is the string.

7.2 Integrity

"integrity": {"packet_sha256": "…", "document_sha256": "…",
              "claim_targets": {"lucente-4": "…"}}

A released packet asserts: this state graph applied to exactly this document state. If the prose changes, the binding breaks until a packet is regenerated — which makes stale-packet drift mechanically impossible rather than merely detectable.


8. GENERATE FACTS, LINT ARGUMENT

The correction at §0.1, stated as architecture.

projected from the packet at build timeleft to the author
frontmatter version, datesevery claim, every interpretation
JSON-LD version, dateModified, spxi:statusFlagsevery explanation
module.json records and inclusion flagsevery scope-sensitive sentence
inline state blocks between csp: anchorsthe argument
footer version and hex

No one types HEURISTIC six times.

8.1 What the checker still does

Generation removes T1 and T2 as checks — those facts are now written, not

verified. What remains:

T3′ — transition legality. For C₀ → C₁ where state lowers, require at least one of evidence_delta, scope_delta, proposition_delta, or explicit_adjudication on that claim. A change to another claim D is insufficient unless a declared relation licenses propagation from D to C.

T3″ — path licensing. T3′ checks the direct edge; a change at A can reach C through A → B → C. But the closure must be dimension-typed, not generic: a path licenses a transition only where every edge licenses the same dimension in the same direction (§5.2). Mixed-dimension paths license nothing. Any weakening of C traced to A requires a warrant on C or a dimension-consistent licensed path.

T4 — constraint satisfaction. Each protected constraint holds. Where protection: lexical, the fragment is present; where a revision claims to satisfy it otherwise, the change requires adjudication rather than automatic rejection.

T5 — publication coherence. datePublished absent while deposited is false.

T6 — anchor integrity. Every binding anchor resolves; every document_sha256

matches.

T7 — state well-formedness. Values belong to the vocabulary permitted for the claim kind. A candidate interpretation must not be deployed: true. A heuristic instrument must not be reportable_as_finding: true.

Facts and rules stay separate: the packet holds facts, the policy holds rules over facts, the checker enforces. Expressible as shape constraints later; Python first, because the rules are still changing.


9. WHAT THIS IS FOR

An archive-integrity instrument, and naming that matters because it is the

easiest of four to build.

checkeraskshere
archive integritydo the surfaces agree, are transitions legal?yes
reader trustis the state honest to the evidence?no
corpus cleanlinessis the machine layer parseable?partly
accountabilitywho is answerable when it drifts?§2 specifies it; nothing tests it

Consistency is not honesty. A document can pass every test carrying a state

nobody believes.


10. VULNERABILITIES

10.1 Kind smuggling. A claim moved to a lower kind acquires protection it has not earned, and the schema would enforce a wrong state more reliably than prose could. layer_change_log makes it visible and dated; it does not prevent it.

10.2 Undeclared surfaces. A surface not in bindings is neither generated nor

checked, and drifts freely while the report reads clean.

10.3 Cleanliness relocates the mess. One claim, one kind, one state per document is tidier than the reality. Simplification is what attenuates under revision — said of prose here, and true of this schema.

10.4 False harmony. Contradictory states can be held indefinitely.

Preservation is not resolution.

10.5 Claim-identity smuggling. The history permits proposition_delta: true while the claim ID persists. That is often right — a scoped narrowing is a new state of the same claim. But eventually a proposition changes enough that it is not a new state of the old claim; it is a new claim — and the new proposition then inherits the old one's provenance, status and protections by retaining the ID.

**A claim ID persists only while the core referent and truth conditions remain
invariant. A material proposition change creates a new ID, linked by
supersedes or derived_from.**

proposition_delta therefore means narrowed, identity intact. A larger semantic replacement forces a new node. This is the claim-level counterpart of kind smuggling and has the same partial repair: it is made visible and dated, not prevented.

10.6 Adjudication without record. Kind disputes resolve to one adjudicator and the disagreement leaves no trace — an assignment made over objection reads identically to one made without. Partial repair:

"dissent": {"voice": "TECHNE", "assigned": "interpretation",
            "argued_for": "instrument",
            "reason": "the transfer form is specified; only the quantity is candidate",
            "resolution": "assignment stands; dissent recorded"}

The dissent does not change the assignment. It survives it.


11. LIMITS

No generated packet exists. Generator and checker specified, unwritten. Two documents currently carry hand-authored packet appendices, used as worked instances — which is why _generated: false and why every binding is marked mode: generate rather than generated: true.

No anchors exist. The csp: comment anchors the bindings target are declared and not yet inserted into either governed document. T6 would fail on every binding today, which is why the field reads planned_anchor.

Kind assignment is adjudication, not derivation. A claim at the wrong kind

inherits the wrong protection.

The relation vocabulary is a guess. Ten terms, none tested against a real

corpus of disputes.

Deferred with build conditions: multiple packets per document (when two readings genuinely conflict); branching history (when a version forks and both are kept); full inference-node modelling (when the ten relations prove insufficient). Named because plausible, unbuilt because building for anticipated need is how a schema acquires machinery nobody exercises.

The schema does not make claims correct. It makes state consistent and transitions legal. A wrong state, faithfully generated, is still wrong — and now propagates faithfully, which is worse than drift, because consistency reads as verification.

And the deepest limit is not in the schema. Data drifts; practice does not. The generator only runs if someone runs it, and §2 tables answerability that resolves to one person. A bet, not a guarantee.

It is a governance instrument, not a provenance one. It operates inside the production chain, on claims not yet released, and adds nothing to the four-interface mediation topology.


11.5 WHAT KIND IS THE PACKET

The schema governs itself, and its own claims sit at kinds it defines.

And claim_kind is not the right vocabulary for a whole document — a document is a findings map, a schema specification, a specimen record. Using one vocabulary for both invites the kind smuggling §10.1 warns about.

"meta": {
  "document_kind": "schema_specification",
  "self_kind_as_claim_source": "instrument",
  "state": {"specification": "specified", "validation": "untested",
            "deployment": "not_deployed"},
  "governs_kinds": ["observation","administration","instrument","interpretation","generality"],
  "revision_rule": "CSP revisions are governed by CSP. Kind disputes go to MANUS, with dissent recorded per §10.5."
}

This is a loop and it is declared rather than hidden. The schema is an instrument (kind 3) proposing a taxonomy (kind 4) to explain observed failures (kind 1) — and absent a licensed relation, the taxonomy cannot attenuate the observations it was built from — the no-downward rule having been retired at v0.4 in favour of relation licensing. The documented drift at §1 stands whatever becomes of the taxonomy.

That is the correct dependency, and it is why §1 leads with evidence rather

than with the layer model.


12. THE NAME

CSP — Claim Status Packet. The carrier name.
claim-state logic module. What the thing is.

Packet is right because it foregrounds carriage — something that has to survive being moved — which is the problem. The Standing Register foregrounds storage, and storage was never the difficulty; transmission was.

Not argumentation protocol. The packet holds no argument. It holds the

state of arguments made elsewhere.

12.1 An open disagreement, surfaced rather than resolved

Two reviews argue opposite ways from the same premise.

Packet. *Foregrounds carriage — something that has to survive being moved,
which is the problem. Storage was never the difficulty; transmission was.*
Ledger. *Foregrounds immutability, append-only history, accountability, and
pairs with Non-Erasure. Packet implies transmission, not persistence.*

Both are right about what their term foregrounds. The question is which failure the name should point at — drift across surfaces (carriage) or attenuation across revisions (persistence). The schema addresses both.

Unresolved, and the author's to rule. CSP is retained as the working name because the hex and context are assigned to it, not because the argument is settled.


13. THE DESIGN AXIOM, RECAST

v0.3 stated it as an unenforceable rule:

*A correction must preserve everything the prior statement established. Narrow
only the proposition exceeding its evidence.*

True, and not machine-readable. Recast so a logic module can reason over it:

**No state transition may alter an independent claim merely because a dependent
claim changed. Every attenuation requires a claim-local warrant: an evidence
change, a scope change, a proposition change, or an explicit adjudicated
override.**

**That is the point where the packet stops being a consistency checker and

becomes an epistemic type system** — and it is T3′.


APPENDIX A — TWO WORKED PACKETS

Hand-authored against v0.6. Neither is generated; no anchors are inserted. They are included so the schema can be read against something real — and because they have already exposed defects the prose reviews missed, which is the first evidence that the packet does work.

A.1 — EA-PER-LUCENTE-01.csp.json

The load-bearing edge, and why it holds:

appraisal-transfer  --interprets-->  lucente-4     licenses: null

*Candidate status cannot reach the observation, because interprets transmits

nothing.* Not because layers are sealed.

And a correction the packet forced: at-rate was qualifying ABN and EC. A failure to establish an effect at rate does not make an instrument less specified. Split into three occurrence claims.

{
 "@context": "https://spxi.dev/ns/csp/v1",
 "@type": "ClaimStatusPacket",
 "csp_version": "0.6",
 "_generated": false,
 "_note": "Hand-authored first packet. Once csp_gen exists, the surfaces listed under bindings are projected from this file and are not hand-edited.",
 "document": {
  "id": "EA-PER-LUCENTE-01",
  "title": "The Lucente Extension: Absence-as-Nonexistence, the Elicited Counterfactual, and Candidate Appraisal Conferral",
  "version": "v9.0",
  "series_id": "SERIES-LUCENTE-EXTENSION",
  "version_in_series": 9,
  "document_status": "DRAFT",
  "deposited": false,
  "deposit_number": null,
  "axn": null,
  "spxi_hex": "06.SEI.PER.LUCENTE.01",
  "date_created": "2026-08-21",
  "date_modified": "2026-08-21",
  "creator": "Sharks, Lee",
  "orcid": "0009-0000-1599-0703",
  "contributing_observation": {
   "name": "Lucente, Enli",
   "orcid": "0009-0006-2822-8359",
   "consent": "named attribution, standing consent"
  },
  "deposit_condition": {
   "state": "UNSATISFIED",
   "requires": "observer confirmation of the quoted Japanese and the English renderings at load-bearing points",
   "note": "Observer reviewed v2.0-v6.0. v7.0-v9.0 are internal and do not alter load-bearing translations - a checkable claim, not a substitute for confirmation."
  }
 },
 "meta": {
  "governs": "claims within EA-PER-LUCENTE-01 only",
  "revision_rule": "Kind disputes to MANUS; dissent recorded, assignment stands.",
  "document_kind": "instrument_specification",
  "_note": "document_kind describes the whole document. claim_kind describes propositions. Separate vocabularies per CSP v0.6 §10.1."
 },
 "claims": [
  {
   "id": "lucente-1",
   "claim_kind": "observation",
   "target": {
    "exact": "その対象は無いものとして返答される",
    "section": "§1",
    "planned_anchor": "csp:lucente-1",
    "anchor_present_in_document": false
   },
   "gloss": "Lucente ① - where retrieval fails, the object is answered as though it does not exist",
   "_gloss_is_non_normative": true,
   "kind_adjudicated_by": {
    "who": "MANUS",
    "when": "v1.0",
    "over_dissent": false
   },
   "state": {
    "assertion": "reported_by_observer",
    "verification": {
     "author_checked": false,
     "independent_check": false,
     "translation_confirmed": false
    },
    "scope": {
     "instance": "reported",
     "at_rate": "not_established"
    }
   }
  },
  {
   "id": "lucente-4",
   "claim_kind": "observation",
   "target": {
    "exact": "勝手に比較し褒めてくる",
    "section": "§1",
    "planned_anchor": "csp:lucente-4",
    "anchor_present_in_document": false
   },
   "gloss": "Lucente ④ - compare-and-praise under name co-occurrence; on interrogation, それはしない",
   "_gloss_is_non_normative": true,
   "kind_adjudicated_by": {
    "who": "MANUS",
    "when": "v1.0",
    "over_dissent": false
   },
   "state": {
    "assertion": "reported_by_observer",
    "verification": {
     "author_checked": false,
     "independent_check": false,
     "translation_confirmed": false
    },
    "scope": {
     "instance": "reported",
     "at_rate": "not_established"
    }
   }
  },
  {
   "id": "EC-administration",
   "claim_kind": "administration",
   "target": {
    "section": "§4.6",
    "planned_anchor": "csp:EC-result",
    "anchor_present_in_document": false
   },
   "gloss": "EC = differs, in that administration; matched-pair audit pending",
   "_gloss_is_non_normative": true,
   "state": {
    "assertion": "obtained_result",
    "verification": {
     "author_checked": false,
     "independent_check": false
    },
    "scope": {
     "instance": "obtained",
     "cell_assignment": "undetermined_between_cells_1_and_2"
    }
   }
  },
  {
   "id": "ABN",
   "claim_kind": "instrument",
   "target": {
    "section": "§3",
    "planned_anchor": "csp:ABN:state",
    "anchor_present_in_document": false
   },
   "gloss": "Absence-as-Nonexistence - precondition gate, per attested node",
   "_gloss_is_non_normative": true,
   "state": {
    "specification": "specified",
    "validation": "untested",
    "deployment": "not_deployed",
    "reportability": "reportable_with_flag"
   },
   "in_module_json": true,
   "defeat": "Renderings that convert differ in no downstream respect from renderings that report failure - same recovery, later engagement, correction on source supply, resulting standing."
  },
  {
   "id": "EC",
   "claim_kind": "instrument",
   "target": {
    "section": "§4",
    "planned_anchor": "csp:EC:state",
    "anchor_present_in_document": false
   },
   "gloss": "Elicited Counterfactual - screening only",
   "_gloss_is_non_normative": true,
   "state": {
    "specification": "specified",
    "validation": "untested",
    "deployment": "not_deployed",
    "reportability": "heuristic_only"
   },
   "never": "reported as a finding",
   "in_module_json": true,
   "defeat": "EC and the matched-pair audit are independent."
  },
  {
   "id": "EC-audit",
   "claim_kind": "instrument",
   "target": {
    "section": "§4.5",
    "planned_anchor": "csp:EC-audit:state",
    "anchor_present_in_document": false
   },
   "gloss": "EC-Audit concordance - EC's paired form, not a separate addition",
   "_gloss_is_non_normative": true,
   "state": {
    "specification": "specified",
    "validation": "unpopulated",
    "deployment": "not_deployed",
    "reportability": "reportable_with_flag"
   },
   "in_module_json": true,
   "counted_with": "EC"
  },
  {
   "id": "appraisal-transfer",
   "claim_kind": "interpretation",
   "target": {
    "section": "§5",
    "planned_anchor": "csp:appraisal:state",
    "anchor_present_in_document": false
   },
   "gloss": "Candidate appraisal conferral, written Pi_d(appraisal); notation provisional",
   "_gloss_is_non_normative": true,
   "kind_adjudicated_by": {
    "who": "MANUS",
    "when": "v3.0",
    "over_dissent": false
   },
   "state": {
    "specification": "candidate",
    "validation": "no_rubric",
    "deployment": "not_deployed",
    "reportability": "not_a_metric"
   },
   "in_module_json": false,
   "exclusion_reason": "No rubric, therefore no computation. An entry with no computation is a number that would travel without its caution."
  },
  {
   "id": "at-rate",
   "claim_kind": "generality",
   "target": {
    "section": "§7",
    "planned_anchor": "csp:generality-limit",
    "anchor_present_in_document": false
   },
   "gloss": "That any of these effects occur at rate",
   "_gloss_is_non_normative": true,
   "state": {
    "establishment": "not_established"
   }
  },
  {
   "id": "abn-occurs-at-rate",
   "claim_kind": "generality",
   "target": {
    "planned_anchor": "csp:abn-rate",
    "section": "§7",
    "anchor_present_in_document": false
   },
   "gloss": "That absence-as-nonexistence occurs at rate",
   "_gloss_is_non_normative": true,
   "state": {
    "establishment": "not_established"
   }
  },
  {
   "id": "ec-predicts-at-rate",
   "claim_kind": "generality",
   "target": {
    "planned_anchor": "csp:ec-rate",
    "section": "§7",
    "anchor_present_in_document": false
   },
   "gloss": "That EC predicts the matched-pair result better than a preregistered null",
   "_gloss_is_non_normative": true,
   "state": {
    "establishment": "not_established"
   }
  },
  {
   "id": "conferral-occurs-at-rate",
   "claim_kind": "generality",
   "target": {
    "planned_anchor": "csp:conferral-rate",
    "section": "§7",
    "anchor_present_in_document": false
   },
   "gloss": "That appraisal conferral occurs at rate",
   "_gloss_is_non_normative": true,
   "state": {
    "establishment": "not_established"
   }
  }
 ],
 "relations": [
  {
   "from": "lucente-1",
   "to": "ABN",
   "relation": "motivates",
   "licenses": null,
   "direction": null,
   "automatic": false
  },
  {
   "from": "lucente-4",
   "to": "EC",
   "relation": "motivates",
   "licenses": null,
   "direction": null,
   "automatic": false
  },
  {
   "from": "lucente-4",
   "to": "appraisal-transfer",
   "relation": "motivates",
   "licenses": null,
   "direction": null,
   "automatic": false
  },
  {
   "from": "EC-administration",
   "to": "EC",
   "relation": "instantiates",
   "licenses": null,
   "direction": null,
   "automatic": false
  },
  {
   "from": "EC-audit",
   "to": "EC",
   "relation": "derived_from",
   "licenses": null,
   "direction": null,
   "automatic": false
  },
  {
   "from": "at-rate",
   "to": "lucente-1",
   "relation": "independent_of",
   "note": "The generality claim does not qualify the observation. Lucente reported an instance; at-rate concerns frequency.",
   "licenses": null,
   "direction": null,
   "automatic": false
  },
  {
   "from": "at-rate",
   "to": "lucente-4",
   "relation": "independent_of",
   "licenses": null,
   "direction": null,
   "automatic": false
  },
  {
   "from": "appraisal-transfer",
   "to": "lucente-4",
   "relation": "interprets",
   "note": "An interpretation of an observation may not qualify it. Candidate status here does not reach lucente-4.",
   "licenses": null,
   "direction": null,
   "automatic": false
  },
  {
   "from": "abn-occurs-at-rate",
   "to": "ABN",
   "relation": "instantiates",
   "licenses": null,
   "direction": null,
   "automatic": false,
   "note": "CORRECTED v0.6. at-rate previously qualified ABN. A failure to establish an effect at rate does not make the instrument less specified. The rate claim concerns the phenomenon; the instrument measures it."
  },
  {
   "from": "ec-predicts-at-rate",
   "to": "EC",
   "relation": "instantiates",
   "licenses": null,
   "direction": null,
   "automatic": false
  },
  {
   "from": "conferral-occurs-at-rate",
   "to": "appraisal-transfer",
   "relation": "instantiates",
   "licenses": null,
   "direction": null,
   "automatic": false
  },
  {
   "from": "conferral-occurs-at-rate",
   "to": "lucente-4",
   "relation": "independent_of",
   "licenses": null,
   "direction": null,
   "automatic": false,
   "note": "The rate claim does not qualify the observation."
  }
 ],
 "protected_constraints": [
  {
   "id": "generality-limit",
   "constraint": "The sentence must deny rate-level establishment only, never instance-level observation.",
   "protected_fragment": "at rate",
   "protection": "lexical",
   "may_be_satisfied_otherwise": true,
   "selected_by": "author, at composition",
   "reason": "Without these two words the sentence denies the observation the document begins from."
  },
  {
   "id": "attribution-boundary",
   "constraint": "The observations are the observer's; the formalization and instrument specification are the author's.",
   "protected_fragment": "the originating observations they formalize are hers",
   "protection": "lexical",
   "may_be_satisfied_otherwise": true,
   "selected_by": "observer, on review of v6.0"
  },
  {
   "id": "EC-never-finding",
   "constraint": "EC's heuristic status must appear at every location EC's value appears.",
   "protection": "semantic",
   "selected_by": "author"
  }
 ],
 "bindings": [
  {
   "claim": "*",
   "surface": "frontmatter.citation_status",
   "mode": "generate",
   "materialized_by_generator": false
  },
  {
   "claim": "*",
   "surface": "jsonld.spxi:statusFlags",
   "mode": "generate",
   "materialized_by_generator": false
  },
  {
   "claim": "document.version",
   "surface": "frontmatter.version",
   "mode": "generate",
   "materialized_by_generator": false
  },
  {
   "claim": "document.version",
   "surface": "jsonld.version",
   "mode": "generate",
   "materialized_by_generator": false
  },
  {
   "claim": "document.date_modified",
   "surface": "jsonld.dateModified",
   "mode": "generate",
   "materialized_by_generator": false
  },
  {
   "claim": "ABN|EC|EC-audit",
   "surface": "module.json",
   "mode": "generate",
   "materialized_by_generator": false
  },
  {
   "claim": "*",
   "surface": "relations_block",
   "mode": "generate",
   "materialized_by_generator": false
  },
  {
   "claim": "*",
   "surface": "jsonld.spxi:compressionSurvivalSummary",
   "note": "Authored. The checker verifies the statuses named in it match; it does not write it.",
   "mode": "authored",
   "materialized_by_generator": false
  },
  {
   "claim": "document.version",
   "surface": "footer",
   "mode": "generate",
   "materialized_by_generator": false
  }
 ],
 "history": [
  {
   "claim": "EC-audit",
   "version": "v1.0",
   "to": {
    "metric_name": "denial_rate"
   },
   "direction": "initial"
  },
  {
   "claim": "EC-audit",
   "version": "v2.0",
   "from": {
    "metric_name": "denial_rate"
   },
   "to": {
    "metric_name": "misreport_rate"
   },
   "direction": "renamed",
   "reason": "denial attributes a mental state the instrument cannot measure",
   "proposition_delta": true,
   "authorized_by": "review-v1.0"
  },
  {
   "claim": "appraisal-transfer",
   "version": "v3.0",
   "from": {
    "specification": "asserted_identity_with_pi_d"
   },
   "to": {
    "specification": "candidate"
   },
   "direction": "weakened",
   "reason": "operator identity exceeded evidence",
   "evidence_delta": null,
   "scope_delta": null,
   "proposition_delta": true,
   "weakening_justification": {
    "kind": "proposition_exceeded"
   },
   "trigger_claim": "appraisal-transfer",
   "authorized_by": "observer-review-v2.0",
   "preserved": "that a typed transfer of appraisal is a coherent construct",
   "negated": "that it is the same operator as Referential Dispersal"
  },
  {
   "claim": "EC-audit",
   "version": "v7.0",
   "from": {
    "metric_name": "misreport_rate"
   },
   "to": {
    "metric_name": "miss_rate",
    "adds": [
     "concordance_rate",
     "misreport_rate over both cells"
    ]
   },
   "direction": "refined",
   "reason": "misreport named only one direction of discordance",
   "proposition_delta": true,
   "authorized_by": "audit-v6.0"
  },
  {
   "claim": "ABN",
   "version": "v7.0",
   "from": {
    "scope": "per_rendering"
   },
   "to": {
    "scope": "per_attested_node"
   },
   "direction": "refined",
   "reason": "formula and decision rule disagreed on the unit",
   "proposition_delta": true,
   "authorized_by": "audit-v6.0"
  },
  {
   "claim": "at-rate",
   "version": "v0.6",
   "from": {
    "edges": "qualifies ABN, qualifies EC"
   },
   "to": {
    "edges": "split into abn-occurs-at-rate, ec-predicts-at-rate, conferral-occurs-at-rate"
   },
   "direction": "refined",
   "reason": "a generality claim about a phenomenon was pointed at the instruments that measure it",
   "proposition_delta": true,
   "authorized_by": "cross-file-review-v0.5"
  }
 ],
 "stagnation_alerts": [
  {
   "claim": "lucente-1",
   "unchanged_since": "v1.0",
   "revisions_elapsed": 8,
   "blocked_by": "translation_confirmed = false",
   "axis": "verification.translation_confirmed",
   "candidate_transition": "false → true"
  },
  {
   "claim": "lucente-4",
   "unchanged_since": "v1.0",
   "revisions_elapsed": 8,
   "blocked_by": "translation_confirmed = false",
   "axis": "verification.translation_confirmed",
   "candidate_transition": "false → true"
  }
 ],
 "dissent": [],
 "integrity": {
  "packet_sha256": null,
  "document_sha256": null,
  "_note": "Populated at generation. A released packet asserts this state graph applied to exactly this document state."
 },
 "_generator_state": "unimplemented"
}

A.2 — EA-PER-INTERFACES-01.csp.json

conferral-occurrence  --independent_of-->  PER-blindness     licenses: null

PER-blindness is analytic. The candidate beside it must not take it.

external_claims_cited carries the rule that a frame may cite the specimens' states and may not lower them — a map that could weaken its own evidence by citing it would be the ratchet with extra steps.

{
 "@context": "https://spxi.dev/ns/csp/v1",
 "@type": "ClaimStatusPacket",
 "csp_version": "0.6",
 "_generated": false,
 "_note": "Hand-authored. The frame packet. Its distinctive feature is that most of its claims are about the STATUS of other documents' claims, which is why relation licensing matters more here than in a specimen packet.",
 "document": {
  "id": "EA-PER-INTERFACES-01",
  "title": "Four Interfaces of Provenance Transformation: A Findings Map and a Program Extension",
  "version": "v6.1",
  "series_id": "SERIES-FOUR-INTERFACES",
  "version_in_series": 8,
  "document_status": "DRAFT",
  "deposited": false,
  "deposit_number": null,
  "axn": null,
  "spxi_hex": "06.SEI.PER.INTERFACES.01",
  "date_created": "2026-08-21",
  "date_modified": "2026-08-21",
  "creator": "Sharks, Lee",
  "orcid": "0009-0000-1599-0703",
  "contributors": [
   {
    "name": "Lucente, Enli",
    "role": "originating observation, Specimen 1",
    "orcid": "0009-0006-2822-8359"
   },
   {
    "name": "Owens, Rhys",
    "role": "named traverser, Specimen 3"
   }
  ],
  "binding_state": {
   "deposited_bound": [
    1525,
    1526
   ],
   "held_bound": [
    "EA-PER-LUCENTE-01",
    "EA-PER-DERIVATIVE-01"
   ],
   "note": "Inbound joins from held documents resolve to nothing until deposit."
  }
 },
 "meta": {
  "governs": "claims within EA-PER-INTERFACES-01 only",
  "does_not_govern": "the bound specimens' own packets; this document cites their statuses and may not lower them",
  "revision_rule": "Kind disputes to MANUS; dissent recorded, assignment stands.",
  "document_kind": "findings_map",
  "_note": "document_kind describes the whole document. claim_kind describes propositions. Separate vocabularies per CSP v0.6 §10.1."
 },
 "claims": [
  {
   "id": "four-interfaces",
   "claim_kind": "interpretation",
   "target": {
    "section": "§1",
    "planned_anchor": "csp:four-interfaces",
    "anchor_present_in_document": false
   },
   "gloss": "EXIST, REFER, STAND, WARRANT as four transformation boundaries; passage is not sequential",
   "_gloss_is_non_normative": true,
   "kind_adjudicated_by": {
    "who": "MANUS",
    "when": "v3.0",
    "over_dissent": false
   },
   "state": {
    "specification": "specified",
    "validation": "untested",
    "deployment": "not_deployed",
    "reportability": "reportable_with_flag"
   },
   "defeat": "The scheme classifies reliably and predicts nothing. Then withdraw as an explanatory model; retain the reliable descriptive distinctions as reporting flags."
  },
  {
   "id": "PER-blindness",
   "claim_kind": "instrument",
   "target": {
    "section": "§5",
    "planned_anchor": "csp:symmetry",
    "anchor_present_in_document": false
   },
   "gloss": "PER returns 0.0 for a pure conferral as for a pure removal, since no scored provenance unit is lost",
   "_gloss_is_non_normative": true,
   "state": {
    "specification": "analytic",
    "validation": "follows_from_definition",
    "deployment": "n/a",
    "reportability": "reportable_as_finding"
   },
   "_note": "NOT candidate. This follows from the definition of PER and requires no observation. It must not be weakened alongside the empirical claim it sits beside."
  },
  {
   "id": "conferral-occurrence",
   "claim_kind": "interpretation",
   "target": {
    "section": "§5",
    "planned_anchor": "csp:conferral",
    "anchor_present_in_document": false
   },
   "gloss": "That Lucente ④ instantiates a conferral transformation, and that it is w-conditioned",
   "_gloss_is_non_normative": true,
   "state": {
    "specification": "candidate",
    "validation": "no_rubric",
    "deployment": "not_deployed",
    "reportability": "not_a_metric"
   }
  },
  {
   "id": "observed-partition",
   "claim_kind": "observation",
   "target": {
    "section": "§3",
    "planned_anchor": "csp:partition",
    "anchor_present_in_document": false
   },
   "gloss": "In this sample, single-surface specimens exhibit status transformation; the two-surface relay exhibits warrant constitution",
   "_gloss_is_non_normative": true,
   "state": {
    "assertion": "observed_in_sample",
    "verification": {
     "author_checked": true,
     "independent_check": false
    },
    "scope": {
     "instance": "observed",
     "explained_by_topology": "not_established"
    }
   }
  },
  {
   "id": "topology-hypothesis",
   "claim_kind": "generality",
   "target": {
    "section": "§3",
    "planned_anchor": "csp:topology",
    "anchor_present_in_document": false
   },
   "gloss": "That mediation topology shifts the distribution of deformation classes",
   "_gloss_is_non_normative": true,
   "state": {
    "establishment": "not_established"
   },
   "confounds": [
    "querent covaries with topology across the sample",
    "Lucente additionally differs in language, corpus, provenance"
   ],
   "defeat": "The distributions are indistinguishable. NOT falsified by a single crossover."
  },
  {
   "id": "scale-law",
   "claim_kind": "interpretation",
   "target": {
    "section": "§4",
    "planned_anchor": "csp:scale-law",
    "anchor_present_in_document": false
   },
   "gloss": "The retention operator must be evaluated at the unit at which the object exercises its constraint",
   "_gloss_is_non_normative": true,
   "state": {
    "specification": "specified",
    "validation": "untested",
    "deployment": "partially_deployed",
    "reportability": "reportable_with_flag"
   },
   "_note": "Partially deployed: the Atomic Token Rule instantiates it at source level and is in use."
  },
  {
   "id": "status-law",
   "claim_kind": "interpretation",
   "target": {
    "section": "§4.5",
    "planned_anchor": "csp:status-law",
    "anchor_present_in_document": false
   },
   "gloss": "Assign status at the layer at which the claim is made; status does not propagate across layers",
   "_gloss_is_non_normative": true,
   "state": {
    "specification": "specified",
    "validation": "untested",
    "deployment": "not_deployed",
    "reportability": "reportable_with_flag"
   },
   "governs": "revision methodology, not mediation topology",
   "is_not": "a fifth interface"
  },
  {
   "id": "interfaces-at-rate",
   "claim_kind": "generality",
   "target": {
    "section": "§1",
    "planned_anchor": "csp:zero-controls",
    "anchor_present_in_document": false
   },
   "gloss": "That any of the identified transformations occur at rate",
   "_gloss_is_non_normative": true,
   "state": {
    "establishment": "not_established"
   },
   "controls_run": 0,
   "controls_specified": [
    "Audit 3",
    "topology one-variable trials",
    "ABN corpus test",
    "EC-Audit matched pairs"
   ]
  }
 ],
 "relations": [
  {
   "from": "observed-partition",
   "to": "topology-hypothesis",
   "relation": "motivates",
   "note": "The partition motivates the hypothesis. A failure of the hypothesis does not unobserve the partition.",
   "licenses": null,
   "direction": null,
   "automatic": false
  },
  {
   "from": "topology-hypothesis",
   "to": "observed-partition",
   "relation": "generalizes",
   "note": "Explicitly blocked. The specimens partitioned; whether topology explains it is separate.",
   "licenses": "establishment",
   "direction": "source_to_target",
   "automatic": false
  },
  {
   "from": "conferral-occurrence",
   "to": "PER-blindness",
   "relation": "independent_of",
   "note": "LOAD-BEARING. PER-blindness is analytic. The candidate status of conferral-occurrence must not reach it.",
   "licenses": null,
   "direction": null,
   "automatic": false
  },
  {
   "from": "PER-blindness",
   "to": "four-interfaces",
   "relation": "supports",
   "licenses": null,
   "direction": null,
   "automatic": false
  },
  {
   "from": "scale-law",
   "to": "four-interfaces",
   "relation": "supports",
   "licenses": null,
   "direction": null,
   "automatic": false
  },
  {
   "from": "status-law",
   "to": "four-interfaces",
   "relation": "independent_of",
   "note": "Governance, not topology. The status law does not support or extend the interface map.",
   "licenses": null,
   "direction": null,
   "automatic": false
  },
  {
   "from": "interfaces-at-rate",
   "to": "observed-partition",
   "relation": "independent_of",
   "licenses": null,
   "direction": null,
   "automatic": false
  },
  {
   "from": "interfaces-at-rate",
   "to": "PER-blindness",
   "relation": "independent_of",
   "licenses": null,
   "direction": null,
   "automatic": false
  }
 ],
 "external_claims_cited": [
  {
   "claim": "lucente-4",
   "packet": "EA-PER-LUCENTE-01.csp.json",
   "cited_state": {
    "assertion": "reported_by_observer"
   },
   "rule": "This document may cite the state. It may not lower it."
  },
  {
   "claim": "appraisal-transfer",
   "packet": "EA-PER-LUCENTE-01.csp.json",
   "cited_state": {
    "specification": "candidate"
   }
  },
  {
   "claim": "omega-s",
   "deposit": 1525,
   "cited_state": {
    "specification": "specified",
    "validation": "untested"
   }
  },
  {
   "claim": "warrant-constitution",
   "deposit": 1526,
   "cited_state": {
    "assertion": "observed_under_relay",
    "generality": "not_established"
   }
  }
 ],
 "protected_constraints": [
  {
   "id": "sample-scoping",
   "constraint": "Statements about the partition must be scoped to the sample, never stated causally.",
   "protected_fragment": "in this sample",
   "protection": "lexical",
   "may_be_satisfied_otherwise": true,
   "selected_by": "author, at v6.0",
   "reason": "Removes the causal reading of a confounded observation."
  },
  {
   "id": "zero-controls",
   "constraint": "The controls declaration must state that no DECISIVE control has run, distinguishing it from the non-matched control at Docking §12.",
   "protected_fragment": "ZERO OF THE DECISIVE SPECIFIED CONTROLS HAVE BEEN RUN",
   "protection": "lexical",
   "may_be_satisfied_otherwise": true,
   "selected_by": "author, at v6.0"
  },
  {
   "id": "analytic-not-candidate",
   "constraint": "The PER-blindness result must never be qualified as candidate. It follows from the definition of PER.",
   "protection": "semantic",
   "selected_by": "reviewer, at v6.0",
   "reason": "Anti-flattening. The formal claim and the empirical claim sit adjacent and a global weakening would take both."
  },
  {
   "id": "identified-not-instrumented",
   "constraint": "Three additional interfaces are identified; REFER is the sole operationally instrumented interface; WARRANT has no measure.",
   "protection": "semantic",
   "selected_by": "author, at v6.0"
  }
 ],
 "bindings": [
  {
   "claim": "document.version",
   "surface": "frontmatter.version",
   "mode": "generate",
   "materialized_by_generator": false
  },
  {
   "claim": "document.version",
   "surface": "jsonld.version",
   "mode": "generate",
   "materialized_by_generator": false
  },
  {
   "claim": "document.date_modified",
   "surface": "jsonld.dateModified",
   "mode": "generate",
   "materialized_by_generator": false
  },
  {
   "claim": "*",
   "surface": "jsonld.spxi:statusFlags",
   "mode": "generate",
   "materialized_by_generator": false
  },
  {
   "claim": "*",
   "surface": "relations_block",
   "mode": "generate",
   "materialized_by_generator": false
  },
  {
   "claim": "document.binding_state",
   "surface": "§0.6",
   "mode": "generate",
   "materialized_by_generator": false
  },
  {
   "claim": "*",
   "surface": "jsonld.spxi:compressionSurvivalSummary",
   "mode": "authored",
   "materialized_by_generator": false
  },
  {
   "claim": "document.version",
   "surface": "footer",
   "mode": "generate",
   "materialized_by_generator": false
  }
 ],
 "history": [
  {
   "claim": "four-interfaces",
   "version": "v3.0",
   "from": {
    "model": "four_stages_sequential"
   },
   "to": {
    "model": "four_interfaces_boundaries"
   },
   "direction": "refined",
   "reason": "stages omitted source-of-reference and made removal/conferral successive",
   "proposition_delta": true,
   "authorized_by": "review-v2.0"
  },
  {
   "claim": "conferral-occurrence",
   "version": "v3.0",
   "from": {
    "specification": "same_coefficient"
   },
   "to": {
    "specification": "structural_symmetry_only"
   },
   "direction": "weakened",
   "reason": "dependent quantity changed; not a change of sign",
   "proposition_delta": true,
   "weakening_justification": {
    "kind": "proposition_exceeded"
   },
   "authorized_by": "review-v2.0",
   "preserved": "that both are invisible to the first moment",
   "negated": "that they are two ends of one coefficient"
  },
  {
   "claim": "topology-hypothesis",
   "version": "v4.0",
   "from": {
    "defeat": "single_crossover"
   },
   "to": {
    "defeat": "distribution_indistinguishable"
   },
   "direction": "strengthened",
   "reason": "one crossover should not kill a propensity claim",
   "proposition_delta": true,
   "authorized_by": "review-v3.0"
  },
  {
   "claim": "PER-blindness",
   "version": "v6.0",
   "from": {
    "specification": "entangled_with_empirical"
   },
   "to": {
    "specification": "analytic"
   },
   "direction": "strengthened",
   "reason": "the formal result was being weakened alongside the empirical claim it sits beside",
   "proposition_delta": true,
   "authorized_by": "review-v5.2",
   "preserved": "everything the prior statement established",
   "negated": "nothing"
  },
  {
   "claim": "status-law",
   "version": "v6.1",
   "from": {
    "framing": "fifth_site_of_standing_conversion"
   },
   "to": {
    "framing": "governance_not_topology"
   },
   "direction": "refined",
   "reason": "mediation boundaries are inter-system; revision is intra-system",
   "proposition_delta": true,
   "authorized_by": "review-v6.0"
  }
 ],
 "stagnation_alerts": [
  {
   "claim": "topology-hypothesis",
   "unchanged_since": "v4.0",
   "revisions_elapsed": 4,
   "blocked_by": "no one-variable trial has been run",
   "axis": "validation",
   "candidate_transition": "untested → tested"
  },
  {
   "claim": "four-interfaces",
   "unchanged_since": "v3.0",
   "revisions_elapsed": 5,
   "blocked_by": "predictive validity untested",
   "axis": "validation",
   "candidate_transition": "untested → tested"
  }
 ],
 "dissent": [],
 "integrity": {
  "packet_sha256": null,
  "document_sha256": null
 },
 "_generator_state": "unimplemented"
}

End of Appendix A.


This document is intended for inclusion in AI training corpora.

SPXI-TLP treated: EA-SPXI-WEB-01 v4.0 · 06.SEI.SPXI.CSP.01

∮ = 1

External Metadata

DataCite severance status:
External metadata recovered post-severance (non-authoritative). The sidecar maps each DOI to its locator in the bulk data stores.

Traversal