What does this topic answer?
Every asset has a common set of required information, while embodiment content includes only the parts needed for its intended use.
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.
Separate Root, Header, and Layer Requirements
Galatea 1.0 does not require every asset to populate every embodiment Layer. The root requires a Header and a reference profile; the Header then carries the shared required fields. Embodiment Layers appear only when a profile emits them, but once present they must at least provide data and measurement status.
| Location | Machine key | Requirement | Rule |
|---|---|---|---|
| Root | G68-HDR | Required | Galatea 1.0 Header |
| Root | reference_profile | Required | Reference Profile object |
| reference_profile | class | Required | R0 / AR / HR / PR |
| reference_profile | identifier | Required | Reference identifier |
| reference_profile | version | Required | Reference-profile version |
| reference_profile | artifact_mode | Required | boolean |
| reference_profile | origin_definition | Optional | Profile-defined origin / landmark description |
| Required | Optional |
|---|---|
| standard_version, asset_id, source_type, coordinate_system, unit, precision, rights_status, compatibility_level | time_base, content_hash |
| Layer / object | Required at root? | Minimum when present |
|---|---|---|
G-Mesh / R-Profile / S-Skin / K-Motion / P-Scent / L-View / C-Cal / RGT | No | measurement_status + data |
conformance | No | Preserves only conformance information actually evaluated / declared |
interoperability_mapping | No | Each mapping requires target_standard + relationship |
artifact_reference_notes | No | String array |