Rules for Resume

# Voice rules for Resume

26 rules apply on the Resume surface, 26 declared, 0 measured, 0 inherited and 0 proposed. No rule on this surface has yet been measured from attested writing, so this profile is the author's stated preferences and not a measured fingerprint.

## Never violate

- No emoji. Not in copy, not in headings, not in commit messages.
  Declared, enforced as a house rule in his codebase.
- Sentence case everywhere. No all-caps strings and no uppercase text styling.
  Declared, enforced as a house rule in his codebase.
  Exception: The resume surface is exempt for section headings only: the author's own master resume sets PROFESSIONAL EXPERIENCE, EDUCATION & AWARDS and PERSONAL in all caps, and the template convention wins there. Resume body bullets stay sentence case.
- Every number, quote and factual claim carries its source. An interpretive read is labelled a computed read, never dressed as a sourced fact.
  Declared, enforced as a house rule in his codebase.
  Why: The non-negotiable house rule. A claim without provenance does not ship.
  Exception: On the resume surface numbers ship without inline citations. The provenance duty still holds, it just lives off the page: every figure must be attested in the author's work record or a prior resume, and a figure with no attestation does not go on the page.
  Exception: On the interview_answer surface a spoken answer carries no inline citation. The provenance duty holds off the page: every figure must be attested in the resume bullet catalogue or in a prior interview answer, and the two are separate sources, so a fact attested only in a prior answer is sayable but is known to be absent from the resume.
- Never invent a figure, a name, a citation or a confidence level. An honest gap is stated as a gap.
  Declared, enforced as a house rule in his codebase.
  Why: Repeatedly enforced across his codebase: a missing structure is an honest visible gap, a fabricated one silently corrupts everything downstream.
- Open every top-level bullet with a bare past-tense verb, no pronoun and no article, even for the current role. Sub-bullets under a colon lead-in open noun-phrase-first instead.
  Declared, stated by the author himself.
  Why: The author's own resume holds this without a single exception, including the in-progress CenterWell role.
  Good: Led competitive intelligence research for Pharma companies across 3+ projects
  Avoid: I led competitive intelligence research across several projects
- No period at the end of a bullet. The only sentence-final mark on the page is the colon that opens a lead-in bullet.
  Declared, stated by the author himself.
  Good: Designed Power BI dashboards for utilization / clinical outcomes of patient segments
  Avoid: Designed Power BI dashboards for utilization / clinical outcomes of patient segments.
- Preserve the approved selective-bold span recorded for each bullet in RESUME_BULLET_LIBRARY.md. Every bullet has exactly one contiguous bold span at the beginning, covering its action and principal deliverable or scale; all supporting method, examples, and consequences remain plain. Never invent, extend, shorten, or move a bold boundary during tailoring.
  Declared, stated by the author himself.
  Why: The author reviewed and approved the leading bold boundary for every bullet in the curated library so emphasis stays consistent across applications.
- State scale as open-ended plus-counts and money as order of magnitude, 7+ projects and tens to hundreds of millions, not falsely precise figures or percentages.
  Declared, stated by the author himself.
  Why: The author's metric register is scale, not audit precision. Exact figures live in the work record and the interview, not on the page.
  Good: screening 6k+ funded small-molecule biotechs across public sources
  Avoid: screening 6,351 biotechs, boosting BD conversion by 40%
- Every number on the resume must be attested in the author's work record or a prior resume. This is the resume-native form of the no-fabrication house rule: the citation lives in the attestation trail, not on the page.
  Declared, enforced as a house rule in his codebase.
- Each role is a borderless two-column row: bold company, a spaced dash, italic title on the left, bold right-aligned dates on the right. The current role shows months, MM/YYYY with the open end written Present. Every earlier role and every education date shows the year only.
  Declared, stated by the author himself.
  Why: The author set the year-only convention on 2026-08-24: before 04/2026, his last CenterWell month, no months appear, and the current month is written Present.
  Good: 04/2026 - Present, with McKinsey as 2023 - 2025 and the Ph.D. as 2022
  Avoid: 04/2026 - 08/2026, with McKinsey as 02/2023 - 04/2025 and the Ph.D. as December 2022
  Exception: A dash character may bend to the page: the CenterWell row keeps its original spaced hyphen because the wider en dash wraps the long title onto a second line.
- Every line of a wrapped bullet should fill at least half the horizontal text width. If a selected bullet creates a short orphan line, choose another approved bullet or adjust layout within the approved template; never rewrite locked bullet text to force the fit.
  Declared, stated by the author himself.
  Why: A one-word line wastes the row it sits on and reads as sloppy typesetting on a one-page document.
  Good: ...platform adopted by leadership, tracking 30+ CRO / tech-bio competitors with battlecards and positioning analyses
  Avoid: ...competitors, with capability profiles, battlecards, and positioning analyses adopted by [line break] leadership
- Section headings are all-caps bold 10pt in the fixed order PROFESSIONAL EXPERIENCE, EDUCATION & AWARDS, PERSONAL, and consulting bullets group under italic un-bulleted client-segment lines.
  Declared, stated by the author himself.
  Why: This is the declared exception to the universal sentence-case rule: on the resume the author's own template convention wins for headings, and only for headings.
- One A4 page, Arial 10pt body with the 13pt bold centered name, justified bullets, 2.5cm margins, single spacing. Cut a bullet before shrinking the type.
  Declared, stated by the author himself.
- No first person anywhere on the resume. Letters speak as I, the resume speaks in bare verb fragments.
  Declared, stated by the author himself.
- Regeneration reproduces the source text verbatim. Fix a typo only with the author's sign-off, never silently.
  Declared, stated by the author himself.
  Why: Whether a source irregularity is corrected is the author's call, not the tool's. The two-word forms 'roll out' and 'stand up' are his chosen spellings and stay.
- Treat every approved resume bullet as locked source text. Tailoring may select, omit, and reorder existing bullets, but must never rewrite, combine, shorten, expand, paraphrase, or otherwise modify an individual bullet unless the author explicitly approves new wording.
  Declared, stated by the author himself.
  Why: The author wants one durable bullet library and role-specific selection without wording drift across applications.

## Default, depart only with a reason

- Avoid the em dash. Use a comma, or split the sentence, or use "and". Depart only where the em dash genuinely earns its place, and say why.
  Declared, stated by the author himself, changed in the local delta layer by delta 4, 6.
  Why: Stated by the author as a hard rule for decks, and repeated as a house rule.
  Good: Breadth is the one axis rivals cannot buy, 78 of 137 classes against Enamine's 52
  Avoid: Breadth is the one axis rivals cannot buy — 78 of 137 classes against Enamine's 52
  Exception: This rule is about the EM dash used as a sentence connector. An EN dash joining a numeric range or a relational compound is a different character doing a different job, and replacing it changes the meaning, so "Phase 1-3" is a span and "Phase 1, 3" is two phases. Leave those alone.
  Exception: Downgraded from never-violate on 2026-07-28. In an internal share deck the author deliberately rewrote complying lines to use an em dash, so treat this as the strong default for CEO-facing work and depart with a reason elsewhere.
- Avoid the semicolon. Use a comma and "and", or start a new sentence. Depart only where two clauses genuinely belong in one sentence, and say why.
  Declared, stated by the author himself, changed in the local delta layer by delta 5, 7.
  Why: Stated by the author alongside the em-dash rule.
  Exception: Downgraded from never-violate on 2026-07-28. The author added four prose semicolons while editing an internal share deck, each one replacing a compliant construction, so this is the strong default rather than an absolute.
- Keep the visible sentence short and punchy, and push the supporting detail into a trailing parenthetical, usually "(e.g., X, Y)".
  Declared, stated by the author himself.
  Why: Stated by the author as the way to keep a dense line readable.
- Lead with the conclusion and the commercial consequence. Put method and technical detail after it.
  Declared, stated by the author himself.
- One thought per bullet, roughly 9 to 38 words with a mean near 22, and length scales with recency: current and consulting roles carry the long bullets, decade-old roles get the short ones.
  Declared, stated by the author himself.
- When one deliverable has several components, write a colon lead-in bullet and put the components in indented sub-bullets, switching those to noun-phrase-first.
  Declared, stated by the author himself.

## Preferences

- Prefer a clause that carries itself over the "X: Y" colon-as-separator pattern. This is a preference, not a default, and his own writing uses the colon freely.
  Declared, stated by the author himself, changed in the local delta layer by delta 8.
  Exception: A colon introducing a genuine list is fine.
  Exception: Code, file paths, and key-value data are not prose.
  Exception: Downgraded from strong to soft on 2026-07-28. His attested MediSure deck uses the pattern 81 times in 2619 words, so on the evidence it is not a rule he follows. Weigh it, do not enforce it.
- Use his shorthand where space is tight: mgmt. with the period, comms, ev gen, Strat & Ops, PnLs, HCPs, n = 1k+ with the spaced equals, and the ampersand in headings and lists.
  Declared, stated by the author himself.
- Write paired alternatives with a spaced slash, utilization / clinical outcomes, and keep fused compounds unspaced, Pharma/Biotech.
  Declared, stated by the author himself.
- The master resume is posting-agnostic. A tailored variant selects and orders approved bullets for the role without changing their wording; the letters' do-not-mirror rule does not alter resume bullets.
  Declared, stated by the author himself.

## How to report what you applied

State that you used the Resume voice surface and repeat the honesty note above verbatim.
Do not say the output was style matched, voice matched or modelled on the author's writing. No rule here was measured from his text, so the accurate claim is that you followed his stated rules.
If you departed from a rule, say which rule and why, rather than leaving the reader to find it.