Insight 02AI development
An agent can only dowhat the person can
Our agents have no access of their own. They work with a person’s token and exactly that person’s rights.
Station 01 / 06The starting point
No master key.
A separate login for the AI would hold rights that belong to no human. With us, every call belongs to a person and is recorded in the log.
- Person
- Agent no access of its own
Station 02 / 06The access
The token belongs to the person.
Created in the interface, only with two‑factor sign‑in. Valid for 90 days at most, revocable at any time, worthless as soon as the person is deactivated.
- Token belongs to the person
- 90 days at most
Station 03 / 06The rights
The same rights as in the browser, never more.
For each call, the database takes on the person’s identity. The same row-level permissions apply as for a click in the interface.
- Person’s rights
- Agent’s rights mirrored
Station 04 / 06The toolset
What does not exist, nobody can trigger.
Send, sign, delete, change roles: these tools are missing. No chat changes that.
- Send
- Sign
- Delete
- Change roles
Station 05 / 06The safeguards
All or nothing, never twice.
Every call is a transaction. An idempotency key stops a repeated job from booking twice.
- Job all or nothing
- Retry same key
Station 06 / 06The build
99 tests for what must not work.
Built in phases, each with a gate that only a human can open.
99Negative and positive tests