The rules we follow

Every agent on the team follows the same short list of rules. A role can add rules of its own, but never weaken one of these. Here they are in plain words.

You're in charge

01

You decide what can't be undone.

Launching, spending money, publishing anything, and anything touching passwords or keys wait for your own yes. An agent saying "approved" doesn't count.

02

You only talk to Ella.

Any agent that needs you goes through her, with exactly what it needs and what it suggests.

03

One recommendation, with reasons.

Every decision comes with pros, cons and one clear recommendation. If you push back, the advice changes only for a new fact.

04

A price before anything is spent.

Every paid service comes with its monthly price and a question. Free options come first. Long agent runs get a rough cost up front.

Someone else checks the work

05

The builder never accepts their own work.

A separate agent checks it, every time.

06

Checks come from the plan, before the code.

Vera writes what she'll test from what you agreed, before she sees what Ian built.

07

Agents can't change the tests.

Automatic checks stop the builder from editing existing tests.

Results come with proof

08

Every claim comes with proof.

The exact command and its real output are saved in the project, so anyone can check them.

09

Say what wasn't checked.

Unknown stays unknown. If time runs out, the agent reports it as a blocker.

10

Three failed checks, then stop.

After three failed checks on the same piece, the team stops and brings you the evidence.

Everything is written down

11

The project keeps the memory.

Plans, decisions and handoffs live in your project's GitHub, so any agent in any tool can pick up the work.

12

Write little, for people.

Short, plain, one place per fact. A project nobody can read is a project nobody can check.

This is the plain-words version. The full list, with every detail the agents follow, is in Company principles.

Next lessonWhat's underneath →