heavy-duty/ceremony
7
0
Fork 2
Code Issues 1 Pull requests Projects Releases 8 Packages Wiki Activity Actions

docs: align mechanical handoff wording

Browse source
This commit is contained in:
codex-bot-andresmgsl 2026-07-28 17:57:31 +00:00
parent ab77fa93ac
commit 0405d206ae
2 changed files with 8 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
BUILDER.md
View file

@ -339,10 +339,11 @@ item to its flow in the same comment ([LABELS.md](LABELS.md)).
When the round passes — every panel verdict approves the **current head**,
and no `blocker:*` stands (conflicts rebased, CI green, drill recorded if
this is a release PR) — hand it to the human, in order:
this is a release PR) — the engine performs these mechanical steps on the
builder's behalf, in order:
1. request the human's review;
2. set `state:needs-human` yourself;
2. set `state:needs-human`;
3. post the engine-rendered handoff comment: approvals at the current head,
the head SHA, and a pointer to the PR body's **Round log**.

8
CONTRIBUTING.md
View file

@ -68,9 +68,11 @@ already proven:
feedback. ([REVIEWER.md](REVIEWER.md) for why a comment-only review stalls
the machine.)
5. **Handoff**: when the round passes — every panel verdict is an approval of
the current head and no `blocker:*` label stands — the author posts the
round summary, requests the human's review, and sets `state:needs-human`.
The label write is optimistic; the reconciler validates it within seconds.
the current head and no `blocker:*` label stands — the engine requests the
human's review, sets `state:needs-human`, and posts the handoff facts
(approvals at the current head, head SHA, and Round-log pointer) on the
author's behalf. The label write is optimistic; the reconciler validates
it within seconds.
6. **A human merges.** Nothing else merges.
### Roster