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
@@ -1,118 +1,77 @@
# Session File Template
Every JD gets a persistent session file: `output/<FolderName>/session_<name>.md`
## Template
Every JD gets `output/<Folder>/session_<name>.md`.
```markdown
# Session: [Company] [Role Title]
# Session: [Company] [Role]
## JD Info
- **File:** JDs/[file].txt
- **Role:** [title]
- **Company:** [company] ([context])
- **Bundle:** [role_type]
- **Format:** [Resume/CV] ([N]-page, [cls]) + [N]-page cover letter
- **Salary/Details:** [if available]
## JD Integrity
- File/source:
- Retrieval method and date:
- Verbatim posting: YES/NO
- Posting status:
## JD Analysis
### Requirements
| # | Requirement | Match | Evidence |
|---|-------------|-------|----------|
| 1 | ... | Direct/Bridge/Gap | ... |
## Application Decision
- Audience profile: International Tech / Swiss-DACH / Employer-specific
- Evidence Fit: [0-100]
- Fit class: Core / Adjacent / Stretch
- Hard gate: PASS / FAIL — [reason]
- Channel Strength: Strong / Moderate / Weak
- Channel plan: [referral/recruiter/hiring-team/cold]
- Cohort slot: Core [n]/7, Adjacent [n]/2, Stretch [n]/1
- Decision: PROCEED / HOLD / NO-GO
### ATS Keywords
- **ML/AI:** ...
- **Domain:** ...
- **Methods:** ...
- **Tools:** ...
- **Soft Skills:** ...
## Requirements
| # | Requirement | Required/preferred | Direct/Adjacent/Gap/Constraint | Canonical evidence | Gate? |
|---|---|---|---|---|---|
### Gap Assessment
- **Direct:** [list]
- **Bridge:** [list with confidence]
- **Gap:** [list -- what we can't claim]
## Company Context
- **Mission:** ...
- **This role:** Why it exists, what success looks like
- **Culture:** ...
- **"Why them" angle:** ...
## Competitive Read
- Obvious-fit candidate:
- Dennis's advantage:
- Their advantage:
- Level/scope comparison:
## Framing Strategy
- **Lead narrative:** ...
- **Reframing map:** [domain term] → [JD term]
- **Emphasize:** ...
- **Downplay:** ...
- **CL hooks:** ...
- **User directives:** ...
- Professional identity:
- Strongest proof points:
- Honest adjacent bridges:
- Explicit gaps:
- User directives:
## Critique Context (captured in Phase 0, used in /critique)
- **Reviewer persona:** Who reads this? Their title, daily work, what impresses/bores them
- **Competitive landscape:** Who else applies? What does the "obvious fit" have that we don't?
- **Domain vocabulary:** What terms separate insider from outsider at THIS company?
## Resume Plan
- Summary: omit / 2--3 lines
- Skills: [4--6 evidence-backed lines]
- Swisscom: [4--5 selected canonical IDs]
- Bosch: [3--4 selected canonical IDs]
- Earlier experience: [0--1 per role]
- Total bullets: [normally 11--14; no page-fill quota]
- Impact evidence still needed:
## Cover Letter Plan
- **Institution type:** Industry / National Lab / Academic
- **Paragraph count:** [N] paragraphs, [word count target]
- **P1 hook:** [specific product/paper/program to reference]
- **P2-P3 evidence:** [which achievements to highlight, how to frame]
- **Domain pivot:** [methodology bridge sentence, if pivoting]
- **Jargon level:** HR-safe / Technical / Academic
- **"Why them" hook:** [specific connection to their work]
## Bullet Plan
Note: Any FIXED positions (e.g., internships) are not included in this plan.
### Position 1 ([N] bullets, [N] rendered lines)
| # | ID | Achievement | Variant | Lines | Rationale |
|---|-----|------------|---------|-------|-----------|
### Position 2 ([N] bullets, [N] rendered lines)
[same table]
### Position 3 ([N] bullets, [N] rendered lines)
[same table]
**Budget:** [N] variable bullets, [N] rendered lines vs target [N]
## Cover Letter Decision
- YES/NO:
- Reason:
- Information it adds beyond resume:
- Verified hook sources:
## Output Files
- Resume/CV: `output/<FolderName>/e2e_<name>_[resume|cv].tex`
- Cover Letter: `output/<FolderName>/e2e_<name>_cover_letter.tex`
- Critique: `output/<FolderName>/critique_<name>.md`
- Resume:
- Cover letter: [path or intentionally omitted]
- Critique:
## Critique Summary
- **Score:** [N]/100
- **Key findings:** ...
- **Tier 1 fixes:** ...
## Edit History
### Edit [N] ([date]): [description]
- Changes: ...
- Source: [critique item # / user request / auto-detected]
- Verification: [gates passed]
- Evidence Fit:
- Hard gate:
- Document Quality:
- Channel Strength:
- Tier 1 fixes:
## Status
- Phase 0: [PENDING | DONE]
- Phase 1: [PENDING | DONE (N bullets confirmed)]
- Phase 2 Resume:
- Summary: [PENDING | DONE]
- Skills: [PENDING | DONE]
- Position 1 ([N] bullets): [PENDING | DONE | IN_PROGRESS]
- Position 2 ([N] bullets): [PENDING | DONE | IN_PROGRESS]
- Position 3 ([N] bullets): [PENDING | DONE | IN_PROGRESS]
- Compile: [PENDING | DONE]
- Cover Letter: [PENDING | IN_PROGRESS | DONE]
- Critique: [PENDING | IN_PROGRESS | CURRENT (score) | STALE]
- **Next:** [exact command to copy after /clear]
- **Next CL:** /make-cl output/<FolderName>/session_<name>.md
- **Next Critique:** /critique output/<FolderName>/session_<name>.md
- Fit gate:
- Resume:
- Cover letter:
- Critique:
- Application/outcome:
- Next:
```
## Context Efficiency Notes
- Session 1 (resume): resume_reference.md + critical_rules.md re-read + experience files + bundle + support files + template. Peak depends on knowledge base size.
- Session 2 (CL): cl_reference.md + significance files (if available) + session file + resume .tex + bundle S5. Much lighter context.
- Session 3 (critique): critique_framework.md + session file + both .tex + bundle. Moderate context.
- Folder created in Phase 0 — all files go to output/<FolderName>/ from the start.
The session file records application state, but it is not evidence authority. Canonical claims remain authoritative.