Migration: v5 → v6
Kristal v6 is a breaking semantic upgrade. The active vocabulary changes from epistemic-specific field names to domain-neutral abstractions.
Main mapping
| v5 | v6 |
|---|---|
| Structured Epistemic State | kristal_state |
certainty_level |
valuations[] |
uncertainty |
valuation value state / method / typed value |
qualifiers |
coordinates |
scope |
applicability |
| certainty summary | valuation summary |
| implicit data type | record_role where useful |
| implicit automation assumptions | explicit actionability |
Important semantic change
Do not migrate by replacing:
high → 0.8
or:
unknown → 0
Instead define the dimension and value semantics explicitly.
Working / Reference
The old Working/Reference distinction should be understood through artifact lifecycle/status, validation and authority recognition rather than as two universal artifact classes that duplicate the canonical state.
Exchange / Runtime Pack
Existing Exchange and Runtime Pack consumers can remain as legacy adapters or derived materializations, but new domain models should not make them the canonical truth layer.
Migration strategy
- identify the v5 meaning of
certainty_levelper assertion family; - define explicit valuation dimensions;
- migrate qualifiers to domain coordinates;
- migrate scope to applicability;
- add record roles only where the role is actually known;
- add actionability only where policy explicitly defines human/automation boundaries;
- recompute canonical identities/hashes;
- rerun validation and reader/projection tests.