R3 — Integrate compliance evidence generation into the data deposit workflow

Audience: Research institutions (offices of research compliance, research libraries, research IT).

Action: Modify the data deposit workflow so that every dataset produces, at the point of deposit, the verification artifacts required by funder mandates: content-addressed identifiers, cryptographic hashes of all deposited objects, signed attestations of deposit location and access control state, and machine-readable metadata conforming to the forthcoming NIH standardized DMSP format.

Rationale: Compliance evidence generated as a byproduct of the deposit workflow is the only configuration under which compliance checks become answerable by inspection rather than by retrospective investigation. The May 2026 NIH format transition (E-0044) and the Gates Foundation OA.Works monitoring program (E-0045) are both converging on machine-readable verification, and institutions whose deposit workflows do not produce the required artifacts will fail programmatic compliance checks they cannot currently see coming.

This recommendation is the operational expression of the architectural property C-0007 / C-0033 develop. It connects the institution's operational deposit workflow to the verification regime under construction at the funder side. R3 is the operational counterpart of R4 — the institutional half of the funder/institution handshake by which compliance becomes evidentiary rather than self-reported.