What does this topic answer?
Measurement tools, lighting, lenses, viewing position, and calibration conditions all affect comparison, so those conditions must be preserved together.
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.
Why Can the Same Geometry Still Look Different?
Because a comparison is not determined by geometry alone. Lighting, camera, viewpoint, renderer, measurement instruments, and calibration error can all change the output. Galatea therefore preserves measurement / calibration conditions separately from viewing / capture conditions so environmental differences are not mistaken for differences in embodiment data.
| Layer / field | What it preserves | Reader interpretation |
|---|---|---|
C-Cal | Measurement instruments, calibration, error, and conformance record | Whether the measurement environment is traceable |
L-View | Lighting, camera, viewing position, and capture conditions | Whether viewing conditions are comparable |
conformance.decoder_renderer_id | Declared decoder / renderer used for comparison | Renderer differences cannot automatically be treated as geometry differences |
conformance.tolerance_profile_id | Declared tolerance profile | Physical conformance needs an explicit tolerance basis |
Boundary of Reference Render Identity
Reference Render Identity is comparable only when the decoder / renderer and viewing conditions are sufficiently defined. When those conditions differ, Galatea does not allow a visual difference to be attributed directly to geometry.