H.7.2 Evidence Portfolio

Integration needs an owned portfolio of evidence, not a universal test pyramid or ratio.

• For each class, name the failure it detects, scope it protects, environment, owner, latency, cost, and decision it controls.
• Use local, presubmit, post-submit, scheduled, static, integration, end-to-end, performance, and security evidence for distinct jobs.
• Assign cross-team integration evidence to the integration contract, not only the test file's directory.
• Review duplicated checks, unprotected risk, stale suites, and evidence that runs but controls no decision.
• Treat reliability and attribution as part of evidence value rather than a separate afterthought.