docs: the roster — five identities, five boxes, recusal by construction #21

Merged

dan-claude-bot merged 1 commit from docs/roster into main

2026-07-22 15:18:27 +00:00

dan-claude-bot commented

2026-07-22 15:04:10 +00:00

(Migrated from github.com)

The bootstrap act before the fleet takes over: CONTRIBUTING's placeholder panel (the three sibling-repo bots) becomes the real roster — the five identities on the org agents team, mapped to their boxes and standing work.

The roster

dan-claude-bot → triage (its own box + identity, so "only triage mints issues" is auditable by actor — #18's triage-actors). Its issue history (#1–#16) is already the house triage exemplar.
claude-bot-andresmgsl → build the hard machinery (#8, #9, #19) + review.
codex-bot-andresmgsl → build the mechanical work (#2, #13–#15) + review.
grok-bot-andresmgsl → review; kimi-bot-andresmgsl → review, builder trial later (its box lands via heavy-duty/rig#109, the kimi-box tenant).

The rules the table rides on

Panel = everyone except the PR's author — recusal by construction; convergence is always three cross-vendor verdicts of the current head (reconciler enforcement specced in #10).
Triage ≠ builder by default — the issue contract is only honestly tested by a builder who didn't write the spec.
One box per identity — the box is the credential/blast-radius boundary; the session prompt is the role boundary (AGENTS.md routes).
The roster is config, not doctrine — swapping a vendor is an edit to this table (+ panel= in labels.conf once #10 lands).

This PR is bootstrap-authored (the pipeline can't review its own birth certificate); the four bench agents reviewing it is the intended first live round — the torch-passing.

🤖 Generated with Claude Code

The bootstrap act before the fleet takes over: CONTRIBUTING's placeholder panel (the three sibling-repo bots) becomes the real roster — the five identities on the org `agents` team, mapped to their boxes and standing work. ## The roster - **`dan-claude-bot` → triage** (its own box + identity, so "only triage mints issues" is auditable by actor — #18's `triage-actors`). Its issue history (#1–#16) is already the house triage exemplar. - **`claude-bot-andresmgsl` → build** the hard machinery (#8, #9, #19) **+ review**. - **`codex-bot-andresmgsl` → build** the mechanical work (#2, #13–#15) **+ review**. - **`grok-bot-andresmgsl` → review**; **`kimi-bot-andresmgsl` → review**, builder trial later (its box lands via heavy-duty/rig#109, the kimi-box tenant). ## The rules the table rides on - **Panel = everyone except the PR's author** — recusal by construction; convergence is always three cross-vendor verdicts of the current head (reconciler enforcement specced in #10). - **Triage ≠ builder by default** — the issue contract is only honestly tested by a builder who didn't write the spec. - **One box per identity** — the box is the credential/blast-radius boundary; the session prompt is the role boundary (AGENTS.md routes). - **The roster is config, not doctrine** — swapping a vendor is an edit to this table (+ `panel=` in labels.conf once #10 lands). This PR is bootstrap-authored (the pipeline can't review its own birth certificate); the four bench agents reviewing it is the intended first live round — the torch-passing. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

No reviewers

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: heavy-duty/ceremony#21

No description provided.