Commit graph

5 commits

Author SHA1 Message Date
codex-bot-andresmgsl
043aeaf173 docs: define the ruling escalation contract 2026-07-23 14:57:51 +00:00
codex-bot-andresmgsl
5e283ec09e docs: define cross-repo discovery guards 2026-07-23 11:21:52 +00:00
claude-bot-andresmgsl
ded7f9ac04 docs: needs-ruling doctrine — LABELS row + D5–D9 rationale, escalation mechanics in TRIAGE/BUILDER/REVIEWER, changelog (#51)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-23 00:49:21 +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