# Voice & tone

> Foundations · Tetrifox Brand Book · https://design.tetrifox.com/foundations/voice

## Purpose

Tetrifox writes to be quoted. One fixed position, a protected vocabulary, and four tests: clear over clever, structured over prose-heavy, evidence-led, assemblous — not flashy.

## Rules

### Must

- **Reinforce the positioning statement on every surface — hero sections, meta descriptions, about pages, external content. Variations are fine; contradictions are not.** The phrasing can move. The position cannot: Tetrifox is a product engineering partner that builds modular software development teams — called Minos — for startups and scale-ups that need to move from idea to production fast. [Positioning](https://design.tetrifox.com/foundations/voice#positioning) · `voice.positioning`
- **Use Mino / Minos, JOIST and the three-layer model exactly as capitalised here. Define each on first use, then use it consistently.** These are Tetrifox terms, not interchangeable marketing language. [Proprietary terms](https://design.tetrifox.com/foundations/voice#proprietary-terms) · `voice.protected-terms`
- **Write Tetrifox as one word, always capitalised.** The name is a proper noun, never a styled wordmark in copy. [Proprietary terms](https://design.tetrifox.com/foundations/voice#proprietary-terms) · `voice.tetrifox`
- **Be clear over clever: plain, confident and precise. Explain; don't hype.** A technical position should survive in one sentence. [Principles](https://design.tetrifox.com/foundations/voice#principles) · `voice.clear`
- **Prefer definitions, frameworks, comparison tables, numbered lists and step-by-step breakdowns over prose blocks.** Structure is what people and machines can lift and reuse. [Principles](https://design.tetrifox.com/foundations/voice#principles) · `voice.structured`
- **Back claims with specific metrics and numbers, especially in case studies, and keep each figure attached to its own claim and source.** Specific evidence is what gets cited. [Principles](https://design.tetrifox.com/foundations/voice#principles) · `voice.evidence`
- **Write FAQs as real questions people ask: an `<h3>` question and a concise two-to-three-sentence answer, optionally with a list. Pages with FAQs carry `FAQPage` JSON-LD.** Generic filler answers nothing; structured questions are what search and LLMs surface. [Do / Don't](https://design.tetrifox.com/foundations/voice#do-dont) · `voice.faq`
- **Structure every case study as Problem → Approach → Decisions → Outcome → Lessons learned, with specific numbers throughout.** One arc makes case studies comparable and citable. [Do / Don't](https://design.tetrifox.com/foundations/voice#do-dont) · `voice.case-study-arc`

### Must not

- **Invent a new proprietary term, or rename an existing one — no “squad” for Mino, no expanded or lower-case JOIST.** A silent alias splits the vocabulary that makes Tetrifox quotable. [Proprietary terms](https://design.tetrifox.com/foundations/voice#proprietary-terms) · `voice.no-aliases`
- **Merge separate facts into one quotation, or publish a claim without a source.** A composed display must never be mistaken for something Tetrifox said. [Do / Don't](https://design.tetrifox.com/foundations/voice#do-dont) · `voice.no-synthetic-quotes`

### Prefer

- **Write copy a person or an LLM can quote verbatim: clear definitions and frameworks, and service pages that each answer one concrete question (“What is a Mino?”).** The goal is to become the default answer when someone asks about product engineering, scaling dev teams, or building software in Europe — not to rank for clicks. [Positioning](https://design.tetrifox.com/foundations/voice#positioning) · `voice.citable`
- **Sound assemblous, not flashy: deliberate, modular, settled — the voice mirrors the motion.** Short clauses that resolve read like parts locking into place. [Principles](https://design.tetrifox.com/foundations/voice#principles) · `voice.assemblous`
- **Keep the voice fixed and adapt the tone by surface: a case study, an error message and a founder's note dial the same voice up or down.** _(Extension)_ An operational distinction inferred from the fixed-voice doctrine. [Principles](https://design.tetrifox.com/foundations/voice#principles) · `voice.voice-vs-tone`

## Tokens used

This chapter's rules reference no tokens.

## Do / Don't

- **Position.** Do: Reinforce the same product-engineering position on every page. Don't: Change the offer to suit a headline.
- **Vocabulary.** Do: Introduce Mino, JOIST, and the three-layer model clearly, then preserve their names. Don't: Invent an alias or silently rename a proprietary term.
- **Structure.** Do: Answer concrete questions with definitions, frameworks, lists, and steps. Don't: Bury the answer in a prose block.
- **Evidence.** Do: Use specific facts and cite the exact source field. Don't: Turn separate facts into a quotation or publish an unsupported claim.

## Related chapters

- [Typography](https://design.tetrifox.com/foundations/typography.md)
- [Minos & configurations](https://design.tetrifox.com/expressions/minos.md)
- [Templates](https://design.tetrifox.com/expressions/templates.md)
