The stop rule
The practical rule of the project: if an action is hard to undo, affects other people or uses sensitive data, implied consent is not enough. That is why no stage passes silently — disputed decisions stop and wait for confirmation.
Where the control points stand
- Mail assistant: no draft is sent without explicit confirmation; an employee checks the text and the recipients.
- Legal RAG navigator: the version of the document, the currency of the norm and the final legal position are checked by the relevant specialist.
- Local meeting scribe: the participants, the wording of the decisions, the deadlines and the responsible people are confirmed by the meeting owner.
- Database consultant: the control point is built into the architecture — read-only access, writing is forbidden.
Why this does not slow things down
A human reviews prepared material instead of repeating the agent's work: a draft with its rationale, a set of quotes, or meeting minutes with uncertain points flagged. This removes the backlog of routine preparation while responsibility remains with the appropriate role.
What changes without control points
Without stops, a mistake becomes hard to undo: a sent email, a published promise, changed data. The higher the autonomy and the consequences of a mistake, the stricter the permissions, the journaling and the human confirmation — this is the basic principle of the project's security.
Questions and answers
Can confirmation be disabled for speed?
No: the confirmation point is fixed before launch and goes into the passport. Rules can be configured for routine actions, but the final action stays with a human.
What happens with a disputed decision?
The process stops and waits for confirmation: a human checks the material, adjusts it or rejects the result.
Who confirms the result?
An employee with the right role and competence: the meeting owner, a lawyer, a sales manager — the control point is set before integration.
What is a control point?
A stage where the agent stops and waits for human confirmation before continuing.
Do all actions require confirmation?
No: confirmation is needed where the action is sensitive — its consequence is explained before the confirmation.
Can the agent send an email by itself?
No. The mail assistant sends nothing on its own: the final text and the recipients are confirmed by a human.
Can a disputed decision proceed automatically?
No. The process stops and waits for human confirmation.
Who sets the control points?
They are fixed before integration together with the permissions and are reflected in the passport.
What if a human does not check the result?
The responsibility for acceptance stays on the side of the process; the agent does not make decisions for the employee.
How is control connected to the price?
Human control is part of every launch: no stage passes silently, regardless of the engagement model.