AI & AUTOMATION · READINESS

Find the missing evidence in an AI delivery stack.

Mark each capability Confirmed, Unknown or Gap. The checker preserves uncertainty and produces an accountable review list without scanning infrastructure.

DECISION TOOL / 05

Inputs stay in this browserLogic and sources are visibleDecision support, not approval

LIVE MODEL · PHASE A

Review evidence, domain by domain.

A confirmed item means your team can point to current evidence. Unknown stays unresolved; it is not silently counted as a failure.

Foundation
Business owner and approved outcome
Identity, roles and least privilege
Secrets and service-account boundary
AI delivery
Approved data sources and classification
Model / provider decision record
Evaluation and acceptance criteria
Versioned release and rollback
Operations
Quality, latency, cost and safety telemetry
Incident runbook and accountable escalation
Human fallback and business continuity
Usage budget and cost guardrails

METHOD

Declared readiness should remain explainable.

The checker separates confirmed coverage, unknown evidence and explicit gaps so the next review has a clear owner and question.

01

Foundation

Business ownership, identity, secrets and access boundaries.

02

AI delivery

Data sources, provider decision, evaluation and release controls.

03

Operations

Observability, incident response, rollback, cost and human fallback.

SOURCES AND USE

Where the readiness model comes from.

The checklist combines declared evidence with published lifecycle and architecture guidance. It performs no external discovery.

YOUR EVIDENCE

Confirmed, Unknown or Gap

Your team declares whether current evidence exists. The checker never upgrades a declaration into verification.

USED FOR

Domain status and review list

AWS GENERATIVE AI LENS

Lifecycle and architecture practices

AWS covers operational excellence, security, reliability, performance, cost and responsible AI across the GenAI lifecycle.

USED FOR

Delivery and operations domains

NIST AI RMF

Profile-based gap review

NIST profiles support comparison of current and target risk-management activities and action planning.

USED FOR

Separation of confirmed coverage and unresolved gaps

BOUNDARY

Manual evidence review, not a network scanner.

Phase A makes no DNS, cloud, repository or infrastructure requests. It cannot discover hidden controls or validate the evidence behind a Confirmed answer.

FAQ

Common questions.

A public-domain scan cannot prove application, identity, data or operational controls and adds a security-sensitive lookup surface. Phase A uses accountable declarations instead.

AI & AUTOMATION

Turn a first-pass result into an evidence-backed decision.

Talk to an expert