Skip to content

v1.4.0 — the collection retires its own gate card (14 skills)

Choose a tag to compare

@MrBinnacle MrBinnacle released this 07 Sep 21:45
· 283 commits to main since this release
Immutable release. Only release title and notes can be modified.
9cf70c5

Delivered 2026-08-31 at 9cf70c5. 14 published cards, down from 15. Nineteen changesets, one of them minor.

This release record was created on 2026-09-07. The delivery happened when the version-bump pull request merged to main, which is what ADR 0002 makes the release event; the tag and this page record it. No Release object accompanied the tag at the time, so this repository's Releases page showed v1.1 as the latest release while four deliveries shipped past it. That gap is what this page closes.

What it delivered

The collection retired its own gate card, because the gate card could not pass its own gate. skill-necessity-gate is removed.

ADMISSION.md criterion 1 requires an unaided failure that was observed, not predicted. The card's own EVIDENCE.md answered Occasions counted | 0 — no triggering occurrence, and no occurrence appeared across the card's whole life. That defect is not repairable by rewriting: an occurrence can only be found. The S295 admission triage recorded the card RECURRENCE-THIN on 2026-08-15 and deferred the call; this release makes it.

A third retirement route was added to AGENTS.md before it was used. Withdrawn on the policy covers a published card removed because it cannot satisfy the admission policy it is measured against, with the card's own evidence record as the proof and no screen required — because the failing criterion counts occurrences rather than measuring lift. The route is written narrowly: it fires on a criterion the card's own record demonstrably fails, and the changeset must quote the failing row.

Two rules outlived the card and moved into AGENTS.md in the same commit that removed the directory, so nothing that cited the card now cites a deleted file. The topology rule — decide model-invocable against procedure by asking who does the strategic thinking — is one of them.

What the version number promises

The declared surface is the install path and the card format. The card set is not part of it: adding or retiring a card is a minor change, changing the install path or a card's on-disk shape is a major change, and a correction inside a card is a patch. This release is the case that rule was written for. A scheme under which retirement forced a major bump would either inflate the major number until it carried no information, or create a standing incentive not to retire — and this collection retires cards on recorded evidence and says so on its front page.

Both documented install routes track main, so a consumer receives changed cards when a version bump merges, not when a tag is pushed.

Full changelog

Read the complete section at CHANGELOG.md.