Embodiment Standard
Galatea Standard
Galatea Standard lets different systems describe how a body looks, moves, and is observed while preserving the comparison conditions and rights boundaries needed for reproduction.
First-time readers can begin with why a photograph is not enough; the specification index and developer resources below can be skipped at first.
Reader Layer
In 30 Seconds: One Photograph Is Not a Complete Identity or Self
The same face can look different under another lens, light, angle, or movement, so the standard must preserve more than appearance alone and must also record the conditions needed for a fair comparison.
A portrait is changed by angle, lens, lighting, exposure, distance, camera, and image processing. Galatea Standard therefore records more than what a face “looks like”: form, proportions, surfaces, motion, scent, capture / viewing conditions, provenance, and rights, so systems compare the same thing instead of treating two similar-looking images as proof of the same person.
Story example: Algorithmic Love and the Centenarian Skin uses the Galatea protocol and related embodiment technology to show a life in which embodied appearance is continuously computed, corrected, and maintained.
Specification Index
Specification Topics
The topics below are the deeper specification. You can skip them for the worldbuilding overview and open a topic only when you need formal definitions or implementation details.
Scope
Galatea Standard defines how embodiment references are exchanged and compared without treating appearance as proof of legal personhood identity or subjective continuity.
Read full specification →02Three Conformance Concepts
Identical data, visually matching renders, and a physically conforming embodiment are three different kinds of “same” and must be judged separately.
Read full specification →03Layers 0–8
Galatea keeps form, proportions, surfaces, motion, scent, viewing conditions, calibration, and rights in separate layers so unlike kinds of data are not mixed together.
Read full specification →04Layer Data Contract
Embodiment data keeps its content, confidence, and provenance, and format conversion cannot make uncertain data appear more certain than it was.
Read full specification →05Header Field Dictionary
Every Galatea asset keeps basic identity, version, source, measurement conditions, rights, and compatibility information so later data remains traceable.
Read full specification →06Required Fields
Every asset has a common set of required information, while embodiment content includes only the parts needed for its intended use.
Read full specification →07Coordinate, Unit, and Precision Boundary
Galatea describes geometry in millimeters with a fixed three-dimensional coordinate direction and records uncertainty separately so measurement precision is not mistaken for physical truth.
Read full specification →08Reference Profiles
Galatea separates synthetic neutral references from artwork references; artwork mode describes only information that can be observed or explicitly defined in the work itself.
Read full specification →09Calibration, Measurement, and Viewing Conditions
Measurement tools, lighting, lenses, viewing position, and calibration conditions all affect comparison, so those conditions must be preserved together.
Read full specification →10Conformance
Data, reference-render, and physical-embodiment conformance each have separate judgments and declared scope.
Read full specification →11Rights, Consent, and Provenance
Capture, training, display, replication, modification, mixing, and instantiation are separate permission surfaces, and technical-asset ownership does not become ownership of a new person.
Read full specification →12Interoperability
Galatea can receive affect-expression needs from IAGA and sensory references from S-Code / ISO-Taste without changing the original data’s provenance or permissions.
Read full specification →13Scope Limits
An appearance reference is not personhood identity, consciousness, memory, or first-person continuity; observed, estimated, and verified data must also remain distinct.
Read full specification →14JSON Schema and Reference Example
The machine format fixes version, geometry units, coordinate direction, and uncertainty recording so different implementers can interpret the same embodiment data.
Read full specification →15Version, Compatibility, and Evolution
Each asset preserves its version and compatibility information. New versions may add capabilities, but they cannot rewrite what older data originally meant.
Read full specification →Developer / Machine Resources
Developer and Machine-Readable Resources
These Galatea Standard 1.0 interfaces are for implementers and validation tools; general readers do not need JSON Schema knowledge first.
Galatea JSON Schema
Formally defines how an embodiment reference records form, motion, provenance, permissions, calibration, and conformance information.
Open Schema →ExampleNeutral Reference Example
A neutral embodiment-reference example showing how data is organized, compared, and validated.
Open Example →