Evidence Plan
An Evidence Plan states what evidence is required to determine whether the run satisfied intent — what would prove the relevant capabilities were preserved.
Evidence Plans are broader than gates. Some evidence may be machine-checkable; some may require human review. A gate is one way to produce evidence, but an Evidence Plan can also call for observations that no single executable check can confirm.
Example evidence statements
text
Domain payment rules are tested without LiveView.
Vendor SDK imports appear only in payment adapters.
Checkout interaction acceptance checks pass.
Foundry trace shows verification gates passed after execution.
No existing tests were weakened or removed.Each statement describes an outcome that, if observed, helps confirm intent was honoured. Some of these map cleanly onto gates (for example, an import-boundary check); others depend on trace inspection or human judgement.
Related
- Evidence and Gates — evidence types, status lifecycle, and observations
- Gate Overlay — how some evidence is enforced as executable gates
- Formation Brief — Required Sections — where the Evidence Plan sits within a brief
- Runtime Artifact Family — section overview
Source: Integration Architecture §7.4.