Documentation/Requirements

Requirements

Legal and evidence refresh: 14 November 2026

SDK 0.7.3a4 developer alpha. This supplements the dated source review and requirements matrix, without certifying a preset or turning declared operator settings into verified facts.

Dates and source revisions

The official Commission reproduction of Article 111(4) gives providers of systems placed on the market before 2 August 2026 until 2 December 2026 for Article 50(2). It does not postpone a deployer's applicable deepfake disclosures. The planner already distinguishes these roles and dates.

The final voluntary Code Measure 3.4(c) specifies 2 February 2027 for its detection-interoperability milestone. It is a milestone on the chosen Code route, not statutory approval of a particular SDK. An adequate route may be selected; implementing every provider detector is not required by that measure.

The retrieved official guidelines PDF is C(2026)7702 final, 5 November 2026, not just the original publication date of its landing page. Paragraphs 71–88 discuss marking, detection, feasibility and cost. No numerical frame cadence or 90/95% statutory safe harbor was established in the reviewed texts.

California's chaptered SB1000, effective 30 September 2026, removes the covered-provider monthly-user threshold and the former offer of a manifest disclosure. Latent disclosure, no-cost verification, privacy, feedback and relevant licensing processes remain. This amended provider scope is already in the planner. Other actor duties have separate dates. EU cost language does not override California's latent-disclosure durability wording.

Versioned evidence and remaining work

R4 source CI and review qualify 0.7.3a1 at 52abf6e, not a later revision. The completed adoption emulator pilot used 0.7.2a1: 21 video exports and 96 verification checks including 13 intact controls. Of 83 modified checks, 80 recovered the expected ID. Economy5s missed three tested excerpts/short windows. This is a small scoped corpus, not a population error rate or proof that earlier portrait-crop, letterbox or removal failures are fixed.

Economy5s default, Economy2s and Resilient remain available. Select using actual delivery evidence and compute cost. The candidate's accompanying exact-version qualification records state which checks were run; older speed figures are not relabelled as new candidate measurements.

Supply truthful publisher/system/version/action/time fields; deploy the free verifier/API and registry with an accessible product entry point; maintain privacy, feedback and continuity. Review applicable deepfake UI disclosures and synthetic audio separately. A successful own-registry lookup does not prove full provider-agnostic interoperability. Retain an independent client and external-validator check with their exact scope and versions.

The authenticated TSA route enables a bearer credential on the pinned pair. Offline test PKI is separate from enrollment, real timestamp-signer trust and live operator qualification.

Source-access limits

EU PDFs were retrieved from Commission URLs and relevant articles from its Service Desk. EUR-Lex redirected to its homepage and was not counted as reading the act. Leginfo returned 403: a retained official chaptered SB1000 capture was cross-checked against the chaptered statutory-text republication and the Governor's signing announcement. This is not a fresh download of the entire consolidated BPC. Future platform or device-role implementation needs another official-text check and is outside this provider visual-media qualification.