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.
One or more deltas in the database have changed this surface relative to the seed. Changed rules are marked overridden.
never violate
Breaking one of these is a defect, not a judgement call. 7 rules.
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
- 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.
- 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.
- 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.
- 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.
- 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. 5 rules.
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.
declaredhis own wordsmechanicsoverridden
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, so "Phase 1-3" is a span and "Phase 1, 3" is two phases. Leave those alone.
- 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.
- 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."
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.
declaredhis own wordsmechanicsoverridden
Stated by the author alongside the em-dash rule.
- 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.
- Declared: "No em dashes AND no semicolons anywhere in the copy."
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."
preferences
Taste. Use judgement. 1 rules.
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.
declaredhis own wordssentenceoverridden
- A colon introducing a genuine list is fine.
- Code, file paths, and key-value data are not prose.
- 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.
- Declared: "Avoid the 'X: Y' colon-as-separator pattern too."
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 - 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. - 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 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. - 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. ## 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. ## 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.