verification

Verification procedure

Status: proposed LMA-PROC-003 procedure using existing checks and campaign planners. Owner role: verification owner. Input: candidate revision, affected requirements and configuration scope.

1. Identify the applicable CI controls and SDD acceptance cases.
2. Select the runbook and record expected configurations before execution.
3. Prepare its declared tools and a fresh attempt directory. Retain the source identity and tool versions.
4. Execute the campaign and retain failed, missing and unavailable results alongside successful cases.
5. Reconcile returned evidence with the plan using that campaign's reporter. Review remaining findings and the evidence contract before accepting the stated scope.

Acceptance: applicable required results cover the selected revision and configurations; reviewers record permitted dispositions for unresolved findings. A missing result cannot count as a successful check. Current qualification covers the mock contract. The process pilot covers parser, documentation, compilation and automation-regression controls.

Records: plan, command logs, configuration identity, artifact hashes, report and review decision. Keep working logs under .cache/; retain accepted records under the campaign's artifact policy.