What does this topic answer?
IAGA checks in stages whether data can be read, refers to the right thing, carries valid meaning, and satisfies rights and research conditions; passing one stage does not mean all stages pass.
Story relation: This story can be used to understand mixed affect with several simultaneous components. It is a reading example, not a claim that the chapter directly uses the name IAGA. Causal Stack Overflow and the Dirty Golden Age
Authority links: System overview
If you only need the worldbuilding context, you can stop here. The sections below contain formal definitions, fields, governance, and implementation details for deeper reference.
Core Principle
IAGA conformance is not one pass/fail judgment. Structural validity, reference integrity, semantic governance, rights/provenance, and research governance are separate checks; passing an earlier layer does not automatically establish a later one.
CL1–CL6
The six conformance levels answer different questions. CL6 remains undefined and locked in the current IAGA 1.0 RC.
| Level | Formal name | What it checks |
|---|---|---|
CL1 | Parse Conformance | Whether the structure is valid. |
CL2 | Referential Conformance | Whether IDs and references resolve. |
CL3 | Semantic Governance Conformance | Whether cross-record semantic rules hold. |
CL4 | Rights / Provenance Conformance | Whether rights and provenance rules hold. |
CL5 | Research Conformance | Whether Target-Native, R5, and interoperability research governance hold. |
CL6 | Production Conformance | Undefined / locked in the current IAGA 1.0 RC. |
Validation Pipeline
Validation proceeds in a fixed order. The Interop Bridge runs only when cross-system exchange is required, and Migration runs only when a version transition occurs.
Any mandatory ERROR should fail closed. A validator must not mutate the Core or add a Dimension merely because a packet appears unusual.
P1–P8 Validation Pipeline
P1Structural ParseP2Referential IntegrityP3Semantic GovernanceP4Rights / ProvenanceP5Research GovernanceP6Interop BridgeRuns only when exchange is required.P7MigrationRuns only when a version transition occurs.P8ValidatorReport / ConformanceReport
Scope and Limits
Passing CL5 establishes only research-layer conformance. It does not imply legal authorization, reconstruction permission, a new Dimension, a new Core axis, or first-person equivalence. Conformance answers which rule layers are satisfied; it does not replace other governance decisions.