Studio

Design and engineering, kept together.

Strategy, design, implementation and verification stay connected. One continuous process, with clear decisions and evidence at each stage.

Send a project briefSee the working system
Operating model

A small practice by design.

  • Direct accountability for decisions that ship.
  • Fixed scope before implementation begins — the boundary is contractual.
  • Limited handovers between intent and evidence.
  • Specialist contribution where the work requires it.
  • Implementation kept close to architecture.
  • Evidence defines completion, not a verbal handover.
Commercial fit

Where the model fits.

Best for established organisations with a defined initiative—where architecture, interface and implementation must stay in one accountable thread. Not open-ended staff augmentation, and not a handover chain that separates the decision from the verified result.

Read the longer argument
How we work

From intent to evidence.

Each step keeps the original requirement in view, from the first constraint to the verified result.

  1. Intent
  2. Constraint
  3. Design
  4. Implementation
  5. Verification
  6. Evidence
Working principles

Keep the work clear.

  1. Remove what does not improve the system.
  2. Separate observation from judgement.
  3. Verify every implemented change.
Read the approach
Identity

Four marks. One system.

Each mark has one job. They belong together but never stand in for each other — the one you see tells you what the system is doing.

  1. COMMAND

    Structure. How it's built.

    An isometric frustum with the asterisk on its top face; the main brand object.

  2. brtk.

    Signature. Who made it.

    Our custom wordmark, always placed from the master drawing, never typed in a font.

  3. ASTERISK

    Connection. How things link up.

    Routing and coordination, and the small mark used for avatars and the favicon.

  4. Runtime

    Live. When it's running.

    Pixel lettering with monospace labels, used only when the system is doing work.

Interaction discipline

Movement has an operational role.

Brittek uses motion to explain hierarchy, orientation, disclosure, progress, feedback and completion. Essential content stays complete without animation, and reduced-motion users reach the same state without decorative travel.

Inspect the motion system
Published evidence

Verification is part of the design output.

This record is compiled from the repository. Inspect the system and the evidence behind its public claims.

Explore the evidence records
Design governor
103 public-surface files governed
Unit verification
146 deterministic tests
Public graph
24 entities across 29 routes
Machine surfaces
8 published endpoints
Graph version
2026-10-16