Ship's Library — Computer, Access the Files
Documentation, straight from the source
On this crew, documentation isn't a summary somebody wrote about the work — it links to the work itself. Every text below is a real file in the repository. The computer does not paraphrase. The computer does not improvise. The computer retrieves.
Start Here — Orientation
-
README — Mission Briefing
What Spokbot is, why it exists, the crew roster, and how the pieces fit. Your first stop on the tour.
-
SETUP — Boarding Procedures
The full setup guide: backends, shared memory, deployment, and the live smoke test.
-
AGENT_SETUP — Crew Assignments
How agents are defined, granted tools, and put to work.
Engineering — How the Ship Works
-
ARCHITECTURE — Schematics
The full design: platform adapters, the core layer, and the production engine in slack-agents/.
-
MODELS — Choosing a Warp Core
Model switching in plain English: three tiers (Quick, Smart, Best), a free local default, and what upgrades actually cost.
-
LLM Management — Routing & the Gateway
How requests are routed through the self-hosted LiteLLM gateway, and how local and hosted models share the load.
-
Hands — The Tool Deck
The MCP servers and grants system: how tools reach agents, and how the dangerous ones stay behind explicit owner decisions.
The Law — Verification
-
Definition & Verification Spec
The constitution of the project: every function, the outcome that counts for each, and the standard the system is audited against. This is the document that currently keeps us at yellow alert — by design.
-
Execution Kernel Spec
How directives become delegations, delegations become receipts, and receipts become — or fail to become — "done."
-
User Stories — The Ship's Log, In Advance
Every unit of work is a story — "As a …", Given/When/Then, a difficulty score — built BDD-first, then TDD. Read what the crew has sworn to, in writing.
A Note on Sources
This library links to the repository because the repository is where the truth lives. If a page here ever disagrees with the code, believe the code — and file an issue so the page gets corrected. Discrepancies are treated as defects, not as marketing opportunities.