Skip to content

Host Bindings — v10

A kristal_host_binding connects a stable Kristal node_id to a concrete host. Hosting metadata is replaceable and must not redefine the v9 state.

The generic binding carries a stable binding_id, host profile/version, account scope, primary host resource and optional source, publication, activation, materialization, attestation, automation and discovery surfaces.

node_id ─── binding A → GitHub repository
       ├── binding B → object-storage mirror
       └── binding C → offline archive

Rules

  • No reusable credentials (tokens, keys or passwords) inside a Host Binding.
  • Host-specific repository paths, URLs, branch names and release IDs are not included in v9 logical/state commitments unless a domain contract explicitly defines them as logical data.
  • Rehosting or mirroring alone does not create a logical revision.
  • kristal.host/github/1.0 is an optional reference profile, not the only conforming host.

See GitHub-Reference-Profile-v10, Security-and-Confidentiality-v10 and Compatibility-v9-v10.

Normative source: Framework spec/v10/Host-Bindings.md.