Verification & Validation (V&V)
Two distinct activities. Verification asks "are we building the system right?" — typically by testing against requirements. Validation asks "are we building the right system?" — typically by testing against user needs in the real environment. Robotics safety standards (ISO 10218, ISO 26262, IEC 61508) require both, with documented evidence.
Why It Matters
V&V is the umbrella under which most robotics safety work sits. The standards prescribe what verification activities must occur (unit test, integration test, system test) and what evidence each must produce. Roboticks targets the verification side primarily; validation often requires real-world deployment that customers run themselves.
How Roboticks Implements It
Test runs against pinned commits, requirement linkage via @confirms, evidence packs that bundle the JUnit + SARIF + ReqIF artifacts a safety assessor expects to see. Validation evidence (real-world deployment data) can be uploaded into evidence packs as auxiliary artifacts but isn't generated by the platform.