# Minos & configurations

> Expressions · Tetrifox Brand Book · https://design.tetrifox.com/expressions/minos

## Purpose

Consultancy, technical leadership, and engineering delivered as one accountable unit. The problem sets the composition; the Mino carries it into production.

## Rules

### Must

- **Define a Mino as consultancy, technical leadership and engineering delivered as one embedded, accountable unit — never as “a team” or “a squad” alone.** A Mino is not just a team—it’s consultancy, technical leadership, and engineering delivered as one embedded unit. We start by understanding your business problem, then build the capability to solve it. [What a Mino is](https://design.tetrifox.com/expressions/minos#what-is-a-mino) · `minos.definition`
- **Name all three layers, in order, when introducing the model: Strategic Consultancy, Technical Leadership, Engineering.** The three-layer model is protected vocabulary; its order is the argument (business problem first, then direction, then delivery). [What a Mino is](https://design.tetrifox.com/expressions/minos#what-is-a-mino) · `minos.three-layers`
- **Use the five JOIST configurations with their sourced descriptors: J-Mino (Ops enhanced), O-Mino (Balanced), I-Mino (Dev-heavy), S-Mino (Strategic Unit), T-Mino (Test-focused).** Each Tetris shape tells you the competency emphasis at a glance. [Configurations](https://design.tetrifox.com/expressions/minos#configurations) · `minos.joist`
- **Start every Mino with consultancy: in copy, in process and in diagrams.** “Every Mino starts with consultancy, not code.” (Home · How we work) [The anchor law](https://design.tetrifox.com/expressions/minos#the-anchor-law) · `minos.consultancy-first`

### Must not

- **Invent use cases or role mappings for a configuration. Only I, J and T have sourced use cases; O and S keep their descriptors alone.** A Mino claim without a source is an invented brand fact. [Configurations](https://design.tetrifox.com/expressions/minos#configurations) · `minos.no-invented-scenarios`

### Prefer

- **Describe how a Mino forms as four steps: understand the problem, design the Mino, embed and deliver, adapt and scale.** The composition follows a business challenge, not a staffing request. [What a Mino is](https://design.tetrifox.com/expressions/minos#what-is-a-mino) · `minos.problem-first`
- **Frame JOIST as the load-bearing beam the unit rests on only as a gloss, never as a sourced claim.** _(Extension)_ The five letters are sourced; the beam reading is the book's framing. [Configurations](https://design.tetrifox.com/expressions/minos#configurations) · `minos.beam`
- **In Mino diagrams, keep the consultancy cell fixed and orange while the rest of the silhouette changes. Do not present cell coordinates or orientations as a specification.** _(Extension)_ The source specifies no geometry; the fixed anchor is an illustration of consultancy-first doctrine. [The anchor law](https://design.tetrifox.com/expressions/minos#the-anchor-law) · `minos.anchor-geometry`

## Tokens used

This chapter's rules reference no tokens.

## Do / Don't

- **Definition.** Do: A Mino: consultancy, technical leadership, and engineering delivered as one accountable unit. Don't: Our Mino squads are flexible dev teams.
- **Configurations.** Do: T-Mino (Test-focused): hardening quality before a major release. Don't: O-Mino: perfect for greenfield AI projects.

## Related chapters

- [Voice & tone](https://design.tetrifox.com/foundations/voice.md)
- [Layout & grid](https://design.tetrifox.com/foundations/layout.md)
- [Components](https://design.tetrifox.com/expressions/components.md)
