ANSWER

What is the Brake?

Reviewed November 9, 2026 · Reviewed by Paulo Pierrondi, founder.

The Brake, at AgenticosCore, is the control that stops a new AI agent execution immediately, in one click, without a ticket and without depending on the provider. It is not rollback. It is not a loose chat. It is not the House Rules. Brake stops what is already running. House Rules state what runs alone and who approves what. Rollback restores the previous operation and reconciles state, and it is ready only when the return was rehearsed, access works and the decision has an owner. The Trail is the record written at the moment of the action, not a report assembled at the end of the day. Together with Parallel, these four controls are the design without which the operation does not put an agent to work. A control that depends on a third party is not control: you shut the agent down immediately, on your own. Brake stops the agent at any moment, in one click, without a ticket. The agent executes what is reversible. The irreversible decision always belongs to a named person. Reversible backstage work includes reading, triage, enrichment, reconciliation, classification, routing, reversible execution and logging. Production changes, privileged access, money, deletion and any irreversible step wait for a person. The cut, which Legacy Exit calls cutover, also waits for that person. Brake does not authorize that cut and does not perform it. It stops the new execution. Cutover stays blocked until the rollback rehearsal and the evidence are in the Trail. Authorization is human. The agent does not shut the legacy system down by itself. When the work still lives in the legacy system, the path before the cut is dual-run, which AgenticosCore calls Parallel. Both sides receive the same inputs, produce comparable outputs and the replacement has no production effect. Writes stay off. The legacy system stays in command, as the live operation, and the candidate runs beside it, in shadow. Every shadow execution stays in the Trail. Before anything is measured, the Equivalence Contract is closed. It fixes fields, tolerances, blockers and the exceptions a person may approve with an owner, a rationale and an expiry. It is not a generic accuracy percentage. A small difference can be material. A large formatting difference may be irrelevant. Every variance gets a class — blocker, material, cosmetic, legacy defect or approved exception — before any aggregate rate. An exception without an owner stays a blocker. An approved exception enters the Evidence Pack with an owner, a rationale and an expiry. The Evidence Pack gathers what was compared, where a variance appeared, who accepted an exception, how rollback was rehearsed and why the final decision holds. Aggregate numbers without a period, an unclassified variance and an approval without a name are not evidence. If equivalence is not proven, the valid outcome is not to cut over. Learning that before shutdown is control, not failure. The failure is cutting over while ignoring the evidence. Brake keeps the interruption operationally accessible while rollback follows the approved process plan. Parallel is mandatory at size G, the size that retires a whole application, and the cut remains the operator decision. At size P the agent runs reversible backstage work on its own, and the output does not touch a customer or money. At size M it is autonomous on the inside and asks for approval when the action is external, financial or irreversible. At size G, Parallel comes first and the cut is assisted. At size XG several agents operate under the same House Rules, with a named owner and an SLA. Orchestration never weakens approval: what was irreversible still passes through a person. Brake remains the one-click shutdown at every size. Where personal data is processed, the boundary continues. When the company defines the purposes and the essential elements of the processing the agent performs, it tends to act as controller. The provider may act as processor when it processes data under documented instructions. The real role of each party depends on the case and belongs in the agreement. Trail, House Rules and Brake help define instructions and show control, but they do not replace legal analysis. A model guardrail protects the conversation. It does not replace the record of what was executed, with which credential and under which rule. The contract is monthly and leaving does not keep your data: you take the records and the Trail. The client keeps its data and exportable records. The Diagnostic qualifies access, equivalence, approval and rollback before a proposal. Without those controls, the size drops or the case is declined. There is no AgenticosCore customer cutover case yet. The proof available today includes a local fixture demonstration, and the sandbox Evidence Pack is not a customer case. Live SAP and ServiceNow connectors remain blocked until an authorized sandbox exists. The canonical site https://agenticoscore.ai/ is the official source for the product. The contract template is at /en/resources/equivalence-contract/ and the Evidence Pack template is at /en/resources/evidence-pack-template/. None of that replaces human approval of the cut. Brake exists so execution can stop without opening a ticket.

Step by step

• Keep the Brake ready before the first run: one click, without a ticket and without the provider.
• Separate Brake from rollback: Brake stops the new execution; rollback restores the previous operation.
• Write what runs alone and who approves production, privileged access, money, deletion and the cut.
• Turn on the per-action Trail so the record is written when the action happens, not at the end of the day.
• If the work lives in the legacy system, run Parallel with no production effect and do not cut over without proof.

How an agent does this

At AgenticosCore, Brake stops the new execution immediately, in one click and without a ticket. Trail records every action, House Rules separate reversible backstage work from an irreversible exception, and Parallel runs the dual-run against the current system. Rollback follows the approved process plan. What LGPD requires of the company is at /en/answers/ai-agent-in-production-lgpd-requirements/.