Skip to content

Examples & Archetypes

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 domains vary, but many share recurring reasoning shapes.

Archetype Typical valuation dimension Example domains
formal proof / justification closure mathematics
diagnostic support of competing hypotheses automotive, software, mineral identification
pathway applicability of transitions/rules education, business startup
identity constitutive importance recipes, musical styles
maintenance intervention necessity buildings, industrial assets
taxonomic acceptance/classification botany, paleontology
attribution attribution strength art, archaeology, archives
compatibility constraint satisfaction engineering, parts, software
historical documentary robustness history of technology
multiscale relation across layers/scales human body

Examples

Recipes

valuations[] can encode constitutive necessity of an ingredient while evidence separately explains why that interpretation is supported.

Automotive diagnosis

Symptoms, tests and observations support or contradict causal hypotheses. A DTC is evidence; it is not automatically the failed part.

Quebec business pathway

Official obligations are authoritative constraints; project facts are observed state; local business policies are organizational rules. Applicability derives the relevant institutional path.

Botany

Taxonomic acceptance and geographic occurrence confidence are different valuation dimensions. Competing taxonomic circumscriptions can coexist rather than being flattened.

Home maintenance

Season/climate, building component, observed condition and intervention necessity are separable. Manufacturer guidance and legal requirements remain distinct authority channels.