feat: rebuild evidence-first application workflow

This commit is contained in:
2026-07-27 17:56:15 +02:00
parent c24892f381
commit fe5f24704f
57 changed files with 3815 additions and 3555 deletions
+43 -85
View File
@@ -1,104 +1,62 @@
# Cover Letter Generation — Reference
# Cover Letter Reference
> CL-specific rules. Read by `/make-cl` and `/edit-resume` (for CL edits).
> Shared rules (provenance, anti-fabrication, LaTeX notation): `CLAUDE.md`
> A cover letter is optional by default. The resume must earn a screen on its own.
---
## Decision Gate
## CL Format Rules
Generate a cover letter when at least one is true:
- Cover letter with resume: 1 page (250-300 words)
- Cover letter with CV: 1-2 pages (350-450 words). If 2 pages, page 2 >= half filled before signature.
- Full package: Resume + CL = 3 pages | CV + CL = 6-7 pages
- The posting or portal requests one.
- The employer is a traditional Swiss/DACH institution, public body, NGO or mission-led organization where motivation is material.
- A credible career/location/domain transition needs a short explanation.
- Work authorization, language, relocation or a genuine personal connection materially strengthens the application.
- The user explicitly requests a letter.
---
Normally skip it when:
## Institution Type Detection
- The portal provides no upload field.
- A standardized process already asks motivation questions.
- It would merely repeat the resume or paraphrase company news.
- **Industry:** Any company (manufacturing, tech, consulting, energy, etc.)
- **National Lab:** DOE labs, national research facilities, government lab fellowships
- **Academic:** University postdoc or faculty positions
Record `Cover Letter Decision: YES/NO` and the reason in the session file before writing.
---
## Evidence Rules
## INDUSTRY Cover Letter (250-300 words, 3 paragraphs)
1. Read `resume_builder/canonical/claims.json` first.
2. Every work claim must be traceable to the resume and canonical registry.
3. Significance files supply optional context only; reverify external claims from current primary sources.
4. Company or industry scale never becomes Dennis's personal scale or impact.
5. Do not introduce a skill, metric, customer, ownership claim or result absent from the resume.
**P1 — HOOK:** Connect their product/technology to your achievement. State core identity + position. Open with a specific reference to their work, not a generic opener. Minimize jargon for HR readers.
## International Tech / Industry Letter
**P2 — EVIDENCE:** 2-3 achievements translated to business value. Max 3-4 quantified claims. Mirror JD terms. Frame as deliverables.
- One page, normally 200--300 words.
- Two or three short paragraphs.
- Open with the candidate-role connection, not a company press-release summary.
- Use one or two proof points and explain why they matter for this role.
- Add motivation or context the resume cannot show.
- Close directly and professionally.
**P3 — CLOSING:** Forward-looking value + active call to action. Address "why industry" positively if pivoting — frame what industry enables, not what academia lacks.
## Swiss/DACH Letter
---
- One A4 page.
- Match the language and formality of the posting.
- Explain motivation, relevant evidence and practical fit such as location/language.
- References and diplomas remain separate attachments when requested.
## NATIONAL LAB Cover Letter (350-450 words, 4 paragraphs)
## Employer-Specific Formats
**P1 — HOOK:** Mission alignment + division/group + position. Reference specific programmatic thrust or group's publication. Technical vocabulary OK.
For NATO, government or academic applications, follow the employer's explicit format and portal fields. Do not force a generic three-paragraph industry structure when the application requests a motivation statement or competency answers.
**P2 — CURRENT POSITION:** Current work with mission framing. Theory-experiment bridge. HPC scale. Collaborative tone.
## Hook Verification
**P3 — PRIOR WORK:** Transferable methodology arc. Custom tools → ML infrastructure. International collaboration. Quantify.
Verify every named product, programme, paper, executive statement or current company initiative before use. Prefer first-party sources. Record the source in the session file. If a hook is not necessary, omit it rather than spending a paragraph proving company familiarity.
**P4 — CLOSING:** Programmatic vision + collaboration offer + seminar availability. Lab vocabulary: "thrust area," "programmatic direction."
## Quality Checks
---
## ACADEMIC Cover Letter (350-450 postdoc, 450-650 faculty; 4 paragraphs)
**P1 — HOOK:** Connection to PI's specific paper + your identity + position. Name the PI.
**P2 — CURRENT RESEARCH:** Current position with field-context framing (use significance files if available). Future direction: 1-2 sentences MANDATORY.
**P3 — PRIOR FOUNDATION:** Transferable methodology + collaboration + mentorship. Faculty: departmental fit narrative.
**P4 — CLOSING:** Forward-looking + name 2-3 faculty for collaboration. Postdoc: "contribute to your research program." Faculty: "build independent research program complementing..."
---
## Universal CL Rules
- Open with a specific reference to their work — avoid generic openers like "I am writing to express my interest"
- Add narrative context the CV cannot — motivation, "why this company," research vision
- Limit quantified claims to 3-5 per CL
- Credentials woven into body paragraphs, not dumped in closing
- Active call to action in closing — not passive "Thank you for your consideration"
- If pivoting domains: lead with methodology in P1, not apologetic framing
---
## Jargon Calibration
- **Industry:** Assume HR reads first. Minimize subfield jargon.
- **National Lab / Academic:** Domain expert reads. Use field vocabulary.
---
## Package Reading Rules
- Resume/CV must stand alone — many hiring managers never read the CL
- CL deepens, not introduces — every major CL claim traceable to a resume/CV bullet
- No contradictions between documents
- Resume + CL = 3 pages | CV + CL = 6-7 pages
---
## CL Hook Verification (MANDATORY)
Before presenting any CL draft to the user, web-search and verify every external reference:
- **Academic:** PI name + cited paper title/topic → confirm paper exists, journal, year
- **National Lab:** Named program, thrust area, or group publication → confirm it exists
- **Industry:** Product name, technology claim, or company news → confirm accuracy
**If verified:** Note source URL in session file Cover Letter Plan.
**If unverified:** Flag as **"UNVERIFIED — please confirm"** in the draft. Never guess names, titles, or journal details.
---
## CL Anti-Patterns
- No generic opener ("I am writing to express my interest...")
- No defensive framing ("Despite my background in...")
- No credential dump in closing paragraph
- No repeating resume bullets verbatim — CL deepens, doesn't duplicate
- Limit quantified claims to 3-5 per CL
- **Em-dashes in CLs:** Max 2 per document. CLs are prose-heavy and em-dashes compound quickly. Use commas for parenthetical asides, colons for elaborations, periods for new sentences. Paired em-dashes (X --- detail --- Y) should use commas or parentheses instead.
- The resume stands alone.
- The letter adds motivation, decision context or a meaningful connection.
- The voice is direct and natural.
- No generic opening, credential dump, defensive gap list or copied resume bullet.
- The canonical validator passes for the cover-letter `.tex`.
- The compiled document is one readable page unless the employer explicitly requests otherwise.