What Is in the Deployment Completion Package — And Why Your Compliance Officer Needs It | Insights

When Private AI Ltd revokes its own access to your sovereign AI environment, the deployment is not finished. The handover is. What follows revocation is the delivery of a complete compliance and operational documentation package that your Compliance Officer can file, your IT Director can reference, and your Managing Partner can present to the Law Society of Scotland, the ICO, or any client conducting due diligence on your firm’s data governance.

This is the Deployment Completion Package. Most infrastructure vendors deliver a login and an invoice. We deliver the evidence that your deployment satisfies every regulatory obligation a regulated professional services firm faces when processing client data through AI.

For the full Zero-Touch Provisioning and credential revocation lifecycle, read our parent article. This piece breaks down every artefact in the Package, explains why it exists, and maps it to the specific regulatory requirement it satisfies.

Artefact 1: The Dependency Manifest (SBOM Equivalent)

What it is: A complete listing of every package installed within the application runtime — package name, exact version number, one line per dependency. This is the Software Bill of Materials (SBOM) for the firm’s AI application layer.

Why it exists: The SBOM is the baseline against which Private AI Ltd performs offline CVE monitoring. When a vulnerability is disclosed in any package within the manifest, Private AI Ltd identifies the exposure, prepares a cryptographically verified upgrade script, and delivers it for the firm’s IT lead to execute during a guided Over-the-Shoulder session. The monitoring is performed against the offline manifest — Private AI Ltd does not access the client’s server to conduct it.

Which regulatory obligation it satisfies: UK GDPR Article 32 requires “appropriate technical and organisational measures” to ensure security. A documented SBOM with continuous vulnerability monitoring demonstrates proactive security management. Under the DUAA 2025, the ICO can compel production of technical documentation via enhanced information notices — the SBOM is a producible artefact that evidences the firm’s software supply chain governance.

Artefact 2: The Model Manifest

What it is: A listing of every language model loaded on the encrypted persistent storage — model identifiers, versions, format, and file sizes.

Why it exists: The manifest confirms which models the firm is running and verifies that no unauthorised models were installed during deployment. It also documents that all models are open-weight — the firm owns the model weights outright, no API call leaves the server, and no vendor can revoke access to the model.

Which regulatory obligation it satisfies: The Law Society of Scotland’s Guide to Generative AI requires solicitors to understand the AI systems they use. The model manifest documents what is running, its provenance, and its operational characteristics. It also evidences that the models are static — client inputs do not modify model weights or contribute to any training corpus, satisfying a key data protection concern.

Artefact 3: Pre-Filled Infrastructure DPA Template

What it is: A domestic Article 28 UK GDPR Data Processing Agreement covering the infrastructure provider’s role as provider of bare-metal compute and hypervisor-encrypted block storage.

Why it exists: The infrastructure provider acts as a Direct Data Processor to the client for infrastructure provision. The DPA governs the provider’s obligations regarding the physical hardware and storage that hosts the firm’s AI environment and all client data.

Why no international transfer mechanism is required: The infrastructure provider is a UK-registered, UK-owned company with no US corporate parent. Its infrastructure is located exclusively within United Kingdom data centres. The DPA is a domestic agreement under UK GDPR. No Standard Contractual Clauses, no adequacy assessment, no UK Addendum — because no international transfer arises. This is the simplest possible processor relationship under UK data protection law.

What it is: A visual and tabular mapping of every data processing relationship in the firm’s sovereign AI architecture, structured for inclusion in the firm’s Article 30 Records of Processing Activities.

The map identifies two entities:

UK bare-metal infrastructure provider — Direct Data Processor. UK entity. Domestic Article 28 DPA. Provides compute and encrypted storage. No international transfer.
Private AI Ltd — Standing Data Processor under Article 4(8) UK GDPR. Zero Standing Privileges architecture. Zero active access credentials in the Default Operating State post-revocation. Active processing limited to authorised Just-In-Time Support Sessions under the standing DPA.

No third party appears at the access layer. The self-hosted access layer is client-controlled infrastructure — no additional processor, no international transfer mechanism required.

Why it matters: Article 30 requires controllers to maintain records of all processing activities, including the categories of processors. The data flow map is the artefact that populates those records. It is also the document the ICO would request first in any investigation — the map that shows the regulator exactly who processes what, where, and under which legal basis.

Artefact 5: Technical Configuration Letter

What it is: A formal letter from Private AI Ltd confirming its Standing Data Processor status under Article 4(8) UK GDPR, its Zero Standing Privileges architecture, and its zero active access credentials in the Default Operating State post-revocation.

Why it exists: This letter is designed to be produced in response to three specific scenarios: an ICO investigation requesting clarification of processor relationships; a Law Society of Scotland inquiry into the firm’s AI governance; or a client due diligence request where the firm’s own clients ask how their data is protected when AI tools are used on their files.

The letter states, in formal terms, that Private AI Ltd deployed the environment, handed over all credentials, retains no active access credentials in the Default Operating State, and operates under a Zero Standing Privileges architecture. It is signed, dated, and referenced to the firm’s specific deployment.

Artefact 6: Law Society of Scotland Technology Compliance Summary

What it is: A mapping document that takes each requirement identified in the Law Society of Scotland’s Guide to Generative AI and maps it to the specific technical or contractual control within the firm’s sovereign AI deployment that satisfies it.

Key mappings include:

Confidentiality (Rule B1.6): No client data leaves the firm’s contracted server. Egress sealed at the network level — no outbound data path by design.
Contractual terms with AI vendor: No AI vendor exists in the processing chain. Open-weight models run locally.
Security standards: Encrypted storage, self-hosted access with two-factor authentication, default-deny host firewall, encrypted DNS.
Client consent: The firm can accurately inform clients that AI-assisted work is performed within a sovereign, private environment under the firm’s exclusive control.
Human oversight: All AI output is advisory. Professional sign-off by a qualified solicitor remains mandatory.

This is the document that transforms the Law Society’s principles-based guidance into a compliance checklist with verifiable evidence for each item.

The Compliance Officer’s Takeaway

The Deployment Completion Package is not documentation for documentation’s sake. It is a compliance evidence file designed to satisfy every regulator, professional body, and client that your firm’s AI deployment meets the standard the Law Society of Scotland has set, the UK GDPR requires, and the DUAA 2025 will enforce.

Every artefact maps to a specific obligation. Every obligation is satisfied by a verifiable control. Every control is documented before the firm processes a single client file through the AI environment.

Talk to our team to receive a sample compliance documentation set and review the full deployment evidence file.

Private AI Ltd (SC881079)

What Is in the Deployment Completion Package — And Why Your Compliance Officer Needs It