Rules are the
operating language.

The third root is the language of the work.

A seat and a record still need a rule for how to act. Otherwise the agent improvises a procedure the team never agreed.

In our team, the start check asks which rules are in reach before the task begins. The rule has to be where that check can read it.

A personality describes a voice. A rule describes a boundary.

Three lines are enough to begin.

1. MayWhat this seat may decide.

   The bounded job, and no further.

2. Hand onWhat belongs to another seat.

   Name where it goes.

3. A personWhat still needs a human.

   Consequential calls stay with the person who answers.

Try it with one rule you already follow.

1. Write the rule in the three lines: may, hand on, a person.
2. Name the seat it binds. The rule needs a seat that carries it.
3. Put it where the agent reads rules at the start of the work.
4. Ask the agent to show the rule it is using. A rule named in the answer is not proof it was followed.

The seat check in thefirst lesson is where that reading starts.

What this does not prove.

A rule does not make an agent more accurate. A rule on a page the agent never opens does not bind the work. People still accept purpose, vision, strategy, objectives and key results.

Instructions have to reach the agent, permissions have to hold, and the result still needs review.