Downstream Use Register

Downstream Use Register A data-flow diagram generated by Archify. 01 / Producer 02 / Register and grant 03 / Consumers 04 / Signals Use Policy Card · intended, prohibited · 01 / Producer · Layer 01 Use Policy Card intended, prohibited Layer 01 Producing system · stamped outputs · 01 / Producer · Layer 02 Producing system stamped outputs Layer 02 Use register · consumer, use, test · 02 / Register and grant · Layer 02 Use register consumer, use, test Layer 02 Consuming system · registered use · 03 / Consumers Consuming system registered use Partner · under contract · 03 / Consumers Partner under contract Training pipeline · loop check · 03 / Consumers Training pipeline loop check Off-purpose monitor · vs negative space · 04 / Signals · Layer 04 Off-purpose monitor vs negative space Layer 04 rules outputs access grant check usage reuse Legend primary data policy / PII async batch data store data flow

Decide secondary use

  • • Intended and prohibited uses are rules on a Policy Card
  • • A premortem and abuse cases feed the prohibited list before go-live
  • • A new use is a new approval with its own re-test

Know every consumer

  • • Systems, teams, partners and training pipelines are registered against the producer
  • • Only a registered consumer gets a credential to the outputs
  • • Outputs carry producer, version, intended use and a caveat

Watch and fan out

  • • Off-purpose use and outputs returning as training data raise alerts
  • • A change, incident or retirement notifies every registered consumer