18.9 Evidence Acceptance Criteria

Go To Top

Return to Acceptance Criteria

Evidence satisfies Phase 0 acceptance when it allows a reviewer to understand what the team ran, what the system reported, what passed, what failed, and what remains unresolved.

The evidence package should:

1. Reside in the approved Evidence location.
2. Identify the baseline, run, date, environment, and relevant checklist instance.
3. Support the specific acceptance criteria claimed for the repository, environment, type generation, Nodes, Control Plane, Data Plane, containers, documentation, and completion decision.
4. Identify failures, warnings, exceptions, deviations, approved exceptions, and open risks.
5. Include enough logs, command output, test results, captured messages, manifests, reports, or reviewer notes to support independent review.
6. Remain reproducible or traceable to the scripts, commands, tools, configuration, generated Artifacts, and repository state that produced it.
7. Exclude secrets, credentials, private keys, tokens, passwords, and sensitive local values.

The team should avoid treating evidence collection as a separate paperwork exercise. Evidence should result naturally from prerequisite checks, type generation, builds, Node execution, Control Plane observation, Data Plane validation where applicable, container execution, tests, and reviews. The evidence package should help the team explain the Phase 0 baseline without requiring a reviewer to rerun every step immediately.