What does this topic answer?
Every sensory record needs basic identity, version, measurement status, provenance, and permission information; its purpose then determines whether S-Code or ISO-Taste content is required.
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.
Start with Shared Requirements
Whether a record belongs to S-Code, ISO-Taste, or a mapping between them, it first preserves a shared set of fields. Role-specific blocks are added afterward, and an unperformed conformance check is marked explicitly rather than implied by omission.
| Reader purpose | Machine key |
|---|---|
| Record identity | identifier |
| Packet version | version |
| Registry version | registry_version |
| System role | system_role |
| Measurement / estimate / inference status | measurement_status |
| Provenance | provenance |
| Rights and consent | rights_consent |
| Conformance record | conformance |
| system_role | Required content | Condition |
|---|---|---|
s-code | s_code | At least one S-Code family is populated |
iso-taste | iso_taste, reference_profile, code_registry_ref | At least one of public_code or structural_code is present |
mapped-profile | s_code, iso_taste, mapping | mapping must be non-empty |
| Rule | Machine value | Meaning |
|---|---|---|
| S-Code block version | standard_version = 1.0 | S-Code preserves its own version |
| ISO-Taste block version | standard_version = 1.0 | ISO-Taste preserves its own version |
| Conformance not yet checked | not_evaluated | Must be recorded explicitly in conformance rather than omitted |