Skip to content

Commit eb71c0b

Browse files
Address second review round: verify the tier claim, and stop restating counts
Three findings from a content pass over the prose, which the first round did not cover. - **The self-entry's tier claim was checked against the wrong mechanism.** Classic branch protection reports `main` as unprotected, but an active ruleset governs it. The ruleset requires a pull request and linear history and carries no `required_status_checks` rule, so `advisory CI` stands — but the file now says how the claim was made, with the command, so the next reader can disagree with it rather than trust it. - **ROADMAP.md restated the external count in prose.** Rules 1 and 2 say a number is published from the registry with its date; a second copy in a file nothing checks is how the first one goes stale. It now points at the file instead of repeating its number. - The changelog claimed a 42-case sweep; it is 45 since the last round's fixes. Two added README lines were also left unwrapped. Co-Authored-By: Claude Opus 5 <[email protected]>
1 parent eb128df commit eb71c0b

4 files changed

Lines changed: 17 additions & 12 deletions

File tree

‎ADOPTERS.md‎

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -51,9 +51,13 @@ never counted as external adoption.
5151

5252
That row says `advisory CI`, not `blocking CI`, and the difference is worth
5353
reading. Both workflows do fail the run on `blocked` and `unknown` — but
54-
`main` carries no required status check, so a red run stops no merge. Under
55-
the definitions below that is advisory, and writing anything stronger in our
56-
own row would be the exact failure this file exists to prevent.
54+
`main` carries no required status check, so a red run stops no merge. Anyone
55+
can re-check that claim the way it was made: the branch ruleset on `main`
56+
(`gh api repos/ThreeMoonsLab/agents-shipgate/rulesets`) protects against
57+
deletion and non-linear history and requires a pull request, and carries no
58+
`required_status_checks` rule. Under the definitions below that is advisory,
59+
and writing anything stronger in our own row would be the exact failure this
60+
file exists to prevent.
5761

5862
## What the Use column means
5963

‎CHANGELOG.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,9 @@
3232
rule quietly dropped, a second badge variant, an issue form that drifts from
3333
the registry's vocabulary or stops requiring consent — and any adopter number
3434
stated anywhere in the repository's prose that these rows cannot source. A
35-
42-case perturbation sweep confirmed every one of those fails on the
36-
weakening it exists to catch, and that a correctly added adopter still
37-
passes.
35+
45-case perturbation sweep confirmed every one of those fails on the
36+
weakening it exists to catch, and that a correctly added adopter — or a
37+
second maintainer row, or a grammatically singular count — still passes.
3838

3939
- **The zero-install detector refuses an oversized candidate instead of
4040
reading it.** `tools/shipgate-detect.py` is fetched over `curl | python3`

‎README.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -892,10 +892,10 @@ Agents Shipgate is local-first and static by default, and it collects nothing:
892892
no telemetry, no analytics, no account. It therefore cannot count its own
893893
users. [`ADOPTERS.md`](ADOPTERS.md) is the opt-in public registry that stands
894894
in for that: one line per adopter, added by the adopter, naming what they gate
895-
and whether it runs locally, as advisory CI, or as blocking CI. There is **no automatic collection of any kind** behind it —
896-
every entry is user-initiated and consenting, private repositories are listed
897-
at organization granularity, and an entry is removed on request without a
898-
reason. Private design-partner observations are a separate ledger under
895+
and whether it runs locally, as advisory CI, or as blocking CI. There is **no
896+
automatic collection of any kind** behind it — every entry is user-initiated
897+
and consenting, private repositories are listed at organization granularity,
898+
and an entry is removed on request without a reason. Private design-partner observations are a separate ledger under
899899
separate consent and never become public entries on their own.
900900

901901
Every adoption number this project publishes traces to a named entry there —

‎ROADMAP.md‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,8 +79,9 @@ release qualification or to complete every open issue in that window.
7979
remain visible. [#475](https://github.com/ThreeMoonsLab/agents-shipgate/issues/475)
8080
records public consenting adopters separately, in
8181
[ADOPTERS.md](ADOPTERS.md) — opt-in, one row per adopter, with an
82-
eight-rule claims policy and a published external count of zero;
83-
dogfooding, stars and downloads do not prove external repeat use. Pilot preparation need not wait for the
82+
eight-rule claims policy and a dated external count published in the file
83+
itself rather than restated here; dogfooding, stars and downloads do not
84+
prove external repeat use. Pilot preparation need not wait for the
8485
historical-corpus outreach in
8586
[#511](https://github.com/ThreeMoonsLab/agents-shipgate/issues/511). The
8687
counts, the dated enrollment shortfall and the standing continue/narrow/stop

0 commit comments

Comments
 (0)