Software verification report: filled illustration
ILLUSTRATIVE ONLY. This is a worked example, not an executed run or customer record.
Revision labels and modeled results below are teaching data. No execution log is attached.

Scope and purpose:
  Verify a worker-pool helper that clamps requested workers to 1..20,
  preserving values inside that interval.
Candidate code revision: C2 (illustrative)
Requirement: SYS-REQ-041, R3 (illustrative)
Verification plan: boundary inputs, negative inputs, and a planned restart check.
  Plan revision and restart acceptance condition still need to be supplied.
Environment, dependencies and configuration: not supplied.

Boundary checks
  Test revision: T2 (illustrative)
  Input     Expected     Modeled result
  0         1            1
  1         1            1
  20        20           20
  21        20           20
  Outcome: pass in this illustration.
  Execution: no real command, timestamp or output artifact supplied.
  In a real report, replace modeled results with recorded observations and a log link.

Negative-input check
  Expected: inputs below 1 return 1.
  Actual observation: none supplied.
  Execution: not established in this illustration.
  Outcome: unknown. Obtain the run result or execute the check.

Restart check
  Expected: recover the acceptance condition from the approved plan first.
  Actual observation: none.
  Outcome: not run. The planned obligation remains open.

Uncovered cases and unresolved findings:
  Negative inputs and restart behavior remain open.
  The modeled boundary pass does not close either gap.
Freshness basis:
  A real report must bind results to code, requirement and environment revisions.
  This illustration supplies no execution basis to reuse.
Exceptions: none authorized here.
Acceptance decision: pending; evidence incomplete for the declared plan.
Responsible authority and date: not supplied.
Next action: assign an owner to each gap, complete relevant checks and record the decision.
Reverification: reconsider affected checks when their code, requirements or configuration change.

Actual executed artifacts and their limits:
https://reqproof.com/topics/software-verification-report#executed-package
Blank template and guide:
https://reqproof.com/topics/software-verification-report