GLOSSARY
Seven proprietary terms, each with a citable definition and a link to the answer or template where it is applied. If a term changes, this page changes with it.
Legacy Exit is the controlled retirement of a legacy process or application after a replacement proves sufficient equivalence for the agreed use. Instead of a broad rewrite or a big-bang cutover, the work runs in dual-run, classifies variances and only proceeds with human approval, tested rollback and a written evidence pack.
Full answer: what is Legacy ExitA Parallel run keeps the agent in shadow beside the current system: it receives the same inputs and produces the same outputs, with no effect on production. Both outputs are compared for an agreed period, every variance is classified, and cutover only happens when the agreed match criterion is reached.
Full answer: running in parallelAn Equivalence Contract is the written agreement, defined before the dual-run, that establishes which outputs of the legacy system and the replacement will be compared, the acceptable tolerance per field or rule, what blocks cutover, which exceptions may be approved, by whom, and under which rollback conditions.
Editable contract templateAn Evidence Pack is the dossier that supports the decision to retire a legacy system: the measured parallel-run results, every variance classified with an owner and a decision, human approvals with name and date, and the tested rollback plan. If anyone questions the cutover later, the answer is written down.
Full answer: what is an Evidence PackThe Trail is the audit record generated at the moment of each agent action: who executed, what, when, on which data and under which rule. Unlike a report assembled afterwards, it is born at execution time and is the piece you present when audit, a client or an authority asks how the work was done.
Full answer: auditing an agentThe Brake is the immediate interruption of the agent's execution, triggered by the client in one click, with no ticket and no dependency on third parties. Control that depends on another company is not control: the Brake guarantees the operation stops when you decide — before, during or after the Parallel run.
See the Brake in the walkthroughHouse Rules are the executable boundaries of the agent's autonomy: what it may do on its own, what requires approval and who approves what. Written once, they hold on every execution — production changes, privileged access, money and cutover always stop at the human gate defined there.
See House Rules in practice