K07 · evidence-bundled critical-infrastructure assurance

Model and data provenance gate

Direct answer

Require model, code, prompt-policy, tool, evaluation and data-lineage manifests; gate promotion on signed or checksummed evidence and rollback readiness.

Authority and evidence boundary. K07 publishes knowledge architecture, bounded reference records, procurement structures, local validation tools, signed synthetic fixtures, and point-in-time source review. It does not certify a facility, award a contract, authorize an operation, prove truth, establish deployment, or claim current operation.

Context

Autonomous decisions can be subverted by model substitution, poisoned data, unreviewed updates, or hidden tool changes.

Proposed reference decision

Require model, code, prompt-policy, tool, evaluation and data-lineage manifests; gate promotion on signed or checksummed evidence and rollback readiness.

Alternatives considered

  • vendor name as provenance
  • unversioned model endpoint
  • evaluation without artifact identity

Consequences

  • promotion requires evidence package
  • model drift becomes observable
  • rollback targets are explicit

Defeaters and reversal conditions

  • unknown training/evaluation lineage
  • mutable endpoint without version
  • missing tool-policy manifest
  • no rollback artifact

Source relationships

Use boundary

This record is a proposed reference decision. A competent owner must bind it to actual site constraints, authority, hazards, license conditions, interfaces, implementation evidence, and change control.