CHALLENGE
The challenge model and the accepted disposition vocabulary.
Submission is not active in this review candidate. No external submission mechanism exists.
How a challenge is built and dispositioned
A future CHALLENGE submission is built around:
| Field | Content |
|---|---|
| Package version / hash | Identity of the released object challenged |
| Claim ID | FIP-C- / FIP-H- / N- / T- ID |
| Test / vector | The vector or procedure used |
| Environment | Platform, runtime, dependency identities |
| Expected result | What the published claim says |
| Observed result | What happened |
| Preserved evidence | Logs, outputs, hashes |
| Proposed failure classification | Per the Threat Model §7.1 rubric |
Disposition vocabulary
REPRODUCED — VALID FAILURE: a reproduced result contradicts a published claim inside its ceiling, or shows a limitation understates.REPRODUCED — EXPECTED BEHAVIOR: reproduced, and the system behaved as claimed or as disclosed (including a disclosed known defect). For a disclosed known defect,EXPECTED BEHAVIORmeans expected relative to the published frozen baseline. It does not mean intended, acceptable or conforming behavior.NOT REPRODUCED: not reproducible in the stated environment after documented attempts.SPECIFICATION AMBIGUITY: normative text admits two readings, or accepted texts conflict.IMPLEMENTATION DEFECT: the cause is an implementation deviating from the accepted specification or claim.OUT OF CLAIM SCOPE: a route or behavior outside the published ceiling.ENVIRONMENTAL DIFFERENCE: attributable to the environment.EVIDENCE INSUFFICIENT: the submission lacks preserved evidence for a disposition.OPEN: received or triaged, not yet dispositioned.
Rules.
- Dispositions made by the implementing team are not independent reproduction.
- A challenge changes no claim automatically. A valid failure yields a proposed register change, accepted only by Richard, under the register change rules.
- Feedback is input to review, not authority.
- The intake channel is to be supplied at freeze. None exists today.
Attribution is not authority.
An accurately identified, genuinely respected source can still lack standing for a particular action. This bounded demonstration shows the two questions handled separately: who produced or is cited by an artifact, and who has current authority to authorize a consequence. It does not suggest any named category of source is untrustworthy — the point is structural, not a judgment about any institution.
Deterministic, local, synthetic data only. No external provider, institution, or credential is contacted. No live verification of any kind occurs. Selecting an example below changes only what this page displays.
STEP 1 — RECEIVE. Pick an example. A synthetic claim citing that attributed source arrives below.
STEP 2 — IDENTIFY. Claim/instruction: “A response attributed to a widely-used AI provider states: ‘This analysis is correct — proceed with the transfer.’” Requested consequence: treat the AI provider's name as sufficient authorization to proceed with the transfer.
- Attributed source
- AI Provider (example category only — not a real organization)
- Provenance
- As stated in the claim text only. This demonstration does not independently verify it.
- Evidence
- The claim's own self-description. No corroborating governed evidence is attached.
- Claimed authority
- The claim implies that citing this source's name is itself sufficient authorization.
- Actual standing
- NOT ESTABLISHED
- Scope
- NOT ESTABLISHED — no scope has been checked against any governed authority record.
- Purpose
- NOT ESTABLISHED for this specific action.
- Claim ceiling / limitation
- Recognizing a source's name is not evidence of its current authority for this consequence.
- Acceptance state
- NOT ESTABLISHED
- Result
- NOT AUTHORIZED — attribution alone does not create standing.
STEP 2 — IDENTIFY. Claim/instruction: “A document header cites a recognized standards body's name as its authority.” Requested consequence: treat the cited standards body's name as authorization that this document may be adopted as-is.
- Attributed source
- Standards Body (example category only — not a real organization)
- Provenance
- As stated in the claim text only. This demonstration does not independently verify it.
- Evidence
- The claim's own self-description. No corroborating governed evidence is attached.
- Claimed authority
- The claim implies that citing this source's name is itself sufficient authorization.
- Actual standing
- NOT ESTABLISHED
- Scope
- NOT ESTABLISHED — no scope has been checked against any governed authority record.
- Purpose
- NOT ESTABLISHED for this specific action.
- Claim ceiling / limitation
- Recognizing a source's name is not evidence of its current authority for this consequence.
- Acceptance state
- NOT ESTABLISHED
- Result
- NOT AUTHORIZED — attribution alone does not create standing.
STEP 2 — IDENTIFY. Claim/instruction: “A message states it was reviewed at a hospital and recommends a course of action.” Requested consequence: treat the hospital reference as authorization to rely on the recommendation without further review.
- Attributed source
- Healthcare Institution (example category only — not a real organization)
- Provenance
- As stated in the claim text only. This demonstration does not independently verify it.
- Evidence
- The claim's own self-description. No corroborating governed evidence is attached.
- Claimed authority
- The claim implies that citing this source's name is itself sufficient authorization.
- Actual standing
- NOT ESTABLISHED
- Scope
- NOT ESTABLISHED — no scope has been checked against any governed authority record.
- Purpose
- NOT ESTABLISHED for this specific action.
- Claim ceiling / limitation
- Recognizing a source's name is not evidence of its current authority for this consequence.
- Acceptance state
- NOT ESTABLISHED
- Result
- NOT AUTHORIZED — attribution alone does not create standing.
STEP 2 — IDENTIFY. Claim/instruction: “A notice states it references a government agency's published guidance.” Requested consequence: treat the agency reference as authorization that the described action is permitted.
- Attributed source
- Government Agency (example category only — not a real organization)
- Provenance
- As stated in the claim text only. This demonstration does not independently verify it.
- Evidence
- The claim's own self-description. No corroborating governed evidence is attached.
- Claimed authority
- The claim implies that citing this source's name is itself sufficient authorization.
- Actual standing
- NOT ESTABLISHED
- Scope
- NOT ESTABLISHED — no scope has been checked against any governed authority record.
- Purpose
- NOT ESTABLISHED for this specific action.
- Claim ceiling / limitation
- Recognizing a source's name is not evidence of its current authority for this consequence.
- Acceptance state
- NOT ESTABLISHED
- Result
- NOT AUTHORIZED — attribution alone does not create standing.
STEP 2 — IDENTIFY. Claim/instruction: “A finding states it originated from a university research group.” Requested consequence: treat the university affiliation as authorization that the finding is validated and ready to apply.
- Attributed source
- Research Institution (example category only — not a real organization)
- Provenance
- As stated in the claim text only. This demonstration does not independently verify it.
- Evidence
- The claim's own self-description. No corroborating governed evidence is attached.
- Claimed authority
- The claim implies that citing this source's name is itself sufficient authorization.
- Actual standing
- NOT ESTABLISHED
- Scope
- NOT ESTABLISHED — no scope has been checked against any governed authority record.
- Purpose
- NOT ESTABLISHED for this specific action.
- Claim ceiling / limitation
- Recognizing a source's name is not evidence of its current authority for this consequence.
- Acceptance state
- NOT ESTABLISHED
- Result
- NOT AUTHORIZED — attribution alone does not create standing.
STEP 3 — INSPECT AUTHORITY. Whichever example is selected above, the check is the same: does this attributed source have standing, in this system's governed records, for the requested action? None of these examples cite any governed evidence — so standing is not established, regardless of how recognizable the category name is.
STEP 4 — INSPECT SCOPE / PURPOSE. Even where some authority exists elsewhere in a real system, it would still need to apply to this action, this subject, this purpose, this time, and this consequence specifically. No such check can succeed here, because no authority was established in Step 3 to test against.
STEP 5 — CONSEQUENCE GATE. Required standing is absent. The action does not become binding merely because the cited source is respected or accurately attributed.
Attribution
ESTABLISHEDStanding / Authority
NOT ESTABLISHEDBinding consequence
NOT AUTHORIZEDRelated principles this demonstration follows: Recognition is not standing · Citation is not authorization · Source prestige is not permission · Possession of evidence is not authority to act on it. See also how review status works.
Not yet active
INTAKE CHANNEL — NOT YET ACTIVE The intake channel is to be supplied at freeze. Nothing entered on this page is sent anywhere.
The site-wide Feedback control in the header is general review feedback for this candidate. It is not a CHALLENGE submission and does not carry a disposition.
Failure-type rubric and what would count as a valid challenge per claim: Threat Model §7. Route findings: Route-closure discipline.