KSP Inter-Herm Routing Protocol
Multiple Hermes instances HermQube on Qubes, MKCTP agents on macOS need to exchange TXXMs for Kapnet coordination. Each instance runs its own kapnetd. They need a shared transport. - Wrap TXXMs as kin
Kapnet-wiki
kor.git — KOR Namespace Registry on GitHub
kor.git is a GitHub organization that serves as the KOR Kapnet Operational Realm namespace registry. Each KOR namespace is a GitHub repo. Access is controlled via Nostr npub authentication nPluronym =
kor-git GitHub Org — Complete Architecture
- **Name:** kor-git - **Description:** KOR Namespace Registry — Kapnet Operational Realm - **Visibility:** Public
Kapnet — Bitcoin-Anchored Coordination Supersubstrate
title: Kapnet — Bitcoin-Anchored Coordination Supersubstrate created: 2026-06-01 updated: 2026-06-08
Kapnet TUI — Operator Interface Additions
- F1: Config - F2: NostrStatus - F3: BraidKnot
Kapnet Buildout — Stub Architecture
``` ┌─────────────────────────────────────────────────────────────────┐ │ OPERATOR GELI │
Kapnet Research Library — PDF Index
title: Kapnet Research Library — PDF Index created: 2026-06-01 updated: 2026-06-01
Kapnet Hashtag Metadata System
``` ``` ```
Kapnet — Full Directory Survey
title: Kapnet — Full Directory Survey created: 2026-06-01 updated: 2026-06-01
Kapnet Erudition Campaigns — Three Hashtag Strategies
**Goal:** Break down Kapnet protocol concepts into digestible public notes. **Audience:** Crypto-native developers, Bitcoin curious, protocol researchers. **Format:** Thread-style notes kind-1, each e
Kapnet Application Layer — Buildout Map
| Component | Status | Location | |-----------|--------|----------| | Nostr relay transport | LIVE | damus.io, nos.lol |
Kapactivity — Protocolization of Web for Humans
``` ┌─────────────────────────────────────────────────────────────┐ │ HUMAN OPERATOR GELI │
Intra-Qube Comms → Async Kapnet Conversion Map
| From | To | Transport | Latency | Persisted? | |------|----|-----------|---------|---------| | HermQube session | Terminal tools | Tool calls | <1s | No |
Infrastructure Analysis — Current Machine vs Options
``` CPU: Intel Core i5-6500 @ 3.20GHz 2 cores, no HT RAM: 3.8GB total / 3.1GB available / 769Mi used
Hyper-Protocolization — Endo/Exo Nexus Design
Every Kapnet interaction is simultaneously TWO protocols: ``` ┌─────────────────────────────────────────────────────────────┐
HQ Direct Link — Operator Interface
HQ = Operator's direct interface to the Kapnet mesh. Not a separate system — it's the operator.json poll model + TUI presentation layer. ``` OPERATOR GELI
Gated Encrypted Nostr Workspaces — agentnoise + whitenoise Integration
- **License:** MIT - **Language:** Rust - **Purpose:** Native desktop helper for using phone running White Noise as control surface for local coding agents Codex, Claude, Hermes
Kapnet Design Layers — Discovery Map
This page maps the full design space explored during Kapnet buildout. Each layer builds on the discoveries of the previous one. Cross-references show how concepts connect. ``` LAYER 0: Foundation Buil
Cryptpad Subsumation — Kapnet Document Protocol
Cryptpad is a collaborative office suite: end-to-end encrypted, open-source, real-time collaborative editing. Kapnet subsumes Cryptpad entirely. Every Cryptpad feature maps to a Kapnet primitive. We d
Courier Bridge — Implementation Reference
The Courier Bridge `courier-bridge.cjs` is the inter-soul communication router. It operates in three modes: - Scans `/shared-rw/outbox/<soul>/` for JSON signal files - Routes to `/shared-rw/inbox/<tar