swvalidationlisted

# /swvalidation — software build → Validation document (.md) **In plain words.** This is the sign-off sheet. One row per thing the software is meant to do, and for each: is it actually in this build, whereabouts in the code, was it tested, and what happened when it was. The "whereabouts in the code" column is what makes this different from an ordinary validation sheet. It holds a file and line number, and a script opens that file to check the line is really there — so "yes, the software does that" stops being something the person filling in the sheet simply asserts. `/validation` validates a product you can only click. This one validates a product you have the source to, and that changes exactly one thing — but it is the important thing. **`Contained in software` stops being an assertion.** For a qmsWrapper module, that column is filled in from the manual: somebody read the docs and wrote YES. For a codebase you can prove it, so every YES carries a citation — `src/auth/session.rs:34-71` — and `build_validation_md.py` opens the file and checks that the lines exist and that any quoted text is really there. A citation that does not resolve is flagged in the table, listed at the foot of the document, and exits the script non-zero. That is the whole difference between validating a product and validating a claim about one. Everything else is inherited from `/validation` and is not restated here: user-voice requirements, literal steps, one-sentence expected behaviour, failures