Skip to content

Harden skill refinement from headword hardening work - #48

Open
wtmoose wants to merge 1 commit into
mainfrom
work/skill-refinement
Open

Harden skill refinement from headword hardening work#48
wtmoose wants to merge 1 commit into
mainfrom
work/skill-refinement

Conversation

@wtmoose

@wtmoose wtmoose commented Aug 19, 2026

Copy link
Copy Markdown
Member

Accumulated P3.4.1 changes from the headword-core hardening effort, verified in live use across the P3.4.2 production repair pass and the full P3.4.3 cold-operator re-run (multiple generations of scoped authoring reviews ran on these template slots without a template-side defect).

Cold-review template (Guides/Process/cold-review-prompt-template.md)

  • Optional scoped/empirical-review slots: EXCLUDED_SURFACES, OBSERVED_FAILURES, PROPOSED_EDITS, REPORT_CHARTER — enabling per-change scoped reviews (a fresh cold round that designs an edit from failure evidence) alongside the existing whole-document reviews.
  • Reviewer-facing "Stranded is not broken" triage rule: a gap that merely strands the operator into a designed escalation route is log-only until it occurs; only text teaching a wrong action is repaired at any likelihood.

Skill-refinement guide (Guides/Process/skill-refinement-guide.md)

  • Scoped/empirical reviews recognized as a review kind.
  • Codification bar scoped to codification decisions.
  • Declared size budgets bind repairs: net size cost per repair, pair-with-trim discipline, and cannot-fit routes to a human decision.
  • Strand-class findings are log-only while a designed escalation route exists.

Release and submodule-pointer update handled separately.

🤖 Generated with Claude Code

Accumulated P3.4.1 changes from the headword-core hardening effort:

- Cold-review template: optional scoped/empirical-review slots
  (EXCLUDED_SURFACES, OBSERVED_FAILURES, PROPOSED_EDITS, REPORT_CHARTER)
  and the reviewer-facing "Stranded is not broken" triage rule.
- Skill-refinement guide: scoped/empirical reviews recognized; codification
  bar scoped to codification; declared size budgets bind repairs (net size
  cost, pair-with-trim, can't-fit routes to human decision); strand-class
  findings are log-only while a designed escalation route exists.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant