WS2: Technical Shutdown (Controlled, Logged, Reversible) The Technical SME coordinates the technical shutdown in a controlled, logged, and reversible sequence until the final cutoff. Inference endpoint deactivation proceeds in stages: lower-priority or lower-risk deployments go offline first to identify unexpected dependencies. Endpoints return informative HTTP 410 responses, not silent failures. Model artefacts are moved from the production registry stage to an archived stage. They are not deleted; they are retained for the ten-year period. Cryptographic signatures are verified one final time to confirm artefact integrity at archival. The Technical SME records the final model version, its hash, and the archival location. All production credentials, API keys, service accounts, and access tokens are revoked. The Technical SME verifies revocation by attempting access with the revoked credentials and confirming failure. Dedicated infrastructure is released. Before monitoring infrastructure shutdown, the Technical SME exports a final snapshot of all monitoring data and archives it alongside the PMM records. Key outputs

• Staged endpoint deactivation with HTTP 410 responses
• Model artefacts archived (not deleted) with integrity verification
• Credential revocation with verification testing
• Final monitoring snapshot before infrastructure release