Every deployment comes with an evidence pack, not a black box.
Most consultancies describe ownership in a sentence and leave you to find the exceptions later. This page is the list, in full, before you engage — what the system can reach, what it can do, who has to approve it, what it records, and what transfers to you at the end.
Five questions, answered in writing
The pack is a set of documents, not a policy. Every line below is something that either exists for your engagement or does not, and can be asked for by name.
- What the system can accessAn access map: every system and data source each agent can reach, written down before it runs, with credentials scoped to that map rather than to whatever an account happened to already have. Where an integration is read-only, that is recorded as read-only.
- What it can doThe scope of each agent as a written definition: this task, these inputs, this output, these boundaries. Not a general assistant with broad access and a hope that nobody asks it the wrong question — a named job, in the same words the person who approves it would use.
- Where a human has to approveThe approval point for each agent, by name and by step: who signs off, at what moment, and what the process does if nobody does. An agent drafts; a person sends. The control is only a control if somebody can see where it sits.
- What gets loggedA record of what ran, when, and on whose authority, in a format you can read without us. This is what turns 'how do you know it did that' from a conversation into a file — and it is the part an adviser, a lender or an auditor asks for first.
- What you own when we leaveThe repository, a structured export of your own data, the documentation, and the credentials to run all of it without us. Itemised in the six lines below, and yours whether or not you keep working with us.
The pack is produced by the work rather than written up afterwards. It is also what we would want to be shown if we were the ones being asked to trust a system somebody else built.
The six things that transfer to you
Each line is a concrete artefact handed over, not an assurance. If it cannot be handed over, it is not on this list.
- Source and repository accessThe repository containing every line of what was built, under your organisation's ownership, with full commit history rather than a zipped snapshot.
- Data export rightsA complete, structured export of your own data on request, in an open format, at any point during or after the engagement. No retention period and no exit fee.
- DocumentationWritten architecture notes, the data model, deployment and recovery steps, and the reasoning behind the decisions that would otherwise only exist in our heads.
- Credential handoffEvery account, key and hosting credential transferred into your control, with our access revoked on a date you set rather than one we choose.
- Dependency transparencyA full list of the third-party services and libraries the system depends on, what each one costs, and what it would take to replace any of them.
- Maintenance rightsThe contractual right to maintain, extend or hand the system to another supplier, without permission from us and without a licence that expires.
If any item on this list cannot be delivered for a specific engagement, that exception is written into the proposal before you sign, not discovered at handover.
A clear line between what you own and what you can choose to buy
Everything above is yours whether or not you continue working with us. Ongoing support afterwards is a separate, optional service: keeping the systems running as they change, and adding agents to the business as more of the work becomes worth handing over. It is not access to what was built. You could walk away the day after handover and keep everything that was built for you, in full working order.
| Item | You own / control | Ongoing support covers |
|---|---|---|
| Data, source systems, credentials | You own / controlYou own or control the primary accounts; we receive least-privilege access | Ongoing support coversCredential rotation, connection checks, access reviews |
| Workflows, specs, documentation | You own / controlExportable workflows, runbooks, architecture notes, test results | Ongoing support coversChange requests, optimisation, documentation updates |
| Code and configuration | You own / controlTransfer/licence terms stated explicitly before work starts | Ongoing support coversBug fixes, API/model adaptation, version maintenance |
| Operational performance | You own / controlBaseline metrics and an outstanding-risk register | Ongoing support coversMonthly monitoring, improvement review |