What does this topic answer?
Embodiment data keeps its content, confidence, and provenance, and format conversion cannot make uncertain data appear more certain than it was.
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.
Start with the Shared Rule
Galatea Layers may contain different kinds of embodiment data, but they follow one common contract: the data itself and its measurement status are required, while confidence, provenance, and measurement context are preserved when available. A public reference emits only the Layers actually present in its profile, and format conversion cannot turn estimated data into measured data.
| Reader purpose | Machine key | Schema rule |
|---|---|---|
| Actual Layer content | data | Required; object |
| How the data was obtained | measurement_status | Required; measured / estimated |
| Confidence | confidence | Optional; 0–1 |
| Traceable provenance | provenance | Optional; uses the provenance object |
| Unit | unit | Optional |
| Coordinate system | coordinate_system | Optional |
| Precision / uncertainty representation | precision | Optional; string or number |
| Machine key | Role |
|---|---|
source_basis | Source basis |
source_id | Source identifier |
method | Acquisition / creation method |
instrument_id | Measurement instrument identifier |
calibration_record_id | Calibration record identifier |
Layers Using This Contract
The shared contract applies to G-Mesh, R-Profile, S-Skin, K-Motion, P-Scent, L-View, C-Cal, and RGT. Their data payloads differ, but measurement status and provenance cannot be upgraded by format conversion.