Part IV / Prove

Verify exact outcomes

Prove separates a producer’s completion claim from independent, current evidence that an exact candidate satisfies an explicit contract.

Question this part answers

How do you know the output is correct, safe, and releasable?

27
Quality and evidence architecture ↗
Build criterion-level proof and evidence lineage.
28
Testing strategy for agentic change ↗
Make deterministic, risk-based checks the hard floor.
29
Evaluation engineering ↗
Compare configurations across representative work and repeated trials.
30
Evals as factory assets ↗
Operate evaluation datasets, scorers, drift controls, and promotion ladders.
31
Quality contracts, proof packages, and certificates ↗
Compile proof for exact decisions and bounded reuse.
32
CI/CD, progressive delivery, and production verification ↗
Carry evidence through build, release, and production.
33
Security: identity, secrets, threats, and supply chain ↗
Keep authorization deterministic and external to the model.

Producers should not be their only verifier.
Evidence must bind to an exact subject.
Passing verification makes work eligible; it does not authorize every consequence.