What does this topic answer?
Every Galatea asset keeps basic identity, version, source, measurement conditions, rights, and compatibility information so later data remains traceable.
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.
The Header Is the Asset’s Shared Identity Record
The Header answers the shared questions first: which standard version applies, which asset this is, what its source type is, which coordinates and units it uses, how precision is represented, and what rights and compatibility state apply. A time base and content hash are present when the data needs them.
| Reader label | Machine key | Schema requirement | Normative value / role |
|---|---|---|---|
| Standard version | standard_version | Required | 1.0 |
| Asset identifier | asset_id | Required | Non-empty string |
| Source type | source_type | Required | Non-empty string; e.g. synthetic, artifact, or human-reference class |
| Coordinate system | coordinate_system | Required | G68-RH-XYZ-v1 |
| Geometry unit | unit | Required | mm |
| Precision policy | precision | Required | UNCERTAINTY_DRIVEN_RECORD |
| Time base | time_base | Optional | Temporal basis for dynamic data such as K-Motion |
| Rights status | rights_status | Required | Rights and use-restriction state of the reference |
| Content hash | content_hash | Optional | Preserved when emitted by the reference |
| Compatibility level | compatibility_level | Required | Version / renderer-contract compatibility information |