From 43d845575af32e212ef1e9af0ebf1de1a0e0c0e3 Mon Sep 17 00:00:00 2001
From: cndgrr <59120057+cndgrr@users.noreply.github.com>
Date: Tue, 4 Aug 2026 13:39:06 +0000
Subject: [PATCH] docs(builder): state #276's collapse rule in full, not by
 allusion

---
 BUILDER.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/BUILDER.md b/BUILDER.md
index a1b8650..2aa0929 100644
--- a/BUILDER.md
+++ b/BUILDER.md
@@ -163,9 +163,11 @@ such as the panel roster live in that repo's own CONTRIBUTING.)
    newest entry by start time — not completion, a cancelled run outliving
    its replacement's start — and never a `CANCELLED` entry while the same
    check has a non-cancelled one there. A check whose entries at the head
-   are all cancelled has not reported at all and is not green, the gate
-   collapsing alike (#139, #276). **Then classify that entry by
-   `conclusion`, never `status`**, which can disagree with it (#259). No
+   are all cancelled has not reported at all and is not green — a collapse,
+   not a new class, and the gate partitions alike, dropping a cancelled
+   entry only where a non-cancelled survivor remains and leaving an
+   all-cancelled context blocking (#139, #276). **Then classify that entry
+   by `conclusion`, never `status`**, which can disagree with it (#259). No
    conclusion is not green: a configured run in progress is waited on, and
    waiting is compliance, not a stall. Cancelled or stale is not green,
    *stale* being a superseded head's check, which a head-scoped rollup never