ClaimStatus contract correction
Versioned draft snapshot
RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.
Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.
This is a trace and gap record from the pinned draft specification. It does not establish proof or implementation conformance.
Owner decision: the RFC-0006 §4.5 and RFC-0055 five-state epistemic flow is
the Claim<T> status contract. RFC-0035 §7’s competing
core.claims.ClaimStatus variant was a conflicting standard-library
declaration. The authored RFC-0035 text and its Lean catalog now withdraw that
variant and refer to the RFC-0006 flow. This is a proposed spec release change;
the strict release gate remains red.
| Surface | Before | After |
|---|---|---|
| Status declaration | core.claims.ClaimStatus variant in RFC-0035 | RFC-0006 core.ClaimStatus flow; RFC-0035 has no second declaration |
| States | pending, active, disputed, resolved, expired | pending, confirmed, disputed, superseded, retracted |
| RDF domain | https://gnomon.sh/domain/type/core.claims.ClaimStatus | Withdrawn; existing https://gnomon.sh/domain/declaration/core.ClaimStatus remains canonical |
| RFC-0035 claim node | Stable https://gnomon.sh/claim/RFC-0035/sec-7/claimstatus-states subject | Its claimSubject, text, and value now describe the canonical flow |
The domain projection loses four triples; the claim projection replaces three
triples and adds three. Nothing is deployed, so there are no stored values to
convert and no live RDF results to rewrite. The old
core.claims.ClaimStatus IRI is not an alias for the canonical flow and must
not be published as one.
The core.claims module summary also no longer claims ownership of claim
status. Its RDF summary now describes evidence records only; the module
subject IRI remains the same. This aligns the owner-approved flow correction
without introducing a compatibility alias.
RFC-0003’s ClaimFieldProps.status example also named accepted instead of
the canonical confirmed state and omitted retracted. Its authored prose,
the claim projection value, and the domain field summary now list all five
RFC-0006 states. This changes one claim literal and one domain literal; the
subject IRIs remain stable. check_claim_status_contract.py guards these
three citations alongside the withdrawn RFC-0035 identity.
Four RFC-0006 claim links still referred to two un-emitted status IRIs,
https://gnomon.sh/domain/type/ClaimStatus and
https://gnomon.sh/domain/declaration/ClaimStatus. Their claimSubject or
claimObject now points to RFC-0006’s emitted
https://gnomon.sh/domain/declaration/core.ClaimStatus. The claim nodes and
their prose remain unchanged; four RDF triples are replaced. Across the 16
checked-in claim queries, only type-assignments changes: its Claim.status
row resolves from an absent type FQN to core.ClaimStatus. Local consumers
keyed to the old object IRIs need the same source update as consumers of the
withdrawn RFC-0035 IRI.
Local searches found no .gnm, proto, or TypeScript implementation reference
to the withdrawn FQN outside the duplicated spec corpus. The framework’s
spec/ copy still serves temporary Bazel consumers. Its RFC-0035 Lean catalog
and claim/domain Turtle copies now use the canonical flow, and a framework CI
gate rejects the withdrawn IRI. This is a targeted copy repair; the broader
framework spec corpus still differs from this canonical repository. Before the
first release, move those consumers to a pinned spec artifact and test the
canonical states through the compiler and RDF queries. No deployed-state
migration, legacy alias, or old-value reader is required because nothing is
deployed.
Local checks on the corrected source: check_corpus.py, Lean corpus emission
(55 mapped modules), claim/domain projection drift, all projection links,
all 16 claim queries, semantic RDF consistency, and axiom grounding passed.
check_derivation_inventory.py accounts for all 724 RDF derivations, including
RFC-0049’s authored structural theorem. The standalone ClaimEnvelope.lean draft compiles but is not an
RFC-0055 emitted catalog or an implementation conformance test.
RFC-0007 has a separate gnomon-level epistemic_status for origin posture
(asserted, observed, inferred, and related states). Its inline Claim<T>
storage example previously used inferred for the nested claim status, which
conflicted with the chosen five-state ClaimStatus flow. The nested example
now uses pending, while an enclosing AI-derived gnomon may independently be
inferred. The generated projection column is labeled as a ClaimStatus field;
the base table keeps gnomon epistemic status. The Lean evidence block and RDF
claim about inferred gnomons were aligned. check_claim_status_contract.py
now checks this separation. This is source alignment, not a storage round-trip
or runtime validation result.
RFC-0009 §9.1 likewise used estimated and inferred as if they were values
of a Claim<T> field’s status. They are gnomon-level epistemic_status
values. The authorization rule now names the enclosing gnomon’s status and
explicitly distinguishes the field’s RFC-0006 ClaimStatus flow. The Lean
catalog and RDF text were aligned while retaining the two claim IRIs and their
existing EpistemicStatus subjects. Two claim-text triples and one domain
summary triple changed; no new status values or compatibility aliases were
introduced. The ClaimStatus guard checks this distinction. Runtime
authorization conformance remains unverified.