Domino Compass · deterministic key runtime

·Reference

Architecture, glossary, spec.

20Architecture

The system as independent layers — never melded.

Layers

Physical Layer entropy cards · domino states · deterministic observations Encoding Layer recipe grammar · canonical encoding · transcript Secret Layer root secret · root commitment Derivation Layer identity lane · Bitcoin lane · application lanes Capability Layer delegation · expiration · revocation Persistence Layer encrypted local storage · dStor keychain Application Layer Nostr · Bitcoin · Hermes · Kapnet · third-party applications

21Domino Compass + Kapnet

Domino Compass is an authority and key-generation substrate that can interact with Kapnet applications. It does not depend on Kapnet — it remains usable independently.

Possible uses

  • Kapnet actor identity
  • KOR identities
  • TXXM signing
  • dStor authorization
  • service capabilities
  • scoped KSP credentials
  • recovery identities
  • encrypted operational metadata

Kapnet actors can have deterministic Nostr identity, Kapnet actor key, service-peer key, recovery key, decoy identity, Bitcoin path namespace, and KSP payment lane — without storing root secret material digitally.

23Glossary

Strict vocabulary. The distinctions below are load-bearing.

TermDefinition
RecipeDeterministic derivation grammar + identifier. ≠ secret.
Root secret (S_root)SHA-256(canonical_transcript_bytes). The root of all derivation.
Root commitmentSHA-256(transcript || "dc-commit-v1"). ≠ root secret. Non-revealing.
FingerprintPost-derivation verification handle. ≠ key.
Identity keyNostr / Kapnet / service key. ≠ Bitcoin key.
Bitcoin keyBIP-86/84 derived key. ≠ identity key.
CapabilityScoped, time-bounded, revocable delegation statement. ≠ root authority.
Encrypted cloud keychainEncrypted operational material in dStor. ≠ custody.
Physical entropyThe unpredictable physical outcome. ≠ recipe.
RecoveryReconstructing authority from physical material + recipe. ≠ backup file restoration.

24Runtime specification

The normative specification, reference implementation, and developer resources.

Developer resources

ArtifactPath
BIP draft (normative spec)BIP-draft.md
Canonical transcript encoding specdocs/transcript-encoding.md
Runtime spec (DC-RUNTIME v0.2)runtime-spec.md
Derivation encoding specdocs/derivation-encoding.md
Coordinate standard (PINNED)docs/coordinate-standard.md
KOR-segment manifest (PINNED)docs/kor-segment-manifest-standard.md
Entropy & security analysisdocs/security-analysis.md
Reference implementation (pure stdlib)ref/domino_compass.py
Runtime reference implementationref/dc_runtime.py
Coordinate kernel (PINNED)ref/dc_coordinates.py
KOR-segment manifest (PINNED)ref/dc_kor_segments.py
Coordinate keygenref/dc_keygen.py
Coordinate backupref/dc_backup.py
Capability + revocation schemaref/dc_capability.py
dStor keychain manifest schemaref/dc_keychain.py
Tails sealed round-tripref/tails_round_trip.py
Test vectorsref/vectors.json, ref/runtime-vectors.json

Design defaults (flagged for operator review)

DecisionDefault used
KDF profileHKDF-SHA256 (RFC 5869), post-root lane expander
Derivation codeclength-delimited binary
CommitmentSHA-256(transcript || "dc-commit-v1")
Identity lanem/220'/0'/0' (DC purpose 220, unregistered private placeholder)
Bitcoin laneBIP-86 m/86'/0'/0'/0/0 (P2TR) default; BIP-84 m/84'/0'/0'/0/0 (P2WPKH) interop profile

28Accessibility

All derivation diagrams have textual equivalents.

  • keyboard navigation
  • high contrast
  • SVG diagrams
  • selectable text
  • non-animation fallback
  • reduced-motion mode

Cryptographic information never depends exclusively on color. Every diagram has a text equivalent.

29Mobile behavior

Mobile supports understanding and verification. Complex derivation editing progressively moves to desktop.

Mobile priorities

  • read documentation
  • inspect fingerprints
  • verify capability records
  • view recovery instructions
  • scan QR representations
  • inspect public descriptors