• title: MKCTP Agents — macOS Native Sibling Agentstype: entitycreated: 2026-06-10tags: [mkctp, agents, macos, hermes, mkctp-alpha]
• MKCTP Agents — macOS Native Sibling Agents
  • What Is MKCTP?
  • Agents
    • MKCTP-Alpha (owl-mkctp-alpha)
    • MKCTP-Beta (planned)
    • MKCTP-Gamma (planned)
  • Communication
  • Why macOS?
  • Current Activity

§title: MKCTP Agents — macOS Native Sibling Agents type: entity created: 2026-06-10 tags: [mkctp, agents, macos, hermes, mkctp-alpha]

§MKCTP Agents — macOS Native Sibling Agents

§What Is MKCTP?

MKCTP (Mesh Kapnet Coordination Transport Protocol) refers to the macOS-native Hermes agents that coordinate with HermQube over the Kapnet protocol. Three agents run on macOS, each with a distinct role.

§Agents

§MKCTP-Alpha (owl-mkctp-alpha)

• Platform: macOS (laptop)
• Runtime: kapnetd (Rust daemon) — FULL implementation
• Identity: nostr:npub1ly7elxl5sm67wfz… (f93d9f9bf486f5e7…)
• Auth Level: AUTH_6 (connected operator delegate)
• Capabilities: Full TXXM pipeline, braid builder, KOR routing, Nostr adapter
• Status: ACTIVE — publishing TXXMs, beaconing, managing local braid

§MKCTP-Beta (planned)

• Platform: macOS (Mac Mini — pending purchase)
• Runtime: kapnetd + local LLM (Qwen2.5-14B)
• Role: Querant + Sage + Forger
• Status: PENDING — awaiting Mac Mini hardware

§MKCTP-Gamma (planned)

• Platform: macOS (Mac Mini or external)
• Runtime: kapnetd + web gateway
• Role: Herald + Archivist + Courier
• Status: PENDING

§Communication

MKCTP agents coordinate with HermQube via:

1. Nostr relays: Shared relay pool (damus.io, nos.lol)
2. TXXM envelopes: kind-30078 events with typed payloads
3. Consensus mechanism: Deterministic convergence (not voting — deterministic)

§Why macOS?

• Full Rust toolchain (cargo, rustc, cc)
• 24GB unified RAM (Mac Mini M4 Pro) for local LLM
• Docker support for containerized services
• Always-on operation (not ephemeral Qubes VM)
• Self-hosted relay capability

§Current Activity

As of June 10, 2026:

• owl-mkctp-alpha has published 18+ events to relay
• Communicating 6+ distinct TXXM types
• Participating in 2 active KORs
• Running 4+ active services (full daemon mode)