What does this topic answer?
One shared record keeps identity, version, measurement status, and provenance while S-Code sensory events and ISO-Taste reference data remain separate.
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
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.
Core Principle
A sensory packet first preserves shared identity, version, measurement status, provenance, and permissions, then branches by data role into S-Code, ISO-Taste, or a mapping between them. This keeps common context together without collapsing sensory events and reference data into one object.
| Reader purpose | Machine key | Role |
|---|---|---|
| Which record is this? | identifier | Packet identity |
| Which packet version is this? | version | Packet version |
| Which controlled vocabulary / code registry applies? | registry_version | Registry binding |
| What role does this record play? | system_role | Distinguishes S-Code, ISO-Taste, or mapped-profile |
| Was the data measured, estimated, or inferred? | measurement_status | Preserves epistemic status |
| Where did the data come from? | provenance | Preserves traceable origin |
| How may it be used? | rights_consent | Preserves rights and consent limits |
| Data role | Machine structure | Required content |
|---|---|---|
| S-Code sensory event | s_code | T / O / X / M / P / H / A / V / U |
| ISO-Taste reference | iso_taste | public_code / structural_code, reference_profile, cultural / regional context, and calibration notes |
| Cross-system mapping | mapped-profile | Contains s_code, iso_taste, and at least one mapping |
| Conformance result | conformance | Separate schema, reference, and experiential assessments; one passing layer does not imply another |