# Critical Rules — Generation Preflight

1. Read `resume_builder/canonical/claims.json`; it overrides every narrative source.
2. Run `python resume_builder/helpers/validate_resume_system.py` before generation.
3. Never use an `output/` resume or cover letter as source material.
4. Choose International Tech by default; use Swiss/DACH only for an appropriate employer.
5. Put employer, formal title and dates before any narrative framing.
6. Use an optional 2--3 line summary, 4--6 skills lines and normally 11--14 evidence-led bullets.
7. Mix natural bullet lengths. There is no character target and no page-fill quota.
7a. Vary bullet cadence: keep "X, Y and Z" triples under about half the bullets, avoid two
    adjacent bullets opening with the same verb, and vary length *within* each position.
    Style only — never bend a claim, a scope or a hedged verb to fix rhythm (see §7a).
8. Do not list unverified skills, metrics, customers, scale or causal impact.
9. Scope Swisscom migration and Data Mesh claims to Dennis's domains, components and products.
10. Security Champion means the 2025/2026 team role only; omit by default.
11. LLM evidence is configuration/integration level; no LangChain, fine-tuning, formal evaluation or production LLM ownership.
12. Run the canonical document validator, compile, inspect and test extracted text before presenting.