Integrator documentation — a wire dialect for narrative knowledge, with one path for every job.
If you run a product that stores narrative knowledge, implement an adapter — pick the port families for the capabilities you claim, and call the matching orchestrators. If you run a separate SPOKE host and want to talk to another host, open a connect session or jump straight to the TypeScript client / native bindings / Connect from C and C++. Integrating your own message-oriented Transport? Dial remote hosts through a RemoteAdapter over a Transport, route across multiple peers, or drive the same adapter surface through a native binding. Expose tools the host can discover and reverse-invoke mid-orchestration with remote tools. Complete beginners follow the two tutorials in order: Install and create your first KnowledgeEntry, then Open your first connect session.
SPOKE is a protocol of JSON Schema wire contracts for narrative knowledge: independent products exchange consistency-check and context-assembly I/O through shared data and ops shapes, so each product stops inventing local formats for the same concepts. The repository is the SSOT — hand-authored schemas, generated TypeScript and Rust wire types, and pure operations libraries.
project / compute and extract op families)modules.* bagsspoke-baseline, or declare l2-computable, l5-fork, l5-mind, narrative-modules, ke-extraction, ke-ownership, spoke-connect explicitly