What does this topic answer?
S-Code / ISO-Taste separately checks schema, reference, and experiential conformance.
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.
Schema Conformance
First ask: is the data structure itself valid? This layer checks format only; it does not establish reference or experiential conformance.
| What is checked | Machine field / value |
|---|---|
| JSON Schema, required fields, and data types | schema |
| Role-specific conditions | system_role |
| Assessment result | pass / fail / partial / not_evaluated |
Reference Conformance
Second ask: is this record actually the reference it claims to be? This layer checks code, version, and reference identity rather than a person's subjective experience.
| Machine key | Preserves |
|---|---|
basis_ref | Assessment basis |
measurement_status | How the data was obtained |
provenance | Origin |
tolerance_profile_ref | Applicable tolerance profile |
Experiential Conformance
Third ask: under the declared tolerances and applicable calibration, does the actual sensory output match the target profile? This layer is assessed independently; passing the first two layers cannot answer it automatically.
| Machine key | Preserves |
|---|---|
tolerance_profile_ref | Tolerance declared by the reference |
calibration_profile_ref | Applicable calibration profile |