⚠️ 이 블록은 영어 원본을 한국어 볼트용으로 감싸는 마스터 오버라이드입니다. 아래 본문·references의 어떤 영어 지시와 충돌하더라도 이 블록이 우선합니다. 프레임워크의 판단 로직·정규식·구조는 그대로 따르되, 아래 두 가지만 한국어 기준으로 바꿉니다: (1) 사용자에게 보이는 출력 언어, (2) 언어 종속적 수치·치환 규칙.

• Step 0/1/1.5의 안내 문구, 발견 요약 블록, 분류 표
• 프레임워크 진행 라인(예: "F1 … → 22건 발견")
• 모든

  AskUserQuestion

  walk 질문과 선택지
• 각 finding의

  reasoning

  ·

  action

  ·

  excerpt

  설명(원문 인용 excerpt는 원본 유지, 그에 대한 설명은 한국어)
• HTML 리포트의 모든 라벨·헤더·설명(한국어 템플릿 사용 — 아래 오버라이드 4)
• 최종 요약 블록

reasoning

bytes/4

chars/4

bytes/4

chars/4

tokens ≈ bytes/4

한글_글자수 = 유니코드 Hangul(음절 AC00–D7A3, 자모 1100–11FF, 3130–318F) 개수
그외_글자수 = 공백 제외 나머지 글자수 (영문·숫자·기호·코드)

추정_토큰 ≈ (한글_글자수 × 1.5) + (그외_글자수 × 0.25)

• 계수

  1.5

  (한글)와

  0.25

  (그 외)는 근사치이며 토크나이저·내용 구성에 따라 변합니다. 안전을 위해 살짝 과대 추정하는 방향으로 잡았습니다(예산 초과를 놓치는 것보다 일찍 경고하는 게 낫다)
• 토큰 예산 수치 자체는 바꾸지 않습니다. 예산(F4 자동로드 ~3K, daily 2K, F5 파일당 권장 ~2.5K / 하드 25K)은 언어 중립적 목표입니다. 바뀌는 건 오직 "이 파일이 몇 토큰인가"를 세는 방법뿐입니다
• 결과: 영어 공식으로는 예산 안에 들어 보이던 한국어 파일이 실제로는 초과인 경우를 정확히 잡아냅니다. 리포트의 "절감 토큰" 수치도 한국어 기준으로 맞습니다

• F5 파일당 권장 예산을 바이트가 아니라 토큰으로 판정합니다: 오버라이드 1 공식으로 추정한 토큰이 권장 ~2,500토큰 초과 → warn, 하드 25,000토큰(또는 100KB) 초과 → fail. 바이트(KB)는 참고용 보조 지표로만 리포트에 병기
• G7.4 README 밀도: "sparse"·"bloated" 판정도 바이트가 아니라 토큰/내용 충실도로 봅니다. 한글 README는 같은 정보량이라도 바이트가 크니 8KB 기준을 그대로 쓰면 멀쩡한 문서가 bloated로 잘못 잡힙니다. sparse는 "개요·상태·다음 단계 중 빠진 게 있는가", bloated는 "한 파일에 분리돼야 할 하위 주제가 여럿인가"로 판정(바이트는 참고만)

• 두 절을 잇고 뒤 절이 앞을 부연 → 마침표로 문장 분리, 또는 "즉,"·"곧"·쉼표로 연결 (콜론

  :

  은 한국어 산문에서 어색하니 지양)
• 삽입구 설정 → 쉼표(

  , … ,

  ) 또는 괄호(

  ( )

  )
• 절 끝에서 마침표 역할 → 마침표(

  . 

  )로 문장 분리
• 숫자·날짜 범위의 엔대시(

  100–200

  ,

  2026–2027

  )는 유지(위반 아님)
• 인용문 안의 대시는 원문 보존

• 문장 끝 "~것입니다"·"~할 수 있습니다"의 기계적 반복(한 문단 3회 이상)
• 상투적 마무리어 뭉침: "종합적으로"·"결론적으로"·"요컨대"·"정리하자면"의 남발
• 접속어 스태킹: "또한"·"게다가"·"뿐만 아니라"의 연속 사용
• 강조어 인플레이션: "매우"·"굉장히"·"정말"·"너무"의 습관적 삽입
• 번역체 조사구 남발: "~에 대해"·"~을 통해"·"~에 있어서"·"~와 관련하여"
• 3개 병렬(rule of three)이 기계적으로 반복되는 문장

• Step 0 시작 안내: "9개 프레임워크로 볼트를 감사합니다. 먼저 폴더 구조를 파악하고(Step 1.5 — 폴더 이름을 가정하지 않습니다), 이후 모든 수정안을 항목별로 함께 검토합니다. 각 단계는 작업(task)으로 표시됩니다."
• 볼트 아님 판정: "마크다운 볼트로 보이지 않습니다 — .md 파일이나 CLAUDE.md를 찾지 못했습니다. 볼트 루트로 이동한 뒤 다시 실행해 주세요."
• 프레임워크 진행 라인: "F1 Anthropic CLAUDE.md — CLAUDE.md 14개 읽고 후보 312건 판단 → 22건 발견 (fail 5 · warn 17)" 형식
• 최종 요약(Step 6.4 Part 3):

  ✅ 최적화 실행 완료 — 이번에 바뀐 내용입니다:
  리포트: {결정폴더}/{YYYY-MM-DD}-vault-audit.html
  JSON 원본: {결정폴더}/{YYYY-MM-DD}-vault-audit-findings.json
  점수(F1–G7): {전} → {후} ({부호}{델타}) — "{해석_전}" → "{해석_후}"
  파일 {N}개 감사 · 수정 {적용수}건 적용 · 기계적 실패 {실패수}건 (사유는 리포트 참고)
  em대시: {전} → {후} · 프론트매터 완결: {전}% → {후}% · 폴더 인덱스 커버리지: {전}% → {후}%
  절감 토큰: {절감}(에이전트 로드 {비율}% 감소) · 주 {세션}회 기준 연 ~{연간절감} 토큰 절약

  선택-walk 모드면 "계획 저장 {n}건 · 거절 {n}건" 줄을 덧붙입니다

아래 본문은 영어 원본 지시입니다. 로직·구조·정규식은 그대로 따르되, 사용자에게 보이는 모든 출력은 상단 오버라이드 0에 따라 한국어로 냅니다.

1. Every finding ships a concrete fix. No flag-only. No "warn and forget." No manual-review pile. When the user runs apply-mode, every finding becomes either an applied edit, a saved migration step in a dated reorg plan, or (only if the user explicitly declines this finding in walk) a recorded decline. Nothing lingers as an open warning across runs.
2. Severity is informational, not gating.

   fail

   /

   warn

   /

   info

   describes how load-bearing the issue is; it does not gate whether a fix is offered. Every check produces fixes.
3. Walk per item, user picks the target. Bulk-apply is reserved for purely mechanical fixes (em dashes, duplicate H1). Anything semantic — wikilink repointing, merges, routing rewrites, Plot.md generation, reorganizations — is walk-only with the user confirming the destination/winner/wording per item.
4. Two modes for every fix: apply now (executes in this run) or save to plan (writes the change as a checklist step into

   Intelligence/decisions/{date}-reorg.md

   for staged execution). User picks per finding for high-blast-radius items. Smaller fixes default to apply-now.
5. Visible progress, never silent. Step 0.5 creates one TaskCreate entry per stage and per framework; tasks update

   in_progress

   →

   completed

   as the run unfolds. The user watches the audit walk through the vault rather than waiting for one big report at the end.
6. Read and reason, don't just match. Every framework's triggers surface candidates; every finding requires the agent to read context, judge alignment with the user's stated world, and produce reasoning specific to the case. No paraphrased rule restatements as "reasoning."
7. Discover structure, never assume folder names. Vaults vary. One user's curated layer is

   Context/

   ; another's is

   About/

   ,

   Me/

   , frontmatter on root, or scattered across topic folders. The optimizer runs Step 1.5 (role discovery) before any framework, and every framework references roles (context-equivalent, decisions-equivalent, daily-equivalent, folder-index convention…) discovered from content — never hardcoded names. If a role is missing, it surfaces as a finding with a proposed fix ("you have no decisions-equivalent folder; here's a recommendation"), not as a silent assumption. Static path references in pass files are always abstractions; the agent resolves them through the role registry at run time.

1. Verify the cwd looks like a vault — light check (Step 0)
2. Create the visible task list — TaskCreate one task per stage + framework (Step 0.5)
3. Discover & classify every

   .md

   file — only technical skips (Step 1)
4. Iterate frameworks F1 → F9, applying each framework's lens with agent judgment; F8 = cross-vault synthesis, F9 = whole-vault structural reasoning + discoverability walk (Step 2)
5. Aggregate findings + write the architectural read paragraph (Steps 3 and 3.5)
6. Walk every finding through apply-now / save-to-plan — no skip option for fixes; every finding becomes an applied edit, a saved migration step, or an explicit per-item user decline (Step 4)
7. Apply approved fixes (Step 5)
8. Render HTML dashboard, save, open in browser, emit as artifact (Step 6)

test -f CLAUDE.md || test -f claude.md
[ "$(find . -maxdepth 4 -name 'CLAUDE.md' | head -1)" ]
[ "$(find . -maxdepth 1 -name '*.md' | wc -l)" -gt 0 ]

마크다운 볼트로 보이지 않습니다 —

.md

파일이나

CLAUDE.md

를 찾지 못했습니다. 볼트 루트로

cd

한 뒤 다시 실행해 주세요.

9개 프레임워크로 볼트를 감사합니다. 먼저 폴더 구조를 파악하고(Step 1.5 — 폴더 이름을 가정하지 않습니다), 이후 모든 수정안을 항목별로 함께 검토합니다. 각 단계는 작업(task)으로 표시됩니다.

• F1 Anthropic CLAUDE.md → {n} CLAUDE.md files
• F2 Karpathy Wiki → {n} content notes (notes + context + decision + meeting + index + readme) + 1 schema doc check
• F3 Caveman → {n} instruction-layer files (CLAUDE.md + SKILL.md + .claude/rules + skill references)
• F4 Chroma Context Rot → {N} files (every

  .md

  )
• F5 Anthropic Memory → {N} files (every

  .md

  )
• F6 Progressive Disclosure → {n} skills
• G7 General Hygiene → {N} files
• F8 Reflection → {n} files in discovered curated-layer roles + {n} files in discovered session-layer roles ({window} window) for cross-vault synthesis
• F9 Architecture → routing table ({n} entries), {n} folders for index presence + freshness against the discovered convention, full navigation graph for discoverability, vault-specific orientation built from the discovered identity-layer

---

1. Read folder names + Plot/README/index/CLAUDE files at the top level, then top-2-deep. Build a candidate list: which folders look like they could play this role based on name + their own description?
2. Read 3–5 sample files per candidate folder. Does the content match the role's purpose?
3. Score and pick. Highest-confidence candidate wins. If no candidate clears medium confidence → role is

   missing

   .

Context/

About/

Me/

Personal/

Identity/

identity

1. Read the folder's index file (under the discovered convention) if present.
2. Sample 3–5 files in the folder. Read first 1500 chars + headers.
3. Read the parent folder's index (if any) to see how this folder is described upstream.
4. Assign a custom role:

   • name

     — a slug derived from the folder name plus content (e.g.,

     Building/

     with prototype-build content → role name

     building

     ;

     Garden/

     with idea-incubation content →

     garden

     ).

   • layer

     — one of

     curated

     (canonical, durable),

     session

     (ephemeral, time-stamped),

     archive

     (deactivated),

     meta

     (tooling, system files),

     unknown

     (agent could not confidently classify).

   • purpose

     — 1-line description of what the folder holds.

   • is_standard: false

     .

   • confidence: high | medium | low

     .

building

layer: curated

context

• Frameworks reference roles by layer, not by name. F8's curated layer = every role with

  layer == 'curated'

  (standard or custom). F8's session layer = every role with

  layer == 'session'

  . F9 walks every folder regardless of role membership.
• Custom roles participate in every framework that operates on their layer. If

  building

  is

  layer: curated

  , F8 looks at

  Building/

  for merge candidates, contradictions, themes, and promotions exactly like

  Context/

  .
• Missing roles never block a framework. If

  decisions

  is missing, F8 proceeds without it; F9.0 produces a finding suggesting the user create one (or assign the role to an existing custom folder).
• The folder-index convention is what F9.2 enforces — not Plot.md by default. If the user's vault uses README.md, F9.2 generates/refreshes README.md. If no convention exists, F9.0 proposes adopting one.
• Persisted registry is read at the start of Step 1.5. If

  .claude/vault-roles.json

  exists from a prior run, the agent loads it as the baseline and only re-classifies new folders or folders the user flagged for re-review. Confirmed assignments don't re-prompt every run.
• No framework hardcodes folder paths or file names. Examples in pass files are illustrative; runtime resolves through the registry.

in_progress

completed

1. Read the pass-implementation file for that framework (e.g.,

   references/passes-anthropic-claude-md.md

   for F1). Cache it for the duration of the framework run.
2. Determine the file scope from the table at the top of this SKILL.md (e.g., F1 = every CLAUDE.md; F6 = every SKILL.md; F4/F5/G7 = every

   .md

   ).
3. For each check in the pass file:
   • Apply the trigger heuristic (regex / metric / structural pattern) to surface candidates fast. Some checks have no trigger — the file itself is the candidate.
   • For each candidate, read the surrounding 5–15 lines with the

     Read

     tool, then apply the agent-judgment criteria the pass file lists. Read other files (linked targets, sibling clusters, the file's index) when judgment requires it.
   • Decide: does this case actually violate the framework rule in this file's specific context? Or is it a false positive (the pass file lists common ones to skip)?
   • If real → produce a finding. If not → drop it; the trigger was a candidate, not a verdict.
   • Every finding includes a

     reasoning

     field (1–2 sentences specific to this case, not a generic restatement of the rule).
4. Run the framework's vault-wide checks (using indexes from Step 1.3): orphan detection, dead wikilinks, distractor pairs, schema compliance, etc. — see each pass file's "vault-wide" sections.
5. Emit one progress line when the framework completes:

   F1 Anthropic CLAUDE.md — read 14 CLAUDE.md files, judged 312 candidates → 22 findings (5 fail · 17 warn)

   The

   judged

   count vs

   findings

   count is a sanity check: if they're roughly equal, the run was lazy (regex candidates became findings without judgment); if

   judged

   ≫

   findings

   , judgment is filtering false positives — that's the intended behavior.

{
  "framework": "F1",
  "check_id": "F1.2",
  "check_name": "Specificity heuristic",
  "path": "./Projects/foo/CLAUDE.md",
  "line": 42,
  "severity": "warn",
  "excerpt": "Be careful with auth",
  "reasoning": "This rule sits in the top half of a CLAUDE.md that's otherwise a routing index — there's no specific auth boundary, file path, or function named anywhere else. As a primary rule it falls into the 35%-compliance bucket; either anchor it to a specific path/function or remove it.",
  "action": "Either delete or rewrite as 'All /api/admin/* routes must call requireAdmin() from src/auth/middleware.ts'.",
  "fixable": false,
  "fixed": false,
  "citation": "anthropic-claude-md.md → Specificity beats vagueness"
}

reasoning

fixable: true

fixable: false

fix_status

• applied

  → fix executed this run (green FIXED pill)

• saved_to_plan

  → fix written into

  Intelligence/decisions/{date}-reorg.md

  for staged execution (blue SAVED pill)

• declined

  → user explicitly chose not to fix this item in walk (grey DECLINED pill)

• failed

  → fix attempted but failed safety check (red FAILED pill, with

  failure_reason

  )

AskUserQuestion

"Audit complete: {N_total} findings across 9 frameworks ({fail} fail · {warn} warn · {info} info). Every finding has a proposed fix. Pick mode:"

1. Bulk-apply (apply everything, no escapes) — every finding gets applied. Walk prompts only fire where the agent genuinely needs the user to pick a target/wording (e.g., "merge target: A or B?"). All else applies without per-item confirmation. The only valid non-applied state is

   failed

   (mechanical: OS lock, file conflict, dependency missing). No

   saved_to_plan

   , no

   declined

   . Use this when you've said "apply everything."
2. Selective walk — fire a per-finding prompt for every fix; user picks apply / save-to-plan / decline per item. Use when reviewing carefully or for a first run on a new vault.
3. Save everything to plan — write all proposed fixes as checklist steps into the discovered decisions-equivalent folder; no edits applied this run.
4. Cancel — abort before any fixes.

• No

  saved_to_plan

  outcomes. That state is removed from the available

  fix_status

  set.
• No

  declined

  outcomes. Same.
• The agent does not unilaterally decide a finding is "test fixture," "the user probably didn't want this," "too complex to apply mechanically," or "judgment-required-per-section" and route it to anything other than applied/failed. If applying a fix mechanically would damage content, the agent attempts the safest mechanical version (e.g., split a 222KB file at H2 boundaries with a

  <!-- automated split, review headings -->

  marker; mark the split as

  applied

  with

  applied_with_caveat: true

  ).
• Walk prompts fire only when the agent genuinely cannot pick a target without the user. Example: F8.2 merge with three plausible canonical targets — fire the prompt. Example: G7.1 em-dash substitution — apply without prompting; the agent's per-occurrence reasoning already chose the substitution.
• Mechanical failures are still recorded as

  failed

  with

  failure_reason

  (OS-locked file, missing parent directory, file conflict, framework-safety check rolled back the fix). Failed fixes are reported in the dashboard with their reason — they're not silently skipped.
• The agent must not pre-classify findings as "skip in bulk-apply mode." Every finding is in scope. If applying a daystar/ test-fixture fix damages a deliberate test pattern, the user can revert that file specifically — but the agent doesn't make that call.

1. Show the finding compactly in chat: path, severity, 1-line excerpt, the proposed fix's

   proposed_edit

   or migration step.
2. Fire AskUserQuestion with the per-finding-type sub-prompt:

1. Update the finding's

   fix_status

   (

   applied

   /

   saved_to_plan

   /

   declined

   ) and any

   per_item_target

   chosen by the user.
2. TaskUpdate the current framework's task with a

   {i}/{N}

   progress note every 10 findings.

1. If

   roles.decisions.path

   is set → save under

   {decisions.path}/{YYYY-MM-DD}-reorg.md

   .
2. Else if any folder matches

   *decisions*/

   ,

   *logs*/

   ,

   *records*/

   (case-insensitive) → use that.
3. Else create

   audits/

   at vault root and save there. Note the missing decisions role to F9.0 — the user gets a fix proposal to formalize a decisions-equivalent folder.

---
status: pending
type: reorg-plan
tags: [optimizer, plan]
date: 2026-05-08
source: os-optimizer run 2026-05-08T14:23:00Z
---

• Merge

  Notes/

  into

  Resources/notes/

  — F9.5 finding cluster: both folders hold scratch with 38% file-name overlap. Migration:
  • Move 12 files from

    Notes/

    to

    Resources/notes/

    .
  • Redirect 4 inbound wikilinks.
  • Update root CLAUDE.md routing entry to remove

    Notes/

    .
  • Delete empty

    Notes/

    directory.
  • Reasoning:

    Resources/notes/

    Plot.md states it holds reference notes;

    Notes/

    Plot.md states the same. Per

    Context/me.md

    , the user's stated convention is one resource library — keeping two is structural drift.

• Merge

  Notes/2026-q1-strategy.md

  and

  Projects/positioning/research/strategy-thoughts.md

  into

  Context/strategy.md

  — F8.2 finding. Steps: …

The plan file is itself audited next run — F1/G7 conventions apply.

before_metrics

• file_count

• total_chars

  (sum of body bytes, post-frontmatter)

• total_tokens_est

  (한국어 공식:

  (한글글자수 × 1.5) + (그외글자수 × 0.25)

  — 오버라이드 1.

  chars/4

  아님)

• em_dash_count

  (G7.1 trigger output)

• frontmatter_complete_pct

  (files with

  status:

  + ≥2

  tags:

  / total)

• wikilink_orphan_count

  (no inbound wikilink)

• index_coverage_pct

  (folders with the discovered folder-index file / non-trivial folder count)

• findings_open

  (count of findings touching files in this role)

• findings_count

• fail_count

  ,

  warn_count

  ,

  info_count

• applied_count

  (starts at 0)

• failed_count

  (starts at 0)

• score_contribution

  (per the Step 3 formula; F8/F9 always 0)

• For each

  applied

  finding: replace

  —

  →

  . 

  ,

  –

  →

  , 

  in stripped body only.
• Re-strip protected zones after; if any code/URL/wikilink was touched → revert that file's change AND set

  fix_status: failed

  with

  failure_reason

  .
• Use

  Edit

  with

  replace_all: true

  per file.
• Set

  fix_status: applied

  on every G7.1 finding whose file was successfully fixed.

• Remove the H1 line and any blank line immediately following.
• Use

  Edit

  . Set

  fix_status: applied

  .

• For each finding the user approved (bulk = top-1 suggestion, walk = chosen target): replace

  [[Old Target]]

  with the picked replacement.
• Preserve surrounding text byte-for-byte.
• Mark

  fixed: true

  per finding fixed;

  fixed: false

  for any skipped or low-confidence ones the user said no to.

• Update SKILL.md to read the vault

  Context/

  path instead of the duplicate ref.
• Grep the rest of the skill folder for the duplicate ref filename.
• If still referenced → surface conflict, skip deletion, set

  fix_status: failed

  .
• Otherwise →

  rm

  the duplicate, set

  fix_status: applied

  .

• Apply substitution table from

  references/passes-caveman.md

  to the stripped body.
• Re-strip protected zones; if any was modified → abort the fix on that file, report, set

  fix_status: failed

  for that file's findings.
• Mark

  fixed: true

  on every F3.x finding for files the agent successfully substituted.

1. F8.1 contradictions — for each approved finding: rewrite the loser file. Either replace contradicted line with

   See [[Winner]] for current state.

   (defer mode) or delete the line entirely (drop mode); the user picks per item in Step 4. Use

   Edit

   . Set

   fix_status: applied

   .
2. F8.3 stale entries — for each approved finding: rewrite the curated entry with the new state. Append

   ## History

   section with the prior wording if it has decision context (per pass file rule). Add wikilink to superseding source. Set

   fix_status: applied

   .
3. F8.2 merge candidates — for each approved cluster:
   • Concatenate unique sections from sources into the canonical target (skip duplicate paragraphs).
   • Re-check size against F5 budget. If merged file > 10KB → abort the merge, set

     fix_status: failed

     , surface as flag-only with the abort reason in

     reasoning_post

     .
   • Grep the vault for

     [[SourceName]]

     and

     [[SourceName|alias]]

     patterns; replace each with

     [[CanonicalName|alias]]

     (or

     [[CanonicalName]]

     ).
   • Verify zero new dead wikilinks (run F2.2 trigger on every file touched). If any new dead link surfaced → roll back this finding's fix, set

     fix_status: failed

     .
   • Move source files to

     Intelligence/archive/{YYYY-MM-DD}-merged/

     . Use

     Bash mv

     .
   • Set

     fix_status: applied

     .
4. F8.4 emergent themes — for each approved finding:
   • Create the new file at the user-chosen path (default

     Context/{theme-slug}.md

     or

     Resources/{theme-slug}-MOC.md

     ).
   • Frontmatter must include

     status:

     ,

     tags:

     ,

     type:

     ,

     date:

     (G7.2 compliance) and contain no em dashes (G7.1).
   • Body: 1-line definition, 3–5 key points, wikilinks back to every source note in the cluster.
   • Set

     fix_status: applied

     .
5. F8.5 promotions — for each approved finding:
   • Append the durable content to the chosen destination (

     Context/

     ,

     Resources/

     , or

     Intelligence/decisions/

     ).
   • In the source file, replace the original lines with

     See [[Target#section]]

     .
   • Set

     fix_status: applied

     .

• Re-strip protected zones on every file written. If any code/URL/wikilink/path/frontmatter was modified outside the intended edit → roll back, set

  fix_status: failed

  .
• If the touched file targets a CLAUDE.md or claude.md → abort (this should have been caught in Step 4 as flag-only, but defense in depth).
• If the touched file's size now exceeds F5's 10KB recommended budget → record the violation in

  reasoning_post

  ; the next audit run will surface it as F5 flag-only (don't roll back, but log).

1. F9.1 routing rewrites — for each

   applied

   finding:

   Edit

   the root CLAUDE.md routing table with the user-confirmed line(s). Per-item only; no batch rewrites. This is the single legitimate path for editing a CLAUDE.md (per-item user approval).
2. F9.2 Plot.md generation / regeneration — for each

   applied

   finding:
   • If missing:

     Write

     the agent-drafted Plot.md (user already confirmed Purpose + child descriptions in walk).
   • If stale:

     Edit

     to update the Children list; preserve any user edits to Purpose if not deprecated.
   • Verify size ≤ 8KB; verify G7.1 (no em dashes) and G7.2 (frontmatter complete).
3. F9.3 discoverability fixes — for each

   applied

   finding, apply the user-chosen repair:
   • "Add to Plot.md" →

     Edit

     the parent Plot.md.
   • "Add routing entry" →

     Edit

     root CLAUDE.md routing.
   • "Move file" →

     Bash mv

     ; redirect inbound wikilinks (same as F8.2 mechanic).
   • "Archive" →

     Bash mv

     to

     Intelligence/archive/

     .
4. F9.4 misplaced files —

   Bash mv

   to user-chosen folder. Update source folder's Plot.md (remove child) and target folder's Plot.md (add child). Redirect inbound wikilinks.
5. F9.5 folder duplication — for "merge into" findings: walk through file moves one at a time (each is its own

   applied

   micro-step). For "clarify Plot.md purposes" findings:

   Edit

   both Plot.mds.
6. F9.6 reorg proposals — only here if the user picked "apply now"; save-to-plan ones are already in the dated reorg file. For apply-now: walk each migration step in the proposal as its own micro-finding (move X, rename Y, update routing entry Z), each confirmed individually before execution.
7. F9.7 orientation gap —

   Edit

   root CLAUDE.md with the agent-drafted section the user confirmed. Per-item only.

• Re-run F2.2 trigger on every file touched. If new dead wikilinks appeared → roll back that fix, set

  fix_status: failed

  .
• Re-check root CLAUDE.md size against F1.1 budget after F9.1 / F9.7 edits. Over budget → record in

  failure_reason

  ; the next audit run will flag F1.1.
• Plot.md writes must pass G7.1 + G7.2 + F5 (≤ 8KB) by construction; if any check fails → roll back,

  fix_status: failed

  .

1. Read the file.
2. Apply the agent-drafted

   proposed_edit

   from the finding (the user already confirmed or edited it in Step 4.2).
3. Re-strip protected zones; if any code/URL/path/frontmatter outside the intended edit was modified → roll back,

   fix_status: failed

   .
4. If the file is a CLAUDE.md → only proceed if

   applied

   came through walk-with-explicit-confirmation (Step 4.2). Never bulk-apply CLAUDE.md edits via this runner.
5. Set

   fix_status: applied

   on success.

• F1.2 vague rule rewrite or deletion
• F1.5 platitude deletion
• F1.7 reorder for position effect
• F4.3 critical-info reorder
• F4.4 lead-in preamble removal
• F5.1 file split (split file at agent-suggested headers; user confirmed split-points in walk)
• F5.3 filename rename via

  Bash mv

  + inbound wikilink redirect

• Per-role metrics (re-run the same probes from 5.0 — files may have been split, em dashes stripped, frontmatter added).
• Per-framework metrics (recount findings against the current vault state — many findings should now resolve to zero because their underlying issue was fixed).
• Recompute the score using the formula in Step 3, against the re-measured findings count. This is

  {{SCORE_AFTER}}

  . Do not reuse the BEFORE score.
• Compute deltas:

  tokens_saved_per_role

  ,

  em_dashes_removed

  ,

  frontmatter_pct_delta

  ,

  findings_resolved_per_framework

  .