Migration v9 → v10 (additive)
This is an operational adoption, not a rewrite of existing logical states.
- Retain v9 Logical Artifacts and immutable State Snapshots, including their existing commitments.
- Create
.kristal/node.jsonwith a persistentnode_id. - Add one or more host bindings under
.kristal/bindings/. - Declare hosted capabilities in
.kristal/capabilities.json. - Add a
kristal_directoryif node discovery is needed; keep private mappings private. - Continue verifying v9 logical/state commitments. Qualify the new host/publication contracts separately.
V10 ADOPTION != V9 REWRITE
HOST MOVE != LOGICAL REVISION
For the managed GitHub path, use the declarative GitHub-Reference-Profile-v10 and Workflow-GitHub-v10. For reader synchronization, use the exact derived GitHub-Read-Surfaces-v10 contract; Sync is neither Publication nor Activation.
Normative source: Framework spec/v10/Migration-v9-to-v10.md.