Historical v10 reference: this page documents the frozen v10 hosted-network baseline. The current proposed Framework draft is v11 11.0.0-draft.4; see Home, Kristal-v11 and Status-v11. Its semantic identity/dictionary contracts are additive, not a replacement for historical v10 hosting.
Hosted Kristal Network — Architecture v10
V10 adds a hosted-network plane above the unchanged v9 semantic state plane.
SEMANTIC PLANE — v9
Logical Artifacts → immutable State Snapshot
│
pinned commitments
│
materializations / exchange
│ referenced by
─────────────────────────────┼────────────────────────────────
HOSTED-NETWORK PLANE — v10
Node Manifest
/ \
Host Binding(s) Directory link(s)
│ │
publication/activation discovery
│
attestations / mirrors
Components and ownership
| Component | Owns / describes | Does not define |
|---|---|---|
| v9 State Snapshot | immutable logical membership | repository or Release URL |
| v10 Node Manifest | operational node_id, node role(s) |
semantic contents |
| v10 Host Binding | concrete location/profile/host surfaces | Logical Commitment |
| v10 Publication Record | exact state and retrievable verified bytes | activation or epistemic authority |
| v10 Directory | mutable node/binding discovery | exact v9 federation membership |
| GitHub read surface | verifiable derived reading projection | semantic state or immutable publication |
A repository may host a node, but a repository is not a Kristal node. A collection node may expose multiple independently committed Kristals; one node may have multiple bindings/mirrors.
Start with Nodes-and-Collections-v10, Host-Bindings-v10, Publication-and-Discovery-v10 and Directories-and-Federation-v10.
Normative source: Framework spec/v10/Architecture.md.