Skip to Content
Docs

Autonomy levels

The four autonomy levels L0 to L3, what an agent may do at each, and how a level is raised or lowered.

An autonomy level says how much an agent may do without a person. Tosven has four levels, L0 to L3, set per agent and per type of action. Raising a level is slow and needs evidence. Lowering it takes one person and applies at once.

Try itWhat an agent may do at each level
  • Read records and prepare a proposal
  • Write and edit drafts
  • Complete an action under your limits
  • Post to the ledger under a published rule
  • Act alone within a scope you name
  • Make a payment or file a tax return
L0 · A person decides every card. · Sample data

The four levels

Every agent starts at L0. A level never gives an agent more rights than its manager has. It only decides how much of that boundary the agent may use on its own.

L0

Suggest only. The agent reads, prepares a proposal and opens a decision card. A person decides every card.

L1

Exact match. The agent may also write and edit drafts on its own, for example a coding draft for a purchase invoice from a supplier it knows. Anything final still waits for a person: approving, posting, cancelling and deleting need at least L2. At L1 no agent posts to the ledger by itself.

L2

Below a threshold. The agent may complete an action on its own when it stays under the limits you set, such as an amount per action and a daily limit. For ledger entries there is one more condition: a posting rule that a person published. Each automatic decision is then signed in the name of that rule. Without a published rule, the entry goes to a person even at L2.

L3

Full authority in a defined area. The agent acts on its own within a scope you name. It needs much stronger evidence than L2, and several kinds of action can never reach it.

What decides the level in practice

For each action Tosven takes the lowest of three ceilings: the one set for the module, the one set for that type of action, and the one fixed by the product. Then four checks can pull the action down to a person:

  • Amount limit. The action is above the amount allowed for this type of action.
  • Daily limit. The agent has used its allowance for the day.
  • New counterparty. A supplier or customer the company has not dealt with before is always handled at L0.
  • Confidence floor. The agent is not sure enough. As a guide, a proposal at 95 % or above may run automatically if the level allows, 80 to 94 % asks for approval, and below 80 % is marked for review.

Two more cases always go to a person: a card from a run that used an AI model, and a card from a run that a person started by hand.

Ceilings the product sets

These are product rules. They are not settings.

Type of actionHighest levelWhy
PaymentNoneAgents propose, people pay
Tax filingL1Filing stays under human approval
Ledger postingL1, or L2 with a published ruleAn entry needs a signature or a documented rule
Payment reminderL2, never L3A letter to a customer stays governed

Even at L2, the Collections agent never sends these on its own: the final reminder, a reminder after a partial payment, a reminder on a disputed invoice, a reminder to an address that bounced before, or the first letter to a customer. In the pilot it runs in review only.

Actions with a significant effect on a private person never reach L3.

Raising a level

A raise is a small ceremony with four parts. At Kaarna Group, Elina Koskinen wants small invoices from known suppliers posted without a click.

Request the raise

Elina requests L2 for invoice coding and names the scope: known suppliers only, with a limit of 500,00 € per invoice.

Read the replay

Tosven replays the last 30 days of the agent's work at the new level and reports how many cards it covered, how many would still go to a person and how many critical errors it found. A raise needs zero critical errors. By default L2 also needs at least 300 verified cases with an error bound of 1 % or less, and L3 at least 3.000 cases with a bound of 0,1 % or less.

Get a second approver

A second person signs the raise. Mikko Lehtonen signs for Kaarna Group. In a company with one person, a written sole-person declaration takes the place of the second approver and stays visible on the record.

Wait 72 hours

The new level takes effect after a cooling period of 72 hours. Until then the agent works at the old level.

The evidence is read per slice of work: type of action, new or known counterparty, amount band and tax type. A slice with too little history stays at the lower level, even when the rest is raised.

Lowering and resetting

Lowering a level takes one person and applies at once. If Elina finds one wrong VAT box in the error log, she can put the Ledger agent back to L1 in the same minute.

Tosven also lowers levels itself:

  • A changed version. If the model, the instructions or the rule version behind an agent changes, the autonomy it earned in that scope returns to L0.
  • A critical error under a rule. When a critical error is confirmed in a decision made under a published rule, that rule is retired at once.
  • A pulled kill switch. An agent stopped by Tosven drops to L0. It can still propose.

Every change of level is written to a chained record. The level that applied on any past day can be read back and is never overwritten.

Next steps

  • Decisions and approvals: what a decision card shows and what happens after you sign.
  • Agents: the roster, managers and the limits no level can lift.
  • Ledger: how entries are posted and why they cannot be edited afterwards.

On this page