What does this topic answer?
The machine interface provides a shared data format, a complete example, and a controlled vocabulary registry so implementers can exchange and validate data consistently.
Story relation: The story directly uses ISO-Taste, providing a concrete narrative anchor for the sensory standards. Plato's Chicken and the Tyranny of the Senses
Authority links: System overview · Sensory JSON Schema · C-772 Example
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.
Developer / Machine Specification
The material below is the implementation contract. General readers only need the distinction: the Schema defines the data shape, the Example demonstrates a complete mapped-profile, and the Registry governs exchangeable controlled vocabulary and codes.
| Resource / rule | Normative content |
|---|---|
| Schema | Draft 2020-12 Sensory Family JSON Schema |
| Example | C-772 mapped-profile example |
| Registry | Sensory Registry 1.0 |
| Registry governance | unit, time_context, descriptor_ref namespaces, structural codes, code lifecycle, migration records |
| Schema enforcement | role-specific blocks, Reference Profile, Calibration Profile, Rights Matrix, mapping pairs, and three-layer conformance |
Executable Validation
CI validates the contract with a pinned Ajv CLI. The normative example and valid fixtures must pass, while fixtures that deliberately violate the contract must be rejected.
| Test type | Expected result | Case |
|---|---|---|
| Normative example | accept | C-772 mapped-profile |
| Valid fixtures | accept | Conforms to the role-specific contract |
| Invalid fixture | reject | Missing role-specific block |
| Invalid fixture | reject | Illegal measurement_status |
| Invalid fixture | reject | Missing standard_version |
| Invalid fixture | reject | Empty mapping |
| Invalid fixture | reject | Incomplete Rights Matrix |