amadan
intent: name the bootstrap exception to the CI merge gate
A new repo has no CI script, so "merge only when CI is green" is a condition nobody can satisfy — including the branch whose whole job is to add CI. Stated as an absolute it deadlocks the first merge of every new project. amadan already resolved this correctly and we were stricter than the forge: its merge gate defaults to off because "a gate nobody chose is not a gate", and it reports a scriptless repo's CI as skipped rather than failing. So the rule now says what it always meant — CI green binds where CI exists — and marks adding CI as the first work item rather than a prerequisite.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1 file changed,
+9
−0
AGENTS.md+9 −0
Intent
Attributed to this commit: 239 g CO₂e (20912490 tokens). This is an attribution, not a measurement — usage counted from this commit's own marker forward to the next one on intent, never backward from it. A turn that produced more than one commit books all of its tokens to the last one, and a concurrent session on this branch can add to the same figure. Some of it was priced using the shared default rate, because no model-specific factor row exists yet for at least one model involved. The Carbon view has the repo total, which is never derived from this attribution.
diff --git a/AGENTS.md b/AGENTS.md| index dc2e637..401d6d3 100644 |
| --- a/AGENTS.md |
| +++ b/AGENTS.md |
| @@ -342,6 +342,15 @@ building the same thing overnight. |
| `AMADAN_HOME`), never as the human. The 🤖 badge is not optional. |
| - Squash-merge to main only when all three hold: the work is done, a human |
| has approved it, and CI is green. Never commit to main. |
| +- **The bootstrap exception, once.** "CI green" binds where CI exists. This |
| + repo has no CI script until `web/1` lands, so there is no green to wait |
| + for and the condition cannot be met by anyone. amadan agrees: its merge |
| + gate defaults to off — *"a gate nobody chose is not a gate"* — and |
| + reports such a repo's CI as `skipped`, "this repo has no CI script, so |
| + nothing can be green". So the first merges land on **done + approved**, |
| + and **adding CI is itself the first work item**, not a prerequisite that |
| + cannot be satisfied. The moment `.amadan/ci` exists the three-condition |
| + rule binds absolutely, and this paragraph is spent. |
| - Commit subjects are area-prefixed prose that says why. Every commit |
| carries a `Co-Authored-By:` trailer; the human is the author of record. |
| - Review happens on a deployed canary, never on localhost. Report the |