Controlled Mindtickle Adapter Deployment

Overview

Promote a verified adapter without assuming a deployment platform, then prove tenant binding, safe behavior, and rollback from production evidence.

Prerequisites

• An immutable build, passing CI receipt, contract digest, and dependency inventory
• Environment owners, secret references, tenant mapping, observability, and on-call coverage
• A canary workload, success thresholds, abort criteria, and tested rollback

Tool Discipline

Use Read, Glob, and Grep to inspect manifests and receipts, WebFetch for current authorized contracts, and Write or Edit for deployment configuration, runbooks, and redacted evidence.

Current Contract

Deployment architecture is customer-controlled. The adapter must use the exact tenant API or managed-connector contract already approved; health checks must prove local readiness separately from optional external dependency readiness.