Trace the service
Start with a real use case and map inputs, processing, models, tools, data, outputs and human approvals.
GUIDE / PROTOCOL
An AI service is more than its model: continuity also depends on data, interfaces, people and contracts.
Direct answer
Describe the chain that delivers the service, assign an owner to each component and simulate failure or replacement. A risk becomes actionable when its effect, detection time and fallback are explicit.
01 / Review method
Start with a real use case and map inputs, processing, models, tools, data, outputs and human approvals.
Record vendor, exchanged data, contractual jurisdiction, cost, quota, version, substitutability and internal owner.
Simulate outage, price change, answer degradation, API withdrawal or failed export.
Define alert thresholds, degraded mode, backups, export, tested migration and an authorized stop decision.
02 / Evidence to keep
Dated diagram of components, data boundaries and human interventions.
Contracts, versions, quotas, costs and exit conditions verified at audit time.
Export and substitute test results, including quality and cost differences.
Thresholds, owners, manual or alternative mode and acceptable recovery time.
AFTER THE REVIEW
Identify what cannot be exported or replaced. Prepare usable copies, degraded operation and a substitution trial before rating the risk.
Name an owner, alert threshold and fallback action. A map without decision or test does not prove an exit capability.
03 / FAQ
No. Decide from the data, required control, skills, cost and ability to exit.
Failure or change blocks an essential outcome with no acceptable fallback.
Export data and configuration, rebuild a minimum journey elsewhere and measure the gaps.
Business and technical owners should both be able to read, update and act on it.
04 / Official references