Verification Precheck
Template Library
Verification Precheck
Identify existing checks, required checks, evidence checks, access-control checks, AI checks, and known verification gaps before implementation.
ES-106
Verification
Precheck
Template purpose
Use this template to identify verification needs before implementation begins.
Project
<Project name>
Document control
| Field |
Value |
| Artifact owner |
<owner> |
| Primary reviewers |
<reviewers> |
| Status |
<draft / in review / accepted / revised> |
| Last updated |
<YYYY-MM-DD> |
| Related Engineering Stage |
ES-106 — Implementation Readiness |
| Project workspace target |
docs/project-workspace/implementation/verification_precheck.md |
Existing checks
| Check |
Command / Method |
Status |
<check> |
<command/method> |
<available / missing / not applicable> |
Required new checks
| Work Item |
Verification Needed |
Type |
Owner |
Status |
<IW-ID> |
<verification> |
<unit / integration / manual / review / security / evidence / AI> |
<owner> |
<planned / open> |
Evidence checks
| Evidence |
Check |
Owner |
<evidence> |
<check> |
<owner> |
Access-control checks
| Rule / Action |
Check |
Owner |
<rule> |
<check> |
<owner> |
AI verification checks
| AI Area |
Check |
Human Review |
<area> |
<check> |
<review> |
Failure and exception checks
| Scenario |
Check |
Owner |
<scenario> |
<check> |
<owner> |
Known verification gaps
| Gap |
Impact |
Action |
<gap> |
<impact> |
<action> |
Review checklist
- [ ] Existing checks are known.
- [ ] Required new checks are identified.
- [ ] Evidence checks are planned.
- [ ] Access-control checks are planned.
- [ ] AI checks are planned or marked not applicable.
- [ ] Failure and exception checks are considered.
- [ ] Verification gaps are visible.
Continue to Implementation Review Plan
Identify existing checks, required checks, evidence checks, access-control checks, AI checks, and known verification gaps before implementation.
Open Implementation Review Plan →