Solution 02
Make legal review a required data-pipeline stage
01 — Root cause addressed
This addresses the need to establish a lawful basis for bulk acquisition before material is copied and retained for future use.
02 — Implementation
Add legal approval as a blocking stage for each bulk external source before ingestion. The review record should identify the acquisition method, proposed uses, retention period, and evidence supporting the lawful basis for each of them. Data engineering should receive an explicit approve, quarantine, or reject result that the pipeline enforces before copies are retained; a model-release checkpoint would occur too late to control acquisition risk.
03 — Prevention
Audit the gate against stored datasets and prevent a job from bypassing review merely because its output is not scheduled for commercial release.
04 — Trade-offs
A blocking review adds cost and queue time, and it becomes a rubber stamp if reviewers lack the authority or expertise to reject a source. It is the wrong choice when implemented as paperwork without substantive legal review, because delay alone does not establish a lawful basis.