Repository navigation
Closed
Feature
2 / 22 of 2 issues completed
Copy link
Description
Parent
Refs #15703
Source: PLAN Phase 6, topic ecosystem-specifics
Depends on
- none: on the frontier now
Outcome
The enforcement ladder reads the same in its contract and five copies at version 3.0.0: capability-named rung ids, a verification tier in third place, the proportion in words and the order of work.
Demo: the ladder contract shows ### Tier 3: Verification, and the shared-copy sync check passes.
Pre-flight first: search scripts, workflows, schemas and docs for every reader of the rung ids and of a tier named by number, and list them in the pull request. Expected: four codify eval files and one fixture file name in a docs-hygiene test (kept, it is not a rung id); no script parses an id.
What changes:
- The ladder contract, to 3.0.0:
semgrep-rulebecomessyntax-pattern-rulewith a capability definition;custom-analyzerandarchitecture-testlose their tool names; a new Tier 3 "Verification" withruntime-verificationandformal-verification(opt-in); Guidance becomes Tier 4 and Human only Tier 5; tests stay in static analysis; a proportion paragraph in words with no digit (most enforcement in the strongest tiers, least in guidance and human review); an "Order of work" paragraph (lint first, clean up, strengthen verification, then automate); an alias line acceptingsemgrep-rulewith a printed notice through 3.x. - The ladder changelog: the 3.0.0 entry lists the rename and the tier move with the tier's reason (the talk's pyramid puts verification third; tests stay in static analysis; formal verification is opt-in).
- The five carrier copies (review, session-flow retro, harness-config automation-gaps audit, architecture improve, corrections codify) are regenerated, each with one
majorchangelog fragment and no plugin version edit. - The old conventions redirect stub keeps its headings and points them at the renumbered anchors.
- Three codify eval cases (and samples) accept both id sets, so the corrections suite stays green until codify itself changes.
- Carrier skill bodies that write "tier 3" or "tier 4" by number name the tier instead.
Method:
- Each carrier's cases run as a two-version compare with graders that accept both id sets, plus one new case where consumer instructions still say
semgrep-rule. - Run budget: 800 runs (43 codify cases and about 23 cases of the four other ladder-reading skills, counted first, on the
opusandsonnetaliases, three runs per side, after two measuring runs). Select cases with--case, use--runs 3and a--max-cost-usdceiling, and start no batch after a usage-limit error. - Eval batches run in the one local eval-runner session in the main checkout. Open the pull request with the
do-not-mergelabel; the compare record releases it.
Decisions
- D6 (interview Q11, Q12): the ladder is the one representation of the pyramid: verification tier third, proportion in words, her order of work.
- Q24: the verification tier and the rung rename ship together as 3.0.0: one contract change, one regeneration, five plugin bumps.
- Q28:
semgrep-ruleis accepted as an alias, with a printed notice, through 3.x and removed in 4.0.0. - D13: public names
syntax-pattern-rule,runtime-verification,formal-verification. - Owner, 2026-11-12 (Q5): the tier's reason and the renames are stated in the 3.0.0 changelog entry, not in decision records.
- Her team's numbers are not targets: the proportion rule holds no digit.
Key interfaces
- "The enforcement-ladder contract gains a verification tier in third position with two rungs,
runtime-verificationandformal-verification(opt-in). Tests stay in static analysis. The rung idsemgrep-rulebecomessyntax-pattern-rule." - "Verification technique: the ladder's verification tier names two capability rungs and no tool. Formal verification stays opt-in."
- Conventions followed: the ladder's own version rule (a tier move or a removed id is a major); the contract-plus-synced-copy style.
Done when
- AC2: the ladder has no tool-named rung id, has a verification tier in third position, states the proportion in words with no numeric target, states the order of work (lint first, clean up, strengthen verification, then automate), and its five copies are in sync.
- The contract's frontmatter reads 3.0.0 and the changelog's 3.0.0 entry states the verification tier's reason.
- Outside the corrections plugin and changelogs,
semgrep-ruleappears only on the alias line. - Every link in the redirect stub resolves to a heading that exists.
- The two-version compare is non-inferior for each carrier and its record is in the pull request body, with this repository's dogfooding step.
- AC7: nothing is cut here, so no control result is owed.
- AC10: no new enforcement-placing skill is added here.
Out of scope
- Codify's finding classes and hand-off (the next item on this path).
- Selection rules rows for carriers (a later item).
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Work status
ready
Priority
medium
Activity
melodic-automation-lanes commentedon Nov 13, 2026
No work-resolve-issue run started in the 1 hour since
agent-readywas last added. work-unblock removed and addedagent-readyback to start a fresh run on main's workflow files. If this run ends the same way, it re-fires the issue again, waiting longer each time.github-actions commentedon Nov 13, 2026
Size: Large
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
I read this as a request to release the enforcement-ladder contract at 3.0.0. That means renaming
semgrep-ruletosyntax-pattern-rule, adding a verification tier in third place, regenerating the five carrier copies, and running the two-version eval compare. The outcome, the decisions and the done-when items are exact, so I have no open questions for you.The 800-run eval budget and the local eval-runner session are not something an unattended lane can do. Admission routes those steps separately.
I found no open duplicate and no merged pull request that already does this. The related open issues are #15703 (the parent) and #15728 (codify routing, which is out of scope here).
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 13, 2026
Not admitted to the issue lane yet: sub-issue #16078 is open.
melodic-automation-lanes commentedon Nov 14, 2026
Split at intake (owner Q93). This issue is Size Large, so its done-when is split into 2 sub-issues, each holding its task-list lines as written.
Automated split by the lanes App. Admission waits on this issue while a sub-issue is open; work-unblock closes it as completed once every sub-issue is closed as completed by a merge or a listed human and its done-when is covered.
melodic-automation-lanes commentedon Nov 15, 2026
Every sub-issue of this split is closed as completed by a listed human or a merge (#16077, #16078), so the lanes App closes it as completed.