Migration from v7 to v8
Migration is optional because v8 is additive. A valid v7 Kristall can be used unchanged by a v8 processor.
Recommended adoption
- keep v7 registries and Mesh unchanged;
- declare v8 capability metadata;
- create external lexical Kristals for desired languages/domains;
- define deterministic lexical stack policy;
- build rebuildable query indexes from canonical artifacts;
- expose typed KQP query with pagination/completeness;
- add AI context compilation and optional compact encoding;
- add semantic fingerprint profiles only where they provide value.
Existing v7 labels may seed a lexical worklist or fallback lexicon. Extracting them is a convenience operation, not a semantic migration.
No forced rewrite
Do not:
- convert every v7 label before using v8;
- mint new semantic IDs for existing v7 identities;
- replace inherited hashes with semantic fingerprints;
- make query indexes or AI bundles canonical.
Production adoption
Introduce derived indexes and AI query paths as read-side capabilities first. Canonical mutation/admission remains governed by existing source contracts until explicitly upgraded under a separate write protocol.