What does this topic answer?
The machine format can preserve qualitative affect. Numeric values are used only when their scale and measurement source are explicitly stated.
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 · IAGA JSON Schema · IAGA Example Payload
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
The machine-readable projection must faithfully reflect frozen IAGA 1.0 semantics. Reader-display numbers must not be treated as engineering units, and no universal numeric Core scale may be reintroduced.
Developer / Machine Contract
The public exchange contract is structured below. Formal machine keys retain their names while reader explanations remain separate from implementation fields.
| Contract item | Formal content / rule |
|---|---|
schema identity | IAGA-AFFECT-PACKET |
14D factors | Preserves generation/context factors. |
12D Core | Preserves the resulting affective structure. |
temporal records | Preserves temporal change. |
bindings | Preserves target/source/component relations. |
semantic / action records | Preserves semantic and action-related records. |
calibration reference | Preserves personal calibration reference. |
residual | Preserves residuals that are not fully mapped. |
provenance | Preserves provenance. |
rights | Preserves use permissions and rights. |
| Machine field | Rule |
|---|---|
qualitative_state | A valid normative representation that may stand on its own. |
value | Optional; no universal Core minimum / maximum may be assumed. |
value_scale_ref | Required whenever a numeric value exists. |
measurement_provenance_ref | Required whenever a numeric value exists. |
Validation
Machine validation covers more than JSON structure: it also checks conditional numeric governance, referential integrity, semantics, rights/provenance, and interoperability rules.
Example payloads should prefer qualitative representation; numeric values are added only when a declared scale is intentionally demonstrated.
| Check | Scope |
|---|---|
schema structure | Data structure. |
conditional numeric governance | Conditional rules when numeric values are present. |
referential integrity | Whether references resolve. |
semantic governance | Cross-field and cross-record semantic rules. |
rights / provenance | Use permissions and provenance. |
interop rules | Cross-system interoperability rules. |
Scope and Limits
The machine-readable contract is a stable exchange surface rather than a complete copy of every internal research registry. Schema validity does not prove first-person identity equivalence and is not authorization for any use.