Docs map

Start here

• Introduction: what Caboodle does and when to use it.
• Getting started: the smallest install, interview and recovery.
• Installing and removing: platforms, source builds, files and updates.
• Using it with agents: standalone MCP clients and managed crews.
• Using Caboodle: the guided and non-interactive workflows.
• Reference: every command and the glossary.
• Configuration: plan, intent, environment and state.

Understand the design

• How it works: the plan/apply/verify engine.
• Three proofs: installed, working and observable.
• Conventions: shared layout without a second manifest.
• Profiles: tool selections, crew ownership and model artifacts.
• Crew capability contracts: browser evidence and admission.
• Emitting to Quipu: durable install and lifecycle records.
• The stack: the six core tools and related projects.
• The corpus: staging canonical knowledge shares.
• Roadmap: planned capabilities, not promises of shipped behavior.
• The stack standard: shared public documentation conventions.

Documents outside the book

These links point to the source repository so they work on both GitHub and the published book. Every loose document under docs/ is listed here.

• Stack README standard: section order, theme, shared stack block and review checklist.
• README template: fill-in template implementing the standard.
• Design vision: Historical design proposal; use the reference for shipped commands.
• txtai gap analysis: Historical comparison and design opportunities, not a current capability guarantee.