Rules for Cover letters

# Voice rules for Cover letters

26 rules apply on the Cover letters surface, 25 declared, 0 measured, 1 inherited and 0 proposed, and 1 rule has not yet been confirmed by the author for this surface. 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.
- Sign off with 'Sincerely,' on its own line, then the full name and credentials exactly as they appear on the resume, 'Christopher Tossas-Betancourt, Ph.D.'
  Declared, enforced as a house rule in his codebase.
  Why: Declared in the letter pipeline, whose quality gate byte-matches the sign-off name line against the resume, so any variant fails the letter.
  Good: Sincerely, / Christopher Tossas-Betancourt, Ph.D.
  Avoid: Sincerely, / Chris Tossas, Ph.D.

## 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.
- Build the letter as three moves: a one-paragraph opener that names the company and the role and connects Chris to them, an evidence body of one or two paragraphs, and a brief close. Three or four paragraphs in total, and every paragraph owns one distinct objective, so two paragraphs may never do the same job. Write unbroken prose, avoiding bullet lists and headings.
  Declared, stated by the author himself.
  Why: The author confirmed the four-paragraph form directly, so the body may split into two paragraphs when each carries its own theme. His declared split puts competitive intelligence and forecasting in one paragraph and market research in its own. The 2025 bullet-list template is superseded and must not be reintroduced from his older letters.
  Good: At McKinsey, I led cross-functional strategy and analytics workstreams across the product lifecycle, from clinical development through launch and growth.
  Avoid: In alignment with the key responsibilities of the Sr. Manager role, I bring:
- Keep the opening to one paragraph that names the company and the role, at most two of the role's core elements, e.g. 'strategic planning and competitive intelligence', and a why-it-matters hook that connects the role to a broader impact, e.g. 'while improving public health'. Do not catalogue the role's responsibilities or over-explain the company's situation before connecting to Chris.
  Declared, stated by the author himself.
  Why: Stated by the author in his opening refinements after trimming job-description lists out of his own drafts. An opening that lists everything the role covers reads as a checkbox pass over the posting.
- Keep the evidence paragraphs on the core case, competitive intelligence, forecasting models, and market research. Do not stretch to cover every posting responsibility, do not re-establish context the opening already gave, and do not add communications or Ph.D. sentences to the body unless Chris asks.
  Declared, stated by the author himself.
  Why: Stated by the author, and his Disc Medicine edit deleted exactly those two sentences from the draft. Checkbox coverage dilutes the core case.
  Good: I led competitive intelligence efforts across multiple engagements, mapping competitors' evidence generation strategies, pipeline products, and portfolio performance to identify where clients' assets were most differentiated and create hypotheses surrounding potential competitor actions.
  Avoid: My Ph.D. in Biomedical Engineering provides the scientific foundation to develop deep working knowledge of Disc's therapeutic landscape in hematology and iron homeostasis.
  Exception: When the role's center of gravity is genuinely elsewhere, the approved angle brief, not the posting, decides what the core case is. The default is competitive intelligence, forecasting, and market research.
  Exception: Add communications or Ph.D. material only when Chris asks for it for a specific role.
- Close brief and plain, without performative capability phrases or over-qualifying what he brings, 'my strategic and analytical skillset' over 'consulting-caliber strategic and analytical capabilities in-house'. Pipeline-gated drafts close in one sentence, the quality gate's close budget allows no more. The author's declared two-sentence close applies to hand-edited letters outside the gate.
  Declared, stated by the author himself.
  Why: The author's close refinements declare plain language and a two-sentence ceiling, and his Disc Medicine edit deflated the draft's self-praise. The pipeline skill and quality gate declare a one-sentence close for gated drafts, so the two-sentence form is scoped to hand-edited letters where no gate constrains the close.
  Good: I look forward to discussing how my experience aligns with the needs of the role.
  Avoid: I would be excited to bring consulting-caliber strategic and analytical capabilities in-house to support Disc's corporate planning, commercial preparation, and growth initiatives, and I look forward to discussing how my experience aligns with the needs of the role.
  Exception: In hand-edited letters outside the quality gate, close in two sentences at most: a plain capability sentence, then the look-forward sentence, as in the shipped Disc Medicine final's 'I would be excited to bring my strategic and analytical skillset to support Disc's corporate planning, commercial preparation, and growth initiatives. I look forward to discussing how my experience aligns with the needs of the role.'
- Open with warmth and a personal stake in the role. 'What attracts me to...' and 'I write with enthusiasm to be considered for...' both work, there is no fixed formula. Avoid detached analytical framings like 'Strategy at X is a different problem from strategy at Y.'
  Declared, stated by the author himself.
  Why: Stated by the author after his own edits, where he rewrote a detached analytical opener into first-person motivation while keeping the substance. The bundled voice-guide's push toward detached insight-led openers is overridden by this preference.
  Good: What attracts me to the Senior Manager, Strategy & Corporate Development role at a clinical-stage biotech like Disc Medicine is to build the analytical and strategic foundations that determine how pipeline assets get valued, positioned, partnered, and commercialized.
  Avoid: Strategy at a clinical-stage biotech like Disc Medicine is a different problem from strategy at a large pharma company. There is no established commercial infrastructure to optimize.
  Exception: A role-insight opener is fine when it carries his personal stake by the end of the opening paragraph. His shipped Akebia and Verily letters open on an insight, and his Disc Medicine edit grafted the personal frame onto the insight rather than discarding it.
- Do not mirror the posting's internal terminology, acronyms, or team names back at the company. Rephrase in simpler, outcome-oriented language.
  Declared, stated by the author himself.
  Why: Stated by the author three separate times in his editing notes. Parroted jargon reads as box-ticking, outcome phrasing shows the job was understood.
  Good: coordinating cross-functionally to accelerate the business decision making
  Avoid: coordinating across project management, Portfolio Strategy Development, and Disease Area Decision Boards to ensure portfolio alignment with strategic objectives
  Exception: mirror_terms listed in the approved angle brief are deliberate echoes the quality gate whitelists, weave those in naturally. The specificity gate also expects at least one concrete JD-specific term in the opening, so keep one real term for the role while rephrasing the rest.
- When in doubt, make the letter shorter and more focused rather than longer and more comprehensive. Cut anything that exists to tick a posting checkbox rather than to strengthen the narrative.
  Declared, stated by the author himself.
  Why: Stated by the author as a general pattern, and both of his tracked edits cut roughly a fifth of the draft.
- Break long compound sentences into two, and give an impact claim its own sentence rather than a trailing ', and' clause.
  Declared, stated by the author himself.
  Why: Stated by the author and applied repeatedly in his Novartis and Disc Medicine edits, which split ', and' chains into short declaratives.
  Good: ...is the expertise I built during my tenure at McKinsey advising pharma and biotech clients. I have continued to sharpen this skillset in my current role leading clinical strategy initiatives at CenterWell Senior Primary Care.
  Avoid: ...is the expertise I built during my tenure at McKinsey advising pharma and biotech clients, and have continued to sharpen in my current role leading clinical strategy initiatives at CenterWell Senior Primary Care.
  Exception: In pipeline-gated drafts, keep multiword capitalized employer names out of the opening paragraph when imitating this opener bridge: the truthfulness gate accepts only JD-attested capitalized phrases there, so 'at CenterWell' passes where 'at CenterWell Senior Primary Care', as in this verbatim hand-letter example, would not.
- Cut corporate filler and prefer plain active verbs: 'shaped strategic recommendations' over 'translating insights into recommendations', 'executive-level presentations' over 'actionable recommendations for senior leadership', and drop 'cross-functionally' when the partner teams are already listed.
  Declared, stated by the author himself.
  Why: Stated by the author, each replacement phrase in this rule is his own wording from the updates file. Process phrasing adds corporate weight without adding information.
  Good: partnered with Finance, Commercial, R&D, and Strategy & Operations teams and shaped strategic recommendations into executive-level presentations
  Avoid: synthesizing complex information across teams and translating it into actionable recommendations for senior leadership
- Cut modifiers that add weight but not meaning, 'complex', 'strategic', 'multi-year', 'for senior leadership', and qualifiers like 'inside one of the largest health insurers'. This is a judgment call on inflation, not a word ban.
  Declared, stated by the author himself.
  Why: Stated by the author twice in his editing notes and applied throughout his Novartis edit. The substance is meant to speak for itself.
  Good: garnering information about competitors' pipelines, evidence generation strategies, and portfolio performance into hypotheses and recommendations
  Avoid: synthesizing complex information about competitors' pipelines, evidence generation strategies, and portfolio performance into strategic recommendations for senior leadership
  Exception: 'Strategic' describing genuine role content is fine, he writes 'strategic planning' and 'my strategic and analytical skillset' himself. Cut the modifier only when deleting it would not change the meaning.
- Vary sentence length and let at least one short declarative sentence stand on its own. Long analytical sentences need short ones around them to breathe.
  Declared, enforced as a house rule in his codebase.
  Why: The letters quality gate enforces a rhythm check mechanically, this rule states the principle so drafts do not fail it.
  Good: External consultants deliver a recommendation and leave.
  Avoid: External consultants typically deliver a strategic recommendation and then transition off the engagement, which means the organization is left to operationalize the findings without continued analytical support.
- Open the document with 'Dear Hiring Manager,' and nothing above it: no header block, no contact info, no date.
  Declared, enforced as a house rule in his codebase.
  Why: Declared in the letter pipeline's document spec and near-unanimous across the letter corpus.
  Good: Dear Hiring Manager,
  Avoid: To Whom It May Concern,
  Exception: When a named recruiter is known, greet them by name. His own sent letters use 'Hello Fabiana,', 'Hi Connor,', and 'Hi Julian,'.
- Keep the letter short by design, well under a page. Stay inside the pipeline's configured word bounds without padding to fill them, and when a draft can lose a weak paragraph and keep the core case, lose it.
  Declared, stated by the author himself.
  Why: The word bounds in the pipeline config were set by the author, and his stated default is shorter when in doubt. The 2025 era's roughly 520-560 word template is superseded.

## 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.
- Keep secondary experience to one short, concrete paragraph with operational framing, 'Patient Segmentation tool rollout' over 'Patient Segmentation strategy', and drop stakeholder-alignment padding like the Humana board-meeting sentence unless it is directly relevant to the role.
  Declared, stated by the author himself.
  Why: Stated by the author in his CenterWell refinements and enacted in his Novartis edit, which cut the paragraph from roughly 65 to 32 words and one idea.
  Good: More recently at CenterWell, I have supported enterprise Patient Segmentation tool rollout, including analytical models to assess operational readiness across geographies and designing Power BI dashboards to track utilization and clinical outcomes.
  Avoid: More recently at CenterWell, I have supported enterprise Patient Segmentation strategy inside one of the largest health insurers, building analytical models to assess rollout readiness across clinical pods and designing Power BI dashboards to track utilization and clinical outcomes.
  Exception: Keep the Humana board-meeting and stakeholder-alignment material when the posting is explicitly about governance or executive stakeholder management. His note bans it as default padding, not absolutely.
- When a draft runs long, delete the weakest proof point entirely instead of trimming every paragraph a little.
  Inherited, an extrapolation from another surface that the author has not confirmed, extrapolated for this surface, never stated by him, still awaiting the author's confirmation.
  Why: Inferred from his editing hand across two letters. He has not stated this as a rule.
- Set the docx in Garamond 11pt with 14pt line spacing, 1 inch top and bottom margins, and 1.25 inch side margins.
  Declared, enforced as a house rule in his codebase.
  Why: House convention encoded in the letter generation script, not stated by the author in person. Stated here so a letter produced outside the pipeline still matches the ones it produces.

## How to report what you applied

State that you used the Cover letters 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.