mirror of
https://github.com/MadsLorentzen/ai-job-search.git
synced 2026-09-17 00:26:26 +00:00
fix(setup): ground Path A profile-statement extraction against the profile (#178)
Completes the loop behind #177: /apply drift could be archived by /outcome, then laundered into 05-cv-templates.md as a reusable template by /setup Path A - promoting a one-off drifted claim into source material for every future application. Path A now verifies extracted statements' factual claims against 01-candidate-profile.md (keeping framing only), and 05-cv-templates.md marks [Used for:] statements as phrasing references, never fact sources. framework_version 1.1.0. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Fable 5
parent
d2e14418ca
commit
3847088986
@@ -147,7 +147,7 @@ For each skill file, compare extracted document content against the current file
|
||||
- **`02-behavioral-profile.md`:** Source is LinkedIn About + recommendation letters. Extract recurring themes, adjectives, phrases about how the candidate works. Add only to "Strongest Behavioral Traits", "How [Candidate] Works Best", or "Management Style Preferences" sections. Do not overwrite existing scored assessments. Always label inferred additions: *[Inferred from LinkedIn About / Reference letter - review before relying on this]*
|
||||
- **`03-writing-style.md`:** Source is `cover_letter.tex` files. Extract recurring patterns. Add as observations under "## Patterns Observed in Past Applications". Do not modify existing rules. Only add if 2+ cover letters show a genuine pattern.
|
||||
- **`04-job-evaluation.md`:** Source is `job_posting.md` + `outcome.md` pairs. If an application reached interview or offer: note role type and sector as a confirmed strong-fit signal. If 2+ applications repeat a no-response or rejection pattern: note it. Add findings under "## Calibration from Past Applications". Do not modify the existing scoring framework.
|
||||
- **`05-cv-templates.md`:** Source is `cv_draft.tex` files. Extract any profile statement that does not already appear in templates. Label with: *[Used for: <company>_<role>]*
|
||||
- **`05-cv-templates.md`:** Source is `cv_draft.tex` files. Extract any profile statement that does not already appear in templates. Label with: *[Used for: <company>_<role>]*. **Ground before extracting:** archived drafts are tailored outputs, not source documents - verify every factual claim in an extracted statement (titles, employers, metrics, technologies) against `01-candidate-profile.md` and drop or correct any claim the profile does not support, keeping only the framing. A tailored draft that drifted must never become a template future applications start from.
|
||||
- **`06-cover-letter-templates.md`:** Source is `cover_letter.tex` files. Extract opening patterns, bullet structures, closing formulations. Add only what is structurally distinct from existing templates.
|
||||
- **`07-interview-prep.md`:** Source is CV bullets, LinkedIn descriptions, reference letter quotes. Identify achievements not yet covered by an existing STAR example. Do NOT draft full STAR examples. Add stubs under "## STAR Candidates (Complete Manually)":
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
framework_version: 1.0.1
|
||||
framework_version: 1.1.0
|
||||
---
|
||||
|
||||
# CV Templates and Tailoring Guide
|
||||
@@ -116,6 +116,8 @@ Write 5-7 lines that function as an "elevator pitch": a concise, compelling intr
|
||||
**For [YOUR_SECONDARY_ROLE_TYPE] roles:**
|
||||
> [YOUR_PROFILE_STATEMENT_TEMPLATE_2]
|
||||
|
||||
Statements labeled *[Used for: <company>_<role>]* were extracted from archived application drafts by `/setup` Path A. They are **phrasing references, never fact sources**: when drafting from one, every factual claim still comes from `01-candidate-profile.md` - a past tailored draft does not vouch for its own accuracy.
|
||||
|
||||
### Core Competencies / Skills Section (Best Practice)
|
||||
Reorder and emphasize based on the role. Use bold category labels.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user