Agents
How AI agents can use Domino Compass as a deterministic key runtime — reproducible identity and key hierarchies without a cloud account, custodial wallet, or opaque recovery service.
Determinism is the point. Domino Compass turns physical entropy into a reproducible 256-bit secret and a hardened BIP32 derivation path. An agent that consumes the runtime gets the same keys from the same recipe every time — no state to lose, no service to trust.
What agents can do
Reproduce identity from a recipe
An agent holding a recipe (the marked domino set + compass board + derivation path) can regenerate the exact same key hierarchy on demand. Identity is a function of physical reality, not a stored secret.
Derive scoped subkeys
From a single master secret, agents derive hardened BIP32 child keys per capability — one key for signing, one for encryption, one per service. Compromise of one never exposes the rest.
Verify without custody
An agent can verify a public key, address, or capability fingerprint against a recipe without ever holding the private material — watch-only operation stays reproducible.
Operate offline
The runtime is entirely offline. Agents that must not touch a network (air-gapped signing, cold storage orchestration) can run the derivation locally with no egress.
Agent integration surface
| Capability | What an agent gets | Boundary |
|---|
recipe → secret | Deterministic 256-bit secret from physical entropy | private never leaves the runtime |
secret → BIP32 path | Hardened derivation path for key hierarchies | private derived locally |
path → pubkey/address | Public identity + capability fingerprints | public safe to share |
recipe → verify | Watch-only reproduction of a known key | public no custody |
Agent safety rules
- Never generate entropy for key material — the ceremony is physical; an agent must not fabricate the secret.
- No network egress — the runtime is air-gapped by design; agents must not exfiltrate derived material.
- Keep the recipe, not the secret — the durable artifact is the recipe, which reproduces the key; the secret itself is ephemeral.
- Scope subkeys per capability — derive a fresh hardened child per service so a compromise is contained.
Example agent workflow
# 1. Load the recipe (physical entropy description)
recipe = load_recipe("domino-set-7 + compass-board-2 + path m/44'/0'/0'")
# 2. Reproduce the secret deterministically
secret = runtime.derive_secret(recipe) # same every time
# 3. Derive a scoped signing key
signing_key = runtime.derive_child(secret, "m/44'/0'/0'/0/1")
# 4. Publish only the public fingerprint
pubkey = signing_key.public_key()
publish(pubkey) # safe to share
Human in the loop. Domino Compass is a physical ceremony. Agents automate the derivation and verification, but the entropy ceremony itself stays a human, physical act — never delegate the source of the secret to an agent.