Dataset Admission Gate

Dataset Admission Gate A workflow diagram generated by Archify. 01 / Data owner and steward 02 / Layer 01 Govern-as-Code 03 / Training or eval job 04 / Layer 02 Inventory & Transparency EX / Read denied Prepare Check + sign Read + record Dataset version · card and snapshot · Data owner and steward › Prepare Dataset version card and snapshot Admission checks · rights, quality, bias · Layer 01 Govern-as-Code › Check + sign Admission checks rights, quality, bias Admission record · signed by the owner · Layer 01 Govern-as-Code › Check + sign · admit / reject Admission record signed by the owner admit / reject Read-time policy · use case admitted? · Layer 01 Govern-as-Code › Read + record Read-time policy use case admitted? Training job · presents use-case id · Training or eval job › Read + record Training job presents use-case id Lineage and evidence · record joined to run · Layer 02 Inventory & Transparency › Read + record Lineage and evidence record joined to run Read denied · no admission for this use · Read denied › Read + record Read denied no admission for this use sign submit request read deny allow and log publish Legend Agent logic Policy Context / trace External system

Admit before training

  • • Rights come first: ledger row, lawful basis, licence, reservation check
  • • Then quality, quantity per group, representativeness and a bias examination
  • • Admit a content-addressed, signed snapshot

Checked at read time

  • • The job presents its use-case id and target system
  • • The policy denies any read the record does not admit
  • • The checklist lives as code, so a missing field fails the run

Evidence by construction

  • • The data owner signs; the steward operates the checks
  • • Lineage joins each admission record to the runs that read it