@forwardimpact/outpost 3.3.4 → 3.4.0

package/templates/.claude/skills/extract-entities/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: extract-entities
-description: Process synced email/calendar files from ~/.cache/fit/outpost/ and ad-hoc document files (e.g. from ~/Desktop/ or ~/Downloads/) to extract structured knowledge into knowledge/ as Obsidian-compatible markdown notes. Use on a schedule, when the user asks to process/extract entities, or when invoked by another skill (e.g. organize-files). Builds the core knowledge graph from raw data.
+description: Process synced email/calendar files from ~/.cache/fit/outpost/ and ad-hoc document files (e.g. from ~/Desktop/ or ~/Downloads/) to extract structured knowledge into Knowledge/ as Obsidian-compatible markdown notes. Use on a schedule, when the user asks to process/extract entities, or when invoked by another skill (e.g. organize-files). Builds the core knowledge graph from raw data.
 ---
 
 # Extract Entities
 
 Process synced email and calendar files from `~/.cache/fit/outpost/`, plus
 ad-hoc documents passed by other skills, into Obsidian-compatible markdown notes
-under `knowledge/`. The core knowledge-graph builder.
+under `Knowledge/`. The core knowledge-graph builder.
 
 ## Trigger
 
@@ -35,13 +35,13 @@ under `knowledge/`. The core knowledge-graph builder.
 
 ## Outputs
 
-- `knowledge/People/`, `knowledge/Organizations/`, `knowledge/Projects/`,
-  `knowledge/Topics/` — created or updated.
-- `knowledge/Goals/`, `knowledge/Priorities/` — **updated only**, never
+- `Knowledge/People/`, `Knowledge/Organizations/`, `Knowledge/Projects/`,
+  `Knowledge/Topics/` — created or updated.
+- `Knowledge/Priorities/` — **updated only**, never
   auto-created.
-- `knowledge/Conditions/` — created when cross-cutting patterns are detected, or
+- `Knowledge/Conditions/` — created when cross-cutting patterns are detected, or
   updated.
-- `knowledge/Roles/`, `knowledge/Candidates/*/brief.md` — enriched with inferred
+- `Knowledge/Roles/`, `Knowledge/Candidates/*/brief.md` — enriched with inferred
   metadata.
 - `~/.cache/fit/outpost/state/graph_processed` — updated.
 
@@ -55,10 +55,10 @@ well-grounded notes">
       a substantive `## Summary`, calendar-only attendees routed to Organization
       `## Contacts`.
 - [ ] All links use absolute paths `[[Folder/Name]]`; bidirectional links
-      consistent (incl. Goal ↔ Project, Priority ↔ Goal).
+      consistent (incl. Project ↔ Priority).
 - [ ] Summaries describe relationship, not communication method; key facts are
       substantive; open items are commitments.
-- [ ] State changes logged with `[Field → value]`; no Goal or Priority entities
+- [ ] State changes logged with `[Field → value]`; no Priority entities
       auto-created.
 - [ ] Conditions created only when ≥ 3 entities reference the same cross-cutting
       state; resolution detected when evidence supports.
@@ -89,13 +89,13 @@ instead of scanning `~/.cache/fit/outpost/` — still check each against
 ### 1. Build the knowledge index
 
 ```bash
-find knowledge/People knowledge/Organizations knowledge/Projects \
-     knowledge/Topics knowledge/Goals knowledge/Priorities \
-     knowledge/Conditions -name "*.md" 2>/dev/null
+find Knowledge/People Knowledge/Organizations Knowledge/Projects \
+     Knowledge/Topics Knowledge/Priorities \
+     Knowledge/Conditions -name "*.md" 2>/dev/null
 ```
 
 For each note, `head -20` to capture key fields. Build a mental index of People,
-Organizations, Projects, Goals, Priorities, Topics by name, email, organization,
+Organizations, Projects, Priorities, Topics by name, email, organization,
 role, status, and aliases.
 
 ### 2. Classify the source
@@ -123,7 +123,7 @@ Collect every name variant per
 For each variant, search the knowledge index. Apply the
 [matching table](references/resolution.md#matching) and the
 [disambiguation priority](references/resolution.md#disambiguation-priority).
-Goals and Priorities are
+Priorities are
 [never auto-created](references/resolution.md#never-auto-create) — link to
 existing entries only.
 
@@ -150,9 +150,8 @@ filler or meta-commentary.
 - **Recruitment** (Req-number detection, hiring-manager / recruiter /
   domain-lead inference):
   [references/recruitment.md](references/recruitment.md).
-- **Goal & Priority links** (Step 7c): rules in
-  [references/links.md](references/links.md#goals-step-7c) and
-  [Priorities](references/links.md#priorities-step-7c). **Never auto-create.**
+- **Priority links** (Step 7c): rules in
+  [references/links.md](references/links.md#priorities-step-7c). **Never auto-create.**
 - **Conditions** (cross-cutting states affecting ≥ 3 entities):
   [references/conditions.md](references/conditions.md).
 

package/templates/.claude/skills/extract-entities/references/TEMPLATES.md

@@ -7,8 +7,8 @@ index.
 - [templates-people-orgs.md](templates-people-orgs.md) — People, Organizations.
 - [templates-projects-topics.md](templates-projects-topics.md) — Projects,
   Topics.
-- [templates-goals-priorities.md](templates-goals-priorities.md) — Goals,
-  Priorities. **Never auto-created** by `extract-entities` or `anarlog-process`
+- [templates-priorities.md](templates-priorities.md) — Priorities.
+  **Never auto-created** by `extract-entities` or `anarlog-process`
   — set by the user.
 - [templates-conditions.md](templates-conditions.md) — Conditions (time-bound
   cross-cutting states).

package/templates/.claude/skills/extract-entities/references/conditions.md

@@ -20,7 +20,7 @@ same constraint or state, suspect a Condition.
 
 ## Creating a Condition
 
-1. Check existing: `ls knowledge/Conditions/ 2>/dev/null`.
+1. Check existing: `ls Knowledge/Conditions/ 2>/dev/null`.
 2. **No match:** create a new Condition note using
    [templates-conditions.md](templates-conditions.md). Name descriptively
    ("Hiring Freeze Q2", "Division Reorg").
@@ -31,8 +31,8 @@ same constraint or state, suspect a Condition.
 
 When a Condition is created or updated:
 
-1. Add `[[Conditions/{Condition}]]` to the `## Blockers` section of affected
-   Goals.
+1. Add `[[Conditions/{Condition}]]` to the `## Affects` section of affected
+   Priorities.
 2. Add `[Status → on hold]` state changes to affected Projects where
    appropriate.
 3. Add a `## Blockers` entry to affected Role files if recruitment is frozen.
@@ -45,7 +45,7 @@ Source content indicates the Condition has ended: "approved", "freeze lifted",
 "reorg complete", "back on track".
 
 - Set `**Status:** resolved`, `**Resolved:** {date}`.
-- Remove `[[Conditions/{Condition}]]` from affected Goal `## Blockers`.
+- Remove `[[Conditions/{Condition}]]` from affected Priority `## Affects`.
 - Log with `[Status → resolved]`.
 
 ## Conservatism

package/templates/.claude/skills/extract-entities/references/links.md

@@ -1,6 +1,6 @@
 # Bidirectional Links
 
-Reference for `extract-entities` Step 10 and Step 7c (Goals / Priorities).
+Reference for `extract-entities` Step 10 and Step 7c (Priorities).
 
 ## Bidirectional link rules
 
@@ -11,28 +11,13 @@ After writing, verify each link goes both ways.
 | Person → Organization  | Organization → Person (in People section)    |
 | Person → Project       | Project → Person (in People section)         |
 | Project → Organization | Organization → Project (in Projects section) |
-| Project → Goal         | Goal → Project (in Projects section)         |
-| Goal → Priority        | Priority → Goal (in Goals section)           |
 | Project → Priority     | Priority → Project (in Projects section)     |
-| Condition → Goal       | Goal → Condition (in Blockers section)       |
 | Condition → Project    | Project → Condition (in Related section)     |
 | Condition → Role       | Role → Condition (notes or status field)     |
 
 Use absolute paths everywhere: `[[People/Sarah Chen]]`,
 `[[Organizations/Acme Corp]]`, `[[Projects/Acme Integration]]`,
-`[[Goals/Goal Name]]`, `[[Priorities/Priority Name]]`,
-`[[Conditions/Condition Name]]`.
-
-## Goals (Step 7c)
-
-When source content references an existing `knowledge/Goals/*.md`:
-
-- Add a `[[Goals/{Goal}]]` link to the relevant Project or Topic activity entry.
-- Add a progress entry to the Goal's `## Progress` section.
-- If evidence suggests a status change ("we won't hit the Q3 target"), update
-  `**Status:**` and log `[Status → value]`.
-
-**Never auto-create Goals.**
+`[[Priorities/Priority Name]]`, `[[Conditions/Condition Name]]`.
 
 ## Priorities (Step 7c)
 
@@ -44,5 +29,5 @@ Match source themes against priority names and descriptions.
   serves it.
 
 **Never auto-create Priorities.** Don't over-link — a project that already links
-to a Goal which links to a Priority doesn't need a redundant direct Priority
+to a Priority through a related Topic doesn't need a redundant direct Priority
 link.

package/templates/.claude/skills/extract-entities/references/recruitment.md

@@ -1,16 +1,16 @@
 # Recruitment Inference
 
-Reference for `extract-entities` Step 7b. Enrich `knowledge/Roles/` and
-`knowledge/Candidates/` with metadata that no single source carries.
+Reference for `extract-entities` Step 7b. Enrich `Knowledge/Roles/` and
+`Knowledge/Candidates/` with metadata that no single source carries.
 
 ## Requisition number detection
 
 Scan email subjects and bodies for requisition numbers (e.g. 7-digit Workday
 IDs).
 
-1. `ls knowledge/Roles/ | grep "{req_number}"` — does a Role file exist?
+1. `ls Knowledge/Roles/ | grep "{req_number}"` — does a Role file exist?
 2. **No file:** create a stub using the Role-stub template in `req-track` Step
-   0b. Search `rg "{req_number}" knowledge/` for context to enrich it.
+   0b. Search `rg "{req_number}" Knowledge/` for context to enrich it.
 3. **File exists:** check whether the email provides new metadata (hiring
    manager, recruiter, locations) and update the Role file.
 
@@ -20,11 +20,11 @@ When a calendar event title matches an interview pattern — "Interview",
 "Screening", "Screen", "Decomposition", "Panel", "Technical Assessment",
 "Candidate" — combined with a person name:
 
-1. Cross-reference the candidate against `knowledge/Candidates/`.
+1. Cross-reference the candidate against `Knowledge/Candidates/`.
 2. Extract the **organizer**. If the organizer isn't the user (per
    `~/.cache/fit/outpost/state/identity.md`),
    they are likely the hiring manager.
-3. Confirm: look up the organizer in `knowledge/People/` for a manager/HM role
+3. Confirm: look up the organizer in `Knowledge/People/` for a manager/HM role
    indication.
 4. Check the candidate's `brief.md` for a `Req` field; if known, set the
    matching Role file's `Hiring manager` (only if currently `—`).
@@ -33,9 +33,9 @@ When a calendar event title matches an interview pattern — "Interview",
 ## Recruiter — email-thread inference
 
 When a thread references candidates (name match against
-`knowledge/Candidates/`):
+`Knowledge/Candidates/`):
 
-1. Cross-reference To/CC against `knowledge/People/`.
+1. Cross-reference To/CC against `Knowledge/People/`.
 2. If a CC'd person's note mentions "recruiter", "talent acquisition", or a
    similar role, they are likely the internal recruiter.
 3. Update the candidate's `brief.md` recruiter field and the matching Role file

package/templates/.claude/skills/extract-entities/references/resolution.md

@@ -11,10 +11,8 @@ Extract every way each entity is referenced.
 - **Organizations:** full names, short names, abbreviations, email domains.
 - **Projects:** explicit names, descriptive references ("the pilot", "the
   deal").
-- **Goals:** references to time-bound targets, OKRs, or measurable outcomes that
-  match `knowledge/Goals/` entries.
-- **Priorities:** references to strategic directions that match
-  `knowledge/Priorities/` entries.
+- **Priorities:** references to strategic directions, time-bound targets, or
+  measurable outcomes that match `Knowledge/Priorities/` entries.
 
 ## Matching
 
@@ -82,5 +80,5 @@ Format: `**Role:** Product Lead (inferred from evaluation discussions)`.
 
 ## Never auto-create
 
-`Goals/` and `Priorities/`. Link to existing entries when referenced; update
+`Priorities/`. Link to existing entries when referenced; update
 progress / backlinks; never create new ones from extracted content.

package/templates/.claude/skills/extract-entities/references/sources.md

@@ -40,7 +40,7 @@ write a placeholder profile; see the
 
 ## Process — update existing notes only
 
-- Emails from people already in `knowledge/People/`.
+- Emails from people already in `Knowledge/People/`.
 - Emails referencing existing projects or organizations.
 
 ## Process — can create new notes

package/templates/.claude/skills/extract-entities/references/templates-conditions.md

@@ -16,8 +16,8 @@ are detected, or manually created by the user. Lifecycle: active → resolved.
 **Resolution signal:** {What would indicate this condition has ended}
 
 ## Affects
-{Goals, Projects, Roles, and People impacted by this condition}
-- [[Goals/{Goal}]] — {how it's affected}
+{Priorities, Projects, Roles, and People impacted by this condition}
+- [[Priorities/{Priority}]] — {how it's affected}
 - [[Projects/{Project}]] — {how it's affected}
 - [[Roles/{Role}]] — {how it's affected}
 

package/templates/.claude/skills/extract-entities/references/templates-priorities.md

@@ -0,0 +1,32 @@
+# Priority Templates
+
+Priorities are **never auto-created** by `extract-entities`. They are set
+deliberately by the user. This template is for manual creation only —
+`extract-entities` and `anarlog-process` only **link to** and **update progress
+on** existing notes.
+
+## Priorities
+
+```markdown
+# {Priority Name}
+
+## About
+{2-3 sentences: what this strategic direction means and why it matters}
+
+**Status:** {active|paused|retired}
+**Owner:** [[People/{Person}]]
+**Set:** {YYYY-MM-DD}
+
+## What this means
+{Bullet list of concrete implications — what does pursuing this priority look like?}
+
+## Actions
+{Concrete, time-bound actions that ladder to this priority. Targets live inline
+here — there is no separate Goals entity.}
+
+## Projects
+- [[Projects/{Project}]] — {relationship}
+
+## Key facts
+{substantive facts only — leave empty if none}
+```

package/templates/.claude/skills/extract-entities/references/templates-projects-topics.md

@@ -14,8 +14,8 @@
 ## Summary
 {2-3 sentences}
 
-## Goals
-- [[Goals/{Goal}]] — {how this project contributes}
+## Priorities
+- [[Priorities/{Priority}]] — {how this project contributes}
 
 ## People
 - [[People/{Person}]] — {role}

package/templates/.claude/skills/meeting-prep/SKILL.md

@@ -22,13 +22,12 @@ meetings.
 ## Inputs
 
 - `~/.cache/fit/outpost/apple_calendar/*.json` — calendar events
-- `knowledge/People/*.md` — attendee context
-- `knowledge/Organizations/*.md` — company context
-- `knowledge/Projects/*.md` — project context
-- `knowledge/Goals/*.md` — active goals relevant to the meeting topic
-- `knowledge/Priorities/*.md` — strategic context for framing
-- `knowledge/Candidates/*/brief.md` — candidate context (for interview meetings)
-- `knowledge/Roles/*.md` — role/requisition context (for interview meetings)
+- `Knowledge/People/*.md` — attendee context
+- `Knowledge/Organizations/*.md` — company context
+- `Knowledge/Projects/*.md` — project context
+- `Knowledge/Priorities/*.md` — active priorities and strategic context for framing
+- `Knowledge/Candidates/*/brief.md` — candidate context (for interview meetings)
+- `Knowledge/Roles/*.md` — role/requisition context (for interview meetings)
 
 ## Outputs
 
@@ -44,8 +43,8 @@ knowledge base.**
 When the user asks to prep for a meeting:
 
 1. **STOP** — Do not create a generic brief
-2. **SEARCH** — Look up each attendee: `rg -l "Attendee Name" knowledge/`
-3. **READ** — Read their notes: `cat "knowledge/People/Attendee Name.md"`
+2. **SEARCH** — Look up each attendee: `rg -l "Attendee Name" Knowledge/`
+3. **READ** — Read their notes: `cat "Knowledge/People/Attendee Name.md"`
 4. **UNDERSTAND** — Extract role, organization, history, open items
 5. **THEN BRIEF** — Create the meeting brief using this context
 
@@ -92,18 +91,18 @@ Extract: summary, start/end time, attendees (names and emails), description.
 For each attendee:
 
 ```bash
-rg -l "attendee_name" knowledge/People/
-rg -l "attendee_email" knowledge/People/
-cat "knowledge/People/Attendee Name.md"
-cat "knowledge/Organizations/Their Company.md"
-rg -l "attendee_name" knowledge/Projects/
+rg -l "attendee_name" Knowledge/People/
+rg -l "attendee_email" Knowledge/People/
+cat "Knowledge/People/Attendee Name.md"
+cat "Knowledge/Organizations/Their Company.md"
+rg -l "attendee_name" Knowledge/Projects/
 ```
 
 Extract: role/title, company, key facts, previous interactions, open items.
 
-Also check `knowledge/Goals/` and `knowledge/Priorities/` for context relevant
+Also check `Knowledge/Priorities/` for context relevant
 to the meeting topic — e.g. if the meeting is about hiring, surface the relevant
-hiring Goal's status and progress.
+hiring Priority's status and progress.
 
 ### Step 4: Create Meeting Brief
 
@@ -141,11 +140,11 @@ Suggested Talking Points
 ### Interview Meeting Context
 
 When preparing for interview meetings (title contains "Interview", "Screening",
-"Decomposition", "Panel", or a candidate name from `knowledge/Candidates/`):
+"Decomposition", "Panel", or a candidate name from `Knowledge/Candidates/`):
 
-1. **Read the candidate brief:** `knowledge/Candidates/{Name}/brief.md`
+1. **Read the candidate brief:** `Knowledge/Candidates/{Name}/brief.md`
 2. **Read the Role file:** Look up the `Req` field and read the corresponding
-   `knowledge/Roles/*.md` file.
+   `Knowledge/Roles/*.md` file.
 3. **Include in the briefing:**
    - Candidate's current status, skills, and screening recommendation
    - Role context: hiring manager, domain lead, remaining positions

package/templates/.claude/skills/req-assess/SKILL.md

@@ -22,7 +22,7 @@ This is **Stage 2** of the three-stage hiring pipeline:
 
 ## Trigger
 
-- A new `transcript-*.md` file appears in `knowledge/Candidates/{Name}/`.
+- A new `transcript-*.md` file appears in `Knowledge/Candidates/{Name}/`.
 - The user asks to analyze an interview or debrief.
 - The user asks to prepare a panel brief.
 - The concierge agent processes a Anarlog interview recording.
@@ -30,22 +30,22 @@ This is **Stage 2** of the three-stage hiring pipeline:
 ## Prerequisites
 
 - `fit-pathway` CLI installed.
-- At least one transcript in `knowledge/Candidates/{Name}/`.
+- At least one transcript in `Knowledge/Candidates/{Name}/`.
 - `screening.md` should exist; if missing, run `req-screen` first (proceed
   regardless).
 
 ## Inputs
 
-- `knowledge/Candidates/{Name}/transcript-{date}.md`.
-- `knowledge/Candidates/{Name}/screening.md`.
-- `knowledge/Candidates/{Name}/brief.md` — target role.
+- `Knowledge/Candidates/{Name}/transcript-{date}.md`.
+- `Knowledge/Candidates/{Name}/screening.md`.
+- `Knowledge/Candidates/{Name}/brief.md` — target role.
 
 ## Outputs
 
-- `knowledge/Candidates/{Name}/interview-{date}.md`.
-- `knowledge/Candidates/{Name}/panel.md` — only when more interviews are
+- `Knowledge/Candidates/{Name}/interview-{date}.md`.
+- `Knowledge/Candidates/{Name}/panel.md` — only when more interviews are
   planned.
-- Updated `knowledge/Candidates/{Name}/brief.md`.
+- Updated `Knowledge/Candidates/{Name}/brief.md`.
 
 <do_confirm_checklist goal="Verify the assessment is grounded in transcript
 evidence">
@@ -105,7 +105,7 @@ Apply the [level signals](references/rubric.md#level-signals).
 
 ### 6. Write the interview assessment
 
-Save to `knowledge/Candidates/{Name}/interview-{date}.md` using
+Save to `Knowledge/Candidates/{Name}/interview-{date}.md` using
 [references/interview-template.md](references/interview-template.md). Include
 only skills with new evidence — don't repeat the full matrix.
 
@@ -118,14 +118,14 @@ candidates:
 bunx fit-pathway interview {discipline} {level} --track={track}
 ```
 
-Save `knowledge/Candidates/{Name}/panel.md` using
+Save `Knowledge/Candidates/{Name}/panel.md` using
 [references/panel-template.md](references/panel-template.md). Audience:
 next-stage interviewers, often non-engineers — explain without jargon and tie
 suggested questions to remaining gaps.
 
 ### 8. Update the candidate brief
 
-Apply targeted Edit operations to `knowledge/Candidates/{Name}/brief.md`:
+Apply targeted Edit operations to `Knowledge/Candidates/{Name}/brief.md`:
 
 - Append a Pipeline entry with date, type, and outcome.
 - Add `## Interview Notes` if missing, with key observations.

package/templates/.claude/skills/req-assess/references/interview-template.md

@@ -1,7 +1,7 @@
 # Interview Assessment Template
 
 Reference template for `req-assess` Step 6. Save to
-`knowledge/Candidates/{Name}/interview-{date}.md`. Include only skills the
+`Knowledge/Candidates/{Name}/interview-{date}.md`. Include only skills the
 interview produced new evidence for — don't repeat the full matrix.
 
 ```markdown

package/templates/.claude/skills/req-assess/references/panel-template.md

@@ -1,7 +1,7 @@
 # Panel Brief Template
 
 Reference template for `req-assess` Step 7. Save to
-`knowledge/Candidates/{Name}/panel.md`. Audience: **next-stage interviewers,
+`Knowledge/Candidates/{Name}/panel.md`. Audience: **next-stage interviewers,
 often non-engineers** — explain without jargon, focus on behaviours and scope.
 
 ```markdown

package/templates/.claude/skills/req-decide/SKILL.md

@@ -29,25 +29,25 @@ This is **Stage 3** of the three-stage pipeline:
 ## Prerequisites
 
 - `fit-pathway` CLI installed.
-- `knowledge/Candidates/{Name}/screening.md` exists.
-- At least one `knowledge/Candidates/{Name}/interview-*.md`.
-- `knowledge/Candidates/{Name}/brief.md` exists.
+- `Knowledge/Candidates/{Name}/screening.md` exists.
+- At least one `Knowledge/Candidates/{Name}/interview-*.md`.
+- `Knowledge/Candidates/{Name}/brief.md` exists.
 
 ## Inputs
 
-- All artifacts in `knowledge/Candidates/{Name}/`.
+- All artifacts in `Knowledge/Candidates/{Name}/`.
 - Standard data via `fit-pathway`.
-- `knowledge/Candidates/Insights.md` — cross-candidate context.
-- `knowledge/Roles/*.md` — the candidate's requisition (positions, hiring
+- `Knowledge/Candidates/Insights.md` — cross-candidate context.
+- `Knowledge/Roles/*.md` — the candidate's requisition (positions, hiring
   manager, domain lead).
-- `knowledge/Goals/*.md`, `knowledge/Priorities/*.md` — strategic context.
+- `Knowledge/Priorities/*.md` — strategic context.
 - Other active candidates at the same level — relative positioning.
 
 ## Outputs
 
-- `knowledge/Candidates/{Name}/recommendation.md` — final recommendation.
-- Updated `knowledge/Candidates/{Name}/brief.md` — status and link.
-- Updated `knowledge/Candidates/Insights.md` — cross-candidate observations.
+- `Knowledge/Candidates/{Name}/recommendation.md` — final recommendation.
+- Updated `Knowledge/Candidates/{Name}/brief.md` — status and link.
+- Updated `Knowledge/Candidates/Insights.md` — cross-candidate observations.
 
 <do_confirm_checklist goal="Verify the recommendation is grounded and
 audit-ready">
@@ -71,7 +71,7 @@ audit-ready">
 ### 1. Gather all evidence
 
 ```bash
-ls knowledge/Candidates/{Name}/
+ls Knowledge/Candidates/{Name}/
 ```
 
 Read in order: `brief.md`, `screening.md`, every `interview-*.md`, relevant
@@ -114,8 +114,8 @@ Apply the level-confirmation criteria in
 If `brief.md` carries a `Req`:
 
 ```bash
-ls knowledge/Roles/ | grep "{req_number}"
-cat "knowledge/Roles/{matching file}"
+ls Knowledge/Roles/ | grep "{req_number}"
+cat "Knowledge/Roles/{matching file}"
 ```
 
 Capture remaining positions, hiring manager, domain lead, goal alignment, other
@@ -125,9 +125,9 @@ in terms of strategic impact.
 ### 6. Assess against the active pipeline
 
 ```bash
-cat knowledge/Candidates/Insights.md
+cat Knowledge/Candidates/Insights.md
 
-for dir in knowledge/Candidates/*/; do
+for dir in Knowledge/Candidates/*/; do
   if [ -f "$dir/screening.md" ]; then
     head -5 "$dir/screening.md"
   fi
@@ -144,7 +144,7 @@ Apply the [decision rules](references/rubric.md#decision-rules) and run the
 
 ### 8. Write the recommendation
 
-Save to `knowledge/Candidates/{Name}/recommendation.md` using the template in
+Save to `Knowledge/Candidates/{Name}/recommendation.md` using the template in
 [references/template.md](references/template.md). Carry the **advisory-only**
 banner. Cite specific evidence in skill, behaviour, level, and track sections.
 
@@ -156,7 +156,7 @@ Update `brief.md`:
 - Append `- [Hiring Recommendation](./recommendation.md)`.
 - Add the final pipeline entry with date and outcome.
 
-Update `knowledge/Candidates/Insights.md` only when there's a cross-candidate
+Update `Knowledge/Candidates/Insights.md` only when there's a cross-candidate
 observation worth keeping (strongest at level, sourcing channel pattern,
 level-adjustment implications).
 

package/templates/.claude/skills/req-decide/references/template.md

@@ -1,7 +1,7 @@
 # Recommendation Template
 
 Reference template for `req-decide` Step 6. Save to
-`knowledge/Candidates/{Name}/recommendation.md`.
+`Knowledge/Candidates/{Name}/recommendation.md`.
 
 ```markdown
 # Hiring Recommendation — {Full Name}

package/templates/.claude/skills/req-forget/SKILL.md

@@ -37,7 +37,7 @@ what was found, deleted, and redacted — the compliance audit trail.
 
 ## Outputs
 
-- `knowledge/Erasure/{Name}--{YYYY-MM-DD}.md` — erasure report.
+- `Knowledge/Erasure/{Name}--{YYYY-MM-DD}.md` — erasure report.
 - Deleted files and redacted references across the knowledge base.
 
 <do_confirm_checklist goal="Verify erasure is complete and the audit trail is
@@ -92,8 +92,8 @@ Process most-specific to most-general.
 **3a. Dedicated files and directories:**
 
 ```bash
-rm -rf "knowledge/Candidates/{Name}/"
-rm -f "knowledge/People/{Name}.md"
+rm -rf "Knowledge/Candidates/{Name}/"
+rm -f "Knowledge/People/{Name}.md"
 find ~/.cache/fit/outpost/apple_mail/attachments/ -iname "*{Name}*" -delete
 ```
 
@@ -126,14 +126,14 @@ rg -v "{deleted_path}" ~/.cache/fit/outpost/state/graph_processed \
 
 ### 4. Write the erasure report
 
-Save to `knowledge/Erasure/{Name}--{YYYY-MM-DD}.md` using the template in
+Save to `Knowledge/Erasure/{Name}--{YYYY-MM-DD}.md` using the template in
 [references/report-template.md](references/report-template.md). Record **only**
 what was deleted — never CV content, skills, or assessments.
 
 ### 5. Verify
 
 ```bash
-rg "{Name}" knowledge/ ~/.cache/fit/outpost/ drafts/
+rg "{Name}" Knowledge/ ~/.cache/fit/outpost/ Drafts/
 ```
 
 The only match should be the erasure report. If other matches remain, process
@@ -143,12 +143,12 @@ them and update the report.
 
 **`recruitment-only`** limits erasure to:
 
-- `knowledge/Candidates/{Name}/`
-- `knowledge/Candidates/Insights.md` mentions
+- `Knowledge/Candidates/{Name}/`
+- `Knowledge/Candidates/Insights.md` mentions
 - Recruitment threads (known agency domains)
 - `recruiter_triage.md`
 
-Leaves `knowledge/People/{Name}.md` and the wider graph intact — the person may
+Leaves `Knowledge/People/{Name}.md` and the wider graph intact — the person may
 be a colleague or non-recruitment contact.
 
 **`all`** (default): full erasure across knowledge base, cache, and state.

package/templates/.claude/skills/req-forget/references/classify.md

@@ -5,14 +5,14 @@ action below.
 
 | Reference Type                     | Action                                      | Example                                         |
 | ---------------------------------- | ------------------------------------------- | ----------------------------------------------- |
-| **Dedicated note** (sole subject)  | Delete entire file                          | `knowledge/People/{Name}.md`                    |
-| **Dedicated directory**            | Delete entire directory                     | `knowledge/Candidates/{Name}/`                  |
-| **Mention in another note**        | Redact: remove lines referencing the person | Backlink in `knowledge/Organizations/Agency.md` |
+| **Dedicated note** (sole subject)  | Delete entire file                          | `Knowledge/People/{Name}.md`                    |
+| **Dedicated directory**            | Delete entire directory                     | `Knowledge/Candidates/{Name}/`                  |
+| **Mention in another note**        | Redact: remove lines referencing the person | Backlink in `Knowledge/Organizations/Agency.md` |
 | **Email thread** (sole subject)    | Delete file                                 | `~/.cache/fit/outpost/apple_mail/thread.md`     |
 | **Email thread** (multiple people) | Redact: remove paragraphs about the person  | Thread discussing multiple candidates           |
 | **Attachment** (their CV, etc.)    | Delete file                                 | `attachments/{thread}/CV.pdf`                   |
 | **Triage/state file**              | Redact: remove lines mentioning them        | `recruiter_triage.md`                           |
-| **Insights file**                  | Redact: remove bullets mentioning them      | `knowledge/Candidates/Insights.md`              |
+| **Insights file**                  | Redact: remove bullets mentioning them      | `Knowledge/Candidates/Insights.md`              |
 
 ## Redaction rules