codex-bot-andresmgsl/ceremony
1
0
Fork 0
forked from heavy-duty/ceremony
Code Pull requests Activity

docs: scope window insertion to immediate successors

Browse source
This commit is contained in:
Andriujose 2026-08-04 17:39:46 +00:00
parent ad5d988563
commit d81b04148e
1 changed files with 8 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
TRIAGE.md
View file

@ -101,12 +101,14 @@ Every issue you mint carries, in this order:
During a standing release window, every mint also gets a binary membership
call in the same tick. A non-member names the release issue as its blocker
in its own Dependencies. A member is placed with three writes: the new issue
names its immediate member predecessors; every downstream member adds or
re-points its dependency to the new issue, dropping any predecessor the new
issue now reaches (inserting X into A → B makes A → X → B, so B drops A);
and the release issue adds the new issue to its gate, recording membership
only. A member may have multiple successors. Collision and window edges are
independent, so write both when both apply (#292).
names its immediate member predecessors; every member whose immediate
predecessor the new issue becomes adds or re-points its dependency to the
new issue, dropping any predecessor the new issue now reaches (inserting X
into A → B makes A → X → B, so B drops A); a member that must land after the
new issue but already reaches it through another member declares nothing
new; and the release issue adds the new issue to its gate, recording
membership only. Collision and window edges are independent, so write both
when both apply (#292).
- **Labels**: type (`bug`/`enhancement`/`documentation`), `scope:*`, and
exactly one of `ready` / `blocked` (see [LABELS.md](LABELS.md)).