Repository navigation
Description
Decision (owner, 2026-11-14; answers researched and recorded 2026-11-15)
Source: the talk "All Code Is Slop (Except Mine)" (Lauren Tan, AI Engineer Code Summit, 2026-11-11), slides 12 and 23: every correction becomes a check.
The owner's instruction of 2026-11-14 was to research each interview question and take the recommendation. The answers, recorded 2026-11-15:
-
What counts. A merged change that adds or raises a check, or removes the mistake by design (the
make-impossiblerung), and names the correction it answers. The rule-to-enforcer inventory is no longer this item's: Generate the rule-to-enforcer inventory and its per-tier count #15711 builds it. -
The record. One line in the pull request body, starting at column 0 on a line of its own (not a list item, indented line or quote), at most 72 characters so the squash wrap cannot split it. The source is
#<n>(the issue, or the pull request whose review raised the correction) or the literalsession, never a URL:Codifies: <#issue-or-PR | session> rung=<rung id> <blocking|advisory>The whole line must match
^Codifies: (#[1-9][0-9]*|session) rung=<rung id> (blocking|advisory)$, so a prose mention or quoted example is not counted. It is not a git trailer: the squash commit appends itsCo-authored-by:paragraph after the body, so a body line is never in the trailer block. It is read withgit log --grep='^Codifies: '. The key is fixed.make-impossiblerecords areblocking. -
Rung ids. Counted rungs are the codebase, static-analysis and verification tiers of the ladder; guidance and human-review rungs are listed as not counted.
semgrep-rulereads assyntax-pattern-rule. -
Ladder ids (owner, 2026-11-15). The ladder rows "Compiler or type settings" and "Tests" get rung ids, as a minor ladder version (3.0.0 to 3.1.0). The owner copy is
docs/contracts/enforcement-ladder/README.md, with a[3.1.0]entry in theCHANGELOG.mdbeside it; the five plugin copies listed inscripts/shared-copies.txtare regenerated byscripts/sync-shared-copies.sh, and each plugin carrying a copy takes a version bump. Proposed ids, for/planning:planto confirm against the existing ids:compiler-settingandbehavior-test. -
Who writes it.
/corrections:codify's proposal holds the line, and for work filed as an issue, a task-list item carrying it in a code span. The issue lane copies such a line from the issue into its pull request body, the same way it copiesRefs:lines today (.github/scripts/work-resolve-issue/report-outcome.mjs,linkageLines), and never from the run's own text. -
Who reads it. A new read-only action,
/corrections:codify count-checks [--since] [--until] [--bucket week|month], from default-branch git history only, with no forge call. -
The number. A cumulative count per week or month and the window total, like slide 23. Blocking checks are the headline; advisory checks get their own column; a column per rung that occurs. No ratio.
-
Advisory checks. The change that makes an advisory check blocking carries the line again with
blocking, and the check moves columns; it is counted once. How that line names the earlier record is for/planning:planto settle. -
Start. The count starts when
count-checksships. No backfill, and no hand-kept list inside the action. The seven checks that landed on 2026-11-13 without a record (feat(guardrails): block foreground until loops and --watch waits #15955, feat(scripts): flag docs-page links with no section anchor in skill and agent files #15960, ci: run the rules-index check on every pull request #15965, feat(guardrails): make the unpinned force-with-lease a setting; this repository blocks it #15968, ci: check that an as-of date in a skill file carries a recheck trigger #15989, feat(ci): report a Follow-ups bullet without the advisory marker #16008, ci: fail a price or savings figure in skills, docs and prompts #16022) are named in the dogfood result posted on this issue as landed before the record. -
Trust measures. They stay at three. Pull-request volume is covered by deployment frequency (
/work-items:measure-delivery), app performance by/performance:protect. Release cadence is skipped because it tracks the release bot's schedule; contributors per month is skipped because it is a per-person count. -
No-human-touch merge share. One new item builds it in
/work-items:morning-brief, beside Owner touches. No combined trust view.
Done when
-
/corrections:codify count-checksis listed in the skill's Actions table, argument hint and action words; a bad--since,--untilor--bucketvalue stops it before it reads history; it writes no file and calls no forge. - It counts each
Codifies:line on the default branch that matches the grammar above in full; a malformed line, a line with other text on it, a list-item line, or one naming a guidance or human-review rung is listed as not counted, with its commit. - Its output has one row per period (new and cumulative) and a window row, with blocking, advisory and per-rung columns, and no ratio; the cumulative value counts from the first record in history whatever
--sinceis; an empty history prints zeros. - A check recorded as advisory and later recorded as blocking is counted once, in the blocking column from the later change.
- A record whose commit was later reverted on the default branch is not counted, and is listed as reverted.
- Tests over a fixture repository cover the squash shape (line, then the
Co-authored-by:paragraph), a list-item line, a line with trailing prose, a malformed and a placeholder line, thesemgrep-rulealias, a record naming one of the two new rung ids, a promotion, a revert, and an empty history. - Codify's proposal for a checking rung or
make-impossibleholds the literal line, and the task-list item form for an issue; amake-impossibleproposal names the type or API to change. - The issue lane copies a
Codifies:line from an issue's task-list item into its pull request body in both of its body builders, and does not copy one from the run's own text; its tests cover both. -
docs/contracts/enforcement-ladder/README.mdis atenforcement-ladder: 3.1.0, its "Compiler or type settings" and "Tests" rows carry backticked rung ids, itsCHANGELOG.mdhas a[3.1.0]entry naming both, andscripts/sync-shared-copies.sh --checkand--check-bumppass on the pull request. - One issue is filed for the no-human-touch merge share in
/work-items:morning-brief. - Map: integrate the 'All Code Is Slop (Except Mine)' talk into plugins and skills #15651 records that the trust measures stay at three, with the covered and skipped slides.
Out of scope
-
The recorded
/app-control:driverun ofcount-checksand its posted output: moved to Let the pr-verify capture record a command-running skill's drive run #16383 (owner, 2026-11-15), because the capture cannot record a command-running skill yet. -
The rule-to-enforcer inventory and its per-tier count: Generate the rule-to-enforcer inventory and its per-tier count #15711.
-
A ratio of converted corrections, or a store of every correction.
-
Backfilling checks that landed before the record.
-
Release cadence or contributors per month as measures; a combined trust view.
-
Building the no-human-touch share (this item only files it).
-
A configurable record key; reading the findings buffer.
-
Moving, renaming or removing any ladder rung.
Metadata
Metadata
Assignees
Labels
Type
Fields
Work status
Priority
Activity
github-actions commentedon Nov 12, 2026
Size: Medium
Complexity: Medium
Uncertainty: Knowable
Flags: intent
Blocked by: none
Understood: count the corrections that became checks, and generate the rule-to-enforcer inventory (each written rule and the check enforcing it) instead of keeping it by hand. Dogfood on this repo's always-loaded rules. I found no duplicate open issue or merged fix.
Open design questions the issue leaves unpicked:
/corrections:codify(group action) or/session-flow:audit-sessions? RECOMMENDED:/corrections:codify, because corrections are its subject and the count then sits beside the rule-to-check step. Basis: the issue's candidate list; no repo evidence checked beyond it.To answer, post a comment that starts with this line:
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 12, 2026
The triage verdict left this issue at
needs-owner-decision:Reason:
intentmelodic-automation-lanes commentedon Nov 12, 2026
Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.
Intended outcome: A generated rule-to-enforcer inventory, probably owned by /corrections:codify, with the count of rules that name an enforcer as a rollup of it, plus a dogfood run on this repository's always-loaded rules.
Related work
Open questions
RECOMMENDED: /corrections:codify, as a new read-only action rather than an extension of group, because group counts buffer rows by mistake and the inventory reads rule files. Basis: .base/plugins/corrections/skills/codify/SKILL.md:34
RECOMMENDED: Count inventory rules that name an enforcer, so the count is a rollup of the inventory and needs no second source. The owner said /planning:interview should lock this. Basis: judgment
RECOMMENDED: Yes, one artifact with the count as a rollup. The Brief was not found in the checkout, so confirm it exists before design. Basis: judgment
RECOMMENDED: Read AGENTS.md and the root rule files, and map each rule to a check by an explicit marker or reference in the rule text. Do not infer by guessing. Basis: .base/docs/upstream/cursor-pstack.md:101
RECOMMENDED: Yes, in generated form only: output goes to a report or generated file, never into AGENTS.md. Record this so the cursor-pstack row is updated to match. Basis: .base/docs/upstream/cursor-pstack.md:101
Sources read
To answer, post a comment that starts with this line:
Automated refinement by the lanes App. Answer with a comment whose first line is
**Decision recorded.**.github-actions commentedon Nov 15, 2026
fix(corrections): keep a malformed record at column 0 in the default …
test(corrections): make the emphasis-form fixture independent of the …
kyle-sexton commentedon Nov 16, 2026
Narrowing, as #15711 asks (plan decision D5): this item is the corrections-to-checks counter only. The rule-to-enforcer inventory, its per-tier count and the "sits lower than it could" list are built once, in #16555, as the "Ladder spread" step of
/harness-config:audit-automation-gaps. The counter stays a separate measure and reads none of it.