Rules for PowerPoint
Best-evidenced surface. Decks reviewed by the CEO.
22 rules apply on the PowerPoint surface, 22 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.
This surface is running the seed profile exactly. The database holds no delta for it.
never violate
Breaking one of these is a defect, not a judgement call. 15 rules.
Never use an em dash. Use a comma, or split the sentence, or use "and".
declaredhis own wordsmechanics
Stated by the author as a hard rule for decks, and repeated as a house rule.
Breadth is the one axis rivals cannot buy, 78 of 137 classes against Enamine's 52
Breadth is the one axis rivals cannot buy — 78 of 137 classes against Enamine's 52
- 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: "Phase 1-3" is a span, "Phase 1, 3" is two phases. Leave those alone.
- Declared: "No em dashes anywhere in the copy."
- Declared again, jointly with the semicolon rule: "No em dashes AND no semicolons anywhere in the copy."
Never use a semicolon. Use a comma and "and", or start a new sentence.
declaredhis own wordsmechanics
Stated by the author alongside the em-dash rule.
- Declared: "No em dashes AND no semicolons anywhere in the copy."
No emoji. Not in copy, not in headings, not in commit messages.
declaredhouse rulemechanics
- Declared house rule: "No emoji. Not in copy, not in commits, not in CHANGELOG entries."
Sentence case everywhere. No all-caps strings and no uppercase text styling.
declaredhouse rulemechanics
- Declared house rule: "No uppercase. Headings, buttons, chips, labels, sentence case throughout."
Every number, quote and factual claim carries its source. An interpretive read is labelled a computed read, never dressed as a sourced fact.
declaredhouse rulestanceguidance only, not mechanically checked
The non-negotiable house rule. A claim without provenance does not ship.
- Declared house rule: "Every data claim ships with a Cite chip."
- Declared: "Source the big claims inline with a short tag right after the claim."
Never invent a figure, a name, a citation or a confidence level. An honest gap is stated as a gap.
declaredhouse rulestanceguidance only, not mechanically checked
Repeatedly enforced across his codebase: a missing structure is an honest visible gap, a fabricated one silently corrupts everything downstream.
- Declared house rule, stated in the codebase as: "A missing structure is an honest visible gap; a fabricated one silently corrupts every downstream metric."
Every slide title states the conclusion, not the topic, and carries the number that proves it.
declaredhis own wordsstructureguidance only, not mechanically checked
A topic title makes the reader do the work. He reads a topic title as amateur, and read a reviewer complaint about missing insight as a demand for sharper conclusions, not for bare labels.
Breadth is the one axis rivals cannot buy, 78 of 137 classes against Enamine's 52
Reaction class coverage comparison
- Declared: "Titles are action/so-what takeaways (state the conclusion, not the topic)."
- Confirmed 2026-07-17: titles stay conclusions but get shorter and carry the number.
Bold the lead phrase of each bullet and weave it grammatically into the unbolded remainder, with no punctuation break between them.
declaredhis own wordssentenceguidance only, not mechanically checked
**Chemify alone scores strong on both make axes** while every rival spikes on one and collapses on the other
**Make axes:** Chemify is the only strong performer.
- Declared: "Selectively bold the lead of each bullet, and make the bold phrase weave grammatically into the non-bold remainder (no punctuation break between them)."
No terminal period at the end of a bullet.
declaredhis own wordsmechanics
- Declared: "No terminal punctuation at the end of a bullet (no final period)."
Black font everywhere. No coloured text.
declaredhis own wordsformatguidance only, not mechanically checked
- Declared: "Color: black font EVERYWHERE. No colored text."
No coloured boxes, fills or decoration. The only section-header treatment is a thin black horizontal line placed under the header text, never above it.
declaredhis own wordsformatguidance only, not mechanically checked
- Orange CUSTOMER-FACING / INTERNAL chips at (0, -0.29) are real furniture on the Chemify template and are kept.
- Declared: "Minimal formatting: do NOT use colored boxes/fills or heavy decoration. The ONLY section-header treatment is a thin BLACK horizontal line, placed UNDER the section header, never above it."
Slide title 28pt and unbolded, maximum two lines. Section header 16pt. Body and bullets 14pt. Shorten copy to fit rather than shrinking the type.
declaredhis own wordsformatguidance only, not mechanically checked
The large sizes are deliberate. They force lower density, so copy gets shortened rather than the type getting smaller.
- Declared: "slide TITLE = 28pt and UNBOLDED, max 2 lines; section HEADER = 16pt; body / bullets / material = 14pt. Bigger fonts are deliberate."
Set internal margins to zero on all four sides of every text box.
declaredhis own wordsformatguidance only, not mechanically checked
- Declared: "Text boxes: internal margins = 0 on all four sides on every text box."
Use the font the template actually runs, not the theme default. On the Chemify deck that is Century Gothic even though the theme reports Calibri.
declaredhis own wordsformatguidance only, not mechanically checked
Reading the theme is not enough. Every run in the Chemify deck overrides the theme font.
- Declared: "the actual run font in this deck's tables/titles is Century Gothic (theme major/minor is Calibri, but every run overrides to Century Gothic)."
Every source used on a slide is cited in a footnote on that specific slide.
declaredhis own wordsstanceguidance only, not mechanically checked
- Declared: "every source used on a slide is cited in a FOOTNOTE on that specific slide."
default, depart only with a reason
Follow unless the case is genuinely different, and say why when departing. 6 rules.
Avoid the "X: Y" colon-as-separator pattern. Rewrite so the clause carries itself.
declaredhis own wordssentence
- A colon introducing a genuine list is fine.
- Code, file paths, and key-value data are not prose.
- Declared: "Avoid the 'X: Y' colon-as-separator pattern too."
Keep the visible sentence short and punchy, and push the supporting detail into a trailing parenthetical, usually "(e.g., X, Y)".
declaredhis own wordssentenceguidance only, not mechanically checked
Stated by the author as the way to keep a dense line readable.
- Declared: "Keep the visible sentence short and punchy; push rich detail into a trailing '(e.g., XXX, YYY)'."
- Instance, his own typing: "transfer all files ... (without breaking anything)".
- Instance, his own typing: "CI platform information (e.g., claude.md, project_state.md, changelog_be.md, etc.)".
Lead with the conclusion and the commercial consequence. Put method and technical detail after it.
declaredhis own wordsstructureguidance only, not mechanically checked
- Declared: "Open with BD-executive-focused slides (commercial so-what first, not technical)."
Within one list, every bullet opens with the same grammatical form. Pick present-tense verbs or noun phrases, then hold it across that list.
declaredhis own wordssentenceguidance only, not mechanically checked
- Declared: "Parallel openings within a list: all bullets in one section start with the same grammatical form."
Bulletize most body text. Prefer indented bullets over prose, especially when each line is short.
declaredhis own wordsstructureguidance only, not mechanically checked
- Declared: "Bulletize most body text, especially when each line of info is short."
Charts earn their place by carrying the synthesis, never as decoration. Compress a chart to about three quarters of slide width and put a "what this means" insights rail on the right.
declaredhis own wordsstructureguidance only, not mechanically checked
- Declared: "Compress each chart to ~3/4 slide width and put an insights rail ('What this means') on the right with the takeaways."
preferences
Taste. Use judgement. 1 rules.
Aim for about ten slides in the main story. Less is more. A longer readable appendix is acceptable as backup.
declaredhis own wordsstructureguidance only, not mechanically checked
- Declared: "exec-friendly, aim ~10 slides for the main story ('less is more')."
the exact text an agent receives
# Voice rules for PowerPoint 22 rules apply on the PowerPoint surface, 22 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 - Never use an em dash. Use a comma, or split the sentence, or use "and". Declared, stated by the author himself. 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: "Phase 1-3" is a span, "Phase 1, 3" is two phases. Leave those alone. - Never use a semicolon. Use a comma and "and", or start a new sentence. Declared, stated by the author himself. Why: Stated by the author alongside the em-dash rule. - 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. - 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. - 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. - Every slide title states the conclusion, not the topic, and carries the number that proves it. Declared, stated by the author himself. Why: A topic title makes the reader do the work. He reads a topic title as amateur, and read a reviewer complaint about missing insight as a demand for sharper conclusions, not for bare labels. Good: Breadth is the one axis rivals cannot buy, 78 of 137 classes against Enamine's 52 Avoid: Reaction class coverage comparison - Bold the lead phrase of each bullet and weave it grammatically into the unbolded remainder, with no punctuation break between them. Declared, stated by the author himself. Good: **Chemify alone scores strong on both make axes** while every rival spikes on one and collapses on the other Avoid: **Make axes:** Chemify is the only strong performer. - No terminal period at the end of a bullet. Declared, stated by the author himself. - Black font everywhere. No coloured text. Declared, stated by the author himself. - No coloured boxes, fills or decoration. The only section-header treatment is a thin black horizontal line placed under the header text, never above it. Declared, stated by the author himself. Exception: Orange CUSTOMER-FACING / INTERNAL chips at (0, -0.29) are real furniture on the Chemify template and are kept. - Slide title 28pt and unbolded, maximum two lines. Section header 16pt. Body and bullets 14pt. Shorten copy to fit rather than shrinking the type. Declared, stated by the author himself. Why: The large sizes are deliberate. They force lower density, so copy gets shortened rather than the type getting smaller. - Set internal margins to zero on all four sides of every text box. Declared, stated by the author himself. - Use the font the template actually runs, not the theme default. On the Chemify deck that is Century Gothic even though the theme reports Calibri. Declared, stated by the author himself. Why: Reading the theme is not enough. Every run in the Chemify deck overrides the theme font. - Every source used on a slide is cited in a footnote on that specific slide. Declared, stated by the author himself. ## Default, depart only with a reason - Avoid the "X: Y" colon-as-separator pattern. Rewrite so the clause carries itself. Declared, stated by the author himself. Exception: A colon introducing a genuine list is fine. Exception: Code, file paths, and key-value data are not prose. - 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. - Within one list, every bullet opens with the same grammatical form. Pick present-tense verbs or noun phrases, then hold it across that list. Declared, stated by the author himself. - Bulletize most body text. Prefer indented bullets over prose, especially when each line is short. Declared, stated by the author himself. - Charts earn their place by carrying the synthesis, never as decoration. Compress a chart to about three quarters of slide width and put a "what this means" insights rail on the right. Declared, stated by the author himself. ## Preferences - Aim for about ten slides in the main story. Less is more. A longer readable appendix is acceptable as backup. Declared, stated by the author himself. ## How to report what you applied State that you used the PowerPoint 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.