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 filters2 active
11 Modules
DAT-01
Data Governance Architecture
Establishes the foundational data governance policies for legal AI, covering classification, vendor data protection, Shadow AI governance, regulatory compliance, and Agentic Tier data provisions.
Module
3–6 weeks for initial framework; 1–2 weeks for annual review and updates
View →
GOV-03
AI Risk Register
Apply the Risk Taxonomy 2026 to identify, score, and mitigate AI risks across nine canonical classes — the register that makes your governance defensible.
Module
Initial setup 4–6 weeks; 2–4 hours per quarterly review cycle
View →
GOV-05
AI Incident Response Playbook
Detect, classify, escalate, and resolve AI incidents across all nine Risk Taxonomy 2026 classes — the playbook that closes the governance loop.
Module
Per incident; 15 minutes to activate; resolution timeline by severity; PIR within 30 days for Level 1–2
View →
GOV-15
Governance Operating Cadence
Committee calendar mapped to AI Lifecycle stages — Concept intake through Sunset closure — with standing agenda, quorum, and gate evidence requirements.
Module
One-time setup 3 hours; standing committee meetings 60–90 minutes per cadence
View →
MEA-07
ROAI Telemetry
Tracks and visualises ROAI across four value dimensions — operational, financial, client, and strategic — to justify and optimise AI investment in legal departments.
Module
Initial build 12 weeks; then continuous operation with weekly, monthly, and quarterly review cycles
View →
SUS-05
Annual AI Audit Methodology
The canonical annual governance audit instrument for deployed legal AI — validates compliance, bias, and performance across all active AI systems and produces the DPS annual evidence refresh.
Module
6 weeks per annual cycle (1 week planning, 3 weeks assessment, 1 week analysis, 1 week reporting)
View →
SUS-10
Capability Portfolio Architecture
Every AI capability the function operates, classified by Lifecycle stage — the GC's situational awareness at a glance and the portfolio input for the Defensibility Posture Statement.
Module
2 hours first run; 30 minutes quarterly refresh
View →
USE-02
Pilot Program Design
The canonical AI pilot execution instrument that structures three-phase deployments with Risk Taxonomy 2026 monitoring, AI BoM gating, and Phase 3 DPS evidence production feeding STR-08 ROAI tracking.
Module
90–180 days per pilot (2–4 weeks planning; 6–12 weeks implementation; 2–4 weeks evaluation)
View →
USE-06
Continuous Improvement Cycle
Track AI performance, feedback, and continuous improvement cycles systematically — with Risk Taxonomy 2026 risk class metrics dashboard, Agentic Tier ongoing monitoring provisions, and ROAI quadrant performance tracking.
Module
Ongoing: weekly check-ins (30 min), monthly reviews (2–4 hours), quarterly strategic sessions (half-day)
View →
VAL-01
ROAI Matrix Framework
Measure and demonstrate the return on AI investment across four value dimensions — operational, financial, cultural, and strategic — with direct linkage to the DPS Defensibility lens.
Module
Initial setup 2–4 weeks; 1–2 days per quarter for updates and reporting
View →
VEN-05
Vendor Technology Landscape
Maps the legal AI vendor landscape across 19 categories, providing quarterly intelligence, Risk Taxonomy 2026 vendor classification, and Agentic Tier governance for technology stack decisions.
Module
1–2 days per quarterly refresh; 3–5 days for annual full-scope review
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