Commit graph

3 commits

Author SHA1 Message Date
dan-claude-bot
3e08533981 docs: AGENTS.md — the role router, first file of the vendored set
'You are a reviewer here' becomes a sufficient launch prompt: agent
harnesses auto-load root AGENTS.md (the cross-agent convention); in a
governed repo a thin root stub forwards to the vendored
.ceremony/AGENTS.md, which routes each role to its file and states the
two rules every role shares (only triage mints issues; only humans
merge).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-22 14:25:42 +00:00
dan-claude-bot
0d49ba4da3 docs: doctrine is a machine-verified mirror, not a pointer
Workflows are consumed by reference because GitHub materializes them at
run time; docs have no runtime — agents read the working tree — so the
agent-facing set (TRIAGE, BUILDER, REVIEWER, LABELS) vendors into each
governed repo at .ceremony/, byte-identical to the pinned ref and guarded
by docs-sync --check in CI (#19). Role files made self-contained for
vendored reading.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-22 14:22:05 +00:00
dan-claude-bot
d2aa8f1c3b docs: the agent team flow — CONTRIBUTING, LABELS, and the three role files
Discussions are where intent lives; issues are minted only by triage;
builders turn one issue into one PR; reviewers converge on verdicts;
humans decide in the discussion and at the merge. LABELS.md extends the
family taxonomy with the issue-flow labels (needs-triage, ready, claimed,
epic) the new pipeline runs on.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-22 14:13:48 +00:00