How does it work?
One repo, flat areas, five agents. The essence.
How does it work?
1. One repo, FLAT areas
No code lives here. be-internal is the only repo, and every area of work is
one flat subdirectory under docs/, named be-<category>-<name>.
be-internal/
├── docs/
│ ├── be-category-name/
│ ├── be-category-name/
│ ├── be-category-name/
│ ├── be-category-name/
│ ├── handbook/
│ └── how-to-fly/
├── .claude/ the harness — one, shared by every area
└── CLAUDE.mdOne level. Nothing nests. A folder is a sidebar group, a file is a page, and adding a folder publishes it. See Architecture for why.
2. One keystroke puts you in an area
┌────────────────────────┐ ┌────────────────────┐ ┌────────────────────┐
│ @be-category-name │ ──▶ │ cd docs/<that one> │ ──▶ │ lead agent (Opus) │
└────────────────────────┘ │ start Claude │ │ + 4 subagents │
└────────────────────┘ │ + advisor attached │
└────────────────────┘A shell function, not a Claude feature — see The entry point.
3. Five agents, each returns a pointer
┌─ Researcher Opus · xhigh
lead agent ─┼─ Historian Haiku · low
(you talk ├─ Librarian Sonnet · high
to this) └─ Designer Opus · medium
│
└──▶ hands back a PATH or URL, never proseDefined once in be-internal/.claude/agents/. One file each:
---
name: historian
description: Returns URLs to relevant git and web history. Never summarizes.
model: haiku
effort: low
tools: [Bash, Read, Grep, WebFetch]
---Same shape for researcher (opus / xhigh), librarian (sonnet /
high) and designer (opus / medium).
See The fleet.
4. A stronger model checks the work
claude --advisor opusA server-side tool Claude calls when it is deciding or about to declare done — not a fifth agent. See The advisor.
5. Ready to build? Open a PR
We write what we want; engineering proves it works. No code is read or written here. See Handoff.