This section collects the formal in-world standards used to describe affect, sensory experience, and embodiment, as reference material for understanding the stories behind them.
If this is your first visit, start with the four main entries below: affect, sensory experience, embodiment, and affective reconstruction. No data-format knowledge is required.
Interoperability
A Common Technical Language
Aistory's standards cover different domains while preserving traceability, calibration, versioning, and interoperability boundaries.
When a story needs to state what a person is feeling, what sensory effect a food should produce, or how an embodied form should be recorded and reproduced, these standards let different systems exchange those descriptions consistently and traceably. IAGA covers affect; S-Code / ISO-Taste covers sensory experience; Galatea Standard covers embodiment; Elysium uses affective targets under rights and safety constraints for reconstruction. These are in-world Aistory technical settings, not claims of real-world ISO, regulatory, clinical, or industry certification, and none is equivalent to a person’s complete first-person experience, legal identity, or subjective continuity.
System Families
Three Schema-Backed System Families
Affect
IAGA — Iris Affective Gamut Atlas
IAGA is a shared description system for recording and exchanging affective states, so characters and machines can state how an emotion formed, what state is present, and how it changes over time.
S-Code describes sensory events as they unfold; ISO-Taste provides comparable references and codes, turning “what this should taste or feel like” into data that can be exchanged and checked.
Galatea Standard describes how an embodied form can be recorded, compared, and reproduced, including morphology, motion, and other verifiable features; looking the same is not proof of personhood identity.
Elysium is not a fourth encoding standard. It consumes an IAGA target and uses calibration, current state, rights, and safety constraints to run a closed reconstruction loop.
Standard status: Aistory in-world theoretical standards for representing and composing facial, bodily, motion, and contact information through explicit version, provenance, spatial, temporal, and authority bindings.
Standard
Face Code
Represents facial reference geometry, reconstruction-relevant evidence, provenance, and confidence as a versioned facial reference.
Standard
Expression Code
Represents time-varying facial actions relative to a Face Code reference. It describes facial movement rather than asserting a person's internal emotional truth.
Standard
Body Code
Represents body reference geometry, proportions, articulated structure, morphology, provenance, and confidence at a declared reference epoch.
Standard
Body Motion Code
Represents time-varying body articulation, trajectory, and optional dynamic deformation relative to a Body Code reference.
Standard
Touch Code
Represents time-varying physical contact and haptic interaction between a coded body and itself, other bodies, objects, or the environment.
Standard
Whole-Person Human Reconstruction Stack
Integrates Face Code, Expression Code, Body Code, Body Motion Code, and Touch Code through explicit subject, spatial, temporal, version, authority, provenance, and confidence bindings.
Shared Data Contract
Shared Data Contract
These shared fields answer a simple set of questions when one system receives data from another: what version is this, where did it come from, how certain is it, and is this use actually permitted? The field names below remain available for readers and implementers who want the technical details.
Identifier — identifies a data object, reference, or specification instance.
Version — states the specification and data version.
Provenance — preserves source and traceability.
Measurement Status — distinguishes directly measured and estimated data.
Calibration Context — records the conditions required for measurement or reproduction.
Confidence / Residual — expresses confidence, error, or remaining difference.
Rights / Consent — records purpose-bound authorization, consent, revocation, and permitted use for a person or lawful rights holder; one consent field never implies unlimited permission.
Interoperability Mapping — describes how one standard maps to another.
Cross-system mapping must not upgrade source status, measurement status, or rights / consent state. Public records contain only fields that carry content.
Aithos Law Boundary
Relationship to Aithos Law
A technical standard can describe data and reconstruction conditions, but it cannot create consent, personhood identity, governing authority, or permission to modify another person.
Legal Subject: Person. Rights protections across the three systems are species- and substrate-neutral. HR (Human Reference) is a source class, not a rule that only humans receive data, mental, embodiment, or procedural protection. Whenever data identifies or directly affects a person, the applicable personhood rights remain in force.
Technical Conformance ≠ Lawful Use. Schema validity, reference reproduction, or physical tolerance does not itself authorize use. Recording, calibration, model training, sale, reconstruction, sensory or affect induction, embodiment replication, and modification are separate permission surfaces; consent to one does not imply consent to the others.
Data Conformance checks whether data follows the specification. Reference Conformance evaluates reproduction under declared reference conditions. Physical / Experiential Conformance is evaluated against the applicable conditions and tolerances declared by a reference profile. Every conformance result is scoped to a version and declared use context.
Reference Profiles
Reference Profiles
Shared reference types include R0 synthetic neutral, AR artifact, HR human with consent/provenance, and PR personal. HR only identifies human-source data; Aithos and other nonhuman persons remain protected by the same personhood-rights framework. A reference class only identifies what is being used for comparison; it does not automatically change measurements, source status, personhood status, or permission to use the data.
Developer / Machine Resources
Developer and Machine-Readable Resources
These interfaces are for implementers, validators, and machine readers. General readers do not need to understand JSON Schema before reading the worldbuilding sections above.
Machine-readable resources provide the public data contracts and reference examples for the three system families. Human pages and machine-readable surfaces share the same version and interoperability semantics. The human reconstruction standards are currently represented as textual specifications.
Cross-System Example
Cross-System Composition
A single experience can reference an IAGA affective coordinate, an S-Code sensory time curve, and a Galatea Standard embodiment reference at the same time. This allows systems to exchange what affect should be presented, what sensory result should be produced, and through what embodiment. The combination remains a verifiable description rather than a copy of complete subjective consciousness.