What does this topic answer?
Each asset preserves its version and compatibility information. New versions may add capabilities, but they cannot rewrite what older data originally meant.
Story relation: The story directly uses the Galatea protocol and related embodiment technology, providing a narrative anchor for this standard. Algorithmic Love and the Centenarian Skin
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.
Reader Principle: New Versions May Add Capability, Not Rewrite Old Meaning
The first Aistory in-world Galatea Standard specification is 1.0. Assets, reference profiles, and compatibility levels preserve their own version information. If a later version changes a Layer, profile, renderer contract, or tolerance profile, the change is expressed through an explicit version upgrade and migration note rather than backfilling meaning that the older reference never contained.
| Location | Machine key / identity | Role |
|---|---|---|
| G68-HDR | standard_version | Galatea specification version used by the asset; fixed to 1.0 in the 1.0 schema |
| G68-HDR | compatibility_level | Preserves version / renderer-contract compatibility information |
| reference_profile | version | Reference Profile’s own version |
| Header | content_hash | Identifies a content version when emitted by the reference |
| Machine identifiers | G68-HDR / G-Mesh / R-Profile / S-Skin / K-Motion / P-Scent / L-View / C-Cal / RGT | Retain existing meaning until a migration decision |
Migration Boundary
The public Galatea 1.0 JSON Schema does not define a separate migration object. The current specification requires future cross-version changes to be recorded through explicit version upgrades and a migration note, especially for Layer, profile, renderer-contract, or tolerance-profile changes; the process must not rewrite the original meaning of an older reference.