Model Card as Evidence

Model Card as Evidence A workflow diagram generated by Archify. 01 / Layer 02 Inventory & Transparency 02 / Evidence EX / Rejected Generate from outputs Validate at the gate Cite as evidence Training & eval outputs · scores, datasets · Layer 02 Inventory & Transparency › Generate from outputs Training & eval outputs scores, datasets Model card · generated, structured · Layer 02 Inventory & Transparency › Generate from outputs Model card generated, structured Schema check · valid / invalid · Layer 02 Inventory & Transparency › Validate at the gate Schema check valid / invalid Attached to release · versioned · Layer 02 Inventory & Transparency › Validate at the gate Attached to release versioned Evidence record · read by assurance · Evidence › Cite as evidence Evidence record read by assurance Rejected · not attached · Rejected › Validate at the gate Rejected not attached validate invalid valid generate cite Legend Agent logic Policy Context / trace

Generated from the pipeline

  • • Intended use, eval results, datasets, limitations and owner
  • • Rebuilt on each significant change and versioned with the model
  • • The card an auditor reads is the card production produced

Validated, so it is a control

  • • One schema check decides whether the card is attached
  • • Stored as structured data, both human-readable and machine-consumable
  • • Cited by the evidence record, so transparency doubles as evidence

The distinction

  • • A hand-written card is documentation
  • • A generated, validated card is a control