@forwardimpact/outpost 3.3.4 → 3.5.0

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
 

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

@@ -6,21 +6,21 @@ inventory.
 ## Knowledge base — direct notes
 
 ```bash
-ls -d "knowledge/Candidates/{Name}/" 2>/dev/null
-ls "knowledge/People/{Name}.md" 2>/dev/null
+ls -d "Knowledge/Candidates/{Name}/" 2>/dev/null
+ls "Knowledge/People/{Name}.md" 2>/dev/null
 
 # Common name variations
-ls "knowledge/People/{First} {Last}.md" 2>/dev/null
-ls "knowledge/People/{Last}, {First}.md" 2>/dev/null
+ls "Knowledge/People/{First} {Last}.md" 2>/dev/null
+ls "Knowledge/People/{Last}, {First}.md" 2>/dev/null
 ```
 
 ## Knowledge base — backlinks and mentions
 
 ```bash
-rg -l "{Name}" knowledge/
-rg -l "{First name} {Last name}" knowledge/
-rg -l "\[\[.*{Name}.*\]\]" knowledge/
-rg -l "{email}" knowledge/
+rg -l "{Name}" Knowledge/
+rg -l "{First name} {Last name}" Knowledge/
+rg -l "\[\[.*{Name}.*\]\]" Knowledge/
+rg -l "{email}" Knowledge/
 ```
 
 ## Cached email threads
@@ -47,13 +47,13 @@ rg -l "{Name}" ~/.cache/fit/outpost/state/ 2>/dev/null
 ## Drafts
 
 ```bash
-rg -l "{Name}" drafts/ 2>/dev/null
+rg -l "{Name}" Drafts/ 2>/dev/null
 ```
 
 ## Final verification
 
 ```bash
-rg "{Name}" knowledge/ ~/.cache/fit/outpost/ drafts/
+rg "{Name}" Knowledge/ ~/.cache/fit/outpost/ Drafts/
 ```
 
 Expected: only the erasure report matches.

package/templates/.claude/skills/req-forget/references/report-template.md

@@ -1,7 +1,7 @@
 # Erasure Report Template
 
 Audit trail for `req-forget` Step 4. Save to
-`knowledge/Erasure/{Name}--{YYYY-MM-DD}.md`.
+`Knowledge/Erasure/{Name}--{YYYY-MM-DD}.md`.
 
 **The report itself must not contain personal data** beyond the subject's name
 and the actions taken. Do not copy CV content, skills, or assessments into the
@@ -22,15 +22,15 @@ report — record only what was deleted, not what it contained.
 ## Actions Taken
 
 ### Deleted Files
-- `knowledge/Candidates/{Name}/brief.md`
-- `knowledge/Candidates/{Name}/CV.pdf`
-- `knowledge/Candidates/{Name}/screening.md`
-- `knowledge/People/{Name}.md`
+- `Knowledge/Candidates/{Name}/brief.md`
+- `Knowledge/Candidates/{Name}/CV.pdf`
+- `Knowledge/Candidates/{Name}/screening.md`
+- `Knowledge/People/{Name}.md`
 - {list all deleted files}
 
 ### Redacted References
-- `knowledge/Organizations/{Agency}.md` — removed backlink
-- `knowledge/Candidates/Insights.md` — removed {N} bullet(s)
+- `Knowledge/Organizations/{Agency}.md` — removed backlink
+- `Knowledge/Candidates/Insights.md` — removed {N} bullet(s)
 - {list all redacted files and what was removed}
 
 ### Cached Data Removed
@@ -57,7 +57,7 @@ The following are outside this tool's reach:
 ## Verification
 
 ```bash
-rg "{Name}" knowledge/ ~/.cache/fit/outpost/
+rg "{Name}" Knowledge/ ~/.cache/fit/outpost/
 ````
 
 Expected: no matches except this erasure report.

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

@@ -3,7 +3,7 @@ name: req-scan
 description: >
   Scan publicly available sources for candidates who indicate they are open for
   hire. Uses WebFetch to read public APIs (HN Algolia, GitHub, dev.to).
-  Writes prospect notes to knowledge/Prospects/. Maintains
+  Writes prospect notes to Knowledge/Prospects/. Maintains
   cursor/dedup state in ~/.cache/fit/outpost/head-hunter/. Use when the
   head-hunter agent is woken or when the user asks to scan for open candidates.
 ---
@@ -34,7 +34,7 @@ updates.
 
 ## Outputs
 
-- `knowledge/Prospects/{Name}.md`.
+- `Knowledge/Prospects/{Name}.md`.
 - Updated `cursor.tsv`, `seen.tsv`, `prospects.tsv`, and `log.md`.
 - `~/.cache/fit/outpost/state/head_hunter_triage.md`.
 
@@ -103,7 +103,7 @@ Write notes for **strong** and **moderate** matches only, using the template in
 [references/template.md](references/template.md).
 
 ```bash
-mkdir -p "knowledge/Prospects"
+mkdir -p "Knowledge/Prospects"
 ```
 
 ### 5. Update state

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

@@ -1,6 +1,6 @@
 # Prospect Note Template
 
-Reference for `req-scan` Step 4. Save to `knowledge/Prospects/{Name}.md`.
+Reference for `req-scan` Step 4. Save to `Knowledge/Prospects/{Name}.md`.
 
 ```markdown
 # {Name}

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

@@ -22,7 +22,7 @@ This is **Stage 1** of a three-stage hiring pipeline:
 
 ## Trigger
 
-- A new CV is added to `knowledge/Candidates/{Name}/`.
+- A new CV is added to `Knowledge/Candidates/{Name}/`.
 - A CV appears in `~/Downloads/` and is associated with a candidate.
 - The user asks to screen, evaluate, or assess a CV.
 - The user asks "is this person worth interviewing?".
@@ -35,16 +35,16 @@ This is **Stage 1** of a three-stage hiring pipeline:
 
 ## Inputs
 
-- CV file path (e.g. `knowledge/Candidates/{Name}/CV.pdf`).
+- CV file path (e.g. `Knowledge/Candidates/{Name}/CV.pdf`).
 - Target role (optional).
-- Existing `knowledge/Candidates/{Name}/brief.md`, if any.
-- `knowledge/Roles/*.md` matching the candidate's `Req` (provides `Level`,
+- Existing `Knowledge/Candidates/{Name}/brief.md`, if any.
+- `Knowledge/Roles/*.md` matching the candidate's `Req` (provides `Level`,
   `Discipline`, `Hiring manager`, `Domain lead`).
 
 ## Outputs
 
-- `knowledge/Candidates/{Name}/screening.md` — structured assessment.
-- Updated `knowledge/Candidates/{Name}/brief.md` — skills + summary enriched.
+- `Knowledge/Candidates/{Name}/screening.md` — structured assessment.
+- Updated `Knowledge/Candidates/{Name}/brief.md` — skills + summary enriched.
 
 <do_confirm_checklist goal="Verify the screening is grounded and
 decision-rule-compliant">
@@ -76,8 +76,8 @@ Extract the fields listed in
 If `brief.md` carries a `Req`, look up the matching Role file:
 
 ```bash
-ls knowledge/Roles/ | grep "{req_number}"
-cat "knowledge/Roles/{matching file}"
+ls Knowledge/Roles/ | grep "{req_number}"
+cat "Knowledge/Roles/{matching file}"
 ```
 
 Use the Role's `Level` and `Discipline` as the target unless the user specified
@@ -127,7 +127,7 @@ Pick the recommendation using the decision rules and threshold rule in
 
 ### 7. Write the screening
 
-Save to `knowledge/Candidates/{Name}/screening.md` using the template in
+Save to `Knowledge/Candidates/{Name}/screening.md` using the template in
 [references/template.md](references/template.md). Include the **Suggested
 Interview Questions** when the recommendation is "Interview" or "Interview with
 focus areas":

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

@@ -1,7 +1,7 @@
 # Screening Output Template
 
 Reference template for `req-screen` Step 6. Save to
-`knowledge/Candidates/{Name}/screening.md`. Filename **must** be `screening.md`
+`Knowledge/Candidates/{Name}/screening.md`. Filename **must** be `screening.md`
 — not `assessment.md`, `cv-screening.md`, or any variant. If a misnamed
 screening file exists in the folder (look for `# CV Screening` in the header),
 delete it after writing.

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

@@ -1,13 +1,13 @@
 ---
 name: req-track
-description: Scan synced email threads for recruitment candidates, extract structured profiles, and create/update notes in knowledge/Candidates/. Use when the user asks to track candidates, process recruitment emails, or update the hiring pipeline.
+description: Scan synced email threads for recruitment candidates, extract structured profiles, and create/update notes in Knowledge/Candidates/. Use when the user asks to track candidates, process recruitment emails, or update the hiring pipeline.
 ---
 
 # Track Candidates
 
 Scan synced email threads from `~/.cache/fit/outpost/apple_mail/` for
 recruitment candidates. Extract structured candidate profiles and create or
-update notes in `knowledge/Candidates/`. Builds a local, searchable recruitment
+update notes in `Knowledge/Candidates/`. Builds a local, searchable recruitment
 pipeline from scattered email threads.
 
 ## Trigger
@@ -29,7 +29,7 @@ pipeline from scattered email threads.
 - `~/.cache/fit/outpost/apple_mail/attachments/` — CV/resume attachments.
 - `~/.cache/fit/outpost/apple_calendar/*.json` — calendar events (for
   cross-source inference).
-- `knowledge/Roles/*.md` — open role/requisition files (metadata inheritance).
+- `Knowledge/Roles/*.md` — open role/requisition files (metadata inheritance).
 - `~/.cache/fit/outpost/state/graph_processed` — processed-file index (shared
   with `extract-entities`).
 - `~/.cache/fit/outpost/state/identity.md` — user identity for self-exclusion
@@ -37,10 +37,10 @@ pipeline from scattered email threads.
 
 ## Outputs
 
-- `knowledge/Candidates/{Full Name}/brief.md` — candidate profile note.
-- `knowledge/Candidates/{Full Name}/CV.pdf` (or `CV.docx`) — local CV copy.
-- `knowledge/Candidates/{Full Name}/headshot.jpeg` — candidate photo.
-- `knowledge/Roles/*.md` — created/updated role files (Candidates tables
+- `Knowledge/Candidates/{Full Name}/brief.md` — candidate profile note.
+- `Knowledge/Candidates/{Full Name}/CV.pdf` (or `CV.docx`) — local CV copy.
+- `Knowledge/Candidates/{Full Name}/headshot.jpeg` — candidate photo.
+- `Knowledge/Roles/*.md` — created/updated role files (Candidates tables
   rebuilt).
 - `~/.cache/fit/outpost/state/graph_processed` — updated with processed threads.
 
@@ -84,31 +84,31 @@ here.
 ### 2. Build candidate, people, and org indexes
 
 ```bash
-ls -d knowledge/Candidates/*/
+ls -d Knowledge/Candidates/*/
 ```
 
 Read each existing brief's header (Name, Role, Source, Status) to build a mental
-index. Also scan `knowledge/People/`, `knowledge/Organizations/`, and
-`knowledge/Projects/` to resolve recruiter names, agency orgs, and project
+index. Also scan `Knowledge/People/`, `Knowledge/Organizations/`, and
+`Knowledge/Projects/` to resolve recruiter names, agency orgs, and project
 links.
 
-### 3. Sync `knowledge/Roles/`
+### 3. Sync `Knowledge/Roles/`
 
 This keeps role metadata current and enables inheritance.
 
 1. Read each Role file's Info block to map Req → Role file path, Hiring manager,
    Domain lead, recruiter, Channel.
 2. Find Reqs referenced by candidate briefs but missing a Role file:
-   `rg "^\*\*Req:\*\*" knowledge/Candidates/*/brief.md`. For each missing Req,
+   `rg "^\*\*Req:\*\*" Knowledge/Candidates/*/brief.md`. For each missing Req,
    create a stub using the **Role file stub** in
    [references/templates.md](references/templates.md), then enrich by searching
-   the graph: `rg "{req_number}" knowledge/`.
+   the graph: `rg "{req_number}" Knowledge/`.
 3. Rebuild each Role file's `## Candidates` table by scanning briefs:
-   `rg -l "Req:.*{req_number}" knowledge/Candidates/*/brief.md`. Use the **Role
+   `rg -l "Req:.*{req_number}" Knowledge/Candidates/*/brief.md`. Use the **Role
    Candidates table** format from `references/templates.md`. Sort by First seen,
    newest first.
 4. If a Role file has a hiring manager but no domain lead, walk the
-   `**Reports to:**` chain in `knowledge/People/` to a VP or senior leader.
+   `**Reports to:**` chain in `Knowledge/People/` to a VP or senior leader.
 
 ### 4. Identify recruitment threads
 
@@ -137,7 +137,7 @@ forwarded headers).
 
 ### 8. Write or update the candidate note
 
-For **new** candidates, create `knowledge/Candidates/{Full Name}/brief.md` from
+For **new** candidates, create `Knowledge/Candidates/{Full Name}/brief.md` from
 the **Candidate brief** template in
 [references/templates.md](references/templates.md). Place the **Extra Info
 fields** after `Last activity` in the order shown there. Add the **Optional
@@ -149,7 +149,7 @@ known Info fields, and add new Skills.
 
 ### 9. Capture cross-candidate insights
 
-Update `knowledge/Candidates/Insights.md` only when an observation is
+Update `Knowledge/Candidates/Insights.md` only when an observation is
 high-signal: candidate may suit a **different role**, is a **strong match** for
 a specific team or leader, a meaningful **comparison between candidates**, or a
 hiring trade-off needs to be **remembered across sessions**.

package/templates/.claude/skills/req-track/references/fields.md

@@ -43,13 +43,13 @@ Field map and resolution rules for Step 2 of `req-track`.
 
 Stop at the first match:
 
-1. **Req-first inheritance** — look up `knowledge/Roles/*.md` for the matching
+1. **Req-first inheritance** — look up `Knowledge/Roles/*.md` for the matching
    Req; inherit Hiring manager and Domain lead from the Role file.
 2. **Calendar inference** —
    `rg -l "{Candidate Name}" ~/.cache/fit/outpost/apple_calendar/`. The non-user
    organizer of an interview event is likely the hiring manager.
 3. **Email inference** — internal To/CC recipients (besides the user)
-   cross-checked against `knowledge/People/`.
+   cross-checked against `Knowledge/People/`.
 4. **Reporting chain** — read the hiring manager's `**Reports to:**` field; walk
    up to a VP / senior leader for the domain lead.
 5. **Staffing project timeline** — search staffing notes for the candidate or
@@ -71,7 +71,7 @@ hiring decisions, assessment criteria, or candidate visibility.
 
 ## Source and recruiter
 
-- Map sender email domain to an organization in `knowledge/Organizations/`.
+- Map sender email domain to an organization in `Knowledge/Organizations/`.
 - The person who sent or forwarded the profile is the recruiter — link with
   `[[People/Name]]`.
 - Create the organization or recruiter notes if missing.
@@ -80,9 +80,9 @@ hiring decisions, assessment criteria, or candidate visibility.
 
 ```bash
 ls ~/.cache/fit/outpost/apple_mail/attachments/{thread_id}/
-mkdir -p "knowledge/Candidates/{Full Name}"
+mkdir -p "Knowledge/Candidates/{Full Name}"
 cp "~/.cache/fit/outpost/apple_mail/attachments/{thread_id}/{file}" \
-   "knowledge/Candidates/{Full Name}/CV.pdf"
+   "Knowledge/Candidates/{Full Name}/CV.pdf"
 ```
 
 Use `CV.pdf` (PDF) or `CV.docx` (Word). The `## CV` link is `./CV.pdf`.
@@ -106,9 +106,9 @@ Match by name fragment (case-insensitive). Prefer the Downloads match. Always
 write `headshot.jpeg`:
 
 ```bash
-cp "{src}" "knowledge/Candidates/{Full Name}/headshot.jpeg"
+cp "{src}" "Knowledge/Candidates/{Full Name}/headshot.jpeg"
 # PNG → JPEG
-magick "{src}.png" "knowledge/Candidates/{Full Name}/headshot.jpeg"
+magick "{src}.png" "Knowledge/Candidates/{Full Name}/headshot.jpeg"
 # HEIC → JPEG
-magick "{src}.heic" "knowledge/Candidates/{Full Name}/headshot.jpeg"
+magick "{src}.heic" "Knowledge/Candidates/{Full Name}/headshot.jpeg"
 ```

package/templates/.claude/skills/req-track/references/signals.md

@@ -10,7 +10,7 @@ no signal — most email is not.
 
 ## Recruiter sender domains
 
-Sender domain maps to an organization in `knowledge/Organizations/` tagged as a
+Sender domain maps to an organization in `Knowledge/Organizations/` tagged as a
 recruitment agency. When no agencies are catalogued yet, treat these patterns as
 hints:
 
@@ -38,5 +38,5 @@ Structured candidate descriptions containing:
 
 ## Follow-up on existing candidates
 
-A thread mentions a candidate already in `knowledge/Candidates/` by name —
+A thread mentions a candidate already in `Knowledge/Candidates/` by name —
 process it to update pipeline status.

package/templates/.claude/skills/req-track/references/templates.md

@@ -50,7 +50,7 @@ Sort by First seen, newest first.
 ## Candidate brief
 
 Used by Step 5 for new candidates. File:
-`knowledge/Candidates/{Full Name}/brief.md`.
+`Knowledge/Candidates/{Full Name}/brief.md`.
 
 ```markdown
 # {Full Name}