File Genesis governs the life of source files, scripts, documents, and data artifacts. A canonical header says what a file is and who owns it; scan and index records make it findable; provenance survives movement, renaming, and retirement.
07IDENTITY HEADER FIELDS
03WALKTHROUGH CHECKS
▣
Public learning boundary. This page explains the lifecycle and the separation between discovery and registration. It does not scan a device, enumerate private files, display repository contents, mint an FR-ID, write a registry row, move a file, or change any authorization.
A scan discovers and classifies. An index organizes. Canonical registration is a separate governed act.
1. Follow the governed lifecycle
Select a stage to see what evidence it creates and the boundary it must preserve.
01
Identify · Establish file identity first
Before interpreting content, determine the stable Script ID, canonical path, purpose, owner, tags, creation date, and last-review date.
Evidence createdA human-readable identity contract attached to the artifact.
Boundary preservedA filename or folder location alone is not canonical identity.
2. Match the three consumer checks
The AIAGF walkthrough presents the protocol in three bounded questions.
I · IDENTIFY
Read the file identity header
Confirm stable identity, owner, purpose, and review date before interpreting the contents.
II · TRACE
Trace provenance and lifecycle
Creation, movement, renaming, and retirement retain history through path updates, tombstones, and regenerated indexes.
III · VERIFY
Verify registry and index status
Check scan coverage and registered identity separately. One does not silently imply the other.
Discovery is not registration. The scanner finds metadata and gaps. The index builder produces navigational indexes. Neither writes a canonical Function Registry identity; allocation and registration follow their own governed path.
Continue the matched topic
Walk File Genesis, or inspect the gated protocol reference
The AIAGF walkthrough explains identity, provenance, and verification for consumers. The live OQS Protocol Library contains the operator-side governed reference.