GENESIS AiX — BUILD 16 PUBLIC REVIEW CANDIDATE  ·  OPEN FOR TECHNICAL REVIEW — NOT PRODUCTION / NOT FINAL
Public Review CandidateBuild 16 · SIW / Canon Reader integrationReview guidepublic review deployment
FRONTIER INSPECTION PROGRAM — SITE REVIEW CANDIDATENOT A FROZEN INSPECTION RELEASESITE REVIEW CANDIDATE — NOT FROZEN / NOT RELEASED
VERIFY · freeze manifest pending

VERIFY

The intended verification surface: artifact identity, version, status, provenance, SHA-256 and accepted / conditional classification.

FREEZE MANIFEST — PENDING

The final package manifest and package hash do not exist. This page shows identities and hashes already recorded in the accepted FIP record, and describes what the freeze will generate.

Identities already recorded

Accepted identities

Identifier and hash only. The artifacts themselves are not published on this surface.

Artifact / identityClassRecorded standingFIP classProvenanceSHA-256 / commit
SIW-DM-001_v0.1.1.mdR2 normative authoritySIW-DM-001 v0.1.1 is the ratified R2 engineering baseline.ACCEPTEDManifest §2f0649f8d926cf3175abc12ca3ea31d6d48c54288f78d41c8d4ec19df7308bc8e
siw-authoritative.schema.v0.1.1.jsonR2 normative authoritySIW-DM-001 v0.1.1 is the ratified R2 engineering baseline.ACCEPTEDManifest §23b930f373514d30a1dd2582999c4a1e2ed5e283dc06e852919b0e9ef820251c1
SIW-DM-001_v0.1.1.pdfR2 normative authoritySIW-DM-001 v0.1.1 is the ratified R2 engineering baseline. The PDF was not byte-compared with the Markdown.ACCEPTEDManifest §2ada936cde17250735e8eb591566cdced188efef7b90dd227d037d17a69e7c02b
SIW-R2-RAT-058Later accepted R2 authorityAcceptance / ratification record: establishes gate and implementation standing; not a normative specification.ACCEPTEDManifest §34699bc06001e5635294d5d9114194876816cf61748dc5727a5a4d56437b70955
SIW-R2-SPRINT13-ACCEPT-001Later accepted R2 authorityAcceptance / ratification record: establishes gate and implementation standing; not a normative specification.ACCEPTEDManifest §35b7e58b838407963462feaeb1f1f202caaca98700df0db30c2052c5e130bf14a
Accepted R2 implementation headImplementation-state identifier — not an authority artifactAccepted R2 implementation head.ACCEPTEDManifest §3ca596c0b69b0f8ef324c327ff271f9d9310a7663
001B1 approvalR3 approved architectureArchitecture approval is not implementation acceptance.ACCEPTEDManifest §48009f0cd191c5865607ceea23d7fccfe1a8320ea359f1cb0fd0485ef4b340fbc
001B2 approvalR3 approved architectureArchitecture approval is not implementation acceptance.ACCEPTEDManifest §464ac339fd0c71feb2f1b2d42c80f18f4db9d9f7b354d28b166c5516ef0226954
001B3 approvalR3 approved architectureArchitecture approval is not implementation acceptance.ACCEPTEDManifest §4d97fa187aba8bd004ded55215ebf401d333e1a8cad4e68e593f3eb1e4be40385
001C gate exitR3 approved architectureArchitecture approval is not implementation acceptance.ACCEPTEDManifest §46358f83d10edb8b006c0e03a47f8faadeb66f6d595c8ecfa644d651ee547b13f

The FIP class chip maps the recorded standing to the FIP status vocabulary; the recorded-standing text is the authority. Identities, hashes and commit identifiers are copied from the accepted Specification Authority Manifest v0.1.2. The approved GXC v0.2 files retain PROPOSED headers (Manifest §8).

R3 implementation standing

R3 milestoneRecorded standingFIP classProvenanceIdentity
M1AM1A — ACCEPTEDACCEPTEDManifest §5No identifier is recorded in the accepted Manifest
M1BM1B — ACCEPTED, scopedACCEPTEDManifest §5No identifier is recorded in the accepted Manifest
M1CM1C — ACCEPTEDACCEPTEDManifest §5No identifier is recorded in the accepted Manifest
M1DM1D — CONDITIONALCONDITIONALManifest §5No identifier is recorded in the accepted Manifest

The accepted Manifest records standing, not identifiers, for M1A–M1D. The five M1D-related remediation branches are recorded in Manifest §6 as PENDING REVIEW / UNACCEPTED; they are not baselines, and nothing here points to a remediation branch.

FIP control artifacts

Identity and version — hash not yet recorded

ArtifactAccepted versionFIP classSHA-256
GAIX-FIP-001-SPECIFICATION-AUTHORITY-MANIFESTv0.1.2ACCEPTEDNot recorded — generated at freeze
GAIX-FIP-001-CLAIMS-NONCLAIMS-REGISTERv0.1.2ACCEPTEDNot recorded — generated at freeze
GAIX-FIP-001-KNOWN-LIMITATIONS-REGISTERv0.1.2ACCEPTEDNot recorded — generated at freeze
GAIX-FIP-001-THREAT-MODEL-AND-FAILURE-MODESv0.1.2ACCEPTEDNot recorded — generated at freeze
GAIX-FIP-001-00_START_HEREPacket 002 v0.1.1ACCEPTEDNot recorded — generated at freeze
GAIX-FIP-001-PACKAGE-ARCHITECTUREPacket 002 v0.1.1ACCEPTEDNot recorded — generated at freeze
Freeze

What the freeze will generate — none of it exists yet

FREEZE MANIFEST — PENDING

The final package is assembled from accepted baseline commits and artifacts, not from currently checked-out pending remediation branches.

  1. Verify every dependency's HEAD equals its pinned baseline commit (Manifest §5), and verify each specification hash.
  2. Assemble only entries that pass §3.
  3. Freeze generates:
    • a package version identifier (format fixed in the freeze record);
    • an artifact manifest;
    • SHA-256 per released artifact;
    • a whole-package hash where practical (SHA-256 over the manifest's sorted path<TAB>sha256 lines, and over a deterministic archive if one is produced; the method is recorded in the manifest);
    • the creation date;
    • the claim ceiling;
    • the accepted / conditional / pending classification of every artifact;
    • dependency identities (repository commits and specification hashes).
  4. Re-derive the manifest from the assembled tree and confirm identical hashes.
  5. After freeze the package is immutable. Corrections issue as a new version.
Verifier tooling

The R2 independent verifier CLI is a placeholder (LIM-017). It is not operational and is not relied on. Verification here means comparing identities and hashes against the manifest once it exists.