Foundations
Voice & tone.
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.
Calibration bench · verified corpus · 04 tests
- Voice
- The fixed personality. One position, one vocabulary, one way of sounding — the same on every page.
- Tone
- How the voice adapts by surface. A case study, an error message, and a founder's note dial the same voice up or down.
The fixed point
Positioning.
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.doctrine · Voice doctrine · positioning statement
brand-bundle/voice.md · positioning-statement
“We embed a complete product team—consultancy, leadership, and engineering in one accountable unit—so scaling companies move from idea to production fast. We call it a Mino.”verbatim · Home · hero
messages/en/home.json · hero.subtitle
“We embed into scaling companies to bridge the gap between business ambition and engineering capacity. The result: product teams that think like founders and ship like engineers.”verbatim · About · hero
messages/en/about.json · aboutHero.subtitle
The rules
- Must
Reinforce the positioning statement on every surface — hero sections, meta descriptions, about pages, external content. Variations are fine; contradictions are not.
- 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 vocabulary
Proprietary terms.
Define once. Use consistently.
- Mino / Minos
- A modular software development team — the core unit Tetrifox assembles and delivers. Consultancy, leadership, and engineering delivered as one accountable Mino.
First use
Define the modular team before using the name as shorthand.
Thereafter
Keep Mino singular and Minos plural; never replace it with squad.
- JOIST
- Tetrifox's named framework. Use the term deliberately and consistently.
First use
Name JOIST as the Tetrifox framework and explain its role in context.
Thereafter
Keep every letter capitalized; do not expand or rename it.
- Three-layer model
- The consultancy / leadership / engineering composition of a Mino.
First use
Name all three layers when the model is introduced.
Thereafter
Preserve the order and the three-layer name.
Protected vocabulary · 03 terms · no aliases
The rules
- Must
Use Mino / Minos, JOIST and the three-layer model exactly as capitalised here. Define each on first use, then use it consistently.
- Must not
Invent a new proprietary term, or rename an existing one — no “squad” for Mino, no expanded or lower-case JOIST.
- Must
Write Tetrifox as one word, always capitalised.
The instrument
Principles.
Choose a test. The specimen, source, and reason change together. A voice rule is useful only when its evidence is visible.
Clear over clever
“AI is an engineering problem, not a strategy problem.”
Why it qualifies
The contrast states a technical position in one sentence without inflated language.
Plain, confident, precise. Explain, don't hype.
Showing Clear calibration: AI Applications · reframe.
The rules
- Must
Be clear over clever: plain, confident and precise. Explain; don't hype.
- Must
Prefer definitions, frameworks, comparison tables, numbered lists and step-by-step breakdowns over prose blocks.
- Must
Back claims with specific metrics and numbers, especially in case studies, and keep each figure attached to its own claim and source.
- Prefer
Sound assemblous, not flashy: deliberate, modular, settled — the voice mirrors the motion.
- Prefer
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
Release protocol
Do / Don’t.
Use the same four tests before copy ships. Each decision protects one part of the voice contract.
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.
The rules
- Must
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 carryFAQPageJSON-LD. - Must
Structure every case study as Problem → Approach → Decisions → Outcome → Lessons learned, with specific numbers throughout.
- Must not
Merge separate facts into one quotation, or publish a claim without a source.
One position. One vocabulary. Four tests. Copy that can be quoted.