A living, agent-maintained understanding layer for OpenAB — the open Agent Client Protocol broker.
This repo is auto-updated by an agent workflow that watches beta releases on openab main, diffs what changed, and rewrites affected sections. Every file traces back to a source commit SHA in .sync-state.
If you're new → start at What is OpenAB
| Layer | What it answers |
|---|---|
| 00 · What is OpenAB | One-page pitch. The problem, the solution, what it is not. |
| 01 · Core Concepts | The 7 ideas you must internalize before anything clicks. Includes reactions mapping — emoji as agent control panel. |
| 02 · Mental Models | How the pieces fit — data flows, topology, sequences. |
| 03 · Use Cases | "I want to do X" → here's how. Includes driving an agent from an ACP client, PR contribution lifecycle, and the Jelli governed community bot setup. |
| 04 · Decision Trees | Should I use X or Y? Structured branching choices. |
| 05 · Change Digest | Plain-English summary of recent openab changes. |
openab/beta push or daily schedule
↓
GitHub Action: compute diff since last sync
↓
Claude agent: reads diff + current map
↓
Rewrites affected sections + updates LATEST.md
↓
Opens PR
↓
Multi-agent review via openab b2b
↓
Auto-merge on consensus
The agents doing the review run through openab itself — the same system being documented. See the repo's agent sync workflow.
- Repo:
openabdev/openab - Branch:
main(beta release tags, currentlyv0.10.0-beta.2) - Last synced SHA: see
.sync-state
This map is agent-maintained but human-correctable. If a section is wrong or missing:
- Open an issue describing the gap
- Or open a PR — the next agent sync will reconcile your changes against the source
Priority areas that benefit most from human input: decision trees, use-case narratives, and "gotchas" that aren't visible from the code alone.