Rules for MIRA UI copy
Governed by the codebase design system.
13 rules apply on the MIRA UI copy surface, 13 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. 9 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."
No breadcrumb row. The left nav already shows location, so an exec sees the title and the content.
declaredhouse rulestructureguidance only, not mechanically checked
- Declared design-system rule: "No breadcrumbs."
Prose is never monospace. Reserve the mono face for genuinely numeric, tabular or code content.
declaredhouse ruleformatguidance only, not mechanically checked
- Declared design-system rule: "Prose is never monospace."
An interpretive derivation is labelled a computed read. Never present it with the visual authority of a sourced fact.
declaredhouse rulestanceguidance only, not mechanically checked
- Declared across the codebase, e.g. the dashboard capability read renders "computed read".
default, depart only with a reason
Follow unless the case is genuinely different, and say why when departing. 4 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)."
A framing aside is quiet, not a box. Use the surface-alt background with a thin left accent stripe, never a loud filled colour box with a chip label.
declaredhouse ruleformatguidance only, not mechanically checked
- Declared design-system rule: "Framing asides are quiet, not boxes."
the exact text an agent receives
# Voice rules for MIRA UI copy 13 rules apply on the MIRA UI copy surface, 13 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. - No breadcrumb row. The left nav already shows location, so an exec sees the title and the content. Declared, enforced as a house rule in his codebase. - Prose is never monospace. Reserve the mono face for genuinely numeric, tabular or code content. Declared, enforced as a house rule in his codebase. - An interpretive derivation is labelled a computed read. Never present it with the visual authority of a sourced fact. Declared, enforced as a house rule in his codebase. ## 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. - A framing aside is quiet, not a box. Use the surface-alt background with a thin left accent stripe, never a loud filled colour box with a chip label. Declared, enforced as a house rule in his codebase. ## How to report what you applied State that you used the MIRA UI copy 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.