What “Ready to Ship” Means for a High-Risk Build

Path Outline

Progress0%

1Identify Provider and Deployer Responsibilities 2Determine Your Role Using the Key Definitions 3Know the Difference: Placing on the Market vs Putting Into Service 4Case Study: Write a Defensible Role Memo 5Make the Call: Determine Your Role and Next Steps

6Tier Before You Buy to Avoid Owning the Wrong Duties 7Classification Anchors and Annex III as a Tiering Tree 8Minimum Provider Inputs That Make Tiering Defensible 9Case Study on Tiering and Oversight for Hiring AI 10Name the Oversight Owner and Put Stop-Powers in Writing

11What “Ready to Ship” Means for a High-Risk Build

12Article 9 Risk Management as a Living File 13Article 10 Data Decisions You Must Be Able to Defend 14Article 15 Claims That Survive Foreseeable Misuse 15Case Study: Evidence Pack for the Hiring System

16What You Ship Is What Others Can Govern 17Article 16 Provider Deliverables as a Release Spine 18Annex IV Skeleton That a Deployer Can Audit 19Logs a Deployer Can Actually Investigate 20Case Study Provider Release Bundle for Hiring

21Turn Provider Instructions Into Daily Operating Controls 22Deployer High-Risk Duties as an Operating Procedure 23Make Human Oversight an Intervention, Not a Job Title 24Hiring System Case Study First-Month Monitoring Review

25Stop Accidental Role Switching Before You Change Anything 26Modification Triage That Keeps Deployer and Provider Straight 27Article 73 Serious-Incident Reporting Readiness 28Hiring System Case Study on Role Switch and Incident Prep

Hide outline

Home
Paths
EU AI Act: Provider vs Deployer Duties
What “Ready to Ship” Means for a High-Risk Build