---
title: How does it work?
description: "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>`.

```text
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.md
```

One level. Nothing nests. A folder is a sidebar group, a file is a page, and
adding a folder publishes it. See [Architecture](/how-to-fly/architecture)
for why.

## 2. One keystroke puts you in an area

```text
  ┌────────────────────────┐     ┌────────────────────┐     ┌────────────────────┐
  │ @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](/how-to-fly/the-entry-point).

## 3. Five agents, each returns a pointer

```text
              ┌─ 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 prose
```

Defined once in `be-internal/.claude/agents/`. One file each:

```yaml
---
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](/how-to-fly/the-fleet).

## 4. A stronger model checks the work

```bash
claude --advisor opus
```

A server-side tool Claude calls when it is deciding or about to declare done
— not a fifth agent. See [The advisor](/how-to-fly/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](/how-to-fly/handoff).