People responsible for informed decisions
- AI product owners and Builders
- Governance, security, privacy, and assurance practitioners
- Operators responsible for AI incidents and change
- Reviewers responsible for release and lifecycle evidence
Practise an evidence-driven AI lifecycle from use-case impact through evaluation, provenance, agent authorization, incidents, recourse, revalidation, readiness, and retirement.
Individual developers can begin in a free, non-production Developer workspace. Team assignments, teaching, and governance features depend on plan and role.
The Lab combines method, guided practice, evidence, assessment, reflection, and an applicable output.
Define purpose, mode, affected groups, consequences, ownership, risk, prohibited uses, and stop conditions.
Design data, policy, evaluation, threat, AI-BOM, SBOM, provenance, and agent-authorization records for exact versions.
Connect incidents, complaints, appeals, material and supplier change, rollback, emergency stop, revalidation, and retirement.
Preserve blockers, adverse evidence, limitations, remediation, monitoring, recourse, and recovery without claiming certification.
Each stage strengthens the evidence and preserves the distinction between learning and operational authority.
Review the full evidence-driven lifecycle and its decision boundaries.
Apply the method to one of four synthetic application patterns.
Test adverse cases, missing authority, stale evidence, protected mutation, and recovery.
Identify the evidence that most changed the lifecycle decision.
Prepare a Trustworthy AI SDLC evidence and readiness pack for authorized review.
A versioned evidence pack covering intent, impact, data, engineering policy, evaluation, threats, AI-BOM, SBOM, provenance, agent authority, incidents, recourse, revalidation, transparency, scorecards, readiness, and lifecycle decisions.
Feedback and reflection support retry and mastery; they do not replace destination review or approval.
A completed Lab demonstrates learning evidence. It does not grant production authority, certify compliance, accept risk, or bypass human decisions.
The Lab performs no provider call, production read, external write, deployment, or monitoring action.
Synthetic fixtures do not prove factual correctness, security, compliance, certification, or production readiness.
Any application requires current evidence and named accountable approval in the owning product workflow.
My Batoi manages authentication and workspace selection before you enter the workspace-scoped Learn capability.