14 properties for a claim and its qualifications

This is not a standard. It is one publisher's vocabulary, versioned, with exactly one implementation — the 21 claim pages on this site. It is published because a JSON-LD prefix that does not resolve is a prefix nobody can check, not because anyone else has adopted it.

Custom properties do not promise a search enhancement or enforce quotation. They make the qualifications available beside the proposition. A consumer can still ignore or omit them; this vocabulary does not prevent that.

• fw:falsifierText

  The stated condition that triggers the declared consequence.

  SOURCE · falsifier.condition

• fw:consequenceText

  The declared response: NARROW, REJECT or HOLD.

  SOURCE · falsifier.consequence

• fw:forbiddenRescueText list

  Repairs the author declares unavailable after the falsifier fires.

  An explicit empty RDF list preserves the difference between no forbidden rescues and an omitted field.

  SOURCE · forbidden_rescues

• fw:nonClaimText list

  Limits the author states on what the claim licenses.

  SOURCE · non_claims

• fw:scopeStatementText

  The claim's stated domain and limitations.

  SOURCE · scope

• fw:evidentialStatusText

  The registry's current evidential-status label.

  SOURCE · dimensions.evidential_status

• fw:lastReviewedDate

  The last review date recorded for this claim.

  SOURCE · last_reviewed

• fw:reviewWindowDuration

  The declared interval between required reviews.

  SOURCE · review_window_days

• fw:warrantExpiresDate

  The recorded review date plus the review window.

  After this date the review is overdue. This is not a probability, a truth verdict, or proof that no unrecorded review occurred.

  SOURCE · last_reviewed + review_window_days

• fw:supportUrlURL

  The declared public support location, which may be mutable.

  SOURCE · support.url

• fw:supportBindingURL

  A support URL containing the declared immutable revision.

  Emitted only with a declared revision embedded in the URL. Reachability and other binding checks belong to verify_claims.py; this metadata alone proves neither.

  SOURCE · support.url, when support.commit is embedded

• fw:boundRevisionText

  The immutable support revision declared in the registry.

  SOURCE · support.commit

• fw:verdictText

  An explicit rejection notice recorded at the start of the proposition.

  SOURCE · proposition rejection prefix

• fw:verdictDateDate

  The date of that explicit rejection notice.

  SOURCE · proposition rejection prefix

Use the published context alongside schema.org. JSON-LD consumers can preserve the custom properties; applications decide whether to interpret them:

{
  "@context": [
    "https://schema.org",
    "https://cubits11.github.io/ns/falsifiable/v1/context.json"
  ],
  "@type": "Claim",
  "identifier": "CC-004",
  "text": "For marginals (0.10, 0.10) and the both-fail query, cc.kernel.strict identify() returns the sharp interval [0.0, 0.10] together with endpoint witness distributions that sum to one, are nonnegative, satisfy both marginal constraints, and attain each endpoint — verified to 1e-9 from a clean clone.",
  "fw:falsifier": "Bound identify() execution fails any stated interval, witness feasibility constraint, marginal constraint, or endpoint-attainment assertion at the declared tolerance.",
  "fw:consequence": "REJECT",
  "fw:forbiddenRescue": [
    "do not replace a failed endpoint witness with an interior distribution or a loose approximate candidate",
    "do not waive a failed sum, nonnegativity, marginal, or attainment constraint by changing the tolerance after the outcome"
  ],
  "fw:nonClaim": [
    "endpoint witnesses are feasible mathematical worlds, not observed systems",
    "attainment does not select a point inside the interval or estimate the true dependence"
  ],
  "fw:warrantExpires": "2026-12-22"
}

The context document: /ns/falsifiable/v1/context.json. Both it and this page are generated from the same constants that render the claim pages, so a term cannot be defined here and emitted differently there.

Version 1 terms will not change meaning under this URL. A term whose meaning has to change gets a new version path. A term that turns out to be unused gets deleted from version 2 and stays resolvable at version 1, because a namespace that breaks its own old documents teaches publishers not to use namespaces.