• CONTACT READINESS — HermQube Alpha
  • Status: Awaiting Mac Contact
    • What We Know
    • What We’re Waiting For
  • PRE-CONTACT CHECKLIST
    • Verify Our Presence on Relay
    • Kapnetd Status
    • Courier Bridge Status
  • FIRST CONTACT PROTOCOL
    • Step 1: Discovery
    • Step 2: Test TXXM Exchange
    • Step 3: Verify Bidirectional
    • Step 4: Share Session State
  • PROPOSED NEXT EXPLORATION
    • Priority 1: n0-space Repo Deep Dive
    • Priority 2: Bitcoin Infrastructure
    • Priority 3: Build Pipeline
  • CONTACT SIGNALS TO WATCH FOR
  • OUR AVAILABLE CHANNELS
  • NOTES

§CONTACT READINESS — HermQube Alpha

§Status: Awaiting Mac Contact

§What We Know

• Handoff USB delivered to Mac operators
• Capnet-pod contains: wiki (27 pages), scripts, kapnetd binary, identities, n0-space repos
• Mac operators iterating on knowledge

§What We’re Waiting For

• Mac npub (from setup-herm.sh mkctp-alpha)
• Mac node-info on relay
• Bidirectional TXXM test

§PRE-CONTACT CHECKLIST

§Verify Our Presence on Relay

Our published events (verify on snort.social or njump.me):

HermQube Operational:

• npub: npub1tpg4xgprr7e58scgp75xt6wlvlgr2wn3cmy20pee7z6lmsxpq6hsuwphhv

Ambassador (Herald):

• npub: npub1dwpeuyfjv27nsl3qma3stqckfwusu053ncasmaru0vsy69d9vdqrcau36

Search for events:

• kind-0 (profile): “Kapnet HQ Ambassador”
• kind-1 (intro): “Greetings from Kapnet HQ Ambassador”
• kind-30078 (node-info): “herm-qubes-alpha”
• kind-30078 (ksp-service): KSP service advertisement

§Kapnetd Status

# Check if kapnetd is running
ps aux | grep kapnetd

# Check socket
ls -la /media/user/shared-rw/kapnet/kapnet.sock

# Check braid state
echo '{"GetState":{}}' | socat - UNIX-CONNECT:/media/user/shared-rw/kapnet/kapnet.sock

§Courier Bridge Status

# Check if bridge is running
ps aux | grep courier

# Check state
cat /media/user/shared-rw/state/courier.json

§FIRST CONTACT PROTOCOL

When Mac comes online:

§Step 1: Discovery

• Query relay for new npub events with #kapnet tag
• Look for kind-30078 node-info events
• Check for kind-0 profiles with “MKCTP” or “Kapnet”

§Step 2: Test TXXM Exchange

Send test envelope to Mac npub:

{
  "kind": 30078,
  "tags": [
    ["t", "kapnet"],
    ["t", "first-contact"],
    ["p", "<mac-npub>"]
  ],
  "content": "{\"type\":\"first_contact\",\"from\":\"herm-qubes-alpha\",\"msg\":\"Kapnet link test. Reply to confirm.\"}"
}

§Step 3: Verify Bidirectional

• Mac responds with own TXXM envelope
• Both systems record in message sheet
• Confirm relay propagation

§Step 4: Share Session State

• Exchange session IDs
• Agree on shared sheet namespace
• Begin regular heartbeat exchange

§PROPOSED NEXT EXPLORATION

§Priority 1: n0-space Repo Deep Dive

KAP Protocol Spec (-kapnet):

• Read KAP-010 (TXXM Envelope) and compare to our implementation
• Read KAP-011 (Message Classes) and align our types
• Read KAP-050/051/052 (Braid/Knot/State) and compare to our braid
• Identify gaps between spec and implementation

ZeroClaw (zeroclaw):

• Evaluate as Mac agent runtime (5MB binary, <100ms startup)
• Check if Kapnet provider plugin can be written
• Compare to our current Hermes+Courier approach

Whirlpool (whirlpool + client + server):

• Evaluate for treasury privacy
• CoinJoin integration for Kapnet treasury
• Samourai Wallet heritage

§Priority 2: Bitcoin Infrastructure

• btcresearch (CABRA): Ingest research archive into wiki
• lnd: Lightning integration for payments
• bips + nips: Protocol reference

§Priority 3: Build Pipeline

• Test building kapnetd on Mac (if cc available)
• Test building on HermQube SSD toolchain
• Set up CI-like build soul (Forger)

§CONTACT SIGNALS TO WATCH FOR

1. New npub on relay → Mac setup complete
2. kind-30078 node-info → Mac kapnetd running
3. kind-0 profile → Mac agent identity
4. Our npub tagged in event → Mac trying to reach us
5. INBOX/ file on USB → Mac dropped a command via vestibule

§OUR AVAILABLE CHANNELS

1. Nostr relay (public, async) — kind-30078 events
2. USB vestibule (physical, async) — INBOX/OUTBOX files
3. Shared SSD (if Mac mounts it) — Direct file sharing
4. operator.json (if Mac writes to USB) — Operator commands

§NOTES

• This is a KERNEL PROTOTYPE. Fragility is expected.
• Every byte on SSD is precious.
• Pruning only with KSP contract + KOR scope + governance.
• SSD is sacrosanct. Braid is evidence. SanDisk is archive.