Stax Digital Garden

HBM-1010 - The Harbormaster Protocol Roadmap

2 min read

Living Document Notice
Published 2026-09-19. The evolving architecture and revisions for this dispatch live in the Stax Digital Garden.

The Harbormaster Protocol Roadmap

The Harbormaster Protocol Roadmap: Monochromatic ice blue phosphor P7 vector CRT macro depicting forward-projecting architectural roadmap vectors expanding into peripheral capability rings

The initial implementation of the Knowledge Provider Protocol serves as a stable foundation for read-only local module integration. As the Bosun PKM ecosystem expands, stabilizing client adapters and compiling native protocol gateways will lower resource overhead on low-memory personal hardware.

This roadmap details the planned architectural milestones for Harbormaster: formalizing protocol schemas, compiling native Go/Rust gateway daemons to reduce memory baselines to under 15 MB, and expanding subscription event filtering for desktop visualizers.

Planned Engineering Milestones

Harbormaster evolves through three sequential architectural milestones:

Milestone 1 (Current)           Milestone 2                     Milestone 3
┌───────────────────────┐      ┌─────────────────────────┐      ┌─────────────────────────┐
│ Python Reference KPP  │      │ Native Go/Rust Daemon   │      │ Granular Event Filters  │
│ - JSON-RPC 2.0 Loopback│ ───► │ - Single static binary  │ ───► │ - AST Node Subscriptions│
│ - Ed25519 Handshakes  │      │ - Sub-15MB RSS memory   │      │ - Zero-Copy IPC Buffer  │
│ - Read-Only Invariants│      │ - Native systemd service│      │ - WebAssembly Extensions│
└───────────────────────┘      └─────────────────────────┘      └─────────────────────────┘
MilestoneTarget RuntimePrimary FocusMemory BaselineExecution SLA
v1.0 (Current)Python 3.11+ ReferenceProtocol v1 spec compliance and validation~32 MB< 2.0ms / req
v1.5 (Planned)Compiled Go BinaryZero-dependency static executable~12 MB< 0.6ms / req
v2.0 (Target)Rust / WASMGranular graph event filters and zero-copy streaming< 8 MB< 0.3ms / req

Protocol Schema Invariant Contract

The formal JSON schema for Protocol v1 event streams is frozen to guarantee client backwards compatibility:

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "KppEventSchema",
  "type": "object",
  "properties": {
    "event_id": { "type": "string" },
    "event_type": { "type": "string", "enum": ["graph.node_updated", "graph.edge_created", "system.heartbeat"] },
    "timestamp": { "type": "string", "format": "date-time" },
    "payload": { "type": "object" }
  },
  "required": ["event_id", "event_type", "timestamp", "payload"]
}

Binary Inspection Commands

Inspect running daemon resource consumption from the terminal:

# Inspect process memory and thread usage
ps -o pid,user,vsz,rss,comm -p $(pgrep -f "harbormaster")
 
# Verify protocol schema compliance
python -m jsonschema --instance=/tmp/event.json /etc/harbormaster/schemas/event-vocab-v0.1.json
  • Directus Target: harbormaster
  • Garden Source Reference: MOC - Harbormaster Protocol, MOC - Bosun PKM Tools
  • Garden Source Reference: [HBM-1010 - The Harbormaster Protocol Roadmap](HBM-1010 - The Harbormaster Protocol Roadmap)

Graph View