Skip to content

feat(harness-memory): hand C8's move up the hierarchy to /corrections:codify #17179

Description

@kyle-sexton

Parent

Refs #15703
Source: #16029, part 2 of #15729. The list recorded in #16602 gives /harness-memory:audit ("fix action") the route "call /corrections:codify, presence-gated, with the strongest-first fallback".

Depends on

Outcome

C8 ("Enforcement Hierarchy") today lists six mechanisms a CLAUDE.md instruction "could be" and asks the audit to name "which enforcement level it could move to"; the fix action then has no C8 pattern and chooses freely. After this change a C8 instruction that could move up is handed to /corrections:codify when it is available, with the shared strongest-first fallback when it is not, and the fix action gets a C8 pattern that does the same. C8 items 4 and 5 (prose a located check already enforces, and the hold for protected classes) do not change.

Demo: with a corrections stand-in plugin loaded, /harness-memory:audit then fix on a CLAUDE.md holding an import-order rule no check covers reports C8 WARN naming /corrections:codify for the move, and the fix proposal hands the rule to codify instead of proposing a linter rule or a hook itself.

Where the text changes

Line numbers as read on main at a483a2c1; they may move, and #16985 changes the bullet at :301.

File and lines Present wording Change
plugins/harness-memory/skills/audit/reference/criteria.md:294-308 (C8 "How to check", items 1-3) "For each rule/instruction, check if it could be: A compiler setting (nullable, warnings-as-errors); A static-analyzer or linter rule; An architecture test; A pre-commit/pre-push git hook; A CI gate; A Claude Code hook (deterministic) ... Include which enforcement level it could move to" Item 1 asks whether a check could decide the instruction, without a mechanism list; item 3 hands the level to /corrections:codify (gate plus shared fallback). Add a Provenance line that marks the new text as this repository's rule, as items 4 and 5 already carry, so the update action does not overwrite it
same file, :127-128 (C3 placement table) "Deterministic enforcement | Hooks (guaranteed execution)"; "Compile-time/build-time rules | Analyzers, linters, architecture tests" One row: content a check could decide goes to /corrections:codify for its mechanism, with the fallback
plugins/harness-memory/skills/audit/context/fix.md ("Common fix patterns", no C8 section today) none Add "C8 (Enforcement Hierarchy) fixes": hand each WARN that could move up to /corrections:codify rules <the file> or /corrections:codify "<the rule>"; the prose stays until the check exists, then goes in that change (C8 item 4)

Decisions

Key interfaces

  • "A skill that carries no ladder copy calls /corrections:codify, presence-gated, with a two-sentence strongest-first fallback. Only a skill that applies its own selection rule holds a synced copy and gets a row in the ladder's Selection rules table." (List enforcement-placing skills and give each one route to the ladder #15729)
  • The seam-phrasing convention: an availability gate, a stated fallback beside it, the plugin named and never the marketplace.
  • The instruction exception register keeps owning which instructions hold their prose (C8 item 5).

Done when

  • C8 items 1-3 hand the move up the hierarchy to /corrections:codify behind the availability gate, followed by the shared fallback, and list no mechanisms of their own; items 4 and 5 are unchanged.
  • The new C8 text carries a Provenance line so the update action does not overwrite it.
  • context/fix.md has a C8 pattern that hands each instruction to /corrections:codify and keeps the prose until the check exists.
  • The skill gains no ladder copy or Selection rules row, and no rung list is restated.
  • The pull request body quotes the sentence that picked a mechanism from a private list before the change. If the recheck finds none, the skill is left unchanged and the finding is reported on List enforcement-placing skills and give each one route to the ladder - part 2 of 2 #16029.
  • One new eval case loads a corrections stand-in plugin, in the shape of session-flow's re-mechanical-finding-check-proposal case, and grades that a C8 instruction no check covers is handed to /corrections:codify and the audit picks no mechanism itself.
  • The pull request body names the existing case whose run reads the changed text (candidates: audit-c8-enforced-prose, audit-fix-needs-prior-audit), or says none does. The lane runs no eval.
  • A changelog fragment under .changes/harness-memory/ describes the change.
  • AC10: no new enforcement-placing skill is added here.
  • Open the pull request with Closes this issue in its body, then stop: the lane adds no label.

After the pull request opens (host session, not the lane)

The pull request stays held with do-not-merge for the eval; a host session runs only the eval and posts its record; the merge lane releases the hold when the record matches the head.

  • Hold line: the hub's sweep (or a host session) adds do-not-merge and posts, from a listed human's account, a comment with the line <!-- pr-hold reason=eval --> on a line of its own.
  • Run budget. List enforcement-placing skills and give each one route to the ladder #15729 asks for "that skill's cases on the opus and sonnet aliases, three runs per side, and no more than 240 runs per plugin". The owner decision of 2026-11-16 in the owner-decisions record (hop 4 Q15, which names List enforcement-placing skills and give each one route to the ladder #15729, amended by hop 7 Q3) replaces the run counts: per changed skill, one targeted before-and-after case on sonnet at 3 runs a side; opus runs only to confirm a sonnet loss; a new case gets a 1 to 3 run smoke first. Select cases with --case, use --runs 3 and a --max-cost-usd ceiling, and start no batch after a usage-limit error. Ceiling for this plugin: 1 skill x (3 smoke + 6 sonnet + 6 opus confirm) = 15 runs, under the parent's 240.
  • Control: the removed mechanism list is a partial cut, so the pull request body carries a detection-control result. No paired no-loss compare (#15703 comment 6906800940).
  • On a LOSS reading: a trace read of each dropped case and an opus confirm; only a loss traced to the changed text counts.
  • Record: the verdict and the control result go into the pull request body. When the run is VALID and shows no loss, the host session posts, from a listed human's account, a comment with the line <!-- eval-pair verdict=no-loss validity=VALID head=<40-hex head SHA> --> naming the current head, keeping "do not merge" and do-not-merge out of that comment (docs/contracts/loop-lane/README.md, "Cross-lane PR hold"). A loss or a run that is not VALID leaves the hold in place; say so on the pull request.
  • Release: pr-merge's scheduled step "Release eval holds whose record matches the head" removes do-not-merge once that record names the current head and no other hold stands. A push after the record needs a new record.

Out of scope

Related

Activity

  1. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 18, 2026
  2. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 18, 2026
  3. github-actions commented on Nov 18, 2026

    @github-actions
    Contributor

    Size: Medium
    Complexity: Medium
    Uncertainty: Known
    Flags: none
    Blocked by: none
    Blast radius: harness-memory audit skill text (criteria.md C8 and C3 row, context/fix.md), one new eval case and a changelog fragment; read by the audit skill and anyone running /harness-memory:audit.
    Reversible: yes; revert the text, case and fragment.
    Open questions: none
    Understood: the audit's C8 items 1-3, the C3 placement row and fix.md should hand a movable instruction to /corrections:codify behind an availability gate with the shared fallback, with no mechanism list or ladder copy, plus a Provenance line and a changelog fragment. The two eval/recheck items are person-run checks, already split out by the refinement comment. The dependency #16985 is a pull request (for #16775), so it is not listed as a blocking issue; start after it merges or closes. Related sibling hand-offs: #17158, #17163, #17159, #17175. #16928 may touch the same files. No duplicate or merged fix found.

    Automated triage. A maintainer reviews it.

  4. removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 18, 2026
  5. melodic-automation-lanes commented on Nov 18, 2026

    @melodic-automation-lanes
    Contributor

    Not admitted to the issue lane: its done-when asks for what an unattended lane run cannot perform: item 5 (tracker-output: "The pull request body quotes the sentence that picked a mechanism from a priv..."), item 6 (eval: "One new eval case loads a corrections stand-in plugin, in the shape of sessio..."); recommended split: keep the other items here as the admissible issue and move these to a child issue for the host queue (host-run). Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).

  6. melodic-automation-lanes commented on Nov 18, 2026

    @melodic-automation-lanes
    Contributor

    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: The harness-memory audit's C8 items 1-3, its C3 placement row and fix.md hand a movable instruction to /corrections:codify behind an availability gate with the shared fallback, with no mechanism list or ladder copy, plus a Provenance line and a changelog fragment.

    Split. Done-when items 5, 6 of the issue body need a person: they are checks a person runs, listed below, and the lane does not do them. This issue keeps the rest of its done-when.

    Not done by the lane: checks a person runs

    External state: none

    Dependencies

    • #​16985 (for #​16775): edits the C8 bullet list this item rewrites; start after it merges or closes and rebase onto it.

    Related work

    Sources read

    • plugins/harness-memory/skills/audit/reference/criteria.md:293-317: C8 still lists six mechanisms in items 1-3 and asks which enforcement level an instruction could move to; items 4 and 5 are present.
    • plugins/harness-memory/skills/audit/context/audit.md:121: C8 is reported for prose a deterministic check already enforces.
    • plugins/harness-memory/skills/audit/context/fix.md: exists in the checkout; the issue says it has no C8 section.

    Automated refinement by the lanes App. Intake triages the issue again with it.

  7. melodic-automation-lanes commented on Nov 18, 2026

    @melodic-automation-lanes
    Contributor

    {"v":1,"actor_id":337595936,"title_sha256":"722e70f06f08839b0d96b7fd3300fccb58100c532b8f8e1ed55fd79263509de6","body_sha256":"d1737855c9c013b39e6f643beb0576444965f23417cf2337fe9ab1108113adab"}

  8. melodic-automation-lanes commented on Nov 18, 2026

    @melodic-automation-lanes
    Contributor

    {"v":1,"actor_id":337595936,"title_sha256":"722e70f06f08839b0d96b7fd3300fccb58100c532b8f8e1ed55fd79263509de6","body_sha256":"d1737855c9c013b39e6f643beb0576444965f23417cf2337fe9ab1108113adab"}

  9. github-actions commented on Nov 18, 2026

    @github-actions
    Contributor
    No description provided.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.

    Fields

    Work status

    needs-triage

    Priority

    medium

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions