Home → Module Library
The operational capability layer of the Legal AI OS.
Modules are the institutional artefacts a legal function runs to advance maturity, produce Defensibility evidence, and operate on canonical ground in front of a regulator or a board. Anchored across the 8 Pillars and 6 Operating Layers. Methodology-versioned. Editorially independent.
PILLAR
AUDIENCE
+ More filters– Fewer filters1 active
24 Modules
ADM-01
Adoption Telemetry
Continuous measurement framework tracking AI training completion, adoption progress, AI BoM coverage, Class 6 governance incidents, and ROAI attribution across Protect, Comply, Grow, and Transform quadrants, producing DPS-grade evidence for the legal AI programme.
Telemetry source
Initial setup 4–8 weeks; continuous monitoring with weekly and monthly reporting cycles
View →
CHG-01
Change Management Architecture
5-step change management framework for human-centred legal AI adoption and cultural transformation
Module
18-week initial rollout; quarterly reinforcement and annual refresh aligned with SUS-05.
View →
CLI-01
Client Disclosure and Consent Guidelines
Client disclosure and informed consent framework for transparent AI use in legal engagements
Module
1–2 hours per new matter; 30 minutes per material AI change
View →
COM-01
Sponsorship Communication Plan
Stakeholder communication framework for legal AI transformation sponsorship and change management
Module
Initial design 1–2 weeks; 2–4 hours per month for ongoing execution and review.
View →
COT-01
Continuous Optimization Cycle
Systematically capture AI performance feedback, map signals to Risk Taxonomy 2026 classes, and execute ROAI-attributed optimization cycles across the legal department's AI portfolio.
Module
Initial setup 2–4 weeks; continuous telemetry; monthly analysis; quarterly planning and review (0.5–1 day per quarter).
View →
DAT-02
Data Inventory & Classification Methodology
Classify every data asset by sensitivity level, assign AI processing permissions by classification, and build the governance record that proves Defensible AI adoption.
Module
Initial build 4–6 weeks; quarterly updates 1–2 days; annual review 3–5 days
View →
DAT-04
Data Minimization Methodology
Apply data minimization across every stage of the AI data lifecycle, govern shadow AI through the canonical Class 6 protocol, and build the evidence record that proves Defensible AI.
Module
Initial rollout 4–6 weeks; continuous monitoring with monthly and quarterly checkpoints
View →
GOV-01
Defensible AI Governance Framework
Establish the governance structure, policy suite, and risk register that make Legal AI defensible to boards and regulators.
Module
2–4 weeks first run; 1 day annual review
View →
GOV-02
AI Use Policy
Define what AI use is permitted, prohibited, and supervised across the legal department — the operational policy that makes AI governance real.
Module
Initial deployment 2–4 weeks; 1 day for annual review
View →
INS-01
AI Liability & Insurance Posture
Assess professional liability exposure, insurance coverage gaps, and vendor indemnification adequacy for AI tools across the Risk Taxonomy 2026 nine-class framework.
Module
1–2 days initial per tool; 2–4 hours per tool at renewal or quarterly review
View →
MAT-01
Maturity Grid
The canonical Year-1 maturity instrument — plots organisational Adoption against AI Sophistication on a 5×4 grid to produce a defensible quarterly position and Maturity Stack-linked progression evidence.
Module
1–2 days for baseline; 0.5 day per quarterly review; 1 day annual strategic refresh
View →
MAT-02
Legal AI Readiness Baseline
The canonical 8-pillar readiness diagnostic that captures baseline maturity across all Legal AI OS transformation dimensions and maps current position to the MAT-01 2D maturity grid.
Module
1–2 days for full baseline; 0.5 day for quarterly review; 1 day for annual re-baseline
View →
Advisory
The full operating system in one Programme.
Programme Design and Strategic Retainer engagements operate the canonical Module sequence end-to-end — Defensibility evidence produced, Maturity progression evidenced quarterly, methodology version pinned. The Module Library is the artefact; the engagement is the operating posture.
View Engagement Models