Coordinates & Applicability
v9 compatibility note: This page documents the retained v6 portable-state semantics. V9 preserves the contract as a frozen substrate and may wrap/project it through Logical Artifacts without redefining it. See Version-Stack-v6-v7-v8-v9.
Kristal v6 distinguishes where an assertion sits in the domain from where the assertion applies.
Coordinates
coordinates are the domain geometry of an assertion.
Examples:
- source/target biological layer;
- source/target scale;
- recipe tradition or variant family;
- vehicle operating condition;
- technological axis;
- taxonomic rank;
- observation condition;
- process phase.
Coordinates can form a hierarchy, matrix, graph, multiplex, causal network or other geometry. They are not necessarily “minor qualifiers”.
Applicability
applicability is the envelope in which the assertion should be interpreted as applicable.
Typical dimensions include:
- domain / subdomain;
- jurisdiction;
- time window;
- environment;
- language;
- tenant/context.
Examples:
- a Quebec administrative rule in a specified effective period;
- a diagnostic relation for one model year and powertrain;
- a maintenance rule before freezing conditions;
- a botanical occurrence in a territory and time interval.
Same concept, different role
Time can be a coordinate or applicability constraint.
A historical occurrence date describes the content. A regulation effective period describes when the rule applies.
Do not collapse these just because both are temporal.