Advanta is currently undergoing final system calibration ahead of launch. Selected infrastructure and experiences may still be in active refinement.

advanta

Framework / AI Lifecycle

AI is not a procurement event.

Concept · Build · Deploy · Operate · Sunset. The five canonical stages of legal AI operating discipline. Each stage applies different governance, exposes different risk classes, and produces different ROAI return.

Authored by

Nishant Bhaskar — Founder + Editor-in-chief, Advanta Legal Tech

Version 2026-Q3-v1 · Binding canon

Executive Summary

The AI Lifecycle is the temporal frame for institutional AI use in legal functions. Every AI capability the function deploys moves through five canonical stages: Concept, Build, Deploy, Operate, Sunset. Each stage applies different governance disciplines, exposes different Risk Taxonomy classes, requires different Defensibility evidence, and produces different ROAI return. The vendor-centric conversation about AI in legal functions treats AI as a procurement event: select a vendor, deploy the tool, capture the productivity. The Lifecycle frame treats AI as an operational discipline that begins before procurement (Concept) and continues through retirement (Sunset). Functions that operate the Lifecycle compound governance posture over years; functions that operate AI as a procurement event repeat the same governance failures on each new tool. The five stages have been stable across multiple iterations of professional AI governance frameworks and are unlikely to require structural revision. The Lifecycle is the longest-lived element of the operating canon.

Why a Lifecycle Frame

The procurement-event model produces governance drift.

Most conversations about AI in legal functions treat AI as a procurement event. The function identifies a need, evaluates vendors, selects one, deploys the tool, and absorbs the result into the workflow. Governance attention concentrates at procurement and dissipates afterward. Twelve months later the tool is in production, the vendor has shipped two model upgrades, the function's risk register entry has not been refreshed, and the original procurement-stage governance has nothing to say about the current operating state.

The Lifecycle frame rejects the procurement-event model. AI capabilities are not procurement events. They are operating disciplines that have stages. Each stage requires distinct attention, distinct evidence, and distinct accountability. The function that recognises the stages and applies the correct governance at each compounds posture over time. The function that treats AI as procurement repeats the same governance failures on every new tool.

The Lifecycle is also the temporal frame that the other anchor essays in this cluster need. Defensibility names the response capability. Risk Taxonomy 2026 names what must be responded to. ROAI names what returns must be measured. None of these is uniform across the life of a capability — the Lifecycle is the structural answer to the question "what governance applies when?"

The Five Stages

Concept → Build → Deploy → Operate → Sunset.

Each stage has operational tasks, a governance cadence, the Risk Taxonomy classes most exposed during it, and the Defensibility elements most active. The five stages have been stable across multiple iterations of professional AI governance frameworks and are unlikely to require structural revision.

Stage 01

Concept

The function identifies a candidate AI use case. Ends with a pursue-or-not decision.

Operational tasks

Define the problem. Specify success criteria in advance, including which ROAI quadrants matter most. Identify which Pillars are touched. Map against the Risk Taxonomy 2026 to surface which classes the use case will introduce. Document the named accountable owner if pursued.

Governance cadence

Concept decisions are made by the governance committee at its regular cadence, not ad hoc. The committee reviews each candidate against a structured intake (problem statement, success criteria, ROAI hypothesis, Risk Taxonomy exposure, proposed owner).

Risk classes most exposed

Hallucination · Shadow AI proliferation · Accountability dilution

Defensibility elements most active

Governance posture · Methodology transparency

Stage 02

Build

The function commits to the use case and builds toward production. Ends with a passing pilot or abandonment.

Operational tasks

Score candidate vendors against the Vendor Index six dimensions. Negotiate contracting (data isolation, residency, exit-assistance, notice SLAs on upgrades). Configure against data handling standards. Design the pilot with cohort-controlled methodology. Build training. Update the Risk Register with new entries mapped to the Taxonomy.

Governance cadence

Vendor selection requires committee approval. Material configuration choices (residency, training opt-out, retention) require committee approval. Contract execution requires standard procurement governance plus AI-specific committee sign-off. Pilot results reviewed before Stage 3 promotion.

Risk classes most exposed

Vendor lock-in · Data leakage · Regulatory non-compliance

Defensibility elements most active

Methodology transparency · Governance posture · Evidence framework

Stage 03

Deploy

Pilot to production. Cutover, training rollout, initial weeks of production. Ends at steady-state.

Operational tasks

Cutover from baseline to AI-assisted workflow. Update operating procedures and training materials. Roll out training to the user population. Operationalise the audit trail (decision traceability producing logs). Monitor for early-stage issues, exceptions, and output quality below pilot baseline.

Governance cadence

Committee receives weekly status during the first month, shifting to monthly once stable. Any material exception in the first month goes to committee directly rather than the operational layer.

Risk classes most exposed

Professional conduct exposure · Shadow AI proliferation · Hallucination

Defensibility elements most active

Decision traceability · Continuous learning · Governance posture

Stage 04

Operate

Steady-state production. The longest stage by duration — most capabilities spend years here.

Operational tasks

Quarterly refresh of Evidence Register entries. Quarterly review of Risk Register entries. Quarterly review of ROAI performance against the original hypothesis. Annual vendor relationship review. Incident logging with root-cause analysis. Model upgrade impact assessment whenever the vendor ships a new version.

Governance cadence

Quarterly committee review of each capability. Annual deep-dive against the original Concept memo. Out-of-cycle review triggered by incident, regulatory development, or material vendor change.

Risk classes most exposed

Model drift · Data leakage · Accountability dilution

Defensibility elements most active

Continuous learning · Evidence framework · Decision traceability · Methodology transparency

Stage 05

Sunset

Structured retirement, not abandonment. Triggered by vendor failure, replacement, obsolescence, or regulatory change.

Operational tasks

Notify the user population. Migrate workflows to successor or pre-AI baseline. Export data in portable format. Archive the Evidence Register (Defensibility evidence retains relevance after retirement). Capture lessons learned. Decommission technical integration. Close the vendor relationship per contract exit terms.

Governance cadence

Sunset decision requires committee approval with a written assessment of why retirement and what successor (if any) takes its place. Post-sunset, committee receives a final ROAI report comparing realised return against the original Concept hypothesis.

Risk classes most exposed

Vendor lock-in · Client confidentiality breach · Accountability dilution

Defensibility elements most active

Lifecycle · Evidence framework · Continuous learning

Operationalisation

Three artefacts make the Lifecycle operational.

The frame becomes operational when it informs the three artefacts the function maintains. Without these, the stages remain a vocabulary without a calendar.

Capability Portfolio

Every AI capability the function operates is registered with its current Lifecycle stage. A function with twelve capabilities in production might have one in Concept, two in Build, one in Deploy, seven in Operate, and one in Sunset at any given time. The Portfolio view surfaces stage-balance — a function with all twelve in Operate and none in Concept is not actively renewing.

Governance Cadence

The committee's calendar reflects the Lifecycle. Concept candidates are reviewed at the standing intake meeting. Build-stage approvals populate the working cycle. Operate-stage capabilities populate the quarterly review cadence. Sunset decisions are scheduled with the same gravity as Concept approvals — both are structural decisions about the function's AI posture.

Defensibility Posture Statement

The Statement lists capabilities by Lifecycle stage. A reader can see at a glance which capabilities are in Operate (the current production surface), which are in Build (the near-term roadmap), and which are in Sunset (the retirement queue — which often signals security or commercial concerns about a vendor).

Editorial status

The canonical AI Lifecycle essay is in authorship.

The five stages above are anchored to canon 2026-Q3-v1 and structurally complete. The long-form essay extends each stage with worked examples and Advanta Module Library references; it ships incrementally.

Subscribe — get the essay when it lands

From frame to calendar

Make the Lifecycle your committee's calendar.

Two paths. Run the diagnostic to map your current capabilities against the five stages and surface gaps in the governance cadence. Or engage the Strategic Retainer for named-advisor partnership across the Lifecycle.