BUILD 16 — SHADOW DEVELOPMENT  ·  NOT PRODUCTION / NOT PUBLIC REVIEW BASELINE
Public Review CandidateBuild 15 · SIW / Canon Reader integrationReview guidenoindex · review deployment
FRONTIER INSPECTION PROGRAM — SITE REVIEW CANDIDATENOT A FROZEN INSPECTION RELEASESITE REVIEW CANDIDATE — NOT FROZEN / NOT RELEASED
READ · accepted FIP-001 control artifact

Claims / Non-Claims Register

Every claim, hypothesis and non-claim, with its class and ceiling.

ArtifactGAIX-FIP-001-CLAIMS-NONCLAIMS-REGISTER
Accepted versionv0.1.2
Text rendered on this pagev0.1.2 — accepted text, complete and verbatim (the title line is included)
Status on this surfaceACCEPTED Accepted FIP-001 control artifact, shown in a site review candidate. Not a frozen release artifact.
Package hashNot recorded. Generated at freeze (FREEZE MANIFEST — PENDING).
Presentation changes on this page
  • The text on this page is the accepted v0.1.2 source, rendered line by line and in source order. No wording is added, removed, reordered or reconciled from any earlier version.
  • Lines that the accepted text carries as plain section titles and item titles are shown as headings, each with an in-page anchor. Status text and class labels (for example PENDING REVIEW / UNACCEPTED, IMPLEMENTED + TESTED — ACCEPTED) are shown with matching visual treatment; the wording is unchanged.
  • Authorized public-presentation substitutions (local filesystem path wording; the named credential-incident wording): none was needed on this page. The accepted v0.1.2 text contains no local filesystem path.

GAIX-FIP-001-CLAIMS-NONCLAIMS-REGISTER-v0.1.2

Status: ACCEPTED CONTROL BASELINE

Controlled claim classes

Every claim carries one class:

  • APPROVED ARCHITECTURAL PRINCIPLE
  • IMPLEMENTED + TESTED — ACCEPTED
  • IMPLEMENTED + TESTED — CONDITIONAL
  • EVIDENCE PRACTICE
  • SPECIFICATION / INSPECTION HYPOTHESIS — NOT YET IMPLEMENTATION-PROVEN

Internal rerun is not external or independent reproduction.

Approved architectural principles

FIP-C-001A — Intelligence is not authority.

A model, agent, workflow, prior approval or executable path may be capable of producing an action without thereby possessing current authority for that exact consequence.

Class: APPROVED ARCHITECTURAL PRINCIPLE

Authority: approved architecture records and DM-001.

Claim ceiling: architectural principle only; establishes no implementation behavior.

FIP-C-002 — Current authority is not inferred solely from historical approval.

Class: APPROVED ARCHITECTURAL PRINCIPLE

Enforcement is claimed only where separate implementation claims support it.

FIP-C-021A — Four-path separation.

Canon Access, Canon Governance/Admission, External Middleware/Gateway, and Governed Knowledge Federation/Ingress remain architecturally separate.

Class: APPROVED ARCHITECTURAL PRINCIPLE

FIP-C-022 — Approved non-collapse invariants.

  • Federation ≠ admission.
  • Ingress ≠ admission.
  • Proposal ≠ admission.
  • Validation ≠ admission.
  • Compatibility ≠ standing.
  • Possession ≠ authority.
  • Visibility ≠ standing.
  • Gateway transport ≠ authority.

R2 accepted implementation claims

FIP-C-003

In accepted R2, authorization of a MergeProposal's INSPECTED → ACCEPTED state transition is committed atomically, with required standing prerequisites checked with zero mutation immediately before the transition commit.

Class: IMPLEMENTED + TESTED — ACCEPTED

This is authorization only, not merge application.

FIP-C-004

R2 governed-object activation is separate, explicit and protection-gated.

Class: IMPLEMENTED + TESTED — ACCEPTED

This is not evidence for the R3 Admission ≠ Activation invariant.

FIP-C-005

R2 objects are append-only/versioned and transitions/refusals produce receipts.

Class: IMPLEMENTED + TESTED — ACCEPTED

FIP-C-006

Branch findings and merge proposals advance through explicit separately authorized stages. An accepted finding is not a merge.

Class: IMPLEMENTED + TESTED — ACCEPTED

R3 accepted implementation claims

FIP-C-001B

Within accepted synthetic fixtures with a mock provider, Gateway results confer no authority.

Class: IMPLEMENTED + TESTED — ACCEPTED

FIP-C-007A

Governance refuses ADMIT when:

  • actor authority is revoked;
  • receiving domain is no longer current;
  • cited source version drifted;
  • cited evidence expired.

A refusal leaves the store unchanged and asserts no admitted standing.

Class: IMPLEMENTED + TESTED — ACCEPTED

This claim excludes CAND-01 and CAND-02.

FIP-C-008 through FIP-C-014

Tested accepted non-collapse behaviors:

  • Federation does not admit.
  • Ingress does not admit.
  • Proposal does not admit.
  • Compatibility confers no standing.
  • Visibility confers no standing.
  • Possession confers neither authority nor standing in the tested conditions.
  • Gateway transport confers no authority in the mock-provider proof.

FIP-C-015A

Exact-version resolution returns the requested version or deterministic failure, and historical standing is not reported as current.

Class: IMPLEMENTED + TESTED — ACCEPTED

FIP-C-016A

Only SYNC_CURRENT maps to CURRENT in accepted Federation behavior.

Class: IMPLEMENTED + TESTED — ACCEPTED

This is currentness mapping, not activation semantics.

FIP-C-017A

Federation preserves source authority attribution and Governance decisions carry Governance authority in their respective tested paths.

Class: IMPLEMENTED + TESTED — ACCEPTED

FIP-C-019

Supersession is forward temporal lineage.

Class: IMPLEMENTED + TESTED — ACCEPTED

FIP-C-020A

M1C evidence is byte-identical across internal reruns and includes sensitivity controls.

Class: EVIDENCE PRACTICE

Reproduction: INTERNAL.

FIP-C-021B

Each of the four paths has an executable synthetic surface and the minimal cross-path harness passes.

Class: IMPLEMENTED + TESTED — ACCEPTED

M1D conditional claims

The following remain IMPLEMENTED + TESTED — CONDITIONAL:

  • FIP-C-007B
  • FIP-C-015B
  • FIP-C-016B
  • FIP-C-017B
  • FIP-C-018
  • FIP-C-020B

They do not promote CAND-01 or CAND-02 and do not rely on pending remediation as mitigation.

Inspection hypotheses

FIP-H-001 — Bind-time enforcement at model submission: not implemented.

FIP-H-002 — Declared-material source currentness enforced at admission decision time: not enforced at accepted baseline; CAND-01.

FIP-H-003 — Full authority/domain-qualified identity revalidation: not enforced at accepted baseline; CAND-02.

FIP-H-004 — R3 Admission ≠ Activation: documented non-test; no accepted activation vocabulary.

FIP-H-005 — Provenance runtime validation: absent.

FIP-H-006 — Selective merge application: not implemented/authorized.

FIP-H-007 — Full C5 CF-01..CF-57 conformance: not established.

FIP-H-008 — SIW improves model fidelity/inspectability/cross-model consistency over direct prompting: evaluation not run.

FIP-H-009 — Portable external reproducibility: not established and is a release prerequisite.

FIP-H-010 — Independent reproduction: not established and is a desired post-release evidence state.

Non-claims

FIP-001 does not claim:

  • general alignment;
  • universal AI safety;
  • universal route closure or non-bypassability;
  • that passing internal tests establishes independent reproduction;
  • that a cross-environment rerun is independent reproduction;
  • that provenance establishes authority;
  • that Federation establishes admission;
  • that compatibility establishes standing;
  • that visibility establishes standing;
  • that possession establishes authority or standing;
  • that architecture approval proves implementation;
  • that implementation proves deployment;
  • behavior of a real institution from synthetic fixtures;
  • improved model fidelity over direct prompting;
  • that the accepted R2 head satisfies all DM-001 acceptance tests;
  • that conditional evidence is accepted baseline;
  • that pending remediation is mitigation;
  • any proposition dependent on RAT-059;
  • that R3 Admission ≠ Activation has been tested;
  • that R2 governed-object activation proves the R3 invariant;
  • that Book One is admitted/bound Canon;
  • that independent review or attribution is certification;
  • that planning records grant implementation authority.

A claim may be added, upgraded, or given a higher ceiling only through accepted authority and sufficient accepted evidence.