Note /
What you sign at handover
Every deployment ends with a handover document that you sign. What it records is the honest core of the engagement: the security posture you chose, and where responsibility sits once the agents are yours.
The end of every install
Every deployment ships with a sensible-default hardened security posture, and every deployment ends with a signed handover document. A Solo Install closes with a handover and a training session; a Team Install closes with admin training. The document is the last artefact of the install, and the one that keeps meaning something after it.
What the document records
Two things. First, the security posture you chose: what your agents can reach, and which actions wait for human sign-off. The posture is the substance of what hardened means, and the document is where your chosen version of it is written down and signed rather than assumed. Second, your acknowledgement of the residual risk inherent to agentic systems.
Residual risk, named rather than buried
Hardening reduces risk; it does not abolish it. Agentic systems carry residual risk, and the handover document asks you to acknowledge that plainly, at handover, instead of finding it in small print after an incident. It is the same principle as the published exclusions: knowing the edges is part of what you are buying.
Where responsibility lands afterwards
After handover, you are responsible for how the agents are used. Our obligation is hardening to the agreed posture, plus training and guidance. The published exclusions draw the same line: consequences of prompt injection or social engineering after handover, where the posture was signed off, rest with you. Training is part of every install because that line exists.
What we will never sign
There is one posture no handover document will ever record: a dangerous-equivalent one. A deployment you insist on running that way is refused outright, not priced. The signature means something precisely because there are configurations we refuse to put our name to.