tambo 0.11.1

Install and prove the whole AI knowledge-tool kit
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160

<!--
  Shared hero art: thread-workshop/THEME.md; use the tool-specific card.
  Embed the reproducible terminal demo near first success, with transcript and recipe.
  Tambo stack README template: see README-STANDARD.md for the rules.
  Replace every ALL-CAPS placeholder. Delete a section only if the tool truly
  lacks it; never rename or reorder a heading.
  Budget: first install command within 60 lines, whole file under 250.
-->

<p align="center">
  <img src="assets/header.png" width="704" alt="TOOLNAME: DESCRIBE ITS THREAD WORKSHOP MOTIF"/>
</p>

<p align="center">
  <img src="assets/logo.svg" width="200" alt="ALT TEXT FOR THE LOGO"/>
</p>

<h1 align="center">TOOLNAME</h1>

<p align="center">
  <em>EMOJI OUTCOME-FIRST TAGLINE, PLAIN ENGLISH, 90 CHARACTERS OR FEWER</em>
</p>

<p align="center">
  <a href="LICENSE"><img src="https://img.shields.io/badge/License-Apache_2.0-blue.svg" alt="License: Apache-2.0"/></a>
  <a href="https://github.com/scbrown/TOOLNAME/actions/workflows/ci.yml"><img src="https://github.com/scbrown/TOOLNAME/actions/workflows/ci.yml/badge.svg" alt="CI"/></a>
  <a href="https://github.com/intigraph/tambo"><img src="https://img.shields.io/badge/stack-quipu-8B5E3C.svg" alt="Part of the Tambo stack"/></a>
</p>

**TOOLNAME IS A WHAT-IT-IS FOR WHO-IT-IS-FOR. It comes as a CLI, an MCP server
and FORMS.** ONE OR TWO MORE SENTENCES ON WHAT IT DOES FOR THEM. (OPTIONAL: ONE
SENTENCE ON WHERE THE NAME COMES FROM.)

## Why you would want it

- **OUTCOME ONE**, in the reader's terms.
- **OUTCOME TWO**.
- **OUTCOME THREE**.

The full case, and how TOOLNAME compares with the alternatives:
[Why TOOLNAME](docs/book/src/introduction.md).

## Install

Linux x86_64 and macOS (PLATFORMS): download the checksummed release.

```bash
INSTALL COMMAND FROM THE RELEASE
```

Anywhere else, build from source (needs TOOLCHAIN):

```bash
cargo install --git https://github.com/scbrown/TOOLNAME --locked
```

Check it:

```bash
TOOLNAME --version
```

```text
TOOLNAME X.Y.Z
```

If that prints an older version, another copy is earlier on your `PATH`:
`which -a TOOLNAME`.

## First success in three commands

```bash
FIXTURE SETUP (SELF-CONTAINED: A TEMP DIR, A TINY SAMPLE)
COMMAND ONE
COMMAND TWO
```

```text
THE EXACT OUTPUT A CLEAN RUN PRINTS
```

ONE SENTENCE: WHAT THAT OUTPUT SHOWS AND WHY IT MATTERS.

## On your own code

| you want to know | run |
|---|---|
| QUESTION | `COMMAND` |
| QUESTION | `COMMAND` |
| QUESTION | `COMMAND` |

Every command and flag: [CLI reference](docs/book/src/reference.md).

## Wire it into your agent

```bash
MCP ONE-LINER (e.g. claude mcp add TOOLNAME -- TOOLNAME serve)
```

MINIMAL HOOK OR CONFIG, IF ANY.

Hooks, other agents and every option: [Using TOOLNAME with agents](docs/book/src/agents.md).

## Before you start

| | Linux x86_64 | macOS arm64 | macOS x86_64 | Linux arm64 |
|---|---|---|---|---|
| TOOLNAME | release | release | build | build |

PREREQUISITES, ONE LINE EACH.

## What's next

- [The TOOLNAME book](docs/book/src/introduction.md): start here to go deeper
- [Docs map](docs/book/src/docs-map.md): every document in this repo, routed
- [NEXT PAGE A NEW USER SHOULD READ](docs/book/src/PAGE.md)

## 🧺 The stack

Tambo installs these together and proves each one works; every tool also stands alone.

<!-- stack-table:start -->

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.

| tool | what it gives your agents |
|---|---|
| [tambo](https://github.com/intigraph/tambo) | 🧰 Agent Platform Toolkit - installs and configures the quipu stack |
| [quipu](https://github.com/scbrown/quipu) | stores shared facts with provenance and history; can check writes against your rules |
| [camayoc](https://github.com/scbrown/camayoc) | prepares knowledge and vocabulary for Quipu, with checks before it is admitted |
| [quechua](https://github.com/scbrown/quechua) | shared vocabulary and shapes for interoperable knowledge |
| [chaski](https://github.com/scbrown/chaski) | reacts to graph changes and delivers governed notifications |
| [bobbin](https://github.com/scbrown/bobbin) | indexes your codebase and injects context from that index and Quipu knowledge |
| [yupana](https://github.com/scbrown/yupana) | shows code impact and can read policies from Quipu to govern agent actions |
| [desire-path](https://github.com/scbrown/desire-path) | turns agent mistakes into feature requests; works on its own without Quipu |
| [seeds](https://github.com/scbrown/seeds) | a work item tracker backed by the Quipu knowledge base |
| [shantytown](https://github.com/scbrown/shantytown) | runs crews of AI agents on work items, triggered by hand, on a schedule or by events; can share work and memory through Quipu |
| [rikuy](https://github.com/scbrown/rikuy) | live brief: status, graphs, watches and signed decisions over Quipu |
| [shuttle](https://github.com/scbrown/shuttle) | runs signed agent workflows and keeps their records in Quipu |

<!-- stack-table:end -->

## Contributing

```bash
just build
just test
just ci      # what CI runs
```

## 📜 License

[Apache-2.0](LICENSE)

<p align="center">
  <img src="assets/footer.svg" width="100%" alt="ALT TEXT FOR THE FOOTER"/>
</p>