Playbooks
A playbook holds the decisions for one subject. When a question comes up, the answer is in the playbook or the playbook has a gap. A gap is filled by deciding it once with the owner and writing it down. Then everyone builds the same way.
| Playbook | Decides |
|---|---|
| Data | Domains, standards, the canonical model, events as the record, what is not Mongo |
| Platform | Where code runs, Rust and wasmtime, releases, secrets, what must never break |
| API | The four gateways, contracts, errors, auth, limits, conventions |
| Open data | What we publish, in what form, with what privacy guarantee |
| Analytics | How we measure without surveilling |
| Releases | Branches, versions, the release app, the merge gate and the rules still in conflict |
| Web | Astro, Rust serving, PWA, link previews and discoverability |
| Identity | WorkOS, one canonical id, staff roles versus plans versus entity capabilities |
| Notifications | What is decided and built about push, and the owner steps left |
| Agents | How agents work here: issues, hygiene, progress reports, what needs the owner |
| Weather | The weather goal and its objectives. It follows the other playbooks |
| News | Mukoko News: vehicle not publisher, metering, open data, reads through the API |
Where the structure lives
Section titled “Where the structure lives”The playbooks say how we decide. The structure of the data and the standards we adopt and publish live in bundu-labs/bundu-standards: register/ for standards we adopt, standards/ for the ones we publish. The canonical model moves there too. A playbook links to a standard by its register id and never restates it.
Rules for the playbooks themselves
Section titled “Rules for the playbooks themselves”- A decision names its source (an owner message with its date, a repository file, an issue).
- “Decided, not built” is said wherever that is the case.
- No counts of live things in prose; they go stale. Say how to measure them.
- A playbook for a product (weather, news) follows these and does not restate them.
- Each playbook says when it was last reviewed. A review reads the repositories, the open pull requests and the live inventory again, and says what it could not verify.
- Where two written rules conflict, the playbook lists both under “Open for the owner” and does not choose.