Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

The stack

    caboodle                      (interview → plan → apply → verify → observe)
        │  installs, proves, and watches ↓
        ▼
  quipu · bobbin · camayoc · yupana · desire-path · seeds · shuttle · shantytown / creel
        │
        ▼
    prometheus                    (every tool's metrics, consolidated)

Caboodle never re-implements a tool’s job. It installs the tool and then makes the tool demonstrate its own job, through three proofs:

  1. Installed: proven by reading the version back, never by an exit code.
  2. Working: a per-tool round trip. quipu accepts an episode and a query finds it; bobbin indexes a fixture and search returns it; yupana finds a caller in a fixture repository; seeds lists a fresh store, creates a marker work item, and finds it; shuttle defines a workflow, starts a run, advances it through one signed transition, and finds it in the new state; quipu also loads the pinned Quechua vocabulary release, which must resolve quechua:WorkflowRun and must not resolve an undeclared term. Every check first proves its marker is absent, so a pass is capable of failing.
  3. Observable: caboodle generates Prometheus scrape config, starter alerts, and one dashboard for the selected tools, for you to review and deploy.

Install and verification outcomes are also queued as quipu episodes, so a fresh box’s first knowledge is a record of the box itself. The agent-facing version of this workflow is the tambo skill, and the full design is in the book.

The Quipu stack is built around a governed, bitemporal knowledge store: shared facts, decisions and work history your agents can query. Quipu can check writes against your rules, records where each fact came from, and answers what was true when.

toolwhat it gives your agents
caboodle🧰 Agent Platform Toolkit - installs and configures the quipu stack
quipustores shared facts with provenance and history; can check writes against your rules
camayocprepares knowledge and vocabulary for Quipu, with checks before it is admitted
bobbinsearches your code and can include related knowledge from Quipu
yupanashows code impact and can read policies from Quipu to check changes
desire-pathturns agent mistakes into feature requests; works on its own without Quipu
seedsa work item tracker backed by the Quipu knowledge base
shantytownruns crews of AI agents on work items, triggered by hand, on a schedule or by events; can share work and memory through Quipu
shuttleruns signed agent workflows and keeps their records in Quipu

Supporting projects

repowhat it is
shantytowna small harness for running a crew of coding agents
creelparallel agent bursts, entirely in the browser
shantya terminal multiplexer wrapper that makes tmux feel like home
beadsissue tracking as agent memory — br, SQLite + JSONL
quechuathe stack’s shared vocabulary; caboodle pins a release by digest and loads it into Quipu (catalog)

See the corpus for share import and profiles for which tools each selection installs.