BUILD 16 — SHADOW DEVELOPMENT  ·  NOT PRODUCTION / NOT PUBLIC REVIEW BASELINE
Public Review CandidateBuild 15 · SIW / Canon Reader integrationReview guidenoindex · review deployment
Genesis AiXGoverned knowledge
architecture
View
ProfileHistorical Prototype
FRONTIER INSPECTION PROGRAM — SITE REVIEW CANDIDATENOT A FROZEN INSPECTION RELEASESITE REVIEW CANDIDATE — NOT FROZEN / NOT RELEASED
Genesis AiX›SIW›INSPECT SIW›READ›Specification Authority Manifest
READ · accepted FIP-001 control artifact

Specification Authority Manifest

Which artifacts govern interpretation, and their recorded standing and provenance.

ArtifactGAIX-FIP-001-SPECIFICATION-AUTHORITY-MANIFEST
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 and already reads “prior production credential incident”.

GAIX-FIP-001-SPECIFICATION-AUTHORITY-MANIFEST-v0.1.2

Status: ACCEPTED CONTROL BASELINE

Evidence state: Reconciled 2026-09-19

1. Purpose and claim ceiling

This manifest identifies which artifacts govern interpretation of the FIP-001 inspection object and their recorded standing and provenance. It is an authority and provenance record only. It does not merge, rewrite, summarize as normative, or reconcile any specification, and it is not a master specification.

Authority artifacts and implementation baselines are different things. Documents—specifications, approved decisions and ratification records—answer what governs. Commits and heads—the accepted R2 head, R3 milestone commits and remediation branches—answer which implementation state is accepted, conditional or pending. Implementation baselines are never ranked as authority.

Ceiling: this manifest establishes what is recorded as approved, accepted, conditional, pending or unratified. It does not establish that any implementation conforms, that anything is reproducible by others, or that anything is deployed.

2. R2 normative authority

SIW-DM-001_v0.1.1.md

SHA-256: f0649f8d926cf3175abc12ca3ea31d6d48c54288f78d41c8d4ec19df7308bc8e

siw-authoritative.schema.v0.1.1.json

SHA-256: 3b930f373514d30a1dd2582999c4a1e2ed5e283dc06e852919b0e9ef820251c1

SIW-DM-001_v0.1.1.pdf

SHA-256: ada936cde17250735e8eb591566cdced188efef7b90dd227d037d17a69e7c02b

SIW-DM-001 v0.1.1 is the ratified R2 engineering baseline. The Markdown and schema are byte-identical to the copies in the accepted R2 repository state. The PDF was not byte-compared with the Markdown.

3. Later accepted R2 authority

Approved written Release Two decisions outrank DM-001 where an explicit conflict exists. The main SIW architecture specification and SIW-OM-001 remain unratified, so DM-001 remains the highest completed normative engineering specification, subject to later approved decisions.

Acceptance and ratification records establish gate and implementation standing; they do not become normative specifications merely through temporal precedence.

SIW-R2-RAT-058

SHA-256: 4699bc06001e5635294d5d9114194876816cf61748dc5727a5a4d56437b70955

SIW-R2-SPRINT13-ACCEPT-001

SHA-256: 5b7e58b838407963462feaeb1f1f202caaca98700df0db30c2052c5e130bf14a

Accepted R2 implementation head:

ca596c0b69b0f8ef324c327ff271f9d9310a7663

This head is an implementation-state identifier, not an authority artifact and not a source of normative requirements.

At that head, authorizeMergeProposal implements the INSPECTED → ACCEPTED authorization transition only. Merge application, later R2 implementation, merge/push/tag/deploy authority and target-side effects are not authorized.

RAT-059 remains UNVERIFIED and non-head-changing. FIP-001 relies on no proposition from RAT-059.

4. R3 approved architecture

Architecture approval is not implementation acceptance.

001B1 approval:

8009f0cd191c5865607ceea23d7fccfe1a8320ea359f1cb0fd0485ef4b340fbc

001B2 approval:

64ac339fd0c71feb2f1b2d42c80f18f4db9d9f7b354d28b166c5516ef0226954

001B3 approval:

d97fa187aba8bd004ded55215ebf401d333e1a8cad4e68e593f3eb1e4be40385

001C gate exit:

6358f83d10edb8b006c0e03a47f8faadeb66f6d595c8ecfa644d651ee547b13f

Approved GXC v0.2 texts include C1–C5 and GRX.

The approved 001C gate-exit candidate closes only the specified shared control-architecture pause. It creates no implementation authority, deployment authority, admission authority, or forward-integration authority. Forward Canon integration remains frozen where the controlling record says so.

5. R3 implementation acceptance

M1A — ACCEPTED

M1B — ACCEPTED, scoped

M1C — ACCEPTED

M1D — CONDITIONAL

M1B preserves:

  • SYNC_CURRENT / MAPPING_INVALIDATED active/inactive mapping is fixture-local.
  • Admission ≠ Activation is not currently fixture-able under existing contract vocabulary.
  • Provenance runtime validation remains an open contract/schema gap.

M1C carries INV-01..08 as tested and INV-09 as a documented non-test.

M1D exposed CAND-01 and CAND-02. Its remediation remains pending and unaccepted.

Gateway engineering baseline references do not imply production deployment. The prior production credential incident was repaired through a secret replacement; the referenced engineering commit was not deployed for that incident.

6. Pending remediation

The five M1D-related remediation branches remain PENDING REVIEW / UNACCEPTED.

Passing tests on those branches are not acceptance and are not mitigation.

FIP citations use accepted/conditional baseline commits, not pending remediation.

7. Unratified / non-normative material

Includes:

  • Main SIW architecture specification working draft.
  • SIW-OM-001.
  • SIW-MAH-001.
  • SIW-HAR-001.
  • Post-001B2 Specification Package v0.1 as non-normative supporting material.
  • Canon binding contract 007B.
  • R2/R3 continuity handoff without located ratification.
  • Registry-Independent Assurance discussion draft and appendix.
  • Public Web & Knowledge Architecture v0.1.
  • SIW_Release_2.pdf with unresolved provenance.
  • Live frontier-model evaluation readiness proposal, PROPOSED — NOT ACTIVE.
  • Sprint 14 planning material with unverified filing.
  • Build 15 website pages as presentation material rather than authority.

8. Provenance and filing gaps

  • R3 implementation acceptances and SIW-R3-IMPLEMENTATION-AUTH-001 are not yet filed into work control.
  • RAT-059 filing is unverified.
  • August 18 review Revision 1 is absent.
  • Formal R2 evidence bundles do not cover the later R2 sprints.
  • Certain R2 amend/clarify/interpret records remain unadjudicated for their effect on DM-001.
  • RAT-058 / ACCEPT-001 are not fully indexed in 00_READ_FIRST.
  • Approved GXC v0.2 files retain PROPOSED headers and M1 work cites non-normative Post-package numbering.

9. Production / deployment distinction

No commit named in this manifest is asserted to be deployed merely because it is accepted or test-pinned.

Public site deployment state is separate from engineering authority and implementation acceptance.

10. Authority-order summary

R2 authority:

  1. Approved written R2 decisions.
  2. Unratified main SIW architecture / SIW-OM — not in force.
  3. SIW-DM-001 v0.1.1.
  4. Authoritative schema.
  5. Lower-ranked implementation/historical materials.

R3 authority:

  1. 001B1 → 001B2 → 001B3 → bounded 001C gate exit.
  2. Approved GXC-C1..C5 v0.2 and GRX v0.2.

Implementation state:

  • R2 accepted implementation head: ca596c0.
  • R3 M1A–M1C: accepted.
  • M1D: conditional.
  • M1D remediation: pending review / unaccepted.