ADR-0061: CSV — Generated Validation Package per Release¶
Status: accepted (realization deferred — post-demo; SBOM P1 (ADR-0062) lands first so the
report's SOUP annex has data)
Date: 2026-07-12
Deciders: Nicolas Burri ("I have read your decision proposals and agree with all of them"),
on the worked concept in csv-validation-package.md.
Relates to: ADR-0007 (validation evidence), ADR-0018 (targets CSV verifies against),
ADR-0049 (templates — the dogfood vehicle), ADR-0060 (rehearsal records as cited evidence),
ADR-0062 (SBOM annex); REQ-UI-004 (e2e as CSV regression evidence).
Regulatory frame: ISO 13485 §4.1.6 — the validation duty sits with the CUSTOMER (proportionate
to risk, before initial use and after changes, records per §4.2.5); the supplier ships a
package that turns that duty into a days-not-months, mostly-review exercise. LQMS itself is
not medical-device software; the package borrows GAMP-5/IQ-OQ-PQ vocabulary because that is
what customers' auditors expect.
Supplier artifact (C-V1a): the traceability generator gains a validation-report mode
(one tool, one identity — D-3) producing, per tagged release, one self-contained document:
system identification (version/SHA/image digest), requirements baseline in force, matrix
snapshot with explicit gaps, CI evidence references per gate, the requirement delta vs the
previous baseline (the change-based-revalidation scoper — the Confluence-killer), SOUP/SBOM
annex + dependency delta (ADR-0062), known limitations, approval stub. Deterministic
(same tag → same report). Home: docs/validation/<tag>/ + attached to the GitHub release;
PDF later via the same pipeline (D-1).
Customer kit: intended-use specification + tool-risk assessment as seeded TEMPLATE
documents in LQMS itself (C-V2a, ADR-0049); IQ = deploy runbook + smoke output + first
backup-rehearsal record (checklist page, no new artifact); PQ protocol formalized from
DEMO.md's beat structure, executable against a seeded validation scope (C-V3a).
First customer is us (D-2): the operating organization instantiates the intended-use + risk templates for its
own use of LQMS — the first real controlled documents authored in the tool (dogfood + the
worked example customers copy).
Norm-text rule (D-5, standing convention): package documents (and all repo docs)
PARAPHRASE licensed standards with clause citations only; /norms stays git-ignored.
Recorded in conventions.md.
Sequencing (D-4): C-V1 first (mostly generator plumbing, demo-able), C-V2 as the first real
controlled documents, C-V3 opportunistic; all post-demo, none blocks current work.
The revalidation story becomes: customer reads the report delta, re-runs the affected PQ
steps, records — self-hosted deployment means the validated state changes only when the
customer upgrades.
Realization detail lives in the planning doc; this ADR pins the decisions so the arc survives
until scheduled.