What does this topic answer?
One IAGA record keeps the present affect, change over time, linked people or objects, meaning, uncertainty, provenance, and permissions together in a traceable form.
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 Example Payload · Version, Compatibility, and Target-Native
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
An ordinary IAGA packet must preserve enough structure to describe affect, context, interpretation limits, provenance, and rights rather than only an emotion label or an unexplained numeric vector.
Packet Anatomy
The primary schema identity is IAGA-AFFECT-PACKET. The table separates core records from records included when needed.
| Class | Formal record | Role |
|---|---|---|
| Core | PacketHeader | Packet identity and version. |
| Core | ExperiencerRecord | Experiencer data. |
| Core | EmotionEpisode | Affective episode. |
| Core | FactorRecord | Formation context / factors. |
| Core | CoreState12D | 12D resulting state. |
| Core | ProvenanceRecord | Provenance. |
| Core | RightsEnvelope | Use permissions and rights. |
| As needed | EpisodeGraphEdge / AxisBinding / TemporalRecord | Relations, bindings, and time. |
| As needed | SemanticRecord / ActionTendencyRecord | Semantics and action tendency. |
| As needed | CalibrationProfile / ResidualRecord / CrossReference | Calibration, residuals, and cross-references. |
| Information | Rule |
|---|---|
| annotation perspective | Preserves the attribution perspective. |
| confidence | Preserves uncertainty. |
| valid time | Preserves validity time. |
| target/source refs | Preserves directionality. |
| usage intent | Preserves intended use. |
| IAGA_NATIVE | Must not fabricate a TargetNativeState for structural symmetry. |
Scope and Limits
An affective packet is not a reconstruction recipe and is not proof of first-person identity equivalence.
Recording permission does not automatically create training, public-display, reconstruction, or induction permission; a semantic label is not required for packet validity.
Technical Example / Reader Interpretation
Successor-Continuity Ambivalence remains ordinary IAGA because target asymmetry between successor and current self, simultaneous gain/loss, and mixed affect are representable through the existing Core, bindings, and semantic layer. A posthuman subject matter does not itself require Target-Native topology.