# V2 Third-Party DRM Integration API

V2 third-party DRM integration API defines Denuvo and custom provider adapters
as a pluggable module contract. The API interface is `IV2ThirdPartyDrmProvider`,
and every adapter must keep provider SDK secrets out of the repository, load SDK
inputs from secure CI secrets, and stay isolated from deterministic simulation.

pluggable module. vendor SDK secrets. deterministic simulation.

## Provider Contract

`V2/ue/Build/DRM/v2-third-party-drm-integration-api.json` defines the
`DenuvoAntiTamper` and `CustomAntiTamperProvider` modules. Both providers expose
the same adapter methods: initialize provider, prepare build, protect binary,
bind license verification, verify runtime integrity, emit tamper telemetry,
strip protection, and shut down provider.

The provider contract depends on executable packing, license verification,
anti-tamper telemetry, game binary signing, DRM impact benchmarking, DRM removal
pathway, and DRM A/B testing manifests. Provider modules must emit release
evidence, support protection removal, support impact benchmarking, support A/B
testing, and preserve binary signing and telemetry handoffs.

## CI Gates

`V2/ue/Tools/plan-v2-third-party-drm-integration-api.py` emits the deterministic
third-party DRM integration API plan.
`V2/ue/Tools/check-v2-third-party-drm-integration-api.py` validates the
manifest, planner output, Denuvo/custom provider coverage, pluggable module
coverage, dependency wiring, secret isolation, Horde wiring, CI workflow wiring,
and this runbook.

Required release gates:

- `drm-third-party-integration-plan-generated`
- `drm-third-party-provider-coverage`
- `drm-third-party-interface-coverage`
- `drm-third-party-pluggable-module-coverage`
- `drm-third-party-secret-isolation`
- `drm-third-party-release-guardrails`