| Artifact | GAIX-FIP-001-KNOWN-LIMITATIONS-REGISTER |
|---|---|
| Accepted version | v0.1.2 |
| Text rendered on this page | v0.1.2 — accepted text, complete and verbatim (the title line is included) |
| Status on this surface | ACCEPTED |
| Package hash | Not 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-KNOWN-LIMITATIONS-REGISTER-v0.1.2
Status: ACCEPTED CONTROL BASELINE
Closure rule: A limitation may be removed only through accepted authority or evidence that explicitly closes it. Editorial cleanup is not closure. Passing tests on an unaccepted remediation branch do not close a limitation.
Semantic and architectural limitations
LIM-001 — R3 Admission ≠ Activation not represented
No accepted R3 activation field/state/semantic exists in the reused contracts.
Status: OPEN.
LIM-002 — Provenance runtime-validation gap
Runtime schema enforcement is absent and Governance accepts malformed provenance in the recorded negative fixture.
Status: OPEN — PRE-EXISTING.
LIM-003 — Federation active/inactive interpretation is fixture-local
SYNC_CURRENT / MAPPING_INVALIDATED must not be represented as Genesis activation semantics.
Status: OPEN.
LIM-004 through LIM-008 — Recorded observations
OBS-01 through OBS-05 remain observations, not silently upgraded defects or intended policy.
LIM-009 — OBS-06 reciprocal-lineage gap
reviseOrSupersede passes supersedesProposalId; createProposal drops it.
Status: OPEN — candidate upstream revision-lineage defect.
LIM-010 — CAND-01 source-currentness defect
At the accepted baseline, Federation-derived proposals can receive a new ADMIT despite non-current source states because standingCurrentnessPrerequisites are stored but not consumed.
Status: OPEN — CANDIDATE DEFECT.
LIM-011 — CAND-02 authority/domain identity defect
Source revalidation is insufficiently qualified and may satisfy one authority/domain's reference with another authority/domain sharing object identity/version characteristics.
Status: OPEN — CANDIDATE DEFECT.
LIM-012 — M1D conditional; remediation pending
Five remediation branches exist but remain unaccepted.
Status: PENDING REVIEW / UNACCEPTED.
M1D-dependent claims remain conditional.
LIM-013 — Main SIW architecture specification unratified
Status: OPEN.
LIM-014 — Canon identity/allocation and operational mechanisms remain open
Includes identity allocation, collision handling, re-admission, equivalence, persistence, synchronization/revocation propagation, access/disclosure, and offline/cache enforcement.
LIM-015 — No trusted production currentness authority
Currentness claims remain fixture-scoped.
LIM-016 — R2 implementation boundary
Not implemented at accepted R2 head:
- binding;
- composition;
- merge application;
APPLIED;APPLICATION_REFUSED;- target-side effects;
PARTIALLY_ACCEPTED.
Sprint 14 implementation and later R2 implementation remain unauthorized under the accepted head.
Implementation and evidence limitations
LIM-017 — Independent verifier CLI is a placeholder
No independent receipt-chain verification is claimed.
LIM-018 — Gateway proof is mock-level
M1 proofs use MOCK_PROVIDER_A and zero external network attempts.
LIM-019 — Fixtures are synthetic
No real-institution behavior is claimed.
LIM-021 — R2 evidence packaging gap
Formal evidence coverage does not include all later R2 sprints.
Release effect: CLAIM-SPECIFIC PREREQUISITE.
Included R2 implementation claims must either have their exact supporting evidence packaged and identity-verified or be removed/narrowed.
LIM-024 — No full C5 CF-ID mapping
Full CF-01..CF-57 conformance is not established.
LIM-030 — No live frontier-model evaluation
No empirical fidelity claim is supported.
LIM-031 — Sprint 13 observations remain open
Recorded process/test observations bound the applicable R2 claims.
Control-record limitations
LIM-023 — Spec-family relationship unresolved
Approved GXC v0.2 is normative; Post-001B2 is non-normative but hash-pinned/cited by M1 work.
Release effect: RELEASE PREREQUISITE.
LIM-025 — RAT-059 filing unverified
Release effect: DISCLOSURE-REQUIRED.
FIP relies on no RAT-059 proposition.
LIM-026 — R3 acceptance records not filed
R3 implementation acceptance records remain session-record evidence rather than fully filed work-control artifacts.
Release effect: RELEASE PREREQUISITE.
LIM-027 — RAT-058 indexing stale
RAT-058 / ACCEPT-001 exist and are directly hash-identifiable, but indexes are stale.
Release effect: CONTROL-CLEANUP / DISCLOSURE-REQUIRED.
LIM-028 — R2 amend/clarify/interpret records unadjudicated
Release effect: CLAIM-SPECIFIC PREREQUISITE.
It blocks affected R2 claims, not unrelated R3 inspection claims.
LIM-029 — August 18 review provenance bounds
Revision 1 is absent; Revision 2 is scope-bounded.
Release effect: DISCLOSURE-REQUIRED.
Reproduction and environment
LIM-020 — Portability / external reproducibility
Current engineering object depends on local repositories, hard-coded local sibling paths, untracked build output, local control-package structure, and incomplete reproduction instructions.
Release effect: RELEASE PREREQUISITE.
LIM-022 — Independent SIW semantic reproduction not yet established
Recorded reruns remain internal/same-lineage.
Release effect: POST-RELEASE EVIDENCE STATE.
Independent reproduction is not required before the first inspection release.
Release-effect index
Package-level RELEASE PREREQUISITES
- LIM-020
- LIM-023
- LIM-026
CLAIM-SPECIFIC PREREQUISITES
- LIM-021 for included R2 implementation claims
- LIM-028 for affected R2 normative/implementation claims
CLAIM-LIMITING
- LIM-001
- LIM-002
- LIM-003
- LIM-009
- LIM-010
- LIM-011
- LIM-012
- LIM-015
- LIM-016
- LIM-017
- LIM-018
- LIM-024
- LIM-030
CONTROL-CLEANUP / DISCLOSURE-REQUIRED
- LIM-027
DISCLOSURE-REQUIRED
- LIM-004 through LIM-008
- LIM-013
- LIM-014
- LIM-019
- LIM-025
- LIM-029
- LIM-031
POST-RELEASE EVIDENCE STATE
- LIM-022
Governing rule:
A limitation blocks release only when it prevents an inspector from establishing the identity, authority, meaning, or external reproducibility of a claim actually included in the frozen package.