Skip to content
LQMS
Requirements Traceability Matrix
Initializing search
nburri/lqms
LQMS
nburri/lqms
Home
Evaluate LQMS
Evaluate LQMS
LQMS Known Limits
LQMS Security Posture
Architecture
Architecture
1. Introduction and Goals
2. Architecture Constraints
3. Context and Scope
4. Solution Strategy
5. Building Block View
6. Runtime View
7. Deployment View
8. Crosscutting Concepts
9. Architecture Decisions
10. Quality Requirements
11. Risks and Technical Debt
12. Glossary
The arrival bundle format
Decisions (ADRs)
Decisions (ADRs)
ADR-0001: Content-Addressed Document Storage with PostgreSQL as Source of Truth
ADR-0002: Single Instance with Scope Hierarchy and Copy-on-Derive
ADR-0003: Fixed Life Cycle States with Configurable Review Processes
ADR-0004: Global Catalogs for Roles and Document Types with Per-Scope Activation
ADR-0005: Modular Monolith
ADR-0006: Three-Layer Search with In-Database Index and Pluggable LLM
ADR-0007: Angular Frontend with Server-Side-Only Enforcement
ADR-0008: Flyway Migrations and jOOQ Codegen from the Migrated Schema
ADR-0009: RLS Enforcement via a Session-Scoped Authorized Scope Set
ADR-0010: Self-Managed QMS via an Internal Mandator
ADR-0011: Authentication via OIDC SSO with Server-Side (BFF) Sessions
ADR-0012: Permission-Based Authorization and System Bootstrap
ADR-0013: User Identity Lifecycle
ADR-0014: Electronic Signatures (Part 11 / Annex 11-Capable)
ADR-0015: Document Effectivity, Periodic Review & Validity
ADR-0016: Data Retention, Disposal & Privacy (FADP / GDPR)
ADR-0017: Multi-Part Version Content
ADR-0018: Non-Functional Targets (Capacity, Availability, Security)
ADR-0019: Notifications & Tasks
ADR-0020: Internationalization (Content Language, Time Zones, Formatting)
ADR-0021: General Typed Document Relationships
ADR-0022: Read-Acknowledgement & Questionnaires
ADR-0023: Migration / Import — Current Released State
ADR-0024: Draft / In-Review Cancellation
ADR-0025: Disposal & Erasure Mechanics (Storage, Index, Backups)
ADR-0026: RLS Runtime Safety — Connection-Pool Scope Isolation
ADR-0027: RLS Boundary — Content-Plane vs Control-Plane
ADR-0028: Stateless Encrypted Token-State Cookie (no server-side session store)
ADR-0029: Document Content Model — Draft-Freeze, Content-Table RLS, Append-Only Audit
ADR-0030: Review & Life-Cycle Realization Model
ADR-0031: Released-base readability enforcement & copy-on-derive mechanics
ADR-0032: Frontend realization — Quinoa, Angular Material, i18n & E2E
ADR-0033: CSRF control for the BFF session — SameSite + JSON content-type
ADR-0034: Notification realization — in-process domain events + system-context fan-out
ADR-0035: Fan-out contract as shipped — gate semantics, count disclosure, audit protocol
ADR-0036: Repository layer — services carry rules, repositories carry jOOQ
ADR-0037: Task scheduler — in-process tick, advisory-lock election, SQL sweep
ADR-0038: Periodic-review realization — derived due date, policy-gated confirmation
ADR-0039: Sweep & periodic-review contract as shipped — grants, guards, addressing
ADR-0040: Disposal-due surfacing — closure-anchored retention, scope-level legal hold
ADR-0041: Email channel & notification i18n — notification-as-outbox, structured messages
ADR-0042: Disposal execution — document tombstoning, single-actor hard-gated destruction
ADR-0043: Disposal blob deletion is post-commit, GC-backstopped
ADR-0044: Search FTS baseline — event-indexed, RLS-scoped search_index
ADR-0045: Image Attachments as Content Parts (Rich-Content Slice R2)
ADR-0046: Four-Eyes — Submitter Excluded from Approval
ADR-0047: Four-Eyes — Submitter-Only Exclusion
ADR-0048: Document Organization — Folder Tree per Scope
ADR-0049: Content Model Round 2 — Type Categories, Template Instantiation, Trace Relations, Completeness Rules
ADR-0050: Live Frontend — SSE State Push, CodeMirror 6, Draft Presence
ADR-0051: In-Text Document Links (doc: Scheme)
ADR-0052: Addressees & Read-Acknowledgement (REQ-TRN Realization)
ADR-0053: Addressees Per Document + Process Owner (amends ADR-0052 K-1)
ADR-0054: Process Owner Is a Role (amends ADR-0053 P-3)
ADR-0055: WYSIWYG Editing Mode over Markdown (editor step R4)
ADR-0056: Visual-Editor Chrome via Milkdown Crepe (gated adoption)
ADR-0057: Content Record Is the ProseMirror Document Tree; Markdown Becomes a Derived Projection
ADR-0058: PM_DOC Is the Only Content Format (pre-production cut; amends ADR-0057 §5)
ADR-0059: Editor Engine Switches to TipTap (spike-gated; supersedes the Milkdown/Crepe choice)
ADR-0060: Backup & Restore — Scripted Ordered Backup with Automated Restore Rehearsal
ADR-0061: CSV — Generated Validation Package per Release
ADR-0062: SBOM — CycloneDX over the Production Layers, Validated Against the Artifact
ADR-0063: User Identity Binds on Subject Only (Issuer Becomes Provenance)
ADR-0064: Per-Document Workflow Role Bindings (Author / Reviewer / Releaser), Enforced
ADR-0065: Diagrams — Excalidraw as the Manual Layer, Mermaid Stays for Text-First/UML
ADR-0066: WITHDRAW — the Author Side May Reclaim a Version from Review
ADR-0067: Review Comments — Anchored, Immutable, Resolvable
ADR-0068: Confluence/Jira QMS Import — Staged, Read-Only, Repeatable
ADR-0069: Arbitrary File Attachments — Download-Only Confinement
ADR-0070: Training Questionnaires — Versioned, Auto-Scored, Release-Gated
ADR-0071: Training Plans — Document Obligations + External Trainings & Certifications
ADR-0072: Diagrams — Self-Hosted draw.io Replaces Excalidraw
ADR-0073: Per-Scope QMS Configuration Surface
ADR-0074: PDF Export of Released Documents — Server-Side via Apache FOP over the Canonical Projection
ADR-0075: Source History Import — Continuity Without Forged Audit
ADR-0076: Periodic-review status visibility (completing MVP gap #2)
ADR-0077: Requirement Items — Keyed Blocks Inside Controlled Documents
ADR-0078: Generalized Trace Items (Traceability Model — Stage A)
ADR-0079: Risk & Risk-Control Items (Traceability Model — Stage B)
ADR-0080: Traceability Workspace — Hub, Sub-Pages, and Role-Gated Views
ADR-0081: Draft-Only Trace-Structure Changes, Server-Enforced
ADR-0082: Table-Shaped Risk Authoring over Risk Blocks
ADR-0083: The TD Dossier — a Versioned, Cross-Scope, Regulatory-Structured Deliverable
ADR-0084: Validation & Regulatory Axes (Traceability Model — Stage C)
ADR-0085: Relation-Layer Consolidation — One Trace Vocabulary, One Surface
ADR-0086: Requirement Traceability Chains — End-to-End Path View + Flat Path Export
ADR-0087: The Scope Traceability Report — One Derived Overview Artifact, Never a Controlled Document
ADR-0088: Verification Evidence Classes — Planned vs. Verified, Derived at the Read Layer
ADR-0089: Recurring Obligations — Periodic Tasks With Record Evidence, Not Calendar Series
ADR-0090: Release & Versioning Policy — Deliberate Releases, One Auditor-Facing Number
ADR-0091: Release Modes — Single-Person Record Release With a Structural Four-Eyes Floor
ADR-0092: Orphan-Blob Garbage Collection With a Quarantine Bin
ADR-0093: One Scope Context — the Toolbar Switcher Is the Only Scope Selector
ADR-0094: Calendar-Anchored Obligation Schedules (Clamped, Never Too Late)
ADR-0095: Key-Rule Governance — Free Until First Use, Then Frozen
ADR-0096: Transition Permissions — Always Visible, Deny Unless Granted
ADR-0097: A Governed Provisioning Surface — MANAGE_SCOPES
ADR-0098: Org Chart × Role System — Marriage at the Evidence Level, Never in Authorization
ADR-0099: The User Manual is an In-App Topic Reference, Not a Document
ADR-0100: LQMS Is the Living Quality Management System
ADR-0101: The Executable Validation Journey (PQ Evidence That Cannot Drift)
ADR-0102: Typed Template Variables (text | date | number — and Deliberately No Enum)
ADR-0103: npm audit Joins the Verification Gate as a Second Standing Input
ADR-0104: The Issued Dossier Is a Persisted Artifact of Record — and Clones to a New Draft
ADR-0105: Navigation Information Architecture — Group by Moment-of-Use
ADR-0106: The Client Reflection Follows Assignments, Not Only Content Reach
ADR-0107: The Audit Append Gate Follows Assignment Reach, Not Content Reach
ADR-0108: Mandator Membership — Invite-Accept, with Pre-Assigned Responsibilities
ADR-0109: Organization Founding Is Its Own Process
ADR-0110: The Audit Trail Is Not a Read Model
ADR-0111: The Imported-Person Model, and Project Portability's First Doctrines
ADR-0112: The Element-Kind Catalog — Semantics in the Model, Not Only in the Code
ADR-0113: Project Arrival Import — Records Arrive as They Are, People Arrive as They Were
ADR-0114: The Operating Model Arrives — Roles as Functions, Names as Words, People as This Instance's Decision
ADR-0115: Collaborative Draft Editing — Two Carets, One Truth, Honest Credit
ADR-0116: The System Maintenance Surface — the App Backs Itself Up, the Host Keeps One Dumb Job
ADR-0117: Role Documentation — a Link, a Finding, Per-Source Recognizers; Substitution Rejected
ADR-0118: The Offline QMS Copy — the Repo Carries the Audit Pack, Not a Second Renderer
ADR-0119: Module-Internal Package Structure — Capabilities First, Layers Second, the Root Is the Surface
ADR-0120: The Shared Kernel — the Domain-Exception Vocabulary Leaves the Authorization Module
ADR-0121: The Project Administrator Role — Per-Scope Administration With Read Access, Seeded in the Base Catalog
ADR-0122: Organization-Level Administration — the Cascade Stays, Becomes Visible, and Founds Projects
ADR-0123: Draft Save-Points — Every Save Restorable, Kept for the Life of the Version
ADR-0124: The Birth Path Completes Without Borrowing Content Clothes
ADR-0125: The Export Twin — Export Emits an Arrival Bundle
ADR-0126: Project Dissolution — the Un-Birth of an Unused Scope
ADR-0127: The Base-QMS Layers — One Library, Derived Adaptations, Local Records
ADR-0128: The GLOBAL Cascade Carries Administration, Never Content
ADR-0129: Role Identity from a GLOBAL Assignment Acts in GLOBAL Alone
ADR-0130: Break-Glass — the Project Administrator's Escalation Is a First-Class, Witnessed, Self-Expiring Act
ADR-0131: Role Substitution as Declared Adoption Edges — Emergency Cover Is Governed, Own-Name, Timed Staffing
ADR-0132: Dual-Hat Reviewer Satisfaction Is a Declared Policy Choice — the Strict Floor Stays the Default
ADR-NNNN:
</span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_5" > <div class="md-nav__link md-nav__container"> <a href="../../requirements/" class="md-nav__link "> <span class="md-ellipsis"> Requirements </span> </a> <label class="md-nav__link " for="__nav_5" id="__nav_5_label" tabindex="0"> <span class="md-nav__icon md-icon"></span> </label> </div> <nav class="md-nav" data-md-level="1" aria-labelledby="__nav_5_label" aria-expanded="false"> <label class="md-nav__title" for="__nav_5"> <span class="md-nav__icon md-icon"></span> Requirements </label> <ul class="md-nav__list" data-md-scrollfix> <li class="md-nav__item"> <a href="../../requirements/stakeholder_requirements/" class="md-nav__link"> <span class="md-ellipsis"> Stakeholder Requirements </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/gap-analysis/" class="md-nav__link"> <span class="md-ellipsis"> Requirements Gap Analysis </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_admin/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Administration, Permissions & Onboarding </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_api_ui/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: API & User Interface </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_audit_reporting/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Audit Trail & Regulatory Reporting </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_auth/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Authentication & Session </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_backup/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Backup & Restore </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_catalogs/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Catalogs, Roles & Users </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_data_protection/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Data Protection, Retention & Disposal </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_documents/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Documents, Versions & Storage </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_dossiers/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Technical Documentation Dossiers </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_effectivity/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Effectivity, Periodic Review & Validity </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_gspr/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Regulatory Conformity (GSPR / Essential Principles) </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_i18n/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Internationalization </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_lifecycle/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Life Cycle & Reviews </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_memberships/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Mandator Membership & Invitations </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_migration/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Migration & Import </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_nfr/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Non-Functional </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_notifications/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Notifications & Tasks </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_obligations/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Recurring Obligations </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_relationships/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Document Relationships </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_risk/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Risk Management (ISO 14971 Hazards & Controls) </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_sbom/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Software Bill of Materials & Supply-Chain Assurance </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_search/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Search </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_separation/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Scopes, Mandators & Separation </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_signatures/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Electronic Signatures </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_training/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Read-Acknowledgement & Questionnaires </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_users/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: User Identity & Lifecycle </span> </a> </li> <li class="md-nav__item"> <a href="../../requirements/req_validation/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Design Validation & the Validation Traceability Axis </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_6" > <div class="md-nav__link md-nav__container"> <a href="../../process/" class="md-nav__link "> <span class="md-ellipsis"> Process (IEC 62304) </span> </a> <label class="md-nav__link " for="__nav_6" id="__nav_6_label" tabindex="0"> <span class="md-nav__icon md-icon"></span> </label> </div> <nav class="md-nav" data-md-level="1" aria-labelledby="__nav_6_label" aria-expanded="false"> <label class="md-nav__title" for="__nav_6"> <span class="md-nav__icon md-icon"></span> Process (IEC 62304) </label> <ul class="md-nav__list" data-md-scrollfix> <li class="md-nav__item"> <a href="../../process/configuration_management_plan/" class="md-nav__link"> <span class="md-ellipsis"> Configuration Management Plan </span> </a> </li> <li class="md-nav__item"> <a href="../../process/problem_resolution/" class="md-nav__link"> <span class="md-ellipsis"> Problem Resolution Process </span> </a> </li> <li class="md-nav__item"> <a href="../../process/risk_management/" class="md-nav__link"> <span class="md-ellipsis"> Risk Management </span> </a> </li> <li class="md-nav__item"> <a href="../../process/software_development_plan/" class="md-nav__link"> <span class="md-ellipsis"> Software Development Plan </span> </a> </li> <li class="md-nav__item"> <a href="../../process/verification_plan/" class="md-nav__link"> <span class="md-ellipsis"> Verification Plan </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_7" > <label class="md-nav__link" for="__nav_7" id="__nav_7_label" tabindex="0"> <span class="md-ellipsis"> Operations </span> <span class="md-nav__icon md-icon"></span> </label> <nav class="md-nav" data-md-level="1" aria-labelledby="__nav_7_label" aria-expanded="false"> <label class="md-nav__title" for="__nav_7"> <span class="md-nav__icon md-icon"></span> Operations </label> <ul class="md-nav__list" data-md-scrollfix> <li class="md-nav__item"> <a href="../../operations/genesis-installation/" class="md-nav__link"> <span class="md-ellipsis"> Genesis: Birthing an LQMS Installation with a Base Library </span> </a> </li> <li class="md-nav__item"> <a href="../../operations/deployment/" class="md-nav__link"> <span class="md-ellipsis"> LQMS Deployment Guide </span> </a> </li> <li class="md-nav__item"> <a href="../../operations/server-deployment/" class="md-nav__link"> <span class="md-ellipsis"> LQMS Server Deployment (single Linux host, public HTTPS) </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--active md-nav__item--nested"> <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_8" checked> <div class="md-nav__link md-nav__container"> <a href="../" class="md-nav__link "> <span class="md-ellipsis"> Traceability </span> </a> <label class="md-nav__link " for="__nav_8" id="__nav_8_label" tabindex="0"> <span class="md-nav__icon md-icon"></span> </label> </div> <nav class="md-nav" data-md-level="1" aria-labelledby="__nav_8_label" aria-expanded="true"> <label class="md-nav__title" for="__nav_8"> <span class="md-nav__icon md-icon"></span> Traceability </label> <ul class="md-nav__list" data-md-scrollfix> <li class="md-nav__item md-nav__item--active"> <input class="md-nav__toggle md-toggle" type="checkbox" id="__toc"> <label class="md-nav__link md-nav__link--active" for="__toc"> <span class="md-ellipsis"> Requirements Traceability Matrix </span> <span class="md-nav__icon md-icon"></span> </label> <a href="./" class="md-nav__link md-nav__link--active"> <span class="md-ellipsis"> Requirements Traceability Matrix </span> </a> <nav class="md-nav md-nav--secondary" aria-label="Table of contents"> <label class="md-nav__title" for="__toc"> <span class="md-nav__icon md-icon"></span> Table of contents </label> <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix> <li class="md-nav__item"> <a href="#status-counts" class="md-nav__link"> <span class="md-ellipsis"> Status counts </span> </a> </li> <li class="md-nav__item"> <a href="#gap--untraced-requirements-12" class="md-nav__link"> <span class="md-ellipsis"> GAP — untraced requirements (12) </span> </a> </li> <li class="md-nav__item"> <a href="#implemented-but-untested-0" class="md-nav__link"> <span class="md-ellipsis"> Implemented but untested (0) </span> </a> </li> <li class="md-nav__item"> <a href="#pq--the-executable-validation-journey-adr-0101" class="md-nav__link"> <span class="md-ellipsis"> PQ — the executable validation journey (ADR-0101) </span> </a> </li> <li class="md-nav__item"> <a href="#matrix" class="md-nav__link"> <span class="md-ellipsis"> Matrix </span> </a> <nav class="md-nav" aria-label="Matrix"> <ul class="md-nav__list"> <li class="md-nav__item"> <a href="#req-adm" class="md-nav__link"> <span class="md-ellipsis"> REQ-ADM </span> </a> </li> <li class="md-nav__item"> <a href="#req-api" class="md-nav__link"> <span class="md-ellipsis"> REQ-API </span> </a> </li> <li class="md-nav__item"> <a href="#req-aud" class="md-nav__link"> <span class="md-ellipsis"> REQ-AUD </span> </a> </li> <li class="md-nav__item"> <a href="#req-auth" class="md-nav__link"> <span class="md-ellipsis"> REQ-AUTH </span> </a> </li> <li class="md-nav__item"> <a href="#req-bak" class="md-nav__link"> <span class="md-ellipsis"> REQ-BAK </span> </a> </li> <li class="md-nav__item"> <a href="#req-cat" class="md-nav__link"> <span class="md-ellipsis"> REQ-CAT </span> </a> </li> <li class="md-nav__item"> <a href="#req-doc" class="md-nav__link"> <span class="md-ellipsis"> REQ-DOC </span> </a> </li> <li class="md-nav__item"> <a href="#req-dpr" class="md-nav__link"> <span class="md-ellipsis"> REQ-DPR </span> </a> </li> <li class="md-nav__item"> <a href="#req-eff" class="md-nav__link"> <span class="md-ellipsis"> REQ-EFF </span> </a> </li> <li class="md-nav__item"> <a href="#req-gsp" class="md-nav__link"> <span class="md-ellipsis"> REQ-GSP </span> </a> </li> <li class="md-nav__item"> <a href="#req-i18n" class="md-nav__link"> <span class="md-ellipsis"> REQ-I18N </span> </a> </li> <li class="md-nav__item"> <a href="#req-lc" class="md-nav__link"> <span class="md-ellipsis"> REQ-LC </span> </a> </li> <li class="md-nav__item"> <a href="#req-mem" class="md-nav__link"> <span class="md-ellipsis"> REQ-MEM </span> </a> </li> <li class="md-nav__item"> <a href="#req-mig" class="md-nav__link"> <span class="md-ellipsis"> REQ-MIG </span> </a> </li> <li class="md-nav__item"> <a href="#req-nfr" class="md-nav__link"> <span class="md-ellipsis"> REQ-NFR </span> </a> </li> <li class="md-nav__item"> <a href="#req-not" class="md-nav__link"> <span class="md-ellipsis"> REQ-NOT </span> </a> </li> <li class="md-nav__item"> <a href="#req-obl" class="md-nav__link"> <span class="md-ellipsis"> REQ-OBL </span> </a> </li> <li class="md-nav__item"> <a href="#req-rel" class="md-nav__link"> <span class="md-ellipsis"> REQ-REL </span> </a> </li> <li class="md-nav__item"> <a href="#req-rep" class="md-nav__link"> <span class="md-ellipsis"> REQ-REP </span> </a> </li> <li class="md-nav__item"> <a href="#req-risk" class="md-nav__link"> <span class="md-ellipsis"> REQ-RISK </span> </a> </li> <li class="md-nav__item"> <a href="#req-sbom" class="md-nav__link"> <span class="md-ellipsis"> REQ-SBOM </span> </a> </li> <li class="md-nav__item"> <a href="#req-sep" class="md-nav__link"> <span class="md-ellipsis"> REQ-SEP </span> </a> </li> <li class="md-nav__item"> <a href="#req-sig" class="md-nav__link"> <span class="md-ellipsis"> REQ-SIG </span> </a> </li> <li class="md-nav__item"> <a href="#req-srch" class="md-nav__link"> <span class="md-ellipsis"> REQ-SRCH </span> </a> </li> <li class="md-nav__item"> <a href="#req-td" class="md-nav__link"> <span class="md-ellipsis"> REQ-TD </span> </a> </li> <li class="md-nav__item"> <a href="#req-trn" class="md-nav__link"> <span class="md-ellipsis"> REQ-TRN </span> </a> </li> <li class="md-nav__item"> <a href="#req-ui" class="md-nav__link"> <span class="md-ellipsis"> REQ-UI </span> </a> </li> <li class="md-nav__item"> <a href="#req-usr" class="md-nav__link"> <span class="md-ellipsis"> REQ-USR </span> </a> </li> <li class="md-nav__item"> <a href="#req-val" class="md-nav__link"> <span class="md-ellipsis"> REQ-VAL </span> </a> </li> </ul> </nav> </li> </ul> </nav> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_9" > <div class="md-nav__link md-nav__container"> <a href="../../validation/" class="md-nav__link "> <span class="md-ellipsis"> Validation (tool lane) </span> </a> <label class="md-nav__link " for="__nav_9" id="__nav_9_label" tabindex="0"> <span class="md-nav__icon md-icon"></span> </label> </div> <nav class="md-nav" data-md-level="1" aria-labelledby="__nav_9_label" aria-expanded="false"> <label class="md-nav__title" for="__nav_9"> <span class="md-nav__icon md-icon"></span> Validation (tool lane) </label> <ul class="md-nav__list" data-md-scrollfix> <li class="md-nav__item"> <a href="../../validation/templates/ai-authorship-posture/" class="md-nav__link"> <span class="md-ellipsis"> AI-Authorship Posture — How LQMS Is Built, and Why the Validation Evidence Does Not Rest on It (TEMPLATE) </span> </a> </li> <li class="md-nav__item"> <a href="../../validation/templates/intended-use/" class="md-nav__link"> <span class="md-ellipsis"> Intended-Use Specification — LQMS as a QMS / Document-Control Tool (TEMPLATE) </span> </a> </li> <li class="md-nav__item"> <a href="../../validation/templates/tool-risk-assessment/" class="md-nav__link"> <span class="md-ellipsis"> Tool-Risk Assessment — LQMS as a QMS Tool (TEMPLATE) </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_10" > <label class="md-nav__link" for="__nav_10" id="__nav_10_label" tabindex="0"> <span class="md-ellipsis"> Regulatory </span> <span class="md-nav__icon md-icon"></span> </label> <nav class="md-nav" data-md-level="1" aria-labelledby="__nav_10_label" aria-expanded="false"> <label class="md-nav__title" for="__nav_10"> <span class="md-nav__icon md-icon"></span> Regulatory </label> <ul class="md-nav__list" data-md-scrollfix> <li class="md-nav__item"> <a href="../../regulatory/mdr-annex-i-skeleton/" class="md-nav__link"> <span class="md-ellipsis"> MDR Annex I — GSPR authoring skeleton (paraphrased) </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_11" > <div class="md-nav__link md-nav__container"> <a href="../../user-guide/" class="md-nav__link "> <span class="md-ellipsis"> User guide </span> </a> <label class="md-nav__link " for="__nav_11" id="__nav_11_label" tabindex="0"> <span class="md-nav__icon md-icon"></span> </label> </div> <nav class="md-nav" data-md-level="1" aria-labelledby="__nav_11_label" aria-expanded="false"> <label class="md-nav__title" for="__nav_11"> <span class="md-nav__icon md-icon"></span> User guide </label> <ul class="md-nav__list" data-md-scrollfix> <li class="md-nav__item"> <a href="../../user-guide/tutorial/" class="md-nav__link"> <span class="md-ellipsis"> Tutorial — from zero to a released document </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/administration/" class="md-nav__link"> <span class="md-ellipsis"> Administering an LQMS Installation </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/diagrams/" class="md-nav__link"> <span class="md-ellipsis"> Diagrams </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/documents-lifecycle/" class="md-nav__link"> <span class="md-ellipsis"> Documents & the Lifecycle </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/exports/" class="md-nav__link"> <span class="md-ellipsis"> PDF Exports & the Audit Pack </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/obligations/" class="md-nav__link"> <span class="md-ellipsis"> Recurring Obligations </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/project-context/" class="md-nav__link"> <span class="md-ellipsis"> The Project Context & App Version </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/review-comments/" class="md-nav__link"> <span class="md-ellipsis"> Review Comments </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/topics/activity-trail/" class="md-nav__link"> <span class="md-ellipsis"> Who did what, when — reading a project's activity </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/topics/admin-scopes/" class="md-nav__link"> <span class="md-ellipsis"> Renaming a project, and what can never change </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/topics/authority-view/" class="md-nav__link"> <span class="md-ellipsis"> Who holds each function here, and what may it do </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/topics/break-glass/" class="md-nav__link"> <span class="md-ellipsis"> The permission I need is held by a role I do not hold — what now? </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/topics/coverage-and-chains/" class="md-nav__link"> <span class="md-ellipsis"> Coverage or chains? — which requirement view answers your question </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/topics/credentials/" class="md-nav__link"> <span class="md-ellipsis"> Your password: changing it, resetting it — and why LQMS never sees it </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/topics/emergency-cover/" class="md-nav__link"> <span class="md-ellipsis"> Who may cover for whom here — declaring emergency cover, and reading where the glass was broken </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/topics/key-rules/" class="md-nav__link"> <span class="md-ellipsis"> Special elements: what a project declares, and when its names freeze </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/topics/memberships/" class="md-nav__link"> <span class="md-ellipsis"> Belonging to an organization: invitations, acceptance, and what they change </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/topics/provisioning-birth-path/" class="md-nav__link"> <span class="md-ellipsis"> How a new organization and project are born </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/topics/review-policies/" class="md-nav__link"> <span class="md-ellipsis"> What a review policy controls, and what an empty grant means </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/topics/setup-wizard-lanes/" class="md-nav__link"> <span class="md-ellipsis"> The setup wizard: the lanes, and what it writes </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/topics/staffing-and-assignments/" class="md-nav__link"> <span class="md-ellipsis"> Staffing people into roles, and the accountable holder </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/topics/technical-dossier/" class="md-nav__link"> <span class="md-ellipsis"> How do I assemble a technical dossier? </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/trace-items/" class="md-nav__link"> <span class="md-ellipsis"> Trace Items — Requirements, Risks & Risk Controls </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/trace-links/" class="md-nav__link"> <span class="md-ellipsis"> Trace Links & the Suspect Cycle </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/traceability-workspace/" class="md-nav__link"> <span class="md-ellipsis"> The Traceability Workspace </span> </a> </li> <li class="md-nav__item"> <a href="../../user-guide/training/" class="md-nav__link"> <span class="md-ellipsis"> Training & Acknowledgements </span> </a> </li> </ul> </nav> </li> </ul> </nav> </div> </div> </div> <div class="md-sidebar md-sidebar--secondary" data-md-component="sidebar" data-md-type="toc" > <div class="md-sidebar__scrollwrap"> <div class="md-sidebar__inner"> <nav class="md-nav md-nav--secondary" aria-label="Table of contents"> <label class="md-nav__title" for="__toc"> <span class="md-nav__icon md-icon"></span> Table of contents </label> <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix> <li class="md-nav__item"> <a href="#status-counts" class="md-nav__link"> <span class="md-ellipsis"> Status counts </span> </a> </li> <li class="md-nav__item"> <a href="#gap--untraced-requirements-12" class="md-nav__link"> <span class="md-ellipsis"> GAP — untraced requirements (12) </span> </a> </li> <li class="md-nav__item"> <a href="#implemented-but-untested-0" class="md-nav__link"> <span class="md-ellipsis"> Implemented but untested (0) </span> </a> </li> <li class="md-nav__item"> <a href="#pq--the-executable-validation-journey-adr-0101" class="md-nav__link"> <span class="md-ellipsis"> PQ — the executable validation journey (ADR-0101) </span> </a> </li> <li class="md-nav__item"> <a href="#matrix" class="md-nav__link"> <span class="md-ellipsis"> Matrix </span> </a> <nav class="md-nav" aria-label="Matrix"> <ul class="md-nav__list"> <li class="md-nav__item"> <a href="#req-adm" class="md-nav__link"> <span class="md-ellipsis"> REQ-ADM </span> </a> </li> <li class="md-nav__item"> <a href="#req-api" class="md-nav__link"> <span class="md-ellipsis"> REQ-API </span> </a> </li> <li class="md-nav__item"> <a href="#req-aud" class="md-nav__link"> <span class="md-ellipsis"> REQ-AUD </span> </a> </li> <li class="md-nav__item"> <a href="#req-auth" class="md-nav__link"> <span class="md-ellipsis"> REQ-AUTH </span> </a> </li> <li class="md-nav__item"> <a href="#req-bak" class="md-nav__link"> <span class="md-ellipsis"> REQ-BAK </span> </a> </li> <li class="md-nav__item"> <a href="#req-cat" class="md-nav__link"> <span class="md-ellipsis"> REQ-CAT </span> </a> </li> <li class="md-nav__item"> <a href="#req-doc" class="md-nav__link"> <span class="md-ellipsis"> REQ-DOC </span> </a> </li> <li class="md-nav__item"> <a href="#req-dpr" class="md-nav__link"> <span class="md-ellipsis"> REQ-DPR </span> </a> </li> <li class="md-nav__item"> <a href="#req-eff" class="md-nav__link"> <span class="md-ellipsis"> REQ-EFF </span> </a> </li> <li class="md-nav__item"> <a href="#req-gsp" class="md-nav__link"> <span class="md-ellipsis"> REQ-GSP </span> </a> </li> <li class="md-nav__item"> <a href="#req-i18n" class="md-nav__link"> <span class="md-ellipsis"> REQ-I18N </span> </a> </li> <li class="md-nav__item"> <a href="#req-lc" class="md-nav__link"> <span class="md-ellipsis"> REQ-LC </span> </a> </li> <li class="md-nav__item"> <a href="#req-mem" class="md-nav__link"> <span class="md-ellipsis"> REQ-MEM </span> </a> </li> <li class="md-nav__item"> <a href="#req-mig" class="md-nav__link"> <span class="md-ellipsis"> REQ-MIG </span> </a> </li> <li class="md-nav__item"> <a href="#req-nfr" class="md-nav__link"> <span class="md-ellipsis"> REQ-NFR </span> </a> </li> <li class="md-nav__item"> <a href="#req-not" class="md-nav__link"> <span class="md-ellipsis"> REQ-NOT </span> </a> </li> <li class="md-nav__item"> <a href="#req-obl" class="md-nav__link"> <span class="md-ellipsis"> REQ-OBL </span> </a> </li> <li class="md-nav__item"> <a href="#req-rel" class="md-nav__link"> <span class="md-ellipsis"> REQ-REL </span> </a> </li> <li class="md-nav__item"> <a href="#req-rep" class="md-nav__link"> <span class="md-ellipsis"> REQ-REP </span> </a> </li> <li class="md-nav__item"> <a href="#req-risk" class="md-nav__link"> <span class="md-ellipsis"> REQ-RISK </span> </a> </li> <li class="md-nav__item"> <a href="#req-sbom" class="md-nav__link"> <span class="md-ellipsis"> REQ-SBOM </span> </a> </li> <li class="md-nav__item"> <a href="#req-sep" class="md-nav__link"> <span class="md-ellipsis"> REQ-SEP </span> </a> </li> <li class="md-nav__item"> <a href="#req-sig" class="md-nav__link"> <span class="md-ellipsis"> REQ-SIG </span> </a> </li> <li class="md-nav__item"> <a href="#req-srch" class="md-nav__link"> <span class="md-ellipsis"> REQ-SRCH </span> </a> </li> <li class="md-nav__item"> <a href="#req-td" class="md-nav__link"> <span class="md-ellipsis"> REQ-TD </span> </a> </li> <li class="md-nav__item"> <a href="#req-trn" class="md-nav__link"> <span class="md-ellipsis"> REQ-TRN </span> </a> </li> <li class="md-nav__item"> <a href="#req-ui" class="md-nav__link"> <span class="md-ellipsis"> REQ-UI </span> </a> </li> <li class="md-nav__item"> <a href="#req-usr" class="md-nav__link"> <span class="md-ellipsis"> REQ-USR </span> </a> </li> <li class="md-nav__item"> <a href="#req-val" class="md-nav__link"> <span class="md-ellipsis"> REQ-VAL </span> </a> </li> </ul> </nav> </li> </ul> </nav> </div> </div> </div> <div class="md-content" data-md-component="content"> <article class="md-content__inner md-typeset"> <a href="https://github.com/nburri/lqms/edit/main/docs/traceability/matrix.md" title="Edit this page" class="md-content__button md-icon"> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M10 20H6V4h7v5h5v3.1l2-2V8l-6-6H6c-1.1 0-2 .9-2 2v16c0 1.1.9 2 2 2h4zm10.2-7c.1 0 .3.1.4.2l1.3 1.3c.2.2.2.6 0 .8l-1 1-2.1-2.1 1-1c.1-.1.2-.2.4-.2m0 3.9L14.1 23H12v-2.1l6.1-6.1z"/></svg> </a> <h1 id="requirements-traceability-matrix">Requirements Traceability Matrix<a class="headerlink" href="#requirements-traceability-matrix" title="Permanent link">¶</a></h1> <!-- GENERATED FILE — do not edit by hand. Regenerate with `python3 scripts/generate-traceability.py`. --> <p>Generated from commit <code>0a6fc8f6</code>.</p> <p><strong>299 requirements</strong> across 29 groups.</p> <h2 id="status-counts">Status counts<a class="headerlink" href="#status-counts" title="Permanent link">¶</a></h2> <table> <thead> <tr> <th>Status</th> <th style="text-align: right;">Count</th> </tr> </thead> <tbody> <tr> <td>verified</td> <td style="text-align: right;">212</td> </tr> <tr> <td>future</td> <td style="text-align: right;">48</td> </tr> <tr> <td>not-applicable</td> <td style="text-align: right;">4</td> </tr> <tr> <td>accepted-gap</td> <td style="text-align: right;">22</td> </tr> <tr> <td>superseded</td> <td style="text-align: right;">1</td> </tr> <tr> <td>GAP</td> <td style="text-align: right;">12</td> </tr> <tr> <td><strong>total</strong></td> <td style="text-align: right;"><strong>299</strong></td> </tr> </tbody> </table> <h2 id="gap--untraced-requirements-12">GAP — untraced requirements (12)<a class="headerlink" href="#gap--untraced-requirements-12" title="Permanent link">¶</a></h2> <p>No test or implementation citation and no override. These are the actionable traceability gaps.</p> <ul> <li><strong>REQ-ADM-011</strong> — A freshly installed system shall be fully operable from its bootstrap administrator without out-of-band data manipulati…</li> <li><strong>REQ-CAT-008</strong> — Where a guided setup requires catalog entries that do not exist, a caller holding catalog administration shall be offer…</li> <li><strong>REQ-MEM-001</strong> — Membership in a mandator shall be a first-class recorded state (invited → accepted / declined / removed); invitation, a…</li> <li><strong>REQ-MEM-002</strong> — Membership shall begin only upon the invitee's acceptance; an invitation may carry named responsibilities (scope, role)…</li> <li><strong>REQ-MEM-003</strong> — Membership alone shall grant no content access; a member without roles sees nothing, and a non-member cannot observe th…</li> <li><strong>REQ-MEM-004</strong> — Invitation by email shall not disclose to the inviter whether the address is already known to the installation, and sha…</li> <li><strong>REQ-MEM-005</strong> — Email invitation links shall be single-use, unguessable, stored only as a digest, and expire; expired or unknown links…</li> <li><strong>REQ-MEM-006</strong> — Ending a membership shall unassign the person's roles in that mandator and close the membership without affecting the p…</li> <li><strong>REQ-TD-001</strong> — A dossier shall assemble released document versions by frozen reference (pins); issuing shall render the merged deliver…</li> <li><strong>REQ-TD-002</strong> — A reader who cannot see every pinned element shall receive a freshly rendered partial copy visibly marked as not the re…</li> <li><strong>REQ-TD-003</strong> — An issued dossier shall not be deletable; correction is forward-only (clone to a new draft, re-issue as a new version);…</li> <li><strong>REQ-UI-027</strong> — The user manual shall ship inside the application, versioned with it; help affordances on a surface shall open the topi…</li> </ul> <h2 id="implemented-but-untested-0">Implemented but untested (0)<a class="headerlink" href="#implemented-but-untested-0" title="Permanent link">¶</a></h2> <p>Cited in implementation sources but not (yet) referenced by any test — candidates for verification coverage.</p> <p><em>None.</em></p> <h2 id="pq--the-executable-validation-journey-adr-0101">PQ — the executable validation journey (ADR-0101)<a class="headerlink" href="#pq--the-executable-validation-journey-adr-0101" title="Permanent link">¶</a></h2> <p>One walk through the intended use, performed against a running installation, contributes PERFORMANCE-qualification evidence beside the isolated tests: where a requirement's <em>Test evidence</em> cell names the tests that check it in isolation, its <em>PQ evidence</em> cell names the station of the walk in which the same requirement was exercised as part of the whole workflow.</p> <table> <thead> <tr> <th></th> <th></th> </tr> </thead> <tbody> <tr> <td>Evidence bundle</td> <td><code>v0.9.54-1-g9dc234a7-20260908T150135Z</code> (the latest local run, not promoted)</td> </tr> <tr> <td>Walk performed at</td> <td>2026-09-08T15:01:35Z</td> </tr> <tr> <td>Product version under test</td> <td><code>v0.9.54-1-g9dc234a7</code></td> </tr> <tr> <td>Source revision</td> <td><code>9dc234a7</code></td> </tr> <tr> <td>Stations</td> <td>14 of 14 reached their expected result</td> </tr> <tr> <td>Overall verdict</td> <td><strong>PASS</strong></td> </tr> <tr> <td>Requirements carrying PQ evidence</td> <td>39</td> </tr> <tr> <td>Protocol</td> <td><code>backend/api/build/validation-journey/v0.9.54-1-g9dc234a7-20260908T150135Z/journey.md</code></td> </tr> </tbody> </table> <p>1 station of the walk declares NO requirement id — station 10 (Reading who holds which function, and exporting it) — because no requirement in the baseline covers what it exercises. That evidence stands in the protocol; the missing thing is a requirement to carry it.</p> <p><em>The bundle above lives in the build output, which is not committed: it is the run this matrix was generated after. The durable reference for a release is the promoted copy under <code>docs/validation/journeys/<version>/</code>.</em></p> <h2 id="matrix">Matrix<a class="headerlink" href="#matrix" title="Permanent link">¶</a></h2> <h3 id="req-adm">REQ-ADM<a class="headerlink" href="#req-adm" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-ADM-001</td> <td>verified</td> <td>The system shall define a fixed, closed set of named permissions covering content/functional and administrative capabil…</td> <td>STR-017; ADR-0012</td> <td>catalog/catalog/CatalogSchemaTest.kt<br>catalog/catalog/DocumentTypeAdminServiceTest.kt</td> <td>—</td> <td>persistence/V004__catalog_and_permissions.sql</td> <td><code>d23c3fe9</code> feat(catalog): authorization catalogs + permission model (P…<br><code>95dc75c7</code> docs(arch): accept ADR-0012 permission-based authorization…</td> </tr> <tr> <td>REQ-ADM-002</td> <td>verified</td> <td>Each catalog role shall be configurably associated with a set of permissions; changing the mapping shall require the MA…</td> <td>STR-006, STR-017; ADR-0012, ADR-0004</td> <td>api/api/AdminRoleResourceTest.kt<br>api/e2e/admin-roles.spec.ts<br>api/e2e/screenshots.spec.ts<br>catalog/catalog/DocumentTypeAdminServiceTest.kt<br>catalog/catalog/RoleAdminServiceTest.kt</td> <td>—</td> <td>api/src/app/core/lqms-api.ts<br>api/src/app/core/models.ts<br>api/src/app/features/admin/role-editor-dialog.ts<br>api/src/app/features/admin/roles-page.ts<br>catalog/catalog/person/repository/RoleRepository.kt<br>catalog/catalog/person/service/RoleAdminService.kt<br>persistence/V004__catalog_and_permissions.sql</td> <td><code>2fd0769c</code> feat(catalog,api,webui): roles admin page — catalog CRUD, p…<br><code>d23c3fe9</code> feat(catalog): authorization catalogs + permission model (P…</td> </tr> <tr> <td>REQ-ADM-003</td> <td>verified</td> <td>Holding a role in a scope shall grant that role's permissions within the scope and its descendant scopes; a role held a…</td> <td>STR-017; ADR-0012</td> <td>catalog/catalog/AuthzResolutionTest.kt<br>catalog/catalog/UserAdminServiceTest.kt</td> <td>—</td> <td>catalog/catalog/person/service/UserAdminService.kt<br>persistence/V005__role_assignment_and_resolution.sql</td> <td><code>83201d00</code> feat(catalog): role assignments + authorization resolution…</td> </tr> <tr> <td>REQ-ADM-004</td> <td>verified</td> <td>Administrative and content permissions shall be independent; system-administration permissions shall not implicitly gra…</td> <td>STR-003, STR-017; ADR-0012</td> <td>api/api/BlindGovernanceReadResourceTest.kt<br>api/api/FreshInstallReflectionTest.kt<br>api/api/PermissionClassificationTest.kt<br>api/api/ProjectDissolutionFullStackTest.kt<br>api/api/ScopeActivityResourceTest.kt<br>api/api/VirginCatalogBirthFullStackTest.kt<br>api/e2e/admin-scopes.spec.ts<br>api/e2e/scope-config.spec.ts<br>catalog/catalog/AuthzResolutionTest.kt<br>catalog/catalog/DocumentTypeAdminServiceTest.kt<br>catalog/catalog/ScopeProvisioningServiceTest.kt<br>catalog/catalog/UserAdminServiceTest.kt<br>document/document/BlindGovernanceActTest.kt<br>document/document/ImportServiceTest.kt<br>document/document/KeyRuleServiceTest.kt<br>document/document/PortabilityExportServiceTest.kt<br>document/document/ReviewPolicyServiceTest.kt<br>scope/scope/RlsPolicyInventoryTest.kt</td> <td>—</td> <td>api/api/auth/SystemBootstrap.kt<br>api/src/app/core/scope-config-access.ts<br>api/src/app/features/admin/setup-wizard/setup-wizard.ts<br>api/src/app/features/scope-config/scope-config.ts<br>catalog/catalog/person/repository/RoleRepository.kt<br>catalog/catalog/person/service/RoleAdminService.kt<br>catalog/catalog/person/service/UserAdminService.kt<br>catalog/catalog/provisioning/repository/DirectoryRepository.kt<br>catalog/catalog/provisioning/service/DirectoryService.kt<br>catalog/catalog/provisioning/service/ScopeProvisioningService.kt<br>catalog/catalog/types/repository/ActivationRepository.kt<br>catalog/catalog/types/service/DocumentTypeAdminService.kt<br>catalog/catalog/types/service/DocumentTypeDefaultsService.kt<br>document/document/arrival/service/ImportService.kt<br>document/document/core/repository/DocumentRepository.kt<br>document/document/core/service/FolderService.kt<br>document/document/export/service/PortabilityExportService.kt<br>document/document/lifecycle/service/ReviewPolicyService.kt<br>document/document/records/repository/AcknowledgementPolicyRepository.kt<br>document/document/records/service/AcknowledgementPolicyService.kt<br>document/document/setup/service/ScopeSetupReflectionService.kt<br>document/document/setup/service/SetupStatusService.kt<br>document/document/trace/repository/CoverageRuleRepository.kt<br>document/document/trace/repository/DesignKindRepository.kt<br>document/document/trace/service/CoverageRuleService.kt<br>document/document/trace/service/DesignKindService.kt<br>persistence/V005__role_assignment_and_resolution.sql<br>persistence/V078__retire_reserved_permissions.sql<br>persistence/V080__audit_append_assignment_reach.sql<br>persistence/V081__mandator_membership.sql<br>persistence/V085__key_usage_count_on_true_state.sql<br>persistence/V086__blind_governance_acts_on_true_state.sql<br>persistence/V087__manage_mandators_permission.sql<br>persistence/V094__project_arrival_import.sql<br>persistence/V097__role_reference_oracle.sql<br>persistence/V103__type_document_count_on_true_state.sql<br>persistence/V113__project_dissolution.sql<br>persistence/V115__portability_export_permission.sql<br>persistence/V116__dissolution_working_record_line.sql<br>persistence/V121__global_cascade_classification.sql<br>persistence/V126__review_policy_surface_on_true_state.sql<br>scope/scope/EffectiveAuthzRepository.kt<br>scope/scope/ScopeRepository.kt</td> <td><code>dde92cf8</code> feat(api): idempotent system bootstrap (admin grant, base h…<br><code>83201d00</code> feat(catalog): role assignments + authorization resolution…</td> </tr> <tr> <td>REQ-ADM-005</td> <td>accepted-gap</td> <td>Document life-cycle transitions shall remain governed by review policies (ADR-0003); the permission model shall govern… <em>(Dual-governance umbrella: life-cycle transitions are governed by review policies (tested under REQ-LC-003/006) and everything else by the permission model (REQ-ADM-004 and the resource 403 tests); no single code point carries this umbrella id (ADR-0012/0003).)</em></td> <td>STR-002, STR-017; ADR-0012, ADR-0003</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-ADM-006</td> <td>verified</td> <td>A deployment-configured bootstrap identity shall be granted system administration idempotently on startup (initial setu…</td> <td>STR-017; ADR-0012</td> <td>api/api/BootstrapRunnerTest.kt<br>api/api/FreshInstallReflectionTest.kt<br>api/api/SystemBootstrapTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-ADM-007</td> <td>verified</td> <td>On first initialization the system shall create the global base scope and an internal mandator with a QMS-operations sc…</td> <td>STR-015, STR-017; ADR-0012, ADR-0010</td> <td>scope/scope/GlobalScopeUniquenessTest.kt</td> <td>—</td> <td>persistence/V016__released_base_readability.sql<br>persistence/V018__single_global_scope.sql<br>persistence/V117__base_reader_role.sql<br>persistence/V120__base_library_folder_readability.sql</td> <td>—</td> </tr> <tr> <td>REQ-ADM-008</td> <td>future</td> <td>Onboarding a project/scope shall consist of creating the scope, activating the required catalog roles and document type… <em>(Each constituent onboarding operation (catalog activation, role staffing, review-policy config) exists, is permission-gated and tested (REQ-ADM-001..004, REQ-LC rows); the composed onboarding flow does not yet have one end-to-end verification. The scope/mandator-creation surface itself now EXISTS (ADR-0097: the MANAGE_SCOPES-gated provisioning endpoints; the never-enforced CREATE_SCOPE/CREATE_MANDATOR vocabulary that used to stand in for it was retired by V073). Trigger: the first external/standalone installation. Decision 2026-07-22: defer.)</em></td> <td>STR-006, STR-017; ADR-0012, ADR-0004, ADR-0003</td> <td>api/api/ValidationJourneyTest.kt</td> <td>PQ: station 1 (Registering a customer and a project)</td> <td>persistence/V073__retire_dead_letter_permissions.sql</td> <td><code>d5c22c74</code> docs(user-guide): follow-along tutorial — from zero to a re…</td> </tr> <tr> <td>REQ-ADM-009</td> <td>verified</td> <td>All administrative actions (scope/mandator/user/catalog/policy changes and role assignments) shall produce audit events.</td> <td>STR-009, STR-017; ADR-0012, REQ-AUD-001</td> <td>api/api/AdminDocumentTypeResourceTest.kt<br>api/api/ScopeGovernanceResourceTest.kt<br>api/api/ScopeProvisioningResourceTest.kt<br>api/api/ValidationJourneyTest.kt<br>catalog/catalog/DocumentTypeAdminServiceTest.kt<br>catalog/catalog/DocumentTypeDefaultsServiceTest.kt<br>catalog/catalog/RoleAdminServiceTest.kt<br>catalog/catalog/ScopeProvisioningServiceTest.kt<br>catalog/catalog/UserAdminServiceTest.kt<br>document/document/ReviewPolicyServiceTest.kt</td> <td>PQ: station 12 (Reading the project's own activity trail, and exporting it)<br>PQ: station 14 (Inviting a person into the customer's organization, and their accepting it)</td> <td>catalog/catalog/provisioning/service/ScopeProvisioningService.kt<br>catalog/catalog/types/service/DocumentTypeAdminService.kt</td> <td><code>9dc234a7</code> fix(provisioning): the birth activation gets no setting-up…<br><code>49219f41</code> feat(api,document): journey station 12 — the activity trail…<br><code>2da77f9a</code> test(traceability): backfill REQ citations + add REQ-LC-014…<br><code>619d859b</code> feat(catalog,identity,api,webui): admin user lifecycle — in…</td> </tr> <tr> <td>REQ-ADM-010</td> <td>verified</td> <td>The oversight/traceability views shall be governed by two scope permissions added to the fixed permission set (REQ-ADM-…</td> <td>STR-003, STR-011, STR-027; ADR-0080, ADR-0012</td> <td>document/document/TraceabilityPermissionSeparationTest.kt</td> <td>—</td> <td>—</td> <td><code>f2b93b49</code> docs(requirements): prepare the v1.7 delta — trace/risk/aud…</td> </tr> <tr> <td>REQ-ADM-011</td> <td>GAP</td> <td>A freshly installed system shall be fully operable from its bootstrap administrator without out-of-band data manipulati…</td> <td>STR-017; ADR-0106, ADR-0107, ADR-0108</td> <td>—</td> <td>—</td> <td>—</td> <td><code>25fe83b2</code> docs(requirements): baseline v2.0 — the five post-v1.9 func…</td> </tr> <tr> <td>REQ-ADM-012</td> <td>verified</td> <td>The system shall provide an admin System page whose sections render per their own gates: the backup act + evidence (EXP…</td> <td>STR-010, STR-015; ADR-0116</td> <td>api/api/AdminSystemResourceTest.kt<br>backup/backup/SystemJobHeartbeatServiceTest.kt</td> <td>—</td> <td>api/api/backup/AdminSystemResource.kt<br>backup/backup/SystemJobHeartbeatService.kt</td> <td><code>de8db2af</code> docs(requirements): baseline v2.1 — the ADR-0116 delta stam…<br><code>efe6223a</code> feat(backup,api,webui,persistence,deploy): ADR-0116 realize…<br><code>80804346</code> docs(requirements): REQ-BAK-006/007 + REQ-ADM-012 — the ADR…</td> </tr> </tbody> </table> <h3 id="req-api">REQ-API<a class="headerlink" href="#req-api" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-API-001</td> <td>accepted-gap</td> <td>All system functionality shall be exposed via a REST API; the frontend shall use no other channel. <em>(All functionality is REST under /api (ADR-0005/0007) and the SPA consumes only that API (driven end to end by FullStackBrowserSmokeTest); "no other channel" is a structural property without a unit-test carrier.)</em></td> <td>STR-013; ADR-0005, ADR-0007</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-API-002</td> <td>verified</td> <td>Every API request shall be authenticated and executed under the requesting user's permissions; RLS shall apply to all A…</td> <td>STR-003; ADR-0002</td> <td>api/api/AuthBoundaryTest.kt<br>api/api/KeycloakIntegrationTest.kt<br>scope/scope/AuthorizedRequestContextTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-API-003</td> <td>verified</td> <td>The API shall expose the requesting user's effective permissions per resource so clients can reflect them without dupli…</td> <td>STR-007; ADR-0007</td> <td>api/api/DirectoryResourceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-API-004</td> <td>verified</td> <td>The API shall be documented in an OpenAPI specification generated from the implementation.</td> <td>STR-013, STR-014</td> <td>api/api/OpenApiSpecTest.kt</td> <td>—</td> <td>—</td> <td><code>2c3b51f2</code> docs(requirements): prepare the v1.8 delta — obligations, D…<br><code>b24fe8fb</code> feat(api): OpenAPI spec generated from the implementation (…<br><code>c1bc7053</code> feat(api): generate OpenAPI spec from the implementation (R…</td> </tr> <tr> <td>REQ-API-005</td> <td>future</td> <td>The API layer shall be structured so an MCP interface can be added as an additional consumer of the same services, subj… <em>(MCP interface is a Later capability (release-plan.md); the ADR-0005 module structure (thin REST over shared services with service-layer enforcement) is the planned extension point.)</em></td> <td>STR-013; ADR-0005</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-API-006</td> <td>verified</td> <td>The system shall expose a product version (plain semver, per the release ritual) via GET /api/version — a productVersio…</td> <td>STR-014; ADR-0090</td> <td>api/e2e/build-info.spec.ts</td> <td>—</td> <td>—</td> <td><code>f0691e82</code> docs(requirements): v1.8 delta PREPARED — 9 rows, all verif…<br><code>2c3b51f2</code> docs(requirements): prepare the v1.8 delta — obligations, D…</td> </tr> </tbody> </table> <h3 id="req-aud">REQ-AUD<a class="headerlink" href="#req-aud" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-AUD-001</td> <td>verified</td> <td>Every life-cycle transition, every create/modify/delete of a record or security-relevant configuration, and every secur…</td> <td>STR-009; §8.1</td> <td>api/api/ValidationJourneyTest.kt<br>audit/audit/ScopeActivityServiceTest.kt<br>catalog/catalog/DirectoryServiceTest.kt<br>document/document/AuditEventSchemaTest.kt<br>document/document/DocumentServiceTest.kt<br>document/document/PdfExportServiceTest.kt<br>document/document/ValidationAxisSaveTest.kt</td> <td>PQ: station 12 (Reading the project's own activity trail, and exporting it)<br>PQ: station 14 (Inviting a person into the customer's organization, and their accepting it)</td> <td>audit/audit/AuditEventRepository.kt<br>audit/audit/AuditModule.kt<br>audit/audit/ScopeActivityService.kt<br>catalog/catalog/provisioning/service/DirectoryService.kt<br>catalog/catalog/types/service/DocumentTypeAdminService.kt<br>document/document/core/service/DocumentService.kt<br>document/document/trace/service/DesignKindService.kt<br>persistence/V011__audit_event.sql<br>persistence/V129__audit_event_insertion_order.sql<br>search/search/SearchService.kt</td> <td><code>49219f41</code> feat(api,document): journey station 12 — the activity trail…<br><code>39e524f4</code> feat(catalog,document): config-change audit events — MAY_DE…<br><code>115734a1</code> feat(catalog,document): audit the three unaudited config su…<br><code>a01936cc</code> docs(req): release requirements baseline v1.3 (spec-hardeni…<br><code>3bbb5650</code> docs(req): v1.3 spec-hardening round — Tier-B must-fix from…</td> </tr> <tr> <td>REQ-AUD-002</td> <td>verified</td> <td>Audit events shall be append-only: no interface, including administrative ones, shall update or delete them.</td> <td>STR-009</td> <td>document/document/AuditEventSchemaTest.kt</td> <td>—</td> <td>audit/audit/AuditEventRepository.kt<br>document/document/trace/service/DesignKindService.kt<br>persistence/V011__audit_event.sql<br>persistence/V074__audit_event_scope_activity_index.sql<br>persistence/V075__audit_event_scope_entity_read.sql<br>persistence/V080__audit_append_assignment_reach.sql<br>persistence/V086__blind_governance_acts_on_true_state.sql<br>persistence/V088__version_release_stamp.sql<br>persistence/V102__system_maintenance_surface.sql<br>persistence/V106__working_record_tripwire.sql<br>persistence/V107__version_submit_stamp.sql<br>persistence/V128__audit_append_requires_genuine_reach.sql<br>persistence/V134__organization_dissolution_residue.sql</td> <td><code>b2223784</code> feat(document): Phase 3 slices 3.3-3.5 — version, content_p…</td> </tr> <tr> <td>REQ-AUD-003</td> <td>verified</td> <td>For any released version, the system shall reproduce on demand: the exact content (via hash), all approvals (user, role…</td> <td>STR-009; ADR-0001, ADR-0003</td> <td>api/e2e/documents.spec.ts<br>document/document/DocumentServiceTest.kt<br>document/document/LifecycleServiceTest.kt<br>storage/storage/FilesystemContentStoreTest.kt</td> <td>—</td> <td>api/api/document/DocumentResource.kt<br>api/src/app/core/models.ts<br>document/document/core/service/DocumentService.kt<br>persistence/V131__version_revocation_stamp.sql</td> <td><code>3b4a09c2</code> docs(validation): refresh mock-audit walkthrough to shipped…<br><code>2da77f9a</code> test(traceability): backfill REQ citations + add REQ-LC-014…</td> </tr> <tr> <td>REQ-AUD-004</td> <td>verified</td> <td>Audit events shall be queryable and exportable per scope by authorized users.</td> <td>STR-009, STR-011</td> <td>api/api/ValidationJourneyTest.kt<br>audit/audit/ScopeActivityServiceTest.kt<br>document/document/DocumentServiceTest.kt</td> <td>PQ: station 12 (Reading the project's own activity trail, and exporting it)</td> <td>audit/audit/AuditEventRepository.kt<br>persistence/V011__audit_event.sql<br>persistence/V129__audit_event_insertion_order.sql</td> <td><code>49219f41</code> feat(api,document): journey station 12 — the activity trail…</td> </tr> <tr> <td>REQ-AUD-005</td> <td>verified</td> <td>Audit events shall capture field-level changes (old → new values) for mutable records and security-relevant configurati…</td> <td>STR-009; §8.8</td> <td>architecture-tests/architecture/AuditActionVocabularyCensusTest.kt<br>catalog/catalog/DirectoryServiceTest.kt<br>catalog/catalog/DocumentTypeAdminServiceTest.kt<br>catalog/catalog/RetentionRuleServiceTest.kt<br>document/document/AuditEventSchemaTest.kt<br>document/document/DocumentServiceTest.kt<br>document/document/ReviewPolicyServiceTest.kt<br>document/document/ReviewSettingsServiceTest.kt<br>document/document/ValidationAxisSaveTest.kt</td> <td>—</td> <td>catalog/catalog/provisioning/repository/RetentionRuleRepository.kt<br>catalog/catalog/provisioning/service/RetentionRuleService.kt<br>catalog/catalog/types/repository/ActivationRepository.kt<br>catalog/catalog/types/repository/DocumentTypeRepository.kt<br>catalog/catalog/types/service/DocumentTypeAdminService.kt<br>document/document/core/repository/DocumentRepository.kt<br>document/document/core/service/DocumentMetadataService.kt<br>document/document/core/service/DocumentService.kt<br>document/document/core/service/FolderService.kt<br>document/document/lifecycle/service/ReviewPolicyService.kt<br>document/document/lifecycle/service/ReviewSettingsService.kt<br>document/document/records/service/AcknowledgementPolicyService.kt<br>persistence/V011__audit_event.sql<br>persistence/V125__draft_save_points.sql</td> <td><code>3173261b</code> fix(persistence,audit,backup,notification,catalog,document)…<br><code>c8ac3cf6</code> docs(planning): catalog verification 3/3 — declineByToken +…<br><code>39e524f4</code> feat(catalog,document): config-change audit events — MAY_DE…<br><code>115734a1</code> feat(catalog,document): audit the three unaudited config su…<br><code>85793870</code> feat(document): Phase 3 slice 3.7 (part 2) — editDraft + fr…<br><code>b2223784</code> feat(document): Phase 3 slices 3.3-3.5 — version, content_p…<br><code>a01936cc</code> docs(req): release requirements baseline v1.3 (spec-hardeni…<br><code>3bbb5650</code> docs(req): v1.3 spec-hardening round — Tier-B must-fix from…</td> </tr> <tr> <td>REQ-AUD-006</td> <td>accepted-gap</td> <td>The system shall produce, on demand, a complete inspection copy of a record comprising its content, full transition/cha… <em>(Substance realized today: content PDFs (ADR-0074/0083) + the queryable audit trail (DocumentService.auditTrail, tested under REQ-AUD-003 carriers) cover content, history and approvals; the single human-readable inspection ARTIFACT (one dossier rendering all of it) is not built. Re-entry trigger: the ADR-0083 dossier arc ('reviewer's copy'). Decision 2026-07-22: keep as known gap.)</em></td> <td>STR-009, STR-011; ADR-0014</td> <td>api/e2e/documents.spec.ts<br>document/document/DocumentServiceTest.kt</td> <td>—</td> <td>api/api/document/DocumentResource.kt<br>api/src/app/core/models.ts<br>document/document/core/service/DocumentService.kt<br>persistence/V011__audit_event.sql<br>persistence/V131__version_revocation_stamp.sql</td> <td><code>3b4a09c2</code> docs(validation): refresh mock-audit walkthrough to shipped…<br><code>a01936cc</code> docs(req): release requirements baseline v1.3 (spec-hardeni…<br><code>3bbb5650</code> docs(req): v1.3 spec-hardening round — Tier-B must-fix from…</td> </tr> </tbody> </table> <h3 id="req-auth">REQ-AUTH<a class="headerlink" href="#req-auth" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-AUTH-001</td> <td>verified</td> <td>All user authentication shall be delegated to an external OIDC provider; LQMS shall not store user passwords or second-…</td> <td>STR-016; ADR-0011</td> <td>api/api/KeycloakIntegrationTest.kt<br>api/api/ValidationJourneyTest.kt</td> <td>PQ: station 13 (Reading the setup health and signing out)</td> <td>identity/identity/IdentityProviderAdmin.kt</td> <td><code>78434617</code> feat(api): OIDC web-app/BFF auth + authenticated /me with J…<br><code>e7448848</code> docs(arch): accept ADR-0011 authentication via OIDC SSO + B…</td> </tr> <tr> <td>REQ-AUTH-002</td> <td>verified</td> <td>LQMS shall authenticate against any standards-compliant OIDC provider, configured per deployment (e.g.</td> <td>STR-016; ADR-0011</td> <td>api/api/KeycloakIntegrationTest.kt</td> <td>—</td> <td>identity/identity/IdentityProviderAdmin.kt</td> <td>—</td> </tr> <tr> <td>REQ-AUTH-003</td> <td>verified</td> <td>The web client shall use a server-side session (BFF): LQMS performs the OIDC Authorization Code flow with PKCE and hold…</td> <td>STR-016; ADR-0011</td> <td>api/api/FullStackBrowserSmokeTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-AUTH-004</td> <td>accepted-gap</td> <td>The session cookie shall be encrypted with a server-held key, httpOnly, Secure and SameSite, carrying no client-readabl… <em>(Cookie encryption/httpOnly/Secure/SameSite and the no-server-session-store model are Quarkus OIDC configuration per ADR-0028 (application.properties), not application code; per-request revocation teeth are tested under REQ-AUTH-006.)</em></td> <td>STR-003, STR-016; ADR-0011, ADR-0028</td> <td>—</td> <td>—</td> <td>—</td> <td><code>9db4f401</code> docs(req): release requirements-v1.4 baseline<br><code>85a60c48</code> docs(adr): ADR-0028 — stateless encrypted token-state cookie<br><code>78434617</code> feat(api): OIDC web-app/BFF auth + authenticated /me with J…</td> </tr> <tr> <td>REQ-AUTH-005</td> <td>accepted-gap</td> <td>Sessions shall enforce a configurable idle timeout and absolute maximum lifetime, after which re-authentication is requ… <em>(Session idle timeout and absolute maximum lifetime are enforced by the IdP (Keycloak SSO Session Idle/Max), honored by LQMS through the ADR-0028 token-refresh path — the same IdP-delegation pattern accepted for REQ-AUTH-004/007; documented in the deployment docs. Decision 2026-07-22: accepted-gap, no app-side timers.)</em></td> <td>STR-016; ADR-0011</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-AUTH-006</td> <td>verified</td> <td>Administrative revocation of access (user deactivation or role removal) shall take effect on the user's next request th…</td> <td>STR-016; ADR-0011, ADR-0028</td> <td>api/api/DeactivatedUserAccessTest.kt<br>api/api/FullStackBrowserSmokeTest.kt<br>api/api/ValidationJourneyTest.kt</td> <td>PQ: station 13 (Reading the setup health and signing out)</td> <td>api/api/auth/AuthenticatedUserService.kt</td> <td><code>9db4f401</code> docs(req): release requirements-v1.4 baseline<br><code>f9544324</code> feat(identity): require verified email for invite binding;…<br><code>b6995111</code> docs+config: reconcile design record with ADR-0028; restric…<br><code>560077e3</code> feat(api): reject deactivated users per request (REQ-AUTH-0…<br><code>85a60c48</code> docs(adr): ADR-0028 — stateless encrypted token-state cookie<br><code>78434617</code> feat(api): OIDC web-app/BFF auth + authenticated /me with J…</td> </tr> <tr> <td>REQ-AUTH-007</td> <td>accepted-gap</td> <td>State-changing requests shall be protected against CSRF (SameSite plus an anti-CSRF token or required custom header). <em>(CSRF control realized per ADR-0033: SameSite=Lax session cookie + JSON-only mutations (config/framework property, no app-code carrier; no token filter by decision).)</em></td> <td>STR-003; ADR-0011</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-AUTH-008</td> <td>verified</td> <td>Authentication shall not grant authorization: an authenticated user with no role assignment shall have no access to any…</td> <td>STR-003; ADR-0011, ADR-0009</td> <td>api/api/AuthBoundaryTest.kt<br>identity/identity/UserProvisioningTest.kt<br>scope/scope/AuthorizedRequestContextTest.kt</td> <td>—</td> <td>api/api/auth/MeResource.kt<br>identity/identity/UserProvisioning.kt<br>identity/identity/UserRepository.kt<br>scope/scope/AuthorizedRequestContext.kt</td> <td><code>b6995111</code> docs+config: reconcile design record with ADR-0028; restric…<br><code>78434617</code> feat(api): OIDC web-app/BFF auth + authenticated /me with J…<br><code>27d4cef0</code> feat(scope): authn->authz->RLS request bridge (REQ-AUTH-010)<br><code>2d55516d</code> feat(identity): JIT-provision / bind service for OIDC ident…</td> </tr> <tr> <td>REQ-AUTH-009</td> <td>verified</td> <td>On first successful authentication a user record shall be provisioned (JIT), keyed to a stable IdP subject identifier,…</td> <td>STR-006; ADR-0011, ADR-0063</td> <td>api/api/DocumentResourceTest.kt<br>api/api/KeycloakIntegrationTest.kt<br>api/api/MeResourceTest.kt<br>catalog/catalog/MembershipEmailInviteTest.kt<br>identity/identity/UserProvisioningTest.kt</td> <td>—</td> <td>api/api/auth/AuthenticatedUserService.kt<br>api/api/auth/MeResource.kt<br>catalog/catalog/membership/service/MembershipService.kt<br>catalog/catalog/person/repository/UserAdminRepository.kt<br>identity/identity/UserProvisioning.kt</td> <td><code>78434617</code> feat(api): OIDC web-app/BFF auth + authenticated /me with J…<br><code>2d55516d</code> feat(identity): JIT-provision / bind service for OIDC ident…</td> </tr> <tr> <td>REQ-AUTH-010</td> <td>verified</td> <td>On each authenticated request LQMS shall resolve the user's authorized scope set from role assignments and apply it as…</td> <td>STR-003; ADR-0011, ADR-0009</td> <td>api/api/DocumentResourceTest.kt<br>api/api/KeycloakIntegrationTest.kt<br>scope/scope/AuthorizedRequestContextTest.kt</td> <td>—</td> <td>scope/scope/AuthorizedRequestContext.kt</td> <td><code>27d4cef0</code> feat(scope): authn->authz->RLS request bridge (REQ-AUTH-010)</td> </tr> <tr> <td>REQ-AUTH-011</td> <td>verified</td> <td>API clients shall authenticate by OAuth2 <strong>bearer token</strong> validated against the configured OIDC provider — signature/JW…</td> <td>STR-013; ADR-0011, ADR-0005</td> <td>api/api/AuthenticatedUserServiceTest.kt<br>api/api/WrongAudienceTokenTest.kt</td> <td>—</td> <td>api/api/auth/AuthExceptionMappers.kt<br>api/api/auth/AuthenticatedUserService.kt</td> <td><code>d92857ff</code> docs(process,traceability,planning): RISK-008/009 controls…<br><code>914a234c</code> fix(document,catalog,audit,api,scope): the review wave — fo…<br><code>218e6931</code> feat(api): validate OIDC token audience (REQ-AUTH-011 harde…<br><code>ceb0f25a</code> feat(api): OIDC hybrid mode (bearer + BFF) + Keycloak integ…</td> </tr> </tbody> </table> <h3 id="req-bak">REQ-BAK<a class="headerlink" href="#req-bak" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-BAK-001</td> <td>accepted-gap</td> <td>The system shall create a full backup as a zip archive containing all data required to restore the entire installation. <em>(Realized by the deploy-side backup script (deploy/backup.sh: blobs-first-then-DB, pg_dump -Fc, Keycloak realm export, manifest, off-box copy, 35-day prune) — deploy tooling outside the code-scan globs; ADR-0060 B-1a. (Supersedes the 2026-07-05 empty-module note.))</em></td> <td>STR-010; ADR-0060</td> <td>—</td> <td>—</td> <td>backup/backup/BackupModule.kt<br>persistence/V102__system_maintenance_surface.sql</td> <td>—</td> </tr> <tr> <td>REQ-BAK-002</td> <td>future</td> <td>The system shall create a per-scope backup as a self-contained zip archive (database content plus all referenced blobs… <em>(Per-scope backup archive — operational backup/restore, future increment (not in MVP, release-plan.md; ADR-0002 isolation).)</em></td> <td>STR-010; ADR-0002, ADR-0060</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-BAK-003</td> <td>accepted-gap</td> <td>Backups shall be restorable on the same or a different server, yielding a fully functional state; the search index may… <em>(Realized by deploy/restore.sh + the weekly deploy/verify-backup.sh restore rehearsal (migrations/health/manifest-SHA/blob-rehash/ref-closure/search) — deploy tooling outside the code-scan globs; ADR-0060 B-2a.)</em></td> <td>STR-010; ADR-0006, ADR-0060</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-BAK-004</td> <td>accepted-gap</td> <td>Backup creation shall verify blob integrity (re-hash and compare) and report any mismatch. <em>(Realized: backup.sh re-hashes every blob in the copy pass and verify-backup.sh re-hashes the restored store — deploy tooling outside the code-scan globs; ADR-0060.)</em></td> <td>STR-009; ADR-0001, ADR-0060</td> <td>—</td> <td>—</td> <td>storage/storage/BackupArchiveStore.kt<br>storage/storage/FilesystemBackupArchiveStore.kt</td> <td><code>6c4e17b8</code> feat(deploy): backup arc — ordered backup, restore runbook,…</td> </tr> <tr> <td>REQ-BAK-005</td> <td>future</td> <td>Per-scope backups shall contain no data of other scopes. <em>(Per-scope backup contains no other scope's data — verified once per-scope backup (BAK-002) is built; ADR-0002.)</em></td> <td>STR-003; ADR-0002</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-BAK-006</td> <td>verified</td> <td>The system shall offer an in-app, EXPORT_BACKUP-gated backup act: asynchronously executed (one at a time — a concurrent…</td> <td>STR-010; ADR-0116, ADR-0060, ADR-0018</td> <td>api/api/AdminSystemResourceTest.kt<br>backup/backup/BackupServiceTest.kt</td> <td>—</td> <td>api/api/backup/AdminSystemResource.kt</td> <td><code>de8db2af</code> docs(requirements): baseline v2.1 — the ADR-0116 delta stam…<br><code>efe6223a</code> feat(backup,api,webui,persistence,deploy): ADR-0116 realize…<br><code>80804346</code> docs(requirements): REQ-BAK-006/007 + REQ-ADM-012 — the ADR…</td> </tr> <tr> <td>REQ-BAK-007</td> <td>verified</td> <td>The system shall present backup EVIDENCE on the admin System surface: the last recorded backup (time, size, blob count,…</td> <td>STR-010, STR-009; ADR-0116</td> <td>api/api/AdminSystemResourceTest.kt<br>backup/backup/BackupServiceTest.kt</td> <td>—</td> <td>api/api/backup/AdminSystemResource.kt</td> <td><code>de8db2af</code> docs(requirements): baseline v2.1 — the ADR-0116 delta stam…<br><code>efe6223a</code> feat(backup,api,webui,persistence,deploy): ADR-0116 realize…<br><code>80804346</code> docs(requirements): REQ-BAK-006/007 + REQ-ADM-012 — the ADR…</td> </tr> </tbody> </table> <h3 id="req-cat">REQ-CAT<a class="headerlink" href="#req-cat" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-CAT-001</td> <td>verified</td> <td>Roles shall be defined in a global catalog (name, description, translations), maintainable by authorized users without…</td> <td>STR-006; ADR-0004</td> <td>catalog/catalog/CatalogSchemaTest.kt</td> <td>—</td> <td>persistence/V004__catalog_and_permissions.sql</td> <td><code>d23c3fe9</code> feat(catalog): authorization catalogs + permission model (P…</td> </tr> <tr> <td>REQ-CAT-002</td> <td>verified</td> <td>Document types shall be defined in a global catalog including type prefix, numbering mode, and translations.</td> <td>STR-001; ADR-0004</td> <td>api/api/AdminDocumentTypeResourceTest.kt<br>api/api/OpenApiSpecTest.kt<br>api/e2e/admin-document-types.spec.ts<br>api/e2e/screenshots.spec.ts<br>catalog/catalog/CatalogSchemaTest.kt<br>catalog/catalog/DocumentTypeAdminServiceTest.kt</td> <td>—</td> <td>api/api/platform/ServiceProducers.kt<br>api/api/types/AdminDocumentTypeResource.kt<br>api/src/app/app.routes.ts<br>api/src/app/core/lqms-api.ts<br>api/src/app/features/admin/document-types-page.ts<br>catalog/catalog/types/service/DocumentTypeAdminService.kt<br>persistence/V004__catalog_and_permissions.sql</td> <td><code>d23c3fe9</code> feat(catalog): authorization catalogs + permission model (P…</td> </tr> <tr> <td>REQ-CAT-003</td> <td>verified</td> <td>Each scope shall activate the subset of catalog roles and document types it uses; non-activated entries shall not appea…</td> <td>STR-006, STR-007; ADR-0004</td> <td>api/api/ValidationJourneyTest.kt<br>catalog/catalog/DirectoryServiceTest.kt</td> <td>PQ: station 1 (Registering a customer and a project)</td> <td>api/api/types/AdminDocumentTypeResource.kt<br>catalog/catalog/types/service/DocumentTypeAdminService.kt<br>persistence/V005__role_assignment_and_resolution.sql</td> <td>—</td> </tr> <tr> <td>REQ-CAT-004</td> <td>verified</td> <td>Users shall be assignable to activated roles per scope; one user may hold multiple roles in the same scope.</td> <td>STR-006; ADR-0004</td> <td>api/api/ValidationJourneyTest.kt<br>catalog/catalog/AuthzResolutionTest.kt</td> <td>PQ: station 1 (Registering a customer and a project)<br>PQ: station 2 (Staffing the functions and naming who is accountable)<br>PQ: station 14 (Inviting a person into the customer's organization, and their accepting it)</td> <td>catalog/catalog/person/repository/RoleRepository.kt<br>persistence/V005__role_assignment_and_resolution.sql<br>persistence/V015__effective_roles_function.sql<br>persistence/V037__scope_users_function.sql</td> <td><code>83201d00</code> feat(catalog): role assignments + authorization resolution…</td> </tr> <tr> <td>REQ-CAT-005</td> <td>verified</td> <td>Review policies shall only reference catalog roles; activating a policy shall be rejected if it references roles not ac…</td> <td>STR-002; ADR-0004</td> <td>catalog/catalog/AuthzResolutionTest.kt<br>document/document/ReviewPolicyServiceTest.kt</td> <td>—</td> <td>catalog/catalog/person/repository/RoleRepository.kt<br>catalog/catalog/person/repository/UserAdminRepository.kt<br>persistence/V005__role_assignment_and_resolution.sql<br>persistence/V117__base_reader_role.sql</td> <td><code>6e517ca5</code> fix(catalog,document): humanize user-facing "not activated"…<br><code>b6f5d429</code> fix(webui): assignment role picker offers only the scope's…<br><code>83201d00</code> feat(catalog): role assignments + authorization resolution…</td> </tr> <tr> <td>REQ-CAT-006</td> <td>future</td> <td>The derive operation shall validate that all roles referenced by the applicable review policy are activated (and staffe… <em>(The derive-time review-policy role-fit validation/prompt is a deferred slice by the code's own record (DeriveService: 'the review-policy-fit prompt is a later slice'); the existing CAT-006-tagged guard covers type activation only, a different property. ADR-0034.)</em></td> <td>STR-004; ADR-0004</td> <td>document/document/DocumentServiceTest.kt</td> <td>—</td> <td>catalog/catalog/person/repository/RoleRepository.kt<br>catalog/catalog/types/repository/ActivationRepository.kt<br>document/document/core/service/DocumentService.kt<br>document/document/lifecycle/service/DeriveService.kt<br>document/document/lifecycle/service/InstantiateService.kt<br>persistence/V005__role_assignment_and_resolution.sql<br>persistence/V117__base_reader_role.sql</td> <td><code>97c08195</code> test(traceability): implemented-untested backfill — 5 of 7…<br><code>7070565a</code> test(traceability): backfill REQ citations for 5 impl-untes…<br><code>33371734</code> docs(adr): ADR-0031 (proposed) — base-readability enforceme…<br><code>83201d00</code> feat(catalog): role assignments + authorization resolution…</td> </tr> <tr> <td>REQ-CAT-007</td> <td>verified</td> <td>Free-form, scope-local role definitions shall not be possible.</td> <td>STR-006; ADR-0004</td> <td>catalog/catalog/CatalogSchemaTest.kt</td> <td>—</td> <td>catalog/catalog/person/repository/RoleRepository.kt</td> <td><code>97c08195</code> test(traceability): implemented-untested backfill — 5 of 7…<br><code>7070565a</code> test(traceability): backfill REQ citations for 5 impl-untes…</td> </tr> <tr> <td>REQ-CAT-008</td> <td>GAP</td> <td>Where a guided setup requires catalog entries that do not exist, a caller holding catalog administration shall be offer…</td> <td>STR-006; ADR-0004 (decisions: docs/planning/feedback-2026-08-06.md #9/#11/#13)</td> <td>—</td> <td>—</td> <td>—</td> <td><code>25fe83b2</code> docs(requirements): baseline v2.0 — the five post-v1.9 func…</td> </tr> </tbody> </table> <h3 id="req-doc">REQ-DOC<a class="headerlink" href="#req-doc" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-DOC-001</td> <td>verified</td> <td>Every document shall belong to exactly one scope and have exactly one document type from the types activated in that sc…</td> <td>STR-001, STR-003; ADR-0002, ADR-0004</td> <td>api/api/ValidationJourneyTest.kt<br>document/document/DocumentSchemaTest.kt</td> <td>PQ: station 4 (Writing a controlled procedure)</td> <td>persistence/V007__document.sql</td> <td><code>1be7cf4d</code> feat(document): Phase 3 slice 3.1 — document table + first…</td> </tr> <tr> <td>REQ-DOC-002</td> <td>verified</td> <td>Every document shall carry an immutable, human-readable document ID of the form [<SCOPE-CODE>-]<TYPE-PREFIX>-<DESIGNATO…</td> <td>STR-001; §8.1</td> <td>api/api/DocumentResourceTest.kt<br>api/api/ValidationJourneyTest.kt<br>document/document/ContentColumnLifecycleInventoryTest.kt<br>document/document/DocumentSchemaTest.kt<br>document/document/DocumentServiceTest.kt</td> <td>PQ: station 4 (Writing a controlled procedure)</td> <td>catalog/catalog/types/service/DocumentTypeAdminService.kt<br>document/document/arrival/service/ImportService.kt<br>document/document/core/repository/DocumentRepository.kt<br>document/document/core/service/DocumentService.kt<br>persistence/V007__document.sql<br>persistence/V012__draft_content_and_numbering.sql</td> <td><code>c7ae9fe8</code> fix(document): Phase 3 review fixes — permission gating + c…<br><code>1be7cf4d</code> feat(document): Phase 3 slice 3.1 — document table + first…<br><code>a01936cc</code> docs(req): release requirements baseline v1.3 (spec-hardeni…</td> </tr> <tr> <td>REQ-DOC-003</td> <td>verified</td> <td>The designator shall be an auto-sequence number (per scope and type) or a validated slug ([A-Z0-9_], length-limited, re…</td> <td>STR-001; §8.1</td> <td>api/api/ValidationJourneyTest.kt<br>document/document/ContentColumnLifecycleInventoryTest.kt<br>document/document/DocumentServiceTest.kt</td> <td>PQ: station 4 (Writing a controlled procedure)</td> <td>api/api/types/AdminDocumentTypeResource.kt<br>api/src/app/core/models.ts<br>api/src/app/features/admin/document-types-page.ts<br>api/src/app/features/admin/setup-wizard/setup-wizard.ts<br>catalog/catalog/types/service/DocumentTypeAdminService.kt<br>document/document/core/repository/DocumentRepository.kt<br>document/document/core/service/DocumentService.kt<br>persistence/V004__catalog_and_permissions.sql<br>persistence/V007__document.sql<br>persistence/V012__draft_content_and_numbering.sql</td> <td><code>c7ae9fe8</code> fix(document): Phase 3 review fixes — permission gating + c…</td> </tr> <tr> <td>REQ-DOC-004</td> <td>verified</td> <td>A document shall consist of an ordered series of versions; every version shall record its author, life-cycle state, and…</td> <td>STR-001, STR-009; ADR-0003</td> <td>api/api/FullStackBrowserSmokeTest.kt<br>api/api/ValidationJourneyTest.kt<br>document/document/DocumentServiceTest.kt<br>document/document/DocumentVersionSchemaTest.kt</td> <td>PQ: station 4 (Writing a controlled procedure)</td> <td>document/document/core/repository/VersionRepository.kt<br>document/document/core/service/DocumentService.kt<br>persistence/V009__document_version.sql</td> <td><code>77190a84</code> fix(api-test): fullstack smoke — count version rows, not mu…<br><code>87d61045</code> test(e2e): revision-flow full-stack browser E2E (CSV eviden…</td> </tr> <tr> <td>REQ-DOC-005</td> <td>verified</td> <td>Version content shall be either authored in-tool (structured content) or uploaded file(s); both shall behave identicall…</td> <td>STR-001, STR-007; ADR-0045, ADR-0057/0058</td> <td>api/api/ValidationJourneyTest.kt<br>document/document/AttachmentServiceTest.kt<br>document/document/ContentPartSchemaTest.kt<br>document/document/PdfExportServiceTest.kt</td> <td>PQ: station 4 (Writing a controlled procedure)</td> <td>document/document/content/service/AttachmentService.kt<br>persistence/V010__content_part.sql<br>persistence/V030__draft_attachment.sql<br>persistence/V048__file_attachments.sql</td> <td><code>af896454</code> docs(requirements): v1.5 baseline prepared — four-eyes REQ-…<br><code>7d018e1a</code> docs: currency audit after the 2026-07-03 change wave<br><code>c7ae9fe8</code> fix(document): Phase 3 review fixes — permission gating + c…<br><code>558e92f1</code> docs(req): release requirements baseline v1.2<br><code>f2d7249a</code> docs(req): resolve GAP-12/13/14 core clarifications (ADR-00…</td> </tr> <tr> <td>REQ-DOC-006</td> <td>verified</td> <td>On every content-freezing life-cycle transition, version content shall be serialized to a canonical form, hashed (SHA-2…</td> <td>STR-009; ADR-0001, ADR-0057</td> <td>document/document/DocumentServiceTest.kt</td> <td>—</td> <td>document/document/core/service/DocumentService.kt<br>persistence/V039__content_format_tree_record.sql<br>persistence/V040__tree_record_integrity.sql</td> <td>—</td> </tr> <tr> <td>REQ-DOC-007</td> <td>verified</td> <td>The content of a released version shall be reproducible byte-exactly via its hash, and the system shall provide an inte…</td> <td>STR-009; ADR-0001</td> <td>api/api/ArrivalRoundTripFullStackTest.kt<br>document/document/BlobGcRaceTest.kt<br>document/document/DocumentServiceTest.kt<br>document/document/ImportServiceTest.kt<br>storage/storage/FilesystemContentStoreTest.kt</td> <td>—</td> <td>document/document/core/repository/VersionRepository.kt<br>document/document/core/service/DocumentService.kt<br>persistence/V039__content_format_tree_record.sql<br>persistence/V040__tree_record_integrity.sql<br>storage/storage/ContentStore.kt</td> <td><code>85793870</code> feat(document): Phase 3 slice 3.7 (part 2) — editDraft + fr…<br><code>b2ad02e4</code> feat(storage): Phase 3 slice 3.6 — content-addressed blob s…</td> </tr> <tr> <td>REQ-DOC-008</td> <td>verified</td> <td>Blob storage shall be accessed exclusively through a storage interface with a file-system implementation; an S3-compati…</td> <td>STR-013; ADR-0001, ADR-0005</td> <td>storage/storage/FilesystemContentStoreTest.kt</td> <td>—</td> <td>storage/storage/ContentStore.kt</td> <td>—</td> </tr> <tr> <td>REQ-DOC-009</td> <td>verified</td> <td>The blob directory layout shall be partitioned by scope; content shall never be deduplicated across scopes.</td> <td>STR-003; ADR-0001</td> <td>document/document/BlobGcSweepServiceTest.kt<br>document/document/DisposalServiceTest.kt<br>scope/scope/BlobQuarantineRlsSeparationTest.kt<br>storage/storage/FilesystemContentStoreTest.kt</td> <td>—</td> <td>document/document/blob/repository/BlobGcRepository.kt<br>document/document/content/repository/AttachmentRepository.kt<br>storage/storage/ContentStore.kt<br>storage/storage/FilesystemContentStore.kt</td> <td><code>b2ad02e4</code> feat(storage): Phase 3 slice 3.6 — content-addressed blob s…</td> </tr> <tr> <td>REQ-DOC-010</td> <td>verified</td> <td>The derive operation shall copy the full content of a <em>released</em> source version into the target scope as a new document…</td> <td>STR-004; ADR-0002</td> <td>api/api/DeriveResourceTest.kt<br>document/document/DeriveServiceTest.kt</td> <td>—</td> <td>document/document/lifecycle/service/DeriveService.kt<br>persistence/V017__relationships_and_derive_source.sql</td> <td><code>293c748a</code> feat(document): copy-on-derive DeriveService (ADR-0031 slic…<br><code>33371734</code> docs(adr): ADR-0031 (proposed) — base-readability enforceme…</td> </tr> <tr> <td>REQ-DOC-011</td> <td>verified</td> <td>Derived documents shall inherit the source's full document ID unchanged.</td> <td>STR-004; §8.1</td> <td>document/document/DeriveServiceTest.kt</td> <td>—</td> <td>document/document/lifecycle/service/DeriveService.kt<br>persistence/V017__relationships_and_derive_source.sql</td> <td><code>293c748a</code> feat(document): copy-on-derive DeriveService (ADR-0031 slic…<br><code>33371734</code> docs(adr): ADR-0031 (proposed) — base-readability enforceme…</td> </tr> <tr> <td>REQ-DOC-012</td> <td>verified</td> <td>When a new version of a derivation source is released, the system shall notify the affected scopes; derived documents s…</td> <td>STR-005; ADR-0002</td> <td>notification/notification/FanoutDeploymentCheckTest.kt<br>notification/notification/SourceFanoutTest.kt</td> <td>—</td> <td>document/document/lifecycle/service/DeriveService.kt<br>notification/notification/FanoutDeploymentCheck.kt<br>persistence/V020__source_event_fanout.sql<br>persistence/V021__fanout_notifications_and_hardening.sql</td> <td><code>0e7aa06c</code> docs: ADR-0035 (fan-out contract as shipped) + review-round…<br><code>ccc5d088</code> feat(api): derive REST endpoint (ADR-0031 slice 3)<br><code>33371734</code> docs(adr): ADR-0031 (proposed) — base-readability enforceme…</td> </tr> <tr> <td>REQ-DOC-013</td> <td>verified</td> <td>A garbage-collection job shall remove blobs no longer referenced by any version; referenced blobs shall never be delete…</td> <td>STR-009; ADR-0001, ADR-0092</td> <td>document/document/BlobGcRaceTest.kt<br>document/document/BlobGcSweepServiceTest.kt<br>document/document/BlobHashColumnInventoryTest.kt<br>document/document/DisposalServiceTest.kt<br>scope/scope/BlobQuarantineRlsSeparationTest.kt</td> <td>—</td> <td>api/api/blob/BlobGcScheduler.kt<br>api/api/platform/ServiceProducers.kt<br>document/document/blob/repository/BlobGcRepository.kt<br>document/document/blob/service/BlobGcSweepService.kt<br>document/document/records/service/DisposalService.kt<br>persistence/V065__blob_quarantine.sql<br>storage/storage/ContentStore.kt</td> <td><code>396eec8d</code> fix(document): disposal blob-deletion consults all four blo…<br><code>2c3b51f2</code> docs(requirements): prepare the v1.8 delta — obligations, D…<br><code>673d4c24</code> feat(document,storage,api): orphan-blob GC with quarantine…<br><code>9a8e0394</code> feat(document,storage,api): orphan-blob GC with a quarantin…</td> </tr> <tr> <td>REQ-DOC-014</td> <td>verified</td> <td>A version's content shall be an ordered set of one or more named content parts, each stored as an immutable blob (ADR-0…</td> <td>STR-001; ADR-0017, ADR-0045, ADR-0069, ADR-0065</td> <td>document/document/AttachmentServiceTest.kt<br>document/document/ContentPartSchemaTest.kt</td> <td>—</td> <td>document/document/core/service/DocumentService.kt<br>persistence/V010__content_part.sql<br>persistence/V030__draft_attachment.sql<br>persistence/V039__content_format_tree_record.sql<br>persistence/V040__tree_record_integrity.sql<br>persistence/V048__file_attachments.sql</td> <td><code>af896454</code> docs(requirements): v1.5 baseline prepared — four-eyes REQ-…<br><code>558e92f1</code> docs(req): release requirements baseline v1.2<br><code>f2d7249a</code> docs(req): resolve GAP-12/13/14 core clarifications (ADR-00…</td> </tr> <tr> <td>REQ-DOC-015</td> <td>verified</td> <td>The version's integrity/signing hash shall be a manifest hash computed over the ordered set of parts (part name, part h…</td> <td>STR-009; ADR-0017, ADR-0014, ADR-0025</td> <td>api/api/ArrivalRoundTripFullStackTest.kt<br>document/document/AttachmentServiceTest.kt<br>document/document/DocumentServiceTest.kt<br>document/document/ImportServiceTest.kt</td> <td>—</td> <td>document/document/content/service/AttachmentService.kt<br>document/document/core/repository/VersionRepository.kt<br>document/document/core/service/DocumentService.kt<br>document/document/lifecycle/service/LifecycleService.kt<br>persistence/V030__draft_attachment.sql<br>persistence/V039__content_format_tree_record.sql<br>persistence/V040__tree_record_integrity.sql<br>persistence/V048__file_attachments.sql</td> <td><code>c7ae9fe8</code> fix(document): Phase 3 review fixes — permission gating + c…<br><code>a01936cc</code> docs(req): release requirements baseline v1.3 (spec-hardeni…<br><code>3bbb5650</code> docs(req): v1.3 spec-hardening round — Tier-B must-fix from…<br><code>558e92f1</code> docs(req): release requirements baseline v1.2<br><code>f2d7249a</code> docs(req): resolve GAP-12/13/14 core clarifications (ADR-00…</td> </tr> <tr> <td>REQ-DOC-016</td> <td>verified</td> <td>Concurrent edits to a draft shall use optimistic locking: a save based on a stale version token shall be rejected with…</td> <td>STR-001, STR-007; ADR-0003</td> <td>document/document/ContentColumnLifecycleInventoryTest.kt<br>document/document/DocumentServiceTest.kt</td> <td>—</td> <td>document/document/core/repository/VersionRepository.kt<br>document/document/core/service/DocumentService.kt<br>persistence/V009__document_version.sql<br>persistence/V012__draft_content_and_numbering.sql<br>persistence/V125__draft_save_points.sql</td> <td><code>85793870</code> feat(document): Phase 3 slice 3.7 (part 2) — editDraft + fr…<br><code>b2223784</code> feat(document): Phase 3 slices 3.3-3.5 — version, content_p…<br><code>558e92f1</code> docs(req): release requirements baseline v1.2<br><code>7c74a466</code> docs(req): triage Tier-3 gaps GAP-15..22 (ADR-0021/0022/002…</td> </tr> <tr> <td>REQ-DOC-017</td> <td>verified</td> <td>Creating a new version of an existing document shall require a change description (reason/summary of what changed); it…</td> <td>STR-009; ADR-0001</td> <td>api/api/FullStackBrowserSmokeTest.kt<br>document/document/ContentColumnLifecycleInventoryTest.kt<br>document/document/DocumentServiceTest.kt</td> <td>—</td> <td>api/src/app/core/lqms-api.ts<br>api/src/app/core/models.ts<br>document/document/core/DocumentValidation.kt<br>document/document/core/repository/VersionRepository.kt<br>document/document/core/service/DocumentService.kt<br>document/document/core/service/FolderService.kt<br>document/document/records/repository/DisposalRepository.kt<br>document/document/records/service/PeriodicReviewService.kt<br>persistence/V009__document_version.sql<br>persistence/V052__change_impact.sql</td> <td><code>87d61045</code> test(e2e): revision-flow full-stack browser E2E (CSV eviden…<br><code>641e83b6</code> feat(api): Phase 4 REST endpoints for the document life cyc…<br><code>3d4295c3</code> feat(lifecycle): revoke + new-version — document state mach…<br><code>ac9d977f</code> docs(adr): ADR-0030 — review & life-cycle realization model…<br><code>c7ae9fe8</code> fix(document): Phase 3 review fixes — permission gating + c…<br><code>a01936cc</code> docs(req): release requirements baseline v1.3 (spec-hardeni…<br><code>3bbb5650</code> docs(req): v1.3 spec-hardening round — Tier-B must-fix from…</td> </tr> <tr> <td>REQ-DOC-018</td> <td>verified</td> <td>The storage interface shall support deletion of a blob by hash; disposal (REQ-DPR-005) shall delete a version's content…</td> <td>STR-021; ADR-0025, ADR-0001</td> <td>api/api/DisposalResourceTest.kt<br>document/document/DisposalServiceTest.kt<br>storage/storage/FilesystemContentStoreTest.kt</td> <td>—</td> <td>persistence/V027__disposal.sql<br>storage/storage/ContentStore.kt</td> <td><code>24bfe733</code> feat(document,storage,api,webui): disposal execution (ADR-0…<br><code>b2ad02e4</code> feat(storage): Phase 3 slice 3.6 — content-addressed blob s…<br><code>a01936cc</code> docs(req): release requirements baseline v1.3 (spec-hardeni…<br><code>3bbb5650</code> docs(req): v1.3 spec-hardening round — Tier-B must-fix from…</td> </tr> <tr> <td>REQ-DOC-019</td> <td>verified</td> <td>The system shall provide, per scope, a folder tree for organizing documents: folder rows are scope-keyed content-plane…</td> <td>STR-007, STR-003; ADR-0048, ADR-0027</td> <td>api/api/FolderResourceTest.kt<br>document/document/FolderSchemaTest.kt<br>document/document/FolderServiceTest.kt<br>scope/scope/RlsSeparationTest.kt</td> <td>—</td> <td>document/document/core/repository/FolderRepository.kt<br>document/document/core/service/FolderService.kt</td> <td><code>a93b6b95</code> docs(requirements): v1.6 baseline prepared — 21 new rows fo…</td> </tr> <tr> <td>REQ-DOC-020</td> <td>verified</td> <td>Each document shall have an optional folder placement within its scope (nullable; unset = scope root); all of a documen…</td> <td>STR-001, STR-009; ADR-0048</td> <td>api/api/FolderResourceTest.kt<br>document/document/DeriveServiceTest.kt<br>document/document/FolderServiceTest.kt</td> <td>—</td> <td>document/document/core/service/FolderService.kt<br>persistence/V101__document_folder_position.sql</td> <td>—</td> </tr> <tr> <td>REQ-DOC-021</td> <td>verified</td> <td>Folder create, rename, reorder, and re-parent operations and document moves shall be gated by a dedicated ORGANIZE_DOCU…</td> <td>STR-003, STR-009; ADR-0048, ADR-0004, REQ-AUD-001</td> <td>api/api/FolderResourceTest.kt<br>document/document/FolderServiceTest.kt</td> <td>—</td> <td>document/document/core/service/FolderService.kt<br>persistence/V101__document_folder_position.sql</td> <td>—</td> </tr> <tr> <td>REQ-DOC-022</td> <td>verified</td> <td>Each document type shall carry exactly one category from the fixed set PRESCRIPTIVE, RECORD, TEMPLATE, acting as a capa…</td> <td>STR-001, STR-020, STR-021; ADR-0049, ADR-0015, ADR-0040, ADR-0004</td> <td>api/api/DocumentTypeResourceTest.kt<br>api/api/ReviewSettingsResourceTest.kt<br>catalog/catalog/CatalogSchemaTest.kt<br>notification/notification/PeriodicReviewSweepTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-DOC-023</td> <td>verified</td> <td>A TEMPLATE-category document body may declare template variables in a fenced template-vars block (one `key \</td> <td>label \</td> <td>document/document/TemplateInstantiationTest.kt<br>document/document/TemplateVarsTest.kt</td> <td>—</td> <td>document/document/lifecycle/service/LifecycleService.kt</td> <td>—</td> </tr> <tr> <td>REQ-DOC-024</td> <td>verified</td> <td>Instantiating a template shall be permitted only from a RELEASED, currently-effective TEMPLATE version and shall requir…</td> <td>STR-004, STR-001, STR-009; ADR-0049</td> <td>api/api/InstantiateResourceTest.kt<br>document/document/TemplateInstantiationTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-DOC-025</td> <td>verified</td> <td>The controlled markdown record format shall support in-text document links of the form <a href="doc:<DOC-ID>">text</a>, with an op…</td> <td>STR-001, STR-009, STR-008; ADR-0051, ADR-0057</td> <td>api/api/DocumentResolveResourceTest.kt<br>api/e2e/doc-links.spec.ts<br>document/document/DocumentResolveTest.kt</td> <td>—</td> <td>api/src/app/core/markdown.ts</td> <td>—</td> </tr> <tr> <td>REQ-DOC-026</td> <td>verified</td> <td>A version's attachments shall fall into two classes: DISPLAY (the sniffed image set — PNG/JPEG and the Excalidraw SVG/s…</td> <td>STR-001, STR-009; ADR-0069, ADR-0045</td> <td>api/api/AttachmentResourceTest.kt<br>api/e2e/file-attachments.spec.ts<br>document/document/AttachmentServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-DOC-027</td> <td>verified</td> <td>FILE-class attachments shall be download-only: the serving endpoint shall force Content-Disposition: attachment togethe…</td> <td>STR-009, STR-014; ADR-0069</td> <td>api/api/AttachmentResourceTest.kt<br>api/e2e/file-attachments.spec.ts</td> <td>—</td> <td>api/api/backup/AdminSystemResource.kt</td> <td>—</td> </tr> <tr> <td>REQ-DOC-028</td> <td>verified</td> <td>Attachments shall share the version content lifecycle: DRAFT-only upload and delete (EDIT_DRAFT-gated, size- and count-…</td> <td>STR-001, STR-003, STR-009; ADR-0069, ADR-0065, ADR-0045</td> <td>document/document/AttachmentServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-DOC-029</td> <td>verified</td> <td>A diagram shall be a content-tree node referencing a content-part pair — the editable Excalidraw scene.json source plus…</td> <td>STR-001, STR-007; ADR-0065, ADR-0072, ADR-0057, ADR-0045</td> <td>api/e2e/diagram.spec.ts<br>document/document/AttachmentServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-DOC-030</td> <td>verified</td> <td>A diagram's SVG shall be displayed as an <img> through the attachment: resolver (structurally scoping the SVG's @font-f…</td> <td>STR-014, STR-007; ADR-0065, ADR-0072</td> <td>api/e2e/diagram.spec.ts</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-DOC-031</td> <td>verified</td> <td>Creating a new version shall carry a reason for change (REQ-DOC-017: <em>why</em> the change is made, required) plus an option…</td> <td>STR-009; ADR-0001 (ISO 13485 §4.2.4)</td> <td>api/api/EndpointBodyBindingTest.kt<br>api/e2e/change-reason.spec.ts<br>document/document/DocumentServiceTest.kt<br>document/document/LifecycleServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-DOC-032</td> <td>verified</td> <td>An imported document's version numbering shall continue the source system's sequence (a create may start at a provenanc…</td> <td>STR-026, STR-009; ADR-0075, ADR-0068</td> <td>document/document/DisposalServiceTest.kt<br>document/document/DocumentServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-DOC-033</td> <td>verified</td> <td>A post-working version — RELEASED (any effective standing) or REVOKED — shall export as a server-rendered PDF via the c…</td> <td>STR-009, STR-011; ADR-0074, ADR-0057, ADR-0062, ADR-0083</td> <td>api/api/ValidationJourneyTest.kt<br>api/e2e/pdf-export.spec.ts<br>document/document/PdfExportServiceTest.kt</td> <td>PQ: station 7 (Releasing the effective version)</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-DOC-034</td> <td>verified</td> <td>A requirement shall be a keyed block INSIDE a controlled document (tree node requirement, fence :::requirement), never…</td> <td>non-functional \</td> <td>api/e2e/requirement.spec.ts<br>document/document/RequirementLogicTest.kt<br>document/document/RequirementRegistryServiceTest.kt</td> <td>—</td> <td>—</td> <td><code>bfd379ec</code> docs(requirements): prepare the v1.9 delta — Stage C valida…<br><code>f2b93b49</code> docs(requirements): prepare the v1.7 delta — trace/risk/aud…</td> </tr> <tr> <td>REQ-DOC-035</td> <td>verified</td> <td>A requirement item shall be one concrete TYPE of a generalized trace item — a keyed item inside a controlled document d…</td> <td>STR-001, STR-009, STR-027; ADR-0078, ADR-0077, ADR-0057</td> <td>document/document/TraceItemGeneralizationTest.kt</td> <td>—</td> <td>—</td> <td><code>db5ec3ee</code> feat!(model): the born-free rename — system-requirement, sl…</td> </tr> <tr> <td>REQ-DOC-036</td> <td>verified</td> <td>The PDF renderer (REQ-DOC-033) shall emit navigation as CONTEXTS of the one render path, not a second surface: every he…</td> <td>STR-009, STR-011; ADR-0074, ADR-0083, ADR-0051</td> <td>document/document/PdfExportServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-DOC-037</td> <td>verified</td> <td>The system shall export a per-scope AUDIT PACK (GET /api/scopes/{scopeId}/audit-pack) that streams a zip containing the…</td> <td>STR-009, STR-011, STR-003, STR-027; ADR-0083, ADR-0074, ADR-0060, ADR-0069</td> <td>api/api/ValidationJourneyTest.kt<br>api/e2e/audit-pack.spec.ts<br>document/document/PdfExportServiceTest.kt</td> <td>PQ: station 11 (Exporting the project as an audit pack)</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-DOC-038</td> <td>verified</td> <td>The garbage-collection job (REQ-DOC-013) shall delete an orphan blob in TWO phases — quarantine, then purge.</td> <td>STR-009; ADR-0092, ADR-0025, ADR-0042</td> <td>document/document/BlobGcSweepServiceTest.kt<br>document/document/BlobHashColumnInventoryTest.kt</td> <td>—</td> <td>—</td> <td><code>f0691e82</code> docs(requirements): v1.8 delta PREPARED — 9 rows, all verif…<br><code>2c3b51f2</code> docs(requirements): prepare the v1.8 delta — obligations, D…</td> </tr> </tbody> </table> <h3 id="req-dpr">REQ-DPR<a class="headerlink" href="#req-dpr" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-DPR-001</td> <td>verified</td> <td>Personal data shall be minimized: LQMS shall store only the identity data necessary for attribution (stable subject, di…</td> <td>STR-021; ADR-0016</td> <td>identity/identity/DataProtectionMinimizationTest.kt</td> <td>—</td> <td>identity/identity/UserProvisioning.kt</td> <td><code>be140278</code> docs(arch): accept ADR-0016 retention, disposal & privacy (…</td> </tr> <tr> <td>REQ-DPR-002</td> <td>verified</td> <td>Attribution shall reference users by a stable internal identifier; human-readable personal data (name, email) shall res…</td> <td>STR-021; ADR-0016, ADR-0013</td> <td>identity/identity/DataProtectionMinimizationTest.kt</td> <td>—</td> <td>identity/identity/UserRepository.kt</td> <td>—</td> </tr> <tr> <td>REQ-DPR-003</td> <td>verified</td> <td>Retention periods shall be configurable per document/record type and scope, with a defined retention-start event; the s…</td> <td>STR-021; ADR-0016</td> <td>api/api/ScopeGovernanceResourceTest.kt<br>catalog/catalog/RetentionIntervalIsPlainDaysTest.kt<br>catalog/catalog/RetentionRuleServiceTest.kt<br>document/document/RetentionClockHonoursConfiguredDaysTest.kt<br>notification/notification/DisposalSweepTest.kt<br>notification/notification/TaskServiceTest.kt</td> <td>—</td> <td>catalog/catalog/provisioning/service/RetentionRuleService.kt<br>document/document/records/repository/DisposalRepository.kt<br>persistence/V025__retention_and_legal_hold.sql<br>persistence/V132__retention_interval_is_plain_days.sql</td> <td><code>97b7b320</code> feat(notification,persistence): disposal-due surfacing (ADR…</td> </tr> <tr> <td>REQ-DPR-004</td> <td>verified</td> <td>A legal hold shall be applicable to a scope or record set, suspending disposal regardless of retention expiry.</td> <td>STR-021; ADR-0016</td> <td>api/api/ScopeGovernanceResourceTest.kt<br>document/document/DisposalServiceTest.kt<br>notification/notification/DisposalSweepTest.kt</td> <td>—</td> <td>catalog/catalog/provisioning/service/LegalHoldService.kt<br>persistence/V025__retention_and_legal_hold.sql</td> <td><code>97b7b320</code> feat(notification,persistence): disposal-due surfacing (ADR…</td> </tr> <tr> <td>REQ-DPR-005</td> <td>verified</td> <td>Disposal at end of retention shall be a deliberate, authorized, audited action (not automatic); a disposal record (what…</td> <td>STR-021; ADR-0016, ADR-0012</td> <td>api/api/DisposalResourceTest.kt</td> <td>—</td> <td>persistence/V027__disposal.sql</td> <td><code>24bfe733</code> feat(document,storage,api,webui): disposal execution (ADR-0…</td> </tr> <tr> <td>REQ-DPR-006</td> <td>future</td> <td>Personal data held under a retention obligation shall be retained, not erased, during the retention period; the system… <em>(Retention/DPR automation is a Later capability (release-plan.md; ADR-0016); retain-under-hold behaviour is covered by REQ-DPR-004/005, the personal-data report of this requirement is not built yet.)</em></td> <td>STR-021; ADR-0016</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-DPR-007</td> <td>future</td> <td>Where erasure is warranted (no retention basis, non-regulated scope, end of retention, minimization correction), the sy… <em>(Erasure/anonymization workflow not built — DPR automation is Later (release-plan.md; ADR-0016); the ERASE_PERSONAL_DATA permission is seeded but unused.)</em></td> <td>STR-021; ADR-0016, ADR-0013</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-DPR-008</td> <td>future</td> <td>The system shall provide, on request, an export of the personal data held about an identified individual (access). <em>(Personal-data export (subject access) not built — DPR automation is Later (release-plan.md; ADR-0016).)</em></td> <td>STR-021; ADR-0016</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-DPR-009</td> <td>verified</td> <td>Identity claims (name, email) shall be rectifiable by refresh from the identity provider.</td> <td>STR-021; ADR-0016, ADR-0013</td> <td>identity/identity/UserProvisioningTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-DPR-010</td> <td>verified</td> <td>All retention-policy changes, legal holds, disposals, and erasures shall produce audit events.</td> <td>STR-009, STR-021; ADR-0016, REQ-AUD-001</td> <td>api/api/ScopeGovernanceResourceTest.kt<br>document/document/DisposalServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-DPR-011</td> <td>verified</td> <td>Disposal shall delete the record's content blobs and index rows in the live system (REQ-DOC-018, REQ-SRCH-011).</td> <td>STR-021; ADR-0025, ADR-0016</td> <td>document/document/ContentColumnLifecycleInventoryTest.kt<br>document/document/DisposalServiceTest.kt</td> <td>—</td> <td>backup/backup/BackupService.kt<br>persistence/V102__system_maintenance_surface.sql<br>storage/storage/BackupArchiveStore.kt</td> <td><code>a01936cc</code> docs(req): release requirements baseline v1.3 (spec-hardeni…<br><code>3bbb5650</code> docs(req): v1.3 spec-hardening round — Tier-B must-fix from…</td> </tr> </tbody> </table> <h3 id="req-eff">REQ-EFF<a class="headerlink" href="#req-eff" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-EFF-001</td> <td>verified</td> <td>A released version shall carry an effective date (effective_from), defaulting to its release time and settable to a fut…</td> <td>STR-020; ADR-0015, ADR-0003</td> <td>api/api/LifecycleResourceTest.kt<br>api/api/ValidationJourneyTest.kt<br>document/document/ContentColumnLifecycleInventoryTest.kt<br>document/document/DocumentServiceTest.kt<br>document/document/LifecycleServiceTest.kt<br>scope/scope/RlsPolicyInventoryTest.kt</td> <td>PQ: station 7 (Releasing the effective version)</td> <td>api/api/document/DocumentResource.kt<br>document/document/core/repository/VersionRepository.kt<br>document/document/lifecycle/service/LifecycleService.kt<br>persistence/V009__document_version.sql<br>persistence/V041__effective_version_views.sql<br>persistence/V088__version_release_stamp.sql</td> <td><code>a58ca7ea</code> feat(document,api): review REST, future-dated effectivity,…<br><code>3380af35</code> docs(arch): accept ADR-0015 effectivity & periodic review</td> </tr> <tr> <td>REQ-EFF-002</td> <td>verified</td> <td>The currently effective version of a document shall be derived as the released, non-revoked version with the latest eff…</td> <td>STR-020, STR-009; ADR-0015</td> <td>api/e2e/documents.spec.ts<br>document/document/DocumentServiceTest.kt<br>document/document/EffectiveVersionViewEquivalenceTest.kt<br>scope/scope/RlsPolicyInventoryTest.kt</td> <td>—</td> <td>api/src/app/core/doc-nav.ts<br>api/src/app/core/effective-standing.ts<br>api/src/app/core/models.ts<br>api/src/app/core/state-chip.ts<br>document/document/core/EffectiveStanding.kt<br>document/document/core/repository/VersionRepository.kt<br>document/document/core/service/DocumentService.kt<br>document/document/export/PdfRenderer.kt<br>document/document/export/repository/PdfExportRepository.kt<br>document/document/export/service/PdfExportService.kt<br>document/document/lifecycle/service/InstantiateService.kt<br>document/document/lifecycle/service/LifecycleService.kt<br>document/document/records/repository/PeriodicReviewRepository.kt<br>document/document/relation/repository/RelationshipRepository.kt<br>persistence/V041__effective_version_views.sql<br>persistence/V131__version_revocation_stamp.sql</td> <td><code>ce99795f</code> refactor(document): dedupe effective-standing rule; move js…<br><code>fd01e058</code> refactor(document): dedupe effective-standing rule; move js…<br><code>ebacc8a9</code> feat(document,api): scope audit pack — zip of effective-rel…<br><code>c76e669c</code> feat(document,audit,webui): history release/invalid-since t…<br><code>acdf19ec</code> feat(document,webui): superseded/future display standing (R…</td> </tr> <tr> <td>REQ-EFF-003</td> <td>verified</td> <td>A periodic review interval shall be configurable per document type, with an optional per-document override; the system…</td> <td>STR-020; ADR-0015, ADR-0004, ADR-0049</td> <td>api/api/ReviewSettingsResourceTest.kt<br>document/document/PeriodicReviewStatusTest.kt<br>document/document/ReviewSettingsServiceTest.kt<br>notification/notification/PeriodicReviewSweepTest.kt</td> <td>—</td> <td>api/api/document/DocumentResource.kt<br>api/src/app/core/lqms-api.ts<br>document/document/core/repository/DocumentRepository.kt<br>document/document/lifecycle/service/ReviewSettingsService.kt<br>persistence/V023__periodic_review_and_validity.sql<br>persistence/V133__review_interval_is_plain_days.sql</td> <td><code>ca729ad2</code> docs(traceability): v1.8 citation backfill — 164/247 verifi…<br><code>a93b6b95</code> docs(requirements): v1.6 baseline prepared — 21 new rows fo…<br><code>27a44c25</code> feat(document,notification): periodic review core (ADR-0038…</td> </tr> <tr> <td>REQ-EFF-004</td> <td>verified</td> <td>A periodic review shall be recordable with reviewer(s), date, and outcome: "confirmed unchanged" shall reset the next-r…</td> <td>STR-020, STR-009; ADR-0015, ADR-0003</td> <td>api/api/PeriodicReviewResourceTest.kt<br>document/document/PeriodicReviewStatusTest.kt<br>notification/notification/PeriodicReviewServiceTest.kt<br>notification/notification/PeriodicReviewSweepTest.kt</td> <td>—</td> <td>api/api/document/DocumentResource.kt<br>api/src/app/core/lqms-api.ts<br>document/document/records/service/PeriodicReviewService.kt<br>persistence/V023__periodic_review_and_validity.sql<br>persistence/V133__review_interval_is_plain_days.sql</td> <td><code>ca729ad2</code> docs(traceability): v1.8 citation backfill — 164/247 verifi…<br><code>4a9094e9</code> fix(document,api): REVISION_INITIATED outcome + 409/400 gua…<br><code>27a44c25</code> feat(document,notification): periodic review core (ADR-0038…</td> </tr> <tr> <td>REQ-EFF-005</td> <td>future</td> <td>A periodic review may require an electronic signature with meaning REVIEWED, per the review policy. <em>(Periodic-review e-signature hook — e-signatures are post-MVP (release-plan.md); design in ADR-0014; STATUS notes REQ-EFF realized "minus e-sig hook".)</em></td> <td>STR-019, STR-020; ADR-0015, ADR-0014</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-EFF-006</td> <td>verified</td> <td>A document may carry an optional validity end (valid_until).</td> <td>STR-020; ADR-0015</td> <td>api/api/ReviewSettingsResourceTest.kt<br>document/document/ContentColumnLifecycleInventoryTest.kt<br>document/document/ReviewSettingsServiceTest.kt<br>notification/notification/PeriodicReviewSweepTest.kt</td> <td>—</td> <td>api/api/document/DocumentResource.kt<br>api/src/app/core/lqms-api.ts<br>document/document/core/repository/DocumentRepository.kt<br>document/document/lifecycle/service/ReviewSettingsService.kt<br>persistence/V023__periodic_review_and_validity.sql<br>persistence/V024__sweep_hardening.sql<br>persistence/V025__retention_and_legal_hold.sql<br>persistence/V026__notification_delivery_and_i18n.sql<br>persistence/V032__content_model_round2.sql</td> <td>—</td> </tr> <tr> <td>REQ-EFF-007</td> <td>verified</td> <td>When a periodic review is overdue or a document's validity end passes, the document shall be flagged and surfaced for a…</td> <td>STR-020, STR-007; ADR-0015</td> <td>document/document/PeriodicReviewStatusTest.kt<br>notification/notification/PeriodicReviewSweepTest.kt</td> <td>—</td> <td>persistence/V023__periodic_review_and_validity.sql<br>persistence/V024__sweep_hardening.sql<br>persistence/V025__retention_and_legal_hold.sql<br>persistence/V026__notification_delivery_and_i18n.sql<br>persistence/V032__content_model_round2.sql<br>persistence/V133__review_interval_is_plain_days.sql</td> <td><code>ca729ad2</code> docs(traceability): v1.8 citation backfill — 164/247 verifi…<br><code>27a44c25</code> feat(document,notification): periodic review core (ADR-0038…</td> </tr> <tr> <td>REQ-EFF-008</td> <td>verified</td> <td>Periodic reviews and effectivity changes shall produce audit events.</td> <td>STR-009; ADR-0015, REQ-AUD-001</td> <td>notification/notification/PeriodicReviewServiceTest.kt</td> <td>—</td> <td>document/document/records/service/PeriodicReviewService.kt<br>persistence/V023__periodic_review_and_validity.sql</td> <td><code>27a44c25</code> feat(document,notification): periodic review core (ADR-0038…</td> </tr> <tr> <td>REQ-EFF-009</td> <td>verified</td> <td>An imported released version's effective_from may be backdated to the source system's release date (Jira/Comala fields,…</td> <td>STR-020, STR-026; ADR-0075, ADR-0015</td> <td>document/document/DocumentServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> </tbody> </table> <h3 id="req-gsp">REQ-GSP<a class="headerlink" href="#req-gsp" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-GSP-001</td> <td>verified</td> <td>A regulatory reference shall be a keyed trace item (node regulatoryRef, fence :::regulatory-ref) — one GSPR / essential…</td> <td>STR-001, STR-027; ADR-0084, ADR-0078, ADR-0061</td> <td>api/e2e/regulatory-axis.spec.ts<br>document/document/PdfExportServiceTest.kt<br>document/document/RegulatoryAxisRegistryTest.kt<br>document/document/RegulatoryAxisSaveTest.kt<br>scope/scope/RegulatoryLinkRlsSeparationTest.kt</td> <td>—</td> <td>—</td> <td><code>bfd379ec</code> docs(requirements): prepare the v1.9 delta — Stage C valida…</td> </tr> <tr> <td>REQ-GSP-002</td> <td>verified</td> <td>The system shall derive, per scope, a live GSPR CONFORMITY view (VIEW_TRACEABILITY-gated, RLS-scoped, nothing stored):…</td> <td>STR-011, STR-027; ADR-0084, ADR-0088, ADR-0080</td> <td>api/api/GsprConformityResourceTest.kt<br>api/e2e/gspr-conformity.spec.ts<br>document/document/GsprConformityLogicTest.kt<br>document/document/PdfExportServiceTest.kt</td> <td>—</td> <td>—</td> <td><code>bfd379ec</code> docs(requirements): prepare the v1.9 delta — Stage C valida…</td> </tr> </tbody> </table> <h3 id="req-i18n">REQ-I18N<a class="headerlink" href="#req-i18n" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-I18N-001</td> <td>verified</td> <td>All timestamps shall be stored in UTC and displayed in the user's time zone; signature and audit timestamps shall be re…</td> <td>STR-009, STR-024; ADR-0020, ADR-0014</td> <td>identity/identity/TimestampStorageSchemaTest.kt</td> <td>—</td> <td>document/document/records/repository/RecurringObligationRepository.kt</td> <td><code>2da77f9a</code> test(traceability): backfill REQ citations + add REQ-LC-014…<br><code>8e06e9b3</code> docs(arch): accept ADR-0020 internationalization (GAP-11) —…</td> </tr> <tr> <td>REQ-I18N-002</td> <td>future</td> <td>Dates, times, and numbers shall be formatted per the user's locale on display; stored values shall be canonical/locale-… <em>(Locale-aware date/time/number formatting is Increment 2 (release-plan.md); ADR-0020. Stored values are canonical (UTC timestamptz).)</em></td> <td>STR-012, STR-024; ADR-0020</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-I18N-003</td> <td>verified</td> <td>Each document shall have a content language attribute.</td> <td>STR-024; ADR-0020</td> <td>search/search/LanguageDetectionTest.kt<br>search/search/SearchServiceTest.kt</td> <td>—</td> <td>document/document/core/repository/DocumentRepository.kt</td> <td>—</td> </tr> <tr> <td>REQ-I18N-004</td> <td>future</td> <td>A translation shall be a separate, independently controlled document (its own review/approval/signatures/effective date… <em>(Translations as separately controlled documents are Later (release-plan.md; ADR-0020); only the translation-of relationship type value exists in the schema.)</em></td> <td>STR-024; ADR-0020, ADR-0003</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-I18N-005</td> <td>verified</td> <td>Search indexing shall be language-aware (per-language text analysis) so content is findable in its language; multilingu…</td> <td>STR-008, STR-024; ADR-0020, ADR-0006</td> <td>search/search/LanguageDetectionTest.kt<br>search/search/SearchServiceTest.kt</td> <td>—</td> <td>search/search/LanguageDetection.kt</td> <td><code>7d018e1a</code> docs: currency audit after the 2026-07-03 change wave</td> </tr> </tbody> </table> <h3 id="req-lc">REQ-LC<a class="headerlink" href="#req-lc" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-LC-001</td> <td>verified</td> <td>Every document version shall be in exactly one of the states DRAFT, IN_REVIEW, RELEASED, REVOKED, CANCELLED; no other s…</td> <td>STR-001; ADR-0003, ADR-0024</td> <td>api/api/ValidationJourneyTest.kt<br>document/document/ContentColumnLifecycleInventoryTest.kt<br>document/document/DocumentVersionSchemaTest.kt</td> <td>PQ: station 4 (Writing a controlled procedure)<br>PQ: station 5 (Submitting for review, and the author being refused her own approval)<br>PQ: station 7 (Releasing the effective version)</td> <td>persistence/V009__document_version.sql<br>persistence/V088__version_release_stamp.sql<br>persistence/V107__version_submit_stamp.sql</td> <td><code>b2223784</code> feat(document): Phase 3 slices 3.3-3.5 — version, content_p…<br><code>3bbb5650</code> docs(req): v1.3 spec-hardening round — Tier-B must-fix from…</td> </tr> <tr> <td>REQ-LC-002</td> <td>verified</td> <td>State transitions shall be limited to: submit (DRAFT→IN_REVIEW), reject (IN_REVIEW→DRAFT), withdraw (IN_REVIEW→DRAFT, b…</td> <td>STR-001; ADR-0003, ADR-0024, ADR-0066</td> <td>api/api/ValidationJourneyTest.kt<br>document/document/LifecycleServiceTest.kt</td> <td>PQ: station 5 (Submitting for review, and the author being refused her own approval)<br>PQ: station 7 (Releasing the effective version)</td> <td>—</td> <td><code>cb4e3161</code> docs(traceability): citation backfill — 49→102 verified, GA…<br><code>3bbb5650</code> docs(req): v1.3 spec-hardening round — Tier-B must-fix from…</td> </tr> <tr> <td>REQ-LC-003</td> <td>verified</td> <td>A review policy shall be configurable per scope and document type, defining approval requirements, the four-eyes flag,…</td> <td>STR-002; ADR-0003, ADR-0091</td> <td>api/api/ReviewPolicyResourceTest.kt<br>api/api/ValidationJourneyTest.kt<br>document/document/ReviewPolicyServiceTest.kt<br>lifecycle/lifecycle/ReviewPolicySchemaTest.kt</td> <td>PQ: station 1 (Registering a customer and a project)</td> <td>api/api/lifecycle/ReviewPolicyResource.kt<br>document/document/lifecycle/service/ReviewPolicyService.kt<br>persistence/V013__review_policy.sql</td> <td><code>2c3b51f2</code> docs(requirements): prepare the v1.8 delta — obligations, D…</td> </tr> <tr> <td>REQ-LC-004</td> <td>verified</td> <td>Approval requirements shall be expressible as a set of (role, minimum count) pairs that must all be satisfied before re…</td> <td>STR-002; ADR-0003, ADR-0004</td> <td>api/api/ValidationJourneyTest.kt<br>document/document/LifecycleServiceTest.kt<br>document/document/ReviewPolicyServiceTest.kt<br>lifecycle/lifecycle/ReviewPolicySchemaTest.kt</td> <td>PQ: station 6 (The second pair of eyes approving)</td> <td>api/src/app/core/models.ts<br>document/document/arrival/ImportPayloads.kt<br>document/document/export/service/AuthorityViewService.kt<br>document/document/lifecycle/service/LifecycleService.kt<br>document/document/lifecycle/service/ReviewPolicyService.kt<br>lifecycle/lifecycle/ReviewPolicyResolver.kt<br>lifecycle/lifecycle/WorkflowRoleRepository.kt<br>persistence/V013__review_policy.sql<br>persistence/V044__document_workflow_roles.sql</td> <td><code>cb4e3161</code> docs(traceability): citation backfill — 49→102 verified, GA…<br><code>76f97d24</code> feat(lifecycle): Phase 4 slice 4.1 — review_policy schema</td> </tr> <tr> <td>REQ-LC-005</td> <td>superseded</td> <td>The four-eyes rule shall be enforced by default: the author of a version shall not count as one of its approvers; relax… <em>(→ REQ-LC-016)</em></td> <td>STR-002; ADR-0003, ADR-0047</td> <td>document/document/LifecycleServiceTest.kt<br>lifecycle/lifecycle/ReviewPolicySchemaTest.kt</td> <td>—</td> <td>persistence/V013__review_policy.sql<br>persistence/V014__approval_and_review_comment.sql</td> <td><code>af896454</code> docs(requirements): v1.5 baseline prepared — four-eyes REQ-…</td> </tr> <tr> <td>REQ-LC-006</td> <td>verified</td> <td>Each transition shall be executable only by users holding a role permitted for that transition in the applicable review…</td> <td>STR-002, STR-003; ADR-0003</td> <td>document/document/LifecycleServiceTest.kt<br>document/document/ReviewPolicyServiceTest.kt<br>lifecycle/lifecycle/ReviewPolicySchemaTest.kt</td> <td>—</td> <td>api/src/app/core/models.ts<br>document/document/lifecycle/service/LifecycleService.kt<br>document/document/lifecycle/service/ReviewPolicyService.kt<br>lifecycle/lifecycle/ReviewPolicyResolver.kt<br>persistence/V013__review_policy.sql<br>persistence/V044__document_workflow_roles.sql</td> <td><code>cb4e3161</code> docs(traceability): citation backfill — 49→102 verified, GA…<br><code>76f97d24</code> feat(lifecycle): Phase 4 slice 4.1 — review_policy schema</td> </tr> <tr> <td>REQ-LC-007</td> <td>verified</td> <td>The release mode shall be configurable as automatic (on last required approval) or explicit (separate release step by a…</td> <td>STR-002; ADR-0003</td> <td>api/api/ValidationJourneyTest.kt<br>document/document/LifecycleServiceTest.kt<br>document/document/ReviewPolicyServiceTest.kt<br>lifecycle/lifecycle/ReviewPolicySchemaTest.kt</td> <td>PQ: station 7 (Releasing the effective version)</td> <td>persistence/V013__review_policy.sql<br>persistence/V062__review_policy_release_flow.sql</td> <td><code>75028f16</code> feat(lifecycle,document,api): DIRECT release flow + recurri…</td> </tr> <tr> <td>REQ-LC-008</td> <td>verified</td> <td>Every approval shall be recorded with user, the role in which they approved, and timestamp, permanently attached to the…</td> <td>STR-009; ADR-0003</td> <td>api/api/ValidationJourneyTest.kt<br>document/document/DocumentServiceTest.kt<br>document/document/LifecycleServiceTest.kt</td> <td>PQ: station 6 (The second pair of eyes approving)</td> <td>persistence/V014__approval_and_review_comment.sql</td> <td><code>2da77f9a</code> test(traceability): backfill REQ citations + add REQ-LC-014…</td> </tr> <tr> <td>REQ-LC-009</td> <td>verified</td> <td>Review comments shall be attachable to the version under review and shall be preserved with it.</td> <td>STR-001; ADR-0003, ADR-0067</td> <td>document/document/LifecycleServiceTest.kt</td> <td>—</td> <td>persistence/V014__approval_and_review_comment.sql</td> <td>—</td> </tr> <tr> <td>REQ-LC-010</td> <td>verified</td> <td>A released version shall remain unchanged and effective until a newer version of the same document is released or it is…</td> <td>STR-001, STR-009; ADR-0003</td> <td>document/document/DocumentServiceTest.kt</td> <td>—</td> <td>persistence/V131__version_revocation_stamp.sql</td> <td><code>df84a42e</code> docs(req): release requirements baseline v1.1<br><code>3380af35</code> docs(arch): accept ADR-0015 effectivity & periodic review</td> </tr> <tr> <td>REQ-LC-011</td> <td>verified</td> <td>All life-cycle rules shall be enforced server-side; clients shall not be able to bypass them via any interface.</td> <td>STR-003, STR-014; ADR-0007</td> <td>document/document/LifecycleServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-LC-012</td> <td>verified</td> <td>Revocation (RELEASED → REVOKED) shall be terminal for a version; a revoked version shall not return to RELEASED.</td> <td>STR-001; ADR-0003</td> <td>document/document/LifecycleServiceTest.kt</td> <td>—</td> <td>document/document/lifecycle/service/LifecycleService.kt<br>lifecycle/lifecycle/StandingPermission.kt<br>persistence/V131__version_revocation_stamp.sql</td> <td><code>558e92f1</code> docs(req): release requirements baseline v1.2<br><code>f2d7249a</code> docs(req): resolve GAP-12/13/14 core clarifications (ADR-00…</td> </tr> <tr> <td>REQ-LC-013</td> <td>verified</td> <td>Revoking a document that is a derivation source shall notify scopes holding derivations of it, and shall not change tho…</td> <td>STR-005; ADR-0002</td> <td>notification/notification/SourceFanoutTest.kt</td> <td>—</td> <td>persistence/V020__source_event_fanout.sql</td> <td><code>558e92f1</code> docs(req): release requirements baseline v1.2<br><code>f2d7249a</code> docs(req): resolve GAP-12/13/14 core clarifications (ADR-00…</td> </tr> <tr> <td>REQ-LC-014</td> <td>verified</td> <td>Revocation shall be gated by transition permission and may, per the review policy, require approval and/or an electroni…</td> <td>STR-002, STR-009; ADR-0003, ADR-0014</td> <td>document/document/LifecycleServiceTest.kt</td> <td>—</td> <td>—</td> <td><code>2da77f9a</code> test(traceability): backfill REQ citations + add REQ-LC-014…<br><code>558e92f1</code> docs(req): release requirements baseline v1.2<br><code>f2d7249a</code> docs(req): resolve GAP-12/13/14 core clarifications (ADR-00…</td> </tr> <tr> <td>REQ-LC-015</td> <td>verified</td> <td>Cancellation shall be terminal and gated by transition permission; a cancelled version shall never be effective and sha…</td> <td>STR-001; ADR-0024, REQ-AUD-001</td> <td>document/document/LifecycleServiceTest.kt</td> <td>—</td> <td>document/document/core/repository/VersionRepository.kt<br>document/document/lifecycle/service/LifecycleService.kt<br>lifecycle/lifecycle/StandingPermission.kt</td> <td><code>3bbb5650</code> docs(req): v1.3 spec-hardening round — Tier-B must-fix from…</td> </tr> <tr> <td>REQ-LC-016</td> <td>verified</td> <td>The four-eyes rule shall be enforced by default: the user who submitted the current review round — thereby freezing and…</td> <td>STR-002, STR-009; ADR-0003, ADR-0047</td> <td>api/api/ValidationJourneyTest.kt<br>document/document/LifecycleServiceTest.kt<br>document/document/ReviewPolicyServiceTest.kt</td> <td>PQ: station 5 (Submitting for review, and the author being refused her own approval)<br>PQ: station 6 (The second pair of eyes approving)</td> <td>document/document/lifecycle/service/LifecycleService.kt<br>document/document/lifecycle/service/ReviewPolicyService.kt<br>document/document/lifecycle/service/WorkflowActionEvaluator.kt<br>persistence/V107__version_submit_stamp.sql</td> <td><code>c21e73bf</code> fix(document,notification,webui): four-eyes submitter-only…<br><code>af896454</code> docs(requirements): v1.5 baseline prepared — four-eyes REQ-…</td> </tr> <tr> <td>REQ-LC-017</td> <td>verified</td> <td>Each document shall carry three workflow role-group bindings — AUTHOR, REVIEWER (each entry with a minimum-approver cou…</td> <td>STR-002, STR-003; ADR-0064, REQ-LC-004</td> <td>api/e2e/workflow-roles.spec.ts<br>document/document/LifecycleServiceTest.kt<br>document/document/WorkflowRoleServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-LC-018</td> <td>verified</td> <td>Workflow-role bindings shall be editable while the version is DRAFT by holders of the document edit permission — every…</td> <td>STR-002, STR-009; ADR-0064, ADR-0030</td> <td>api/e2e/workflow-roles.spec.ts<br>document/document/WorkflowRoleServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-LC-019</td> <td>verified</td> <td>SUBMIT shall require all three workflow groups to be non-empty (otherwise rejected with a clear message) and shall bloc…</td> <td>STR-002, STR-003; ADR-0064, ADR-0054, REQ-LC-016</td> <td>document/document/LifecycleServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-LC-020</td> <td>verified</td> <td>The author side shall be able to WITHDRAW a version from review (IN_REVIEW→DRAFT): permitted for any holder of the docu…</td> <td>STR-001, STR-002; ADR-0066, ADR-0064</td> <td>api/e2e/withdraw.spec.ts<br>document/document/LifecycleServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-LC-021</td> <td>accepted-gap</td> <td>Content mutation shall be confined to the AUTHOR-side roles while the version is DRAFT; reviewers shall act only throug… <em>(Reviewers-comment-not-edit is a structural property (editing is EDIT_DRAFT- and DRAFT-state-gated; no reviewer edit path exists), enforced across the lifecycle/authz tests but with no single taggable carrier. ADR-0066/ADR-0067.)</em></td> <td>STR-002; ADR-0066, ADR-0067</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-LC-022</td> <td>verified</td> <td>A review comment shall belong to a document version and may carry an anchor into the version's content tree — a block r…</td> <td>STR-001, STR-002; ADR-0067, ADR-0057</td> <td>api/e2e/comment-anchor-determinism.spec.ts<br>api/e2e/comments.spec.ts<br>api/e2e/editor-comments.spec.ts<br>document/document/CommentServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-LC-023</td> <td>verified</td> <td>Holders of the document's AUTHOR, REVIEWER, or RELEASER workflow roles may comment while the version is DRAFT or IN_REV…</td> <td>STR-002, STR-003, STR-023; ADR-0067, ADR-0019</td> <td>api/e2e/comments.spec.ts<br>api/e2e/editor-comments.spec.ts<br>document/document/CommentServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-LC-024</td> <td>verified</td> <td>Review comments shall be immutable records: create, one-level reply, and resolve/unresolve (resolver + timestamp record…</td> <td>STR-002, STR-009, STR-021; ADR-0067, ADR-0025</td> <td>api/e2e/comments.spec.ts<br>document/document/CommentServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-LC-025</td> <td>verified</td> <td>A per-(scope, type) review-policy flag requireCommentsResolved (default ON, the four-eyes configurability pattern) shal…</td> <td>STR-002; ADR-0067, REQ-LC-016</td> <td>api/e2e/comment-gate-visibility.spec.ts<br>document/document/CommentServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-LC-026</td> <td>verified</td> <td>Comment visibility shall be state-bound: while DRAFT/IN_REVIEW the layer is visible to every version reader except that…</td> <td>STR-002, STR-003, STR-009; ADR-0067</td> <td>api/e2e/comment-gate-visibility.spec.ts<br>api/e2e/editor-comments.spec.ts<br>document/document/CommentServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-LC-027</td> <td>verified</td> <td>The per-(scope, type) review policy shall carry a release flow — STANDARD (submit → approve → release, as today) or DIR…</td> <td>STR-002, STR-009; ADR-0091, ADR-0049, ADR-0064</td> <td>api/e2e/direct-release.spec.ts<br>api/e2e/obligations.spec.ts<br>catalog/catalog/DocumentTypeDefaultsServiceTest.kt<br>document/document/DirectReleaseTest.kt</td> <td>—</td> <td>—</td> <td><code>f0691e82</code> docs(requirements): v1.8 delta PREPARED — 9 rows, all verif…<br><code>2c3b51f2</code> docs(requirements): prepare the v1.8 delta — obligations, D…</td> </tr> </tbody> </table> <h3 id="req-mem">REQ-MEM<a class="headerlink" href="#req-mem" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-MEM-001</td> <td>GAP</td> <td>Membership in a mandator shall be a first-class recorded state (invited → accepted / declined / removed); invitation, a…</td> <td>STR-028, STR-009; ADR-0108, ADR-0107</td> <td>—</td> <td>—</td> <td>—</td> <td><code>25fe83b2</code> docs(requirements): baseline v2.0 — the five post-v1.9 func…</td> </tr> <tr> <td>REQ-MEM-002</td> <td>GAP</td> <td>Membership shall begin only upon the invitee's acceptance; an invitation may carry named responsibilities (scope, role)…</td> <td>STR-028; ADR-0108 §5</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-MEM-003</td> <td>GAP</td> <td>Membership alone shall grant no content access; a member without roles sees nothing, and a non-member cannot observe th…</td> <td>STR-028, STR-004; ADR-0108 §1, ADR-0012</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-MEM-004</td> <td>GAP</td> <td>Invitation by email shall not disclose to the inviter whether the address is already known to the installation, and sha…</td> <td>STR-028, STR-013; ADR-0108 §3, ADR-0063</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-MEM-005</td> <td>GAP</td> <td>Email invitation links shall be single-use, unguessable, stored only as a digest, and expire; expired or unknown links…</td> <td>STR-013; ADR-0108 §8</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-MEM-006</td> <td>GAP</td> <td>Ending a membership shall unassign the person's roles in that mandator and close the membership without affecting the p…</td> <td>STR-028; ADR-0108 §7</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> </tbody> </table> <h3 id="req-mig">REQ-MIG<a class="headerlink" href="#req-mig" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-MIG-001</td> <td>future</td> <td>The system shall support importing the current released documents and their metadata from an existing QMS as an initial… <em>(Validated product migration is a future increment; the ADR-0068 importer is dev tooling only (not a shipped/validated migration). Detailed import design ADR-0023/ADR-0068.)</em></td> <td>STR-026, STR-007; ADR-0023, ADR-0068</td> <td>—</td> <td>—</td> <td>—</td> <td><code>41e0d21e</code> docs: pre-implementation spec review + integrity errata (RV…<br><code>7c74a466</code> docs(req): triage Tier-3 gaps GAP-15..22 (ADR-0021/0022/002…</td> </tr> <tr> <td>REQ-MIG-002</td> <td>future</td> <td>Imported documents shall enter as released baseline versions, marked as imported with an imported-from provenance refer… <em>(Validated product migration is a future increment; the ADR-0068 importer is dev tooling only (not a shipped/validated migration). Detailed import design ADR-0023/ADR-0068.)</em></td> <td>STR-026, STR-009; ADR-0023, ADR-0021, ADR-0068</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-MIG-003</td> <td>future</td> <td>Import shall be validated (metadata mapping checked, conflicts reported) before committing; a dry-run shall be supporte… <em>(Validated product migration is a future increment; the ADR-0068 importer is dev tooling only (not a shipped/validated migration). Detailed import design ADR-0023/ADR-0068.)</em></td> <td>STR-026, STR-007, STR-014; ADR-0023</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-MIG-004</td> <td>accepted-gap</td> <td>Import shall execute exclusively through the public authenticated REST API (no SQL side door), so row-level security, a… <em>(Import tooling guarantee realized in scripts/import/ (ADR-0068, exercised via the trial-first DC rollout); the importer is dev-only Python outside the product test globs — no id-taggable product carrier. RLS/authz/audit behaviour it relies on is itself tested under REQ-SEP/REQ-API.)</em></td> <td>STR-026, STR-003, STR-009; ADR-0068, ADR-0007, ADR-0064</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-MIG-005</td> <td>accepted-gap</td> <td>The fetch phase shall be strictly read-only against the source system, and fetched or staged source content shall never… <em>(Read-only fetch + never-in-git staging + idempotent load are import-tooling properties in scripts/import/ (ADR-0068), outside the product test globs — no id-taggable product carrier.)</em></td> <td>STR-026, STR-003; ADR-0068</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-MIG-006</td> <td>accepted-gap</td> <td>The importer shall be a single parameterized code path over a per-source configuration (source space key, target scope… <em>(Importer parameterization (the second-scope and training-history source configs) is dev-only Python in scripts/import/ (test_sources.py, test_transform_training.py, test_source_history.py), outside the product test globs — no id-taggable product carrier. ADR-0068/0071.)</em></td> <td>STR-026, STR-003; ADR-0068, ADR-0071</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-MIG-007</td> <td>accepted-gap</td> <td>The importer shall recognize an existing QMS's requirement representations — <strong>KEY</strong> (JIRA-key) prose headers AND table… <em>(Requirement-item + satisfies-matrix import (ADR-0077 §7) is dev-only Python in scripts/import/ (outside the product test globs), like REQ-MIG-004/005/006 — no id-taggable product carrier. ADR-0068.)</em></td> <td>STR-026, STR-027, STR-009; ADR-0077, ADR-0068</td> <td>—</td> <td>—</td> <td>—</td> <td><code>db5ec3ee</code> feat!(model): the born-free rename — system-requirement, sl…<br><code>f2b93b49</code> docs(requirements): prepare the v1.7 delta — trace/risk/aud…</td> </tr> </tbody> </table> <h3 id="req-nfr">REQ-NFR<a class="headerlink" href="#req-nfr" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-NFR-001</td> <td>future</td> <td>LQMS shall support at least ~100 users (~20 concurrent), tens of projects, and on the order of 100k document versions o… <em>(Capacity target (~100 users / 100k versions) — not yet load-verified; target set in ADR-0018.)</em></td> <td>STR-022; ADR-0018, ADR-0005</td> <td>—</td> <td>—</td> <td>—</td> <td><code>993e88b9</code> docs(req): resolve GAP-08/09/10 NFR block (ADR-0018)</td> </tr> <tr> <td>REQ-NFR-002</td> <td>future</td> <td>Interactive operations shall complete within p95 < 1s under expected load; full-text search within < 1s; LLM-assisted a… <em>(Interactive p95 < 1s / search < 1s — no performance-test harness yet; target set in ADR-0018.)</em></td> <td>STR-022; ADR-0018</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-NFR-003</td> <td>not-applicable</td> <td>Availability shall target ~99.5% during business hours. <em>(Availability ~99.5% is an operational/deployment target, not verifiable by an automated code test (ADR-0018).)</em></td> <td>STR-022; ADR-0018</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-NFR-004</td> <td>future</td> <td>Automated backups shall run at least nightly (RPO ≤ 24h), extending the backup capability (REQ-BAK-001/002). <em>(Nightly automated backups (RPO ≤ 24h) — operational backup automation, future (extends REQ-BAK; ADR-0018).)</em></td> <td>STR-010, STR-022; ADR-0018</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-NFR-005</td> <td>future</td> <td>The system shall be restorable to service within ~1 business day (RTO). <em>(RTO ~1 business day restore — operational, future (ADR-0018).)</em></td> <td>STR-010, STR-022; ADR-0018</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-NFR-006</td> <td>future</td> <td>Backups shall be stored separately from the primary system and retained per the data-protection/retention policy. <em>(Off-site backup storage + retention — operational, future (ADR-0018/0016).)</em></td> <td>STR-022; ADR-0018, ADR-0016</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-NFR-007</td> <td>not-applicable</td> <td>All network transport shall use TLS (current version); session cookies shall use secure attributes (per REQ-AUTH-003). <em>(TLS transport is enforced at the deployment/reverse-proxy layer, not by an application code test (ADR-0018).)</em></td> <td>STR-022, STR-003; ADR-0018</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-NFR-008</td> <td>not-applicable</td> <td>Database and blob storage shall be encrypted at rest (platform-level: disk/volume, DB TDE, or S3 SSE), with keys manage… <em>(Encryption at rest is a platform capability (disk/TDE/SSE), not application code (ADR-0018).)</em></td> <td>STR-022, STR-003; ADR-0018</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-NFR-009</td> <td>not-applicable</td> <td>Secrets and credentials shall be supplied via environment/secret manager and never stored in source or build artifacts. <em>(Secrets supplied via env/secret manager is a deployment/config concern, not application code (ADR-0018).)</em></td> <td>STR-022; ADR-0018</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-NFR-010</td> <td>accepted-gap</td> <td>Dependencies (the SOUP list) shall be scanned for known vulnerabilities in CI, with findings triaged. <em>(Dependency vulnerability scanning is realized in CI (.github/workflows/ci.yml dependency-submission + dependency-review jobs) AND the ADR-0103 npm-audit gate (scripts/audit-gate.mjs in the e2e + sbom jobs: production scope blocking, dev tail report-only, expiring exceptions) — build/CI config outside the code-scan globs; ADR-0018, ADR-0103.)</em></td> <td>STR-014, STR-022; ADR-0018</td> <td>—</td> <td>—</td> <td>—</td> <td><code>7a17e7c5</code> docs(traceability): REQ-NFR-010 cites the ADR-0103 npm-audi…<br><code>04ba49a4</code> feat(webui,ci,security): ADR-0103 realized — the npm-audit…<br><code>1c900c36</code> chore(deps): netty fix-forward 4.1.136.Final; commonmark 0.…<br><code>7a01f90d</code> chore(webui): frontend dependency security wave (2026-07-24…<br><code>ea34921e</code> fix(webui): force patched lodash-es + nanoid — extinguish t…<br><code>71da42b3</code> feat(ci,security): release vulnerability gate + triage log…<br><code>10e60d12</code> ci: make dependency-submission non-blocking until Dependenc…<br><code>24d304b2</code> ci: add GitHub Actions workflow (Phase 0)</td> </tr> <tr> <td>REQ-NFR-011</td> <td>accepted-gap</td> <td>The runtime shall connect to the database as the RLS-subject role lqms_app (non-owner, non-superuser, no BYPASSRLS). <em>(lqms_app is non-owner / no-BYPASSRLS: enforced and tested (RlsScopeContext + startup BYPASSRLS check per STATUS; ADR-0009) but not carrying an explicit REQ-NFR-011 tag in code.)</em></td> <td>STR-003, STR-022; ADR-0018, ADR-0009</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-NFR-012</td> <td>accepted-gap</td> <td>Authentication events, authorization failures, and security-relevant administrative actions shall be audited. <em>(Security-event auditing is realized via the audit trail (auth/authz/admin actions; ties to REQ-AUD-001) but not carrying an explicit REQ-NFR-012 tag in code (ADR-0018).)</em></td> <td>STR-009, STR-022; ADR-0018, REQ-AUD-001</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-NFR-013</td> <td>accepted-gap</td> <td>Brute-force/credential protections and MFA are provided by the identity provider; LQMS shall store no user passwords. <em>(Brute-force/MFA handled by the IdP and LQMS stores no passwords — realized by the OIDC design (ADR-0011) but not carrying an explicit REQ-NFR-013 tag in code.)</em></td> <td>STR-016, STR-022; ADR-0018, ADR-0011</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> </tbody> </table> <h3 id="req-not">REQ-NOT<a class="headerlink" href="#req-not" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-NOT-001</td> <td>verified</td> <td>The system shall distinguish actionable <strong>tasks</strong> (tracked to completion) from informational <strong>notifications</strong>.</td> <td>STR-023; ADR-0019</td> <td>notification/notification/NotificationSchemaTest.kt</td> <td>—</td> <td>notification/notification/NotificationModule.kt<br>persistence/V019__tasks_and_notifications.sql</td> <td><code>6a044b6b</code> docs(arch): accept ADR-0019 notifications & tasks (GAP-07)</td> </tr> <tr> <td>REQ-NOT-002</td> <td>verified</td> <td>Tasks shall be generated from domain events (review requested, approval/signature required, rejection, periodic-review…</td> <td>STR-007, STR-023; ADR-0019, ADR-0003</td> <td>notification/notification/LifecycleTaskFlowTest.kt<br>notification/notification/NotificationSchemaTest.kt<br>notification/notification/TaskServiceTest.kt</td> <td>—</td> <td>document/document/core/repository/VersionRepository.kt<br>document/document/lifecycle/service/LifecycleService.kt<br>notification/notification/LifecycleTaskHandler.kt<br>notification/notification/TaskService.kt<br>persistence/V019__tasks_and_notifications.sql</td> <td><code>5630cf10</code> fix(notification): review-round HIGHs — type-scoped resolut…</td> </tr> <tr> <td>REQ-NOT-003</td> <td>verified</td> <td>A task shall track state (open → done / cancelled) and auto-resolve when its underlying action is completed or no longe…</td> <td>STR-023; ADR-0019</td> <td>notification/notification/LifecycleTaskFlowTest.kt<br>notification/notification/NotificationSchemaTest.kt<br>notification/notification/TaskServiceTest.kt</td> <td>—</td> <td>document/document/core/repository/VersionRepository.kt<br>document/document/lifecycle/service/LifecycleService.kt<br>notification/notification/LifecycleTaskHandler.kt<br>notification/notification/TaskService.kt<br>persistence/V019__tasks_and_notifications.sql</td> <td><code>fc926639</code> feat(lifecycle): pending-items query (versions awaiting my…</td> </tr> <tr> <td>REQ-NOT-004</td> <td>verified</td> <td>Tasks shall support configurable reminders and optional escalation (e.g.</td> <td>STR-007, STR-023; ADR-0019</td> <td>notification/notification/TaskReminderSweepTest.kt</td> <td>—</td> <td>api/api/notification/TaskSweepScheduler.kt<br>catalog/catalog/person/service/UserAdminService.kt<br>persistence/V022__task_due_dates_and_sweep.sql<br>persistence/V072__primary_role_holder.sql</td> <td><code>2c200aa8</code> feat(notification): overdue-task sweep — reminders + escala…</td> </tr> <tr> <td>REQ-NOT-005</td> <td>verified</td> <td>Notifications shall inform users of relevant events (e.g.</td> <td>STR-023; ADR-0019, REQ-DOC-012, REQ-LC-013</td> <td>notification/notification/NotificationSchemaTest.kt<br>notification/notification/NotificationServiceTest.kt<br>notification/notification/SourceFanoutTest.kt</td> <td>—</td> <td>notification/notification/NotificationService.kt<br>persistence/V019__tasks_and_notifications.sql<br>persistence/V021__fanout_notifications_and_hardening.sql<br>persistence/V045__review_comments.sql</td> <td><code>0e7aa06c</code> docs: ADR-0035 (fan-out contract as shipped) + review-round…<br><code>0d2d2742</code> feat(notification): fan-out v2 — notifications (REQ-NOT-005…</td> </tr> <tr> <td>REQ-NOT-006</td> <td>verified</td> <td>Notifications and tasks shall be scope-keyed and subject to RLS; a user shall see only those for scopes they are author…</td> <td>STR-003, STR-023; ADR-0019, ADR-0009</td> <td>notification/notification/NotificationSchemaTest.kt</td> <td>—</td> <td>notification/notification/NotificationModule.kt<br>persistence/V019__tasks_and_notifications.sql</td> <td><code>8f1e7795</code> feat(notification): tasks/notifications schema foundation (…</td> </tr> <tr> <td>REQ-NOT-007</td> <td>verified</td> <td>Delivery shall always include an in-app inbox, plus a pluggable channel interface with an email implementation configur…</td> <td>STR-023; ADR-0019</td> <td>api/api/EmailChannelDeliveryTest.kt<br>api/api/ValidationJourneyTest.kt</td> <td>PQ: station 8 (An addressee acknowledging the released document)</td> <td>api/api/notification/EmailChannel.kt<br>api/api/notification/TaskSweepScheduler.kt<br>catalog/catalog/membership/MembershipMail.kt</td> <td><code>637d2934</code> feat(notification,api,webui): email channel + notification…</td> </tr> <tr> <td>REQ-NOT-008</td> <td>verified</td> <td>Overdue periodic reviews (REQ-EFF-007) and disposal-due records (REQ-DPR-005) shall surface as tasks.</td> <td>STR-020, STR-021, STR-023; ADR-0019, ADR-0015, ADR-0016</td> <td>notification/notification/DisposalSweepTest.kt<br>notification/notification/PeriodicReviewSweepTest.kt</td> <td>—</td> <td>persistence/V025__retention_and_legal_hold.sql</td> <td><code>97b7b320</code> feat(notification,persistence): disposal-due surfacing (ADR…</td> </tr> <tr> <td>REQ-NOT-009</td> <td>verified</td> <td>Notifications and tasks are an operational layer; the authoritative record of actions remains the audit trail and they…</td> <td>STR-009, STR-023; ADR-0019, REQ-AUD-001</td> <td>notification/notification/TaskServiceTest.kt</td> <td>—</td> <td>notification/notification/TaskService.kt<br>persistence/V019__tasks_and_notifications.sql</td> <td>—</td> </tr> <tr> <td>REQ-NOT-010</td> <td>verified</td> <td>The system shall provide a session-authenticated live event channel (Server-Sent Events) that, after a domain transacti…</td> <td>STR-007, STR-023, STR-003; ADR-0050, ADR-0034</td> <td>api/api/EventsResourceTest.kt<br>api/e2e/live-updates.spec.ts<br>scope/scope/TransactionPostCommitTest.kt</td> <td>—</td> <td>—</td> <td><code>a93b6b95</code> docs(requirements): v1.6 baseline prepared — 21 new rows fo…</td> </tr> <tr> <td>REQ-NOT-011</td> <td>verified</td> <td>Draft-editing presence shall be ephemeral: held in memory with a short TTL and heartbeat, never persisted, never audite…</td> <td>STR-007, STR-003; ADR-0050</td> <td>api/api/PresenceResourceTest.kt<br>api/e2e/presence.spec.ts</td> <td>—</td> <td>—</td> <td><code>a93b6b95</code> docs(requirements): v1.6 baseline prepared — 21 new rows fo…</td> </tr> </tbody> </table> <h3 id="req-obl">REQ-OBL<a class="headerlink" href="#req-obl" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-OBL-001</td> <td>verified</td> <td>A recurring obligation shall be a per-scope, RLS-separated configuration object (not a controlled document — its execut…</td> <td>STR-015, STR-003; ADR-0089, ADR-0073</td> <td>api/api/RecurringObligationResourceTest.kt<br>api/api/ValidationJourneyTest.kt<br>api/e2e/obligations.spec.ts<br>document/document/RecurringObligationTest.kt</td> <td>PQ: station 9 (Defining a recurring duty)</td> <td>—</td> <td><code>2c3b51f2</code> docs(requirements): prepare the v1.8 delta — obligations, D…</td> </tr> <tr> <td>REQ-OBL-002</td> <td>verified</td> <td>Completion shall require no extra user action: a newly RELEASED record of the completion type in the scope is the evide…</td> <td>STR-015, STR-023; ADR-0089, ADR-0038, ADR-0039</td> <td>api/api/ValidationJourneyTest.kt<br>document/document/RecurringObligationTest.kt<br>notification/notification/RecurringObligationSweepTest.kt</td> <td>PQ: station 9 (Defining a recurring duty)</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-OBL-003</td> <td>verified</td> <td>The system shall provide a per-scope obligations-status oversight roll-up (GET /api/scopes/{scopeId}/obligations-status…</td> <td>STR-015, STR-011; ADR-0089, ADR-0080</td> <td>api/api/RecurringObligationResourceTest.kt<br>api/api/ValidationJourneyTest.kt<br>api/e2e/obligations.spec.ts<br>document/document/RecurringObligationTest.kt</td> <td>PQ: station 9 (Defining a recurring duty)</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-OBL-004</td> <td>verified</td> <td>An obligation's schedule shall be one of three kinds with per-kind parameters and validation: INTERVAL (every N days fr…</td> <td>STR-015; ADR-0094, ADR-0089</td> <td>api/api/ValidationJourneyTest.kt<br>document/document/ObligationScheduleTest.kt<br>notification/notification/RecurringObligationSweepTest.kt</td> <td>PQ: station 9 (Defining a recurring duty)</td> <td>—</td> <td>—</td> </tr> </tbody> </table> <h3 id="req-rel">REQ-REL<a class="headerlink" href="#req-rel" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-REL-001</td> <td>verified</td> <td>The system shall support typed, directional relationships between documents (and, where relevant, versions) from a defi…</td> <td>STR-001, STR-009; ADR-0021, ADR-0049</td> <td>document/document/DeriveServiceTest.kt</td> <td>—</td> <td>persistence/V017__relationships_and_derive_source.sql</td> <td><code>7c74a466</code> docs(req): triage Tier-3 gaps GAP-15..22 (ADR-0021/0022/002…</td> </tr> <tr> <td>REQ-REL-002</td> <td>verified</td> <td>Existing version-level provenance (derived-from, instantiated-from) and content translation (translation-of) shall be e…</td> <td>STR-004, STR-024; ADR-0021, ADR-0002, ADR-0020, ADR-0049</td> <td>document/document/DeriveServiceTest.kt<br>document/document/RelationServiceTest.kt<br>document/document/TemplateInstantiationTest.kt</td> <td>—</td> <td>document/document/lifecycle/service/DeriveService.kt<br>document/document/relation/service/RelationService.kt</td> <td><code>293c748a</code> feat(document): copy-on-derive DeriveService (ADR-0031 slic…</td> </tr> <tr> <td>REQ-REL-003</td> <td>verified</td> <td>Relationships shall be scope-keyed and subject to RLS; a user may relate only documents they are authorized to see.</td> <td>STR-003; ADR-0021, ADR-0009</td> <td>scope/scope/RelationshipRlsSeparationTest.kt</td> <td>—</td> <td>persistence/V017__relationships_and_derive_source.sql<br>persistence/V124__base_library_relation_readability.sql</td> <td><code>293c748a</code> feat(document): copy-on-derive DeriveService (ADR-0031 slic…</td> </tr> <tr> <td>REQ-REL-004</td> <td>verified</td> <td>Creating, changing, or removing a relationship shall be audited.</td> <td>STR-009; ADR-0021, REQ-AUD-001</td> <td>document/document/RelationServiceTest.kt</td> <td>—</td> <td>api/api/document/DocumentExceptionMappers.kt<br>document/document/relation/service/RelationService.kt</td> <td><code>7070565a</code> test(traceability): backfill REQ citations for 5 impl-untes…</td> </tr> <tr> <td>REQ-REL-005</td> <td>verified</td> <td>The system shall provide create/remove operations for the user-managed relationship vocabulary references, satisfies, v…</td> <td>STR-001, STR-009; ADR-0049, ADR-0021, ADR-0081, REQ-AUD-001</td> <td>api/api/RelationResourceTest.kt<br>document/document/RelationServiceTest.kt</td> <td>—</td> <td>—</td> <td><code>a93b6b95</code> docs(requirements): v1.6 baseline prepared — 21 new rows fo…</td> </tr> <tr> <td>REQ-REL-006</td> <td>verified</td> <td>On SUBMIT, the system shall scan the frozen version body for doc: links (REQ-DOC-025) and synchronize a system-maintain…</td> <td>STR-001, STR-009; ADR-0051, ADR-0049</td> <td>api/e2e/relations.spec.ts<br>document/document/RelationServiceTest.kt</td> <td>—</td> <td>—</td> <td><code>a93b6b95</code> docs(requirements): v1.6 baseline prepared — 21 new rows fo…</td> </tr> <tr> <td>REQ-REL-007</td> <td>verified</td> <td>The relationship model shall extend to typed TRACE LINKS whose endpoints are keyed trace items (of any type) or documen…</td> <td>STR-001, STR-009, STR-027; ADR-0077, ADR-0078, ADR-0079, ADR-0084, ADR-0021</td> <td>api/e2e/requirement-links.spec.ts<br>document/document/RequirementLinkServiceTest.kt</td> <td>—</td> <td>—</td> <td><code>bfd379ec</code> docs(requirements): prepare the v1.9 delta — Stage C valida…<br><code>f2b93b49</code> docs(requirements): prepare the v1.7 delta — trace/risk/aud…</td> </tr> <tr> <td>REQ-REL-008</td> <td>verified</td> <td>User-initiated trace-structure mutations — trace-link create/delete and user-edge relation add/remove — shall be REFUSE…</td> <td>STR-009, STR-027; ADR-0081, ADR-0080, ADR-0049</td> <td>document/document/RelationServiceTest.kt<br>document/document/RequirementLinkServiceTest.kt</td> <td>—</td> <td>—</td> <td><code>f2b93b49</code> docs(requirements): prepare the v1.7 delta — trace/risk/aud…</td> </tr> </tbody> </table> <h3 id="req-rep">REQ-REP<a class="headerlink" href="#req-rep" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-REP-001</td> <td>future</td> <td>The system shall generate a QMS re-evaluation report for a configurable period and set of scopes, auto-filling the sect… <em>(Regulatory / management-review reporting is a future increment (release-plan.md).)</em></td> <td>STR-011</td> <td>—</td> <td>—</td> <td>—</td> <td><code>558e92f1</code> docs(req): release requirements baseline v1.2<br><code>987f73a0</code> docs(req): resolve GAP-22 re-evaluation report content — al…</td> </tr> <tr> <td>REQ-REP-002</td> <td>future</td> <td>Reports shall be exportable in an editable format for completion by the quality manager. <em>(Regulatory / management-review reporting is a future increment (release-plan.md).)</em></td> <td>STR-011</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-REP-003</td> <td>future</td> <td>LLM-assisted report drafting shall honor the per-mandator LLM policy (REQ-SRCH-007). <em>(Regulatory / management-review reporting is a future increment (release-plan.md).)</em></td> <td>STR-011, STR-003; ADR-0006</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-REP-004</td> <td>future</td> <td>Re-evaluation and management reports shall be scopeable to internal (QMS operations) and/or external (customer products… <em>(Regulatory / management-review reporting is a future increment (release-plan.md).)</em></td> <td>STR-011, STR-015; ADR-0010</td> <td>—</td> <td>—</td> <td>—</td> <td><code>df84a42e</code> docs(req): release requirements baseline v1.1<br><code>10a141a2</code> docs(arch): accept ADR-0010 self-managed QMS via internal m…</td> </tr> <tr> <td>REQ-REP-005</td> <td>future</td> <td>The auto-filled report sections shall comprise: document inventory & state; versions released/revoked/superseded in the… <em>(Auto-filled report sections are a future increment; the completeness view (REQ-REP-007/008, realized) is its first building block.)</em></td> <td>STR-011, STR-009; ADR-0019/0015/0016/0021/0022</td> <td>—</td> <td>—</td> <td>—</td> <td><code>558e92f1</code> docs(req): release requirements baseline v1.2<br><code>987f73a0</code> docs(req): resolve GAP-22 re-evaluation report content — al…</td> </tr> <tr> <td>REQ-REP-006</td> <td>future</td> <td>The report shall provide a structured management-review template with manual-input placeholders for inputs LQMS does no… <em>(Regulatory / management-review reporting is a future increment (release-plan.md).)</em></td> <td>STR-011</td> <td>—</td> <td>—</td> <td>—</td> <td><code>558e92f1</code> docs(req): release requirements baseline v1.2<br><code>987f73a0</code> docs(req): resolve GAP-22 re-evaluation report content — al…</td> </tr> <tr> <td>REQ-REP-007</td> <td>verified</td> <td>The system shall support declarative coverage rules per scope (scope-keyed, RLS): each rule specifies a source document…</td> <td>STR-002, STR-011; ADR-0049</td> <td>api/api/CoverageResourceTest.kt<br>api/e2e/completeness.spec.ts<br>document/document/CoverageRuleServiceTest.kt</td> <td>—</td> <td>—</td> <td><code>69c12dd2</code> feat(coverage,seed,webui): ADR-0085 narrowing FINISHED — re…<br><code>a93b6b95</code> docs(requirements): v1.6 baseline prepared — 21 new rows fo…</td> </tr> <tr> <td>REQ-REP-008</td> <td>verified</td> <td>The system shall evaluate coverage rules live (no persisted state) per scope, reporting for each rule the number of sat…</td> <td>STR-011, STR-009; ADR-0049</td> <td>api/api/CoverageResourceTest.kt<br>api/e2e/completeness.spec.ts<br>document/document/CoverageRuleServiceTest.kt</td> <td>—</td> <td>—</td> <td><code>a93b6b95</code> docs(requirements): v1.6 baseline prepared — 21 new rows fo…</td> </tr> <tr> <td>REQ-REP-009</td> <td>verified</td> <td>The system shall derive, per scope, a read-only trace-item REGISTRY (key, type, defining document + version, attributes…</td> <td>STR-009, STR-011, STR-027; ADR-0077, ADR-0078, ADR-0049, ADR-0088</td> <td>api/e2e/traceability.spec.ts<br>document/document/RequirementLinkServiceTest.kt<br>document/document/RequirementRegistryServiceTest.kt</td> <td>—</td> <td>—</td> <td><code>2c3b51f2</code> docs(requirements): prepare the v1.8 delta — obligations, D…<br><code>f2b93b49</code> docs(requirements): prepare the v1.7 delta — trace/risk/aud…</td> </tr> <tr> <td>REQ-REP-010</td> <td>verified</td> <td>The system shall generate, per scope, a derived "Traceability report" PDF — a point-in-time compilation from the existi…</td> <td>STR-011, STR-027; ADR-0087, ADR-0080, ADR-0074, ADR-0084</td> <td>api/api/TraceabilityReportResourceTest.kt<br>document/document/PdfExportServiceTest.kt</td> <td>—</td> <td>—</td> <td><code>69c12dd2</code> feat(coverage,seed,webui): ADR-0085 narrowing FINISHED — re…<br><code>bfd379ec</code> docs(requirements): prepare the v1.9 delta — Stage C valida…<br><code>11435523</code> feat(document,api,webui): Stage C Wave 5 — GSPR conformity…<br><code>f831193c</code> feat(document,api,webui): Stage C Wave 3 — validation matri…<br><code>f0691e82</code> docs(requirements): v1.8 delta PREPARED — 9 rows, all verif…<br><code>2c3b51f2</code> docs(requirements): prepare the v1.8 delta — obligations, D…</td> </tr> </tbody> </table> <h3 id="req-risk">REQ-RISK<a class="headerlink" href="#req-risk" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-RISK-001</td> <td>verified</td> <td>A risk shall be a keyed trace item (node risk, fence :::risk) inside a risk-analysis-capable controlled document, mirro…</td> <td><code>not-acceptable</code>) that is the CURRENT-evaluation outcome, not a residual-only field. The tool shall RECORD these tokens and shall NEVER compute a level from S and P nor validate them against a matrix — the scale and the level calculus are CONTENT (the scope's Risk Management Plan, tied via a document relation); a score shall render as recorded tokens (<code>S3 · P1 · P2 — High</code>), never as a formula. The descriptive narrative (sequence of events, rationale, benefit-risk justification) is the block body.</td> <td>api/e2e/risk.spec.ts<br>document/document/RiskTraceItemTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-RISK-002</td> <td>verified</td> <td>A risk control shall be a keyed trace item (node riskControl, fence :::risk-control) carrying the fixed attribute contr…</td> <td><code>protective-measure</code> \</td> <td>api/e2e/risk.spec.ts<br>document/document/RiskTraceItemTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-RISK-003</td> <td>verified</td> <td>The system shall derive, per scope, a live risk-traceability read model (rows = risks: initial score → mitigating contr…</td> <td>STR-009, STR-011, STR-027; ADR-0079</td> <td>api/e2e/risk.spec.ts<br>api/e2e/traceability.spec.ts<br>document/document/RiskTraceItemTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> </tbody> </table> <h3 id="req-sbom">REQ-SBOM<a class="headerlink" href="#req-sbom" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-SBOM-001</td> <td>accepted-gap</td> <td>The system shall generate, per tagged release, a CycloneDX (JSON) SBOM at version ≥ 1.5 over everything that executes i… <em>(Per-release CycloneDX generation is realized in the CI 'sbom' job (L1 cyclonedxDirectBom + L2 npm run sbom, merged with cyclonedx-cli) — build/CI config outside the code-scan globs (REQ-NFR-010 precedent). L3 container syft pinned in sbom-concept.md pending an image-build job. ADR-0062 P1.)</em></td> <td>STR-013, STR-014; ADR-0062</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-SBOM-002</td> <td>future</td> <td>SBOM accuracy shall be validated against the built artifact: a syft scan of the final image shall be cross-checked agai… <em>(Syft cross-check of the final IMAGE against declared L1+L2 is not yet wired (this CI builds no image; config pinned in sbom-concept.md). ADR-0062.)</em></td> <td>STR-014; ADR-0062</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-SBOM-003</td> <td>accepted-gap</td> <td>License compliance shall be enforced on BOTH stacks against the same all-permissive allow-list — the npm production tre… <em>(License gates on both stacks are realized (scripts/check-backend-licenses.py + backend-license-exceptions.txt; the npm gate) — build/CI config outside the code-scan globs. ADR-0062.)</em></td> <td>STR-014; ADR-0062, ADR-0074</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-SBOM-004</td> <td>accepted-gap</td> <td>Vulnerabilities shall be monitored continuously and gated at release: Dependabot shall watch the npm, Gradle and docker… <em>(grype >=High release gate over the SBOM (CI 'sbom' job, sole exceptions in docs/security/vuln-triage.md) + continuous Dependabot (npm/gradle/docker) — CI config outside the code-scan globs. ADR-0062.)</em></td> <td>STR-014; ADR-0062, REQ-NFR-010</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-SBOM-005</td> <td>future</td> <td>The release job shall flag stale / end-of-life upstream components for human judgment, recorded in the triage log; the… <em>(EOL/stale-upstream release-job flag not yet built; the dependency delta rides the ADR-0061 validation report (also deferred). ADR-0062.)</em></td> <td>STR-014; ADR-0062, ADR-0061</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> </tbody> </table> <h3 id="req-sep">REQ-SEP<a class="headerlink" href="#req-sep" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-SEP-001</td> <td>verified</td> <td>The system shall manage mandators and scopes; every scope shall have a type (GLOBAL, MANDATOR, PROJECT), capability fla…</td> <td>STR-003, STR-006; ADR-0002</td> <td>api/api/ValidationJourneyTest.kt<br>scope/scope/ScopeSchemaTest.kt</td> <td>PQ: station 1 (Registering a customer and a project)</td> <td>persistence/V001__mandator_and_scope.sql<br>persistence/V071__manage_scopes_permission.sql<br>persistence/V087__manage_mandators_permission.sql</td> <td><code>575d8774</code> build(persistence): add Flyway + jOOQ codegen toolchain</td> </tr> <tr> <td>REQ-SEP-002</td> <td>verified</td> <td>Every scope shall have a short, unique, immutable scope code.</td> <td>STR-001; §8.1</td> <td>api/api/ValidationJourneyTest.kt<br>scope/scope/ScopeSchemaTest.kt</td> <td>PQ: station 1 (Registering a customer and a project)</td> <td>persistence/V001__mandator_and_scope.sql</td> <td><code>575d8774</code> build(persistence): add Flyway + jOOQ codegen toolchain</td> </tr> <tr> <td>REQ-SEP-003</td> <td>verified</td> <td>Every content-bearing database row shall carry its scope key.</td> <td>STR-003; ADR-0002</td> <td>document/document/ContentColumnLifecycleInventoryTest.kt<br>document/document/ContentPartSchemaTest.kt<br>document/document/DocumentSchemaTest.kt<br>document/document/DocumentServiceTest.kt<br>document/document/DocumentVersionSchemaTest.kt<br>document/document/DossierServiceTest.kt<br>document/document/DraftAttachmentSchemaTest.kt<br>document/document/FolderSchemaTest.kt<br>scope/scope/EffectiveVersionViewTest.kt<br>scope/scope/RlsPolicyInventoryTest.kt<br>scope/scope/RlsSeparationTest.kt</td> <td>—</td> <td>persistence/V002__row_level_security.sql<br>persistence/V007__document.sql<br>persistence/V009__document_version.sql<br>persistence/V010__content_part.sql<br>persistence/V011__audit_event.sql<br>persistence/V012__draft_content_and_numbering.sql<br>persistence/V030__draft_attachment.sql<br>persistence/V031__document_folder_tree.sql<br>persistence/V032__content_model_round2.sql<br>persistence/V035__acknowledgement.sql<br>persistence/V037__scope_users_function.sql<br>persistence/V039__content_format_tree_record.sql<br>persistence/V040__tree_record_integrity.sql<br>persistence/V041__effective_version_views.sql<br>persistence/V048__file_attachments.sql<br>persistence/V049__training_questionnaires.sql<br>persistence/V050__training_plans.sql<br>persistence/V123__deactivation_licenses_its_children.sql</td> <td><code>1be7cf4d</code> feat(document): Phase 3 slice 3.1 — document table + first…<br><code>c60914f1</code> feat(scope): enforce mandator separation with RLS + separat…</td> </tr> <tr> <td>REQ-SEP-004</td> <td>verified</td> <td>PostgreSQL Row-Level Security policies shall deny any access to rows of scopes the requesting user is not authorized fo…</td> <td>STR-003; ADR-0002</td> <td>document/document/ContentPartSchemaTest.kt<br>document/document/DocumentSchemaTest.kt<br>document/document/DocumentServiceTest.kt<br>document/document/DocumentVersionSchemaTest.kt<br>document/document/DraftAttachmentSchemaTest.kt<br>document/document/FolderSchemaTest.kt<br>scope/scope/BlobQuarantineRlsSeparationTest.kt<br>scope/scope/CoverageRuleRlsSeparationTest.kt<br>scope/scope/EffectiveVersionViewTest.kt<br>scope/scope/RecordFamilyRlsSeparationTest.kt<br>scope/scope/RelationshipRlsSeparationTest.kt<br>scope/scope/RlsPolicyInventoryTest.kt<br>scope/scope/RlsSeparationTest.kt<br>scope/scope/SearchIndexRlsSeparationTest.kt</td> <td>—</td> <td>persistence/V002__row_level_security.sql<br>persistence/V007__document.sql<br>persistence/V009__document_version.sql<br>persistence/V010__content_part.sql<br>persistence/V011__audit_event.sql<br>persistence/V012__draft_content_and_numbering.sql<br>persistence/V030__draft_attachment.sql<br>persistence/V031__document_folder_tree.sql<br>persistence/V039__content_format_tree_record.sql<br>persistence/V040__tree_record_integrity.sql<br>persistence/V041__effective_version_views.sql<br>persistence/V048__file_attachments.sql<br>persistence/V128__audit_append_requires_genuine_reach.sql</td> <td><code>c60914f1</code> feat(scope): enforce mandator separation with RLS + separat…</td> </tr> <tr> <td>REQ-SEP-005</td> <td>verified</td> <td>A user shall access a scope's content only with a role assignment granting a read permission effective in that scope (i…</td> <td>STR-003, STR-004; ADR-0002, ADR-0012</td> <td>api/api/ValidationJourneyTest.kt<br>catalog/catalog/AuthzResolutionTest.kt</td> <td>PQ: station 14 (Inviting a person into the customer's organization, and their accepting it)</td> <td>persistence/V002__row_level_security.sql<br>persistence/V121__global_cascade_classification.sql<br>persistence/V122__global_role_identity.sql</td> <td><code>2cb05e95</code> test(api): journey station 14 — membership as PQ evidence:…<br><code>558e92f1</code> docs(req): release requirements baseline v1.2<br><code>f2d7249a</code> docs(req): resolve GAP-12/13/14 core clarifications (ADR-00…<br><code>c60914f1</code> feat(scope): enforce mandator separation with RLS + separat…</td> </tr> <tr> <td>REQ-SEP-006</td> <td>verified</td> <td>Behavioral differences between scope types shall be implemented exclusively via capability flags, not type-conditional…</td> <td>STR-005; ADR-0002</td> <td>document/document/DocumentServiceTest.kt</td> <td>—</td> <td>persistence/V001__mandator_and_scope.sql<br>persistence/V032__content_model_round2.sql</td> <td><code>575d8774</code> build(persistence): add Flyway + jOOQ codegen toolchain</td> </tr> <tr> <td>REQ-SEP-007</td> <td>verified</td> <td>An automated separation test suite shall prove at the database level that cross-scope access is impossible, and shall r…</td> <td>STR-003, STR-014; ADR-0002, RISK-001</td> <td>scope/scope/BlobQuarantineRlsSeparationTest.kt<br>scope/scope/CoverageRuleRlsSeparationTest.kt<br>scope/scope/RecordFamilyRlsSeparationTest.kt<br>scope/scope/RlsPolicyInventoryTest.kt<br>scope/scope/RlsSeparationTest.kt<br>scope/scope/SearchIndexRlsSeparationTest.kt</td> <td>—</td> <td>persistence/V002__row_level_security.sql</td> <td><code>c60914f1</code> feat(scope): enforce mandator separation with RLS + separat…</td> </tr> <tr> <td>REQ-SEP-008</td> <td>verified</td> <td>A mandator shall be classifiable as internal (the operating organization) or external (a customer).</td> <td>STR-015; ADR-0010, ADR-0002</td> <td>api/api/SystemBootstrapTest.kt</td> <td>—</td> <td>persistence/V006__mandator_internal_flag.sql</td> <td><code>dde92cf8</code> feat(api): idempotent system bootstrap (admin grant, base h…<br><code>df84a42e</code> docs(req): release requirements baseline v1.1<br><code>10a141a2</code> docs(arch): accept ADR-0010 self-managed QMS via internal m…</td> </tr> <tr> <td>REQ-SEP-009</td> <td>verified</td> <td>The operating organization's QMS operations shall be held in one or more PROJECT scopes under an internal mandator, sub…</td> <td>STR-015; ADR-0010</td> <td>api/api/SystemBootstrapTest.kt</td> <td>—</td> <td>—</td> <td><code>df84a42e</code> docs(req): release requirements baseline v1.1<br><code>10a141a2</code> docs(arch): accept ADR-0010 self-managed QMS via internal m…</td> </tr> <tr> <td>REQ-SEP-010</td> <td>verified</td> <td>Released global-base content shall be readable by users holding a base-read permission via a global-scope role assignme…</td> <td>STR-003, STR-004; ADR-0002, ADR-0012</td> <td>api/api/PermissionClassificationTest.kt<br>document/document/BaseLibraryCitationResolveTest.kt<br>scope/scope/BaseReadabilityRlsTest.kt</td> <td>—</td> <td>persistence/V004__catalog_and_permissions.sql<br>persistence/V007__document.sql<br>persistence/V016__released_base_readability.sql<br>persistence/V017__relationships_and_derive_source.sql<br>persistence/V075__audit_event_scope_entity_read.sql<br>persistence/V117__base_reader_role.sql<br>persistence/V120__base_library_folder_readability.sql<br>persistence/V121__global_cascade_classification.sql<br>persistence/V122__global_role_identity.sql<br>persistence/V124__base_library_relation_readability.sql</td> <td><code>b8b13962</code> feat(scope): released-base readability RLS (ADR-0031 Option…<br><code>33371734</code> docs(adr): ADR-0031 (proposed) — base-readability enforceme…<br><code>558e92f1</code> docs(req): release requirements baseline v1.2<br><code>f2d7249a</code> docs(req): resolve GAP-12/13/14 core clarifications (ADR-00…</td> </tr> <tr> <td>REQ-SEP-011</td> <td>verified</td> <td>The RLS scope context (lqms.authorized_scope_ids) shall be request-bounded — set transaction-scoped (SET LOCAL) or rese…</td> <td>STR-003; ADR-0026, ADR-0009</td> <td>scope/scope/RlsConnectionReuseTest.kt<br>scope/scope/RlsScopeContextTest.kt<br>scope/scope/RlsSubjectRoleDeploymentCheckTest.kt</td> <td>—</td> <td>api/api/platform/DeploymentCheckRunner.kt<br>scope/scope/RlsScopeContext.kt<br>scope/scope/RlsSubjectRoleDeploymentCheck.kt</td> <td><code>a18a1988</code> feat(scope): RlsScopeContext runtime RLS mechanism (ADR-002…<br><code>5e2ff336</code> feat(scope): pooled-connection RLS isolation test (REQ-SEP-…<br><code>a01936cc</code> docs(req): release requirements baseline v1.3 (spec-hardeni…<br><code>3bbb5650</code> docs(req): v1.3 spec-hardening round — Tier-B must-fix from…</td> </tr> <tr> <td>REQ-SEP-012</td> <td>verified</td> <td>RLS shall guard content-bearing tables (documents, versions, content parts, audit events, search index, and any table h…</td> <td>STR-003; ADR-0027, ADR-0002</td> <td>document/document/AuditEventSchemaTest.kt<br>document/document/ContentPartSchemaTest.kt<br>document/document/DocumentSchemaTest.kt<br>document/document/DocumentVersionSchemaTest.kt<br>document/document/DraftAttachmentSchemaTest.kt<br>document/document/FolderSchemaTest.kt<br>scope/scope/RlsSeparationTest.kt</td> <td>—</td> <td>persistence/V007__document.sql<br>persistence/V009__document_version.sql<br>persistence/V010__content_part.sql<br>persistence/V011__audit_event.sql<br>persistence/V012__draft_content_and_numbering.sql<br>persistence/V030__draft_attachment.sql<br>persistence/V031__document_folder_tree.sql<br>persistence/V128__audit_append_requires_genuine_reach.sql</td> <td><code>9db4f401</code> docs(req): release requirements-v1.4 baseline<br><code>bdf04444</code> docs(adr): ADR-0027 — RLS content-plane vs control-plane bo…</td> </tr> </tbody> </table> <h3 id="req-sig">REQ-SIG<a class="headerlink" href="#req-sig" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-SIG-001</td> <td>future</td> <td>A review policy may mark a life-cycle step as requiring an electronic signature, with a defined meaning (AUTHORED, REVI… <em>(Electronic signatures are post-MVP (release-plan.md: e-sig deferred unless an early FDA/EU-regulated customer needs them); design in ADR-0014. No SIG id is code-cited yet.)</em></td> <td>STR-019; ADR-0014, ADR-0003, REQ-LC-008</td> <td>—</td> <td>—</td> <td>—</td> <td><code>558e92f1</code> docs(req): release requirements baseline v1.2<br><code>f2d7249a</code> docs(req): resolve GAP-12/13/14 core clarifications (ADR-00…<br><code>3c4534ad</code> docs(arch): accept ADR-0014 electronic signatures (Part 11/…</td> </tr> <tr> <td>REQ-SIG-002</td> <td>future</td> <td>An electronic signature shall capture the signer, the meaning, the timestamp, the bound version and its content hash, a… <em>(Electronic signatures are post-MVP (release-plan.md: e-sig deferred unless an early FDA/EU-regulated customer needs them); design in ADR-0014. No SIG id is code-cited yet.)</em></td> <td>STR-019, STR-009; ADR-0014, ADR-0001</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-SIG-003</td> <td>future</td> <td>Signatures shall be immutable and append-only, forming part of the version's permanent record and audit trail. <em>(Electronic signatures are post-MVP (release-plan.md: e-sig deferred unless an early FDA/EU-regulated customer needs them); design in ADR-0014. No SIG id is code-cited yet.)</em></td> <td>STR-009; ADR-0014, REQ-AUD-002</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-SIG-004</td> <td>future</td> <td>Every human-readable rendering and export of a signed record shall manifest, for each signature, the signer's name, dat… <em>(Electronic signatures are post-MVP (release-plan.md: e-sig deferred unless an early FDA/EU-regulated customer needs them); design in ADR-0014. No SIG id is code-cited yet.)</em></td> <td>STR-019, STR-009; ADR-0014, ADR-0016</td> <td>—</td> <td>—</td> <td>—</td> <td><code>df84a42e</code> docs(req): release requirements baseline v1.1<br><code>be140278</code> docs(arch): accept ADR-0016 retention, disposal & privacy (…</td> </tr> <tr> <td>REQ-SIG-005</td> <td>future</td> <td>A signature shall be linked to the exact content it signs (via its content hash) such that it cannot be transferred to… <em>(Electronic signatures are post-MVP (release-plan.md: e-sig deferred unless an early FDA/EU-regulated customer needs them); design in ADR-0014. No SIG id is code-cited yet.)</em></td> <td>STR-009; ADR-0014, ADR-0001</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-SIG-006</td> <td>future</td> <td>Signing shall require re-authentication on a continuous-session basis: step-up at the start of a signing session, inten… <em>(Electronic signatures are post-MVP (release-plan.md: e-sig deferred unless an early FDA/EU-regulated customer needs them); design in ADR-0014. No SIG id is code-cited yet.)</em></td> <td>STR-019, STR-007; ADR-0014, ADR-0011, ADR-0013, ADR-0028</td> <td>—</td> <td>—</td> <td>—</td> <td><code>9db4f401</code> docs(req): release requirements-v1.4 baseline<br><code>f9544324</code> feat(identity): require verified email for invite binding;…<br><code>b6995111</code> docs+config: reconcile design record with ADR-0028; restric…<br><code>a01936cc</code> docs(req): release requirements baseline v1.3 (spec-hardeni…</td> </tr> <tr> <td>REQ-SIG-007</td> <td>future</td> <td>Each signature shall be uniquely attributable to one individual; shared/generic accounts shall not be able to sign. <em>(Electronic signatures are post-MVP (release-plan.md: e-sig deferred unless an early FDA/EU-regulated customer needs them); design in ADR-0014. No SIG id is code-cited yet.)</em></td> <td>STR-009; ADR-0014, ADR-0013, REQ-USR-008</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-SIG-008</td> <td>future</td> <td>Which steps require signatures (and their meaning) and the re-authentication window shall be configurable per review po… <em>(Electronic signatures are post-MVP (release-plan.md: e-sig deferred unless an early FDA/EU-regulated customer needs them); design in ADR-0014. No SIG id is code-cited yet.)</em></td> <td>STR-002, STR-019; ADR-0014, ADR-0003</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-SIG-009</td> <td>future</td> <td>Where the identity provider supplies it, the signature shall record the authentication method/assurance (e.g. <em>(Electronic signatures are post-MVP (release-plan.md: e-sig deferred unless an early FDA/EU-regulated customer needs them); design in ADR-0014. No SIG id is code-cited yet.)</em></td> <td>STR-019; ADR-0014, ADR-0011</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> </tbody> </table> <h3 id="req-srch">REQ-SRCH<a class="headerlink" href="#req-srch" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-SRCH-001</td> <td>verified</td> <td>The system shall provide full-text search over document metadata and content across all scopes the user is authorized f…</td> <td>STR-008; ADR-0006, ADR-0044</td> <td>document/document/DocumentLookupTest.kt<br>search/search/SearchServiceTest.kt</td> <td>—</td> <td>api/api/search/SearchResource.kt<br>persistence/V029__search_index.sql<br>persistence/V104__search_vector_weights.sql<br>persistence/V120__base_library_folder_readability.sql</td> <td><code>7d018e1a</code> docs: currency audit after the 2026-07-03 change wave</td> </tr> <tr> <td>REQ-SRCH-002</td> <td>future</td> <td>On every content-freezing transition, content shall be indexed: text extracted from the blob, chunked, and embedded; fa… <em>(Extract/chunk/embed indexing pipeline is search layer 2 per ADR-0006; ADR-0044 shipped the FTS-only baseline (index-on-freeze itself is tested in SearchIndexingTest, without embeddings).)</em></td> <td>STR-008; ADR-0006, ADR-0057/0058</td> <td>—</td> <td>—</td> <td>search/search/SearchIndexer.kt</td> <td><code>7d018e1a</code> docs: currency audit after the 2026-07-03 change wave</td> </tr> <tr> <td>REQ-SRCH-003</td> <td>future</td> <td>Embeddings shall be computed exclusively by a locally running model; no content shall be sent to external services at i… <em>(Local-only embeddings — RAG indexing, layer 2 per ADR-0006 (beyond the ADR-0044 FTS baseline).)</em></td> <td>STR-008, STR-003; ADR-0006</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-SRCH-004</td> <td>verified</td> <td>Index data (vectors, FTS rows) shall be stored in PostgreSQL carrying the scope key, subject to the same RLS policies a…</td> <td>STR-003; ADR-0006, ADR-0044, REQ-SEP-007</td> <td>api/api/SearchResourceTest.kt<br>scope/scope/SearchIndexRlsSeparationTest.kt<br>search/search/SearchServiceTest.kt</td> <td>—</td> <td>api/api/search/SearchResource.kt<br>persistence/V029__search_index.sql<br>persistence/V120__base_library_folder_readability.sql<br>search/search/SearchService.kt</td> <td><code>7d018e1a</code> docs: currency audit after the 2026-07-03 change wave<br><code>4c86183a</code> feat(document,api,webui): search indexing seam + /api/searc…</td> </tr> <tr> <td>REQ-SRCH-005</td> <td>future</td> <td>The question-answering function shall send only the retrieved, permission-filtered chunks and the user's question to th… <em>(Permission-filtered chunk retrieval for QA — RAG, layer ⅔ per ADR-0006.)</em></td> <td>STR-008, STR-003; ADR-0006</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-SRCH-006</td> <td>future</td> <td>LLM providers shall be pluggable behind one interface, supporting cloud-based and on-premise providers. <em>(Pluggable LLM provider interface — layer ⅔ per ADR-0006.)</em></td> <td>STR-013; ADR-0006</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-SRCH-007</td> <td>future</td> <td>Each mandator shall configure its LLM policy (cloud / on-prem / none); a query spanning scopes with different policies… <em>(Per-mandator LLM policy — layer ⅔ per ADR-0006.)</em></td> <td>STR-003, STR-008; ADR-0006</td> <td>—</td> <td>—</td> <td>—</td> <td><code>a01936cc</code> docs(req): release requirements baseline v1.3 (spec-hardeni…</td> </tr> <tr> <td>REQ-SRCH-008</td> <td>future</td> <td>Every LLM call shall be audit-logged with provider and the exact chunks sent. <em>(LLM-call audit logging — layer ⅔ per ADR-0006.)</em></td> <td>STR-009; ADR-0006</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-SRCH-009</td> <td>verified</td> <td>The search index shall be derived data: fully rebuildable from stored content on demand.</td> <td>STR-010; ADR-0006, ADR-0044</td> <td>api/api/AdminSearchResourceTest.kt<br>search/search/SearchServiceTest.kt</td> <td>—</td> <td>api/api/search/AdminSearchResource.kt<br>api/src/app/core/lqms-api.ts<br>notification/notification/PoolRoleDeploymentCheck.kt<br>persistence/V029__search_index.sql<br>persistence/V104__search_vector_weights.sql<br>persistence/V120__base_library_folder_readability.sql<br>search/search/SearchService.kt</td> <td><code>7d018e1a</code> docs: currency audit after the 2026-07-03 change wave</td> </tr> <tr> <td>REQ-SRCH-010</td> <td>future</td> <td>Search/RAG quality shall be verified against a curated benchmark query set with expected top results, run as a regressi… <em>(Search/RAG benchmark regression set — layer ⅔ per ADR-0006.)</em></td> <td>STR-008, STR-014; ADR-0006</td> <td>—</td> <td>—</td> <td>—</td> <td><code>558e92f1</code> docs(req): release requirements baseline v1.2<br><code>7c74a466</code> docs(req): triage Tier-3 gaps GAP-15..22 (ADR-0021/0022/002…</td> </tr> <tr> <td>REQ-SRCH-011</td> <td>verified</td> <td>Disposal and erasure shall synchronously delete or invalidate the corresponding full-text and vector index rows (not de…</td> <td>STR-003, STR-021; ADR-0025, ADR-0006, ADR-0044</td> <td>document/document/DisposalServiceTest.kt</td> <td>—</td> <td>persistence/V029__search_index.sql<br>search/search/SearchIndexRepository.kt<br>search/search/SearchPurge.kt</td> <td><code>7d018e1a</code> docs: currency audit after the 2026-07-03 change wave<br><code>4dc34a21</code> feat(search,persistence): FTS baseline — search_index under…<br><code>a01936cc</code> docs(req): release requirements baseline v1.3 (spec-hardeni…<br><code>3bbb5650</code> docs(req): v1.3 spec-hardening round — Tier-B must-fix from…</td> </tr> <tr> <td>REQ-SRCH-012</td> <td>verified</td> <td>The system shall provide a document lookup that matches documents visible to the caller (RLS-scoped) by a fragment of t…</td> <td>STR-007, STR-008, STR-003; ADR-0051, ADR-0049</td> <td>api/e2e/doc-links.spec.ts<br>document/document/DocumentLookupTest.kt</td> <td>—</td> <td>—</td> <td><code>a93b6b95</code> docs(requirements): v1.6 baseline prepared — 21 new rows fo…</td> </tr> </tbody> </table> <h3 id="req-td">REQ-TD<a class="headerlink" href="#req-td" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-TD-001</td> <td>GAP</td> <td>A dossier shall assemble released document versions by frozen reference (pins); issuing shall render the merged deliver…</td> <td>STR-029; ADR-0083, ADR-0104</td> <td>—</td> <td>—</td> <td>—</td> <td><code>25fe83b2</code> docs(requirements): baseline v2.0 — the five post-v1.9 func…</td> </tr> <tr> <td>REQ-TD-002</td> <td>GAP</td> <td>A reader who cannot see every pinned element shall receive a freshly rendered partial copy visibly marked as not the re…</td> <td>STR-029, STR-004; ADR-0104 amendment</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-TD-003</td> <td>GAP</td> <td>An issued dossier shall not be deletable; correction is forward-only (clone to a new draft, re-issue as a new version);…</td> <td>STR-029, STR-009; ADR-0104</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> </tbody> </table> <h3 id="req-trn">REQ-TRN<a class="headerlink" href="#req-trn" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-TRN-001</td> <td>verified</td> <td>Authorized users shall be able to define which roles must be trained on (acknowledge) a given document or document type.</td> <td>STR-025; ADR-0022, ADR-0004</td> <td>api/api/AcknowledgementResourceTest.kt<br>api/api/ValidationJourneyTest.kt<br>architecture-tests/architecture/AuditActionVocabularyCensusTest.kt</td> <td>PQ: station 3 (Requiring a read acknowledgement for the procedure type)</td> <td>api/api/records/AcknowledgementPolicyResource.kt<br>document/document/records/service/AcknowledgementPolicyService.kt<br>persistence/V035__acknowledgement.sql</td> <td><code>a7963285</code> feat(document,notification,api,webui): addressees & read-ac…<br><code>7c74a466</code> docs(req): triage Tier-3 gaps GAP-15..22 (ADR-0021/0022/002…</td> </tr> <tr> <td>REQ-TRN-002</td> <td>future</td> <td>The system shall record that a user has read a specific document version. <em>(Recording a bare read (distinct from acknowledgement) is not built; acknowledgement (REQ-TRN-003) covers read-and-understood. ADR-0022.)</em></td> <td>STR-025; ADR-0022</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-TRN-003</td> <td>verified</td> <td>A user shall be able to acknowledge a specific document version (read & understood); the acknowledgement (user, version…</td> <td>STR-025, STR-009; ADR-0022, ADR-0016</td> <td>api/api/AcknowledgementResourceTest.kt<br>api/api/ValidationJourneyTest.kt<br>notification/notification/AcknowledgementFanoutTest.kt</td> <td>PQ: station 8 (An addressee acknowledging the released document)</td> <td>api/api/records/AcknowledgementResource.kt<br>document/document/records/service/AcknowledgementService.kt<br>persistence/V035__acknowledgement.sql</td> <td><code>7070565a</code> test(traceability): backfill REQ citations for 5 impl-untes…<br><code>a7963285</code> feat(document,notification,api,webui): addressees & read-ac…</td> </tr> <tr> <td>REQ-TRN-004</td> <td>verified</td> <td>A document (its type or a specific version) may carry a simple questionnaire (e.g.</td> <td>STR-025; ADR-0022, ADR-0070</td> <td>document/document/TrainingQuestionnaireTest.kt</td> <td>—</td> <td>api/api/records/AcknowledgementResource.kt<br>document/document/records/repository/AcknowledgementRepository.kt<br>document/document/records/service/AcknowledgementService.kt<br>persistence/V035__acknowledgement.sql<br>persistence/V049__training_questionnaires.sql</td> <td><code>7070565a</code> test(traceability): backfill REQ citations for 5 impl-untes…<br><code>fd01e058</code> refactor(document): dedupe effective-standing rule; move js…</td> </tr> <tr> <td>REQ-TRN-005</td> <td>verified</td> <td>On release of a version whose document requires acknowledgement, holders of the required roles shall receive an acknowl…</td> <td>STR-025, STR-023; ADR-0022, ADR-0019</td> <td>api/api/ValidationJourneyTest.kt<br>notification/notification/AcknowledgementFanoutTest.kt</td> <td>PQ: station 8 (An addressee acknowledging the released document)</td> <td>notification/notification/AcknowledgementFanoutHandler.kt<br>persistence/V035__acknowledgement.sql</td> <td><code>7070565a</code> test(traceability): backfill REQ citations for 5 impl-untes…<br><code>a7963285</code> feat(document,notification,api,webui): addressees & read-ac…</td> </tr> <tr> <td>REQ-TRN-006</td> <td>verified</td> <td>Acknowledgement and questionnaire status shall be reportable per document, role, and scope (e.g.</td> <td>STR-025; ADR-0022</td> <td>api/api/AcknowledgementResourceTest.kt<br>document/document/AcknowledgementStatusRowsTest.kt<br>document/document/DirectReleaseTrainingCarryForwardTest.kt<br>document/document/TrainingBaselineParityTest.kt</td> <td>—</td> <td>api/api/records/AcknowledgementResource.kt<br>api/src/app/core/models.ts<br>api/src/app/features/documents/document-detail.ts<br>document/document/core/repository/VersionRepository.kt<br>document/document/records/repository/AcknowledgementRepository.kt<br>document/document/records/service/AcknowledgementService.kt<br>persistence/V035__acknowledgement.sql<br>persistence/V068__effective_training_baseline_function.sql</td> <td><code>aed197e1</code> refactor(document): single-source the training-baseline rul…<br><code>f05f88ed</code> feat(document,webui): ack-coverage card explains an empty s…<br><code>396eec8d</code> fix(document): disposal blob-deletion consults all four blo…<br><code>cb9078ef</code> fix(document): ack-coverage card anchors on the training ba…<br><code>a7963285</code> feat(document,notification,api,webui): addressees & read-ac…</td> </tr> <tr> <td>REQ-TRN-007</td> <td>verified</td> <td>The acknowledgement policy shall carry a training mode per (scope, type) — NONE, ACKNOWLEDGE, or QUESTIONNAIRE (default…</td> <td>STR-025, STR-002; ADR-0070, ADR-0053</td> <td>document/document/TrainingQuestionnaireTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-TRN-008</td> <td>verified</td> <td>Each release shall carry a training-relevant flag: when set, training tasks shall fan out to all addressees, each compl…</td> <td>STR-025, STR-009; ADR-0070, ADR-0052</td> <td>api/e2e/training-questionnaire.spec.ts<br>document/document/TrainingBaselineParityTest.kt<br>document/document/TrainingQuestionnaireTest.kt</td> <td>—</td> <td>document/document/core/repository/VersionRepository.kt<br>document/document/records/repository/AcknowledgementRepository.kt<br>document/document/records/service/AcknowledgementService.kt<br>persistence/V068__effective_training_baseline_function.sql</td> <td><code>aed197e1</code> refactor(document): single-source the training-baseline rul…<br><code>f9f837fd</code> feat(document,webui): gate the training-relevant toggle on…<br><code>c06e97cd</code> feat(document,webui): floor training_relevant=false to revi…<br><code>cb9078ef</code> fix(document): ack-coverage card anchors on the training ba…</td> </tr> <tr> <td>REQ-TRN-009</td> <td>verified</td> <td>The system shall record external trainings and certifications as first-class per-user, per-scope entries <code>{user, scope,… | CERTIFICATION), title, provider/issuer, completed/issued date, valid-until (null = non-expiring), evidence, notes, recorded-by}</code>, following a self-record + attestation model: a user records their own entries (including PLANNED ones, which convert to RECORDED on completion), and a MANAGE_TRAINING holder <em>other than the subject</em> CONFIRMS them (four-eyes attestation — the subject can never self-confirm). Entries are immutable records with narrow correction-by-supersession (a <em>Correct</em> creates a replacement chained to the original, which remains visible); evidence attaches as FILE-class, download-only blobs; entries are RLS-scoped and retained like other QMS records (access narrowing, not deletion, on offboarding).</td> <td>document/document/TrainingPlanServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> <td></td> </tr> <tr> <td>REQ-TRN-010</td> <td>verified</td> <td>The system shall present a per-user, per-scope training plan that joins, without duplication, the user's DERIVED docume…</td> <td>STR-025, STR-023; ADR-0071, ADR-0019</td> <td>api/e2e/my-training.spec.ts<br>document/document/TrainingPlanServiceTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-TRN-011</td> <td>verified</td> <td>The acknowledgement policy shall carry an optional training due-window per (scope, type) (training_due_days; null = no…</td> <td>STR-025, STR-011; ADR-0071, ADR-0070</td> <td>api/api/EndpointBodyBindingTest.kt<br>api/api/ValidationJourneyTest.kt<br>api/e2e/traceability-training.spec.ts<br>document/document/TrainingComplianceServiceTest.kt</td> <td>PQ: station 3 (Requiring a read acknowledgement for the procedure type)</td> <td>—</td> <td>—</td> </tr> </tbody> </table> <h3 id="req-ui">REQ-UI<a class="headerlink" href="#req-ui" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-UI-001</td> <td>verified</td> <td>The web frontend shall be an Angular application consuming the REST API.</td> <td>STR-007; ADR-0007</td> <td>api/api/FullStackBrowserSmokeTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-UI-002</td> <td>verified</td> <td>All UI texts shall be translatable; language shall be selectable per user.</td> <td>STR-012; ADR-0007</td> <td>api/api/MeResourceTest.kt<br>api/e2e/i18n.spec.ts</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-UI-003</td> <td>verified</td> <td>The UI shall reflect permissions (hide/disable unavailable actions) but never be the enforcement point.</td> <td>STR-003; ADR-0007</td> <td>api/e2e/review.spec.ts</td> <td>—</td> <td>api/api/document/AttachmentResource.kt<br>api/api/document/DocumentResource.kt</td> <td>—</td> </tr> <tr> <td>REQ-UI-004</td> <td>verified</td> <td>UI elements shall carry stable test selectors, and E2E flows shall be runnable against seeded test data, enabling the E…</td> <td>STR-014; ADR-0007</td> <td>api/api/FullStackBrowserSmokeTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-UI-005</td> <td>future</td> <td>The web frontend shall target WCAG 2.2 level AA accessibility. <em>(WCAG 2.2 AA conformance work is Increment 2 (release-plan.md); no accessibility test harness yet.)</em></td> <td>STR-007, STR-012; ADR-0007</td> <td>—</td> <td>—</td> <td>—</td> <td><code>558e92f1</code> docs(req): release requirements baseline v1.2<br><code>7c74a466</code> docs(req): triage Tier-3 gaps GAP-15..22 (ADR-0021/0022/002…</td> </tr> <tr> <td>REQ-UI-006</td> <td>future</td> <td>The web frontend shall support current evergreen browsers (latest stable Chrome, Edge, Firefox, Safari). <em>(Evergreen-browser matrix is Increment 2 (release-plan.md); the E2E suite currently runs Chromium only.)</em></td> <td>STR-007; ADR-0007</td> <td>—</td> <td>—</td> <td>—</td> <td><code>558e92f1</code> docs(req): release requirements baseline v1.2<br><code>7c74a466</code> docs(req): triage Tier-3 gaps GAP-15..22 (ADR-0021/0022/002…</td> </tr> <tr> <td>REQ-UI-007</td> <td>verified</td> <td>The UI shall present the differences between two versions of a document at the content-source level, distinguishing add…</td> <td>STR-001, STR-002; ADR-0007</td> <td>api/e2e/diff.spec.ts</td> <td>—</td> <td>—</td> <td><code>af896454</code> docs(requirements): v1.5 baseline prepared — four-eyes REQ-…</td> </tr> <tr> <td>REQ-UI-008</td> <td>verified</td> <td>The documents view shall present the scope's folder tree as a navigation panel; selecting a folder shall filter the doc…</td> <td>STR-007; ADR-0048, ADR-0007</td> <td>api/e2e/folders.spec.ts</td> <td>—</td> <td>—</td> <td><code>a93b6b95</code> docs(requirements): v1.6 baseline prepared — 21 new rows fo…</td> </tr> <tr> <td>REQ-UI-009</td> <td>verified</td> <td>The documents view shall present category tabs (PRESCRIPTIVE as "Documents", RECORD as "Records", TEMPLATE as "Template…</td> <td>STR-007; ADR-0049, ADR-0007</td> <td>api/e2e/categories.spec.ts</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-UI-010</td> <td>verified</td> <td>The document detail page shall present a References section listing outgoing relationships grouped by type and incoming…</td> <td>STR-001, STR-007; ADR-0049, ADR-0007</td> <td>api/e2e/relations.spec.ts</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-UI-011</td> <td>verified</td> <td>The system shall provide a per-scope traceability/completeness page presenting coverage rules as entry points phrased i…</td> <td>STR-011, STR-007; ADR-0049, ADR-0007</td> <td>api/e2e/completeness.spec.ts<br>api/e2e/traceability.spec.ts</td> <td>—</td> <td>—</td> <td><code>69c12dd2</code> feat(coverage,seed,webui): ADR-0085 narrowing FINISHED — re…</td> </tr> <tr> <td>REQ-UI-012</td> <td>verified</td> <td>The draft editor shall use a CodeMirror 6 markdown editor providing syntax highlighting, a selection/transaction API fo…</td> <td>STR-007; ADR-0050, ADR-0032, ADR-0055, ADR-0056, ADR-0057, ADR-0007</td> <td>api/api/ValidationJourneyTest.kt<br>api/e2e/markdown.spec.ts</td> <td>PQ: station 4 (Writing a controlled procedure)</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-UI-013</td> <td>verified</td> <td>In the CM6 editor, typing [[ shall trigger a document-link autocompletion (fed by the document lookup, REQ-SRCH-012) th…</td> <td>STR-007, STR-008; ADR-0051, ADR-0049, ADR-0007</td> <td>api/e2e/doc-links.spec.ts</td> <td>—</td> <td>api/src/app/features/documents/markdown-editor.ts<br>api/src/app/features/documents/tiptap-editor.ts</td> <td><code>f1350d2c</code> feat(webui): visual-editor <code>[[</code> doc-link completion (findin…</td> </tr> <tr> <td>REQ-UI-014</td> <td>verified</td> <td>The frontend shall consume the live event channel (REQ-NOT-010) to refetch and refresh affected views (document list, o…</td> <td>STR-007; ADR-0050, ADR-0007</td> <td>api/e2e/live-updates.spec.ts<br>api/e2e/presence.spec.ts</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-UI-015</td> <td>verified</td> <td>The draft editor shall offer a diagram slash-command that opens a lazily-loaded Excalidraw editor island; a created dia…</td> <td>STR-007; ADR-0065, ADR-0072, ADR-0007</td> <td>api/e2e/diagram.spec.ts</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-UI-016</td> <td>verified</td> <td>The version detail shall present an Attachments section (name, media type, size, download link) and the draft editor sh…</td> <td>STR-007, STR-001; ADR-0069, ADR-0007</td> <td>api/e2e/file-attachments.spec.ts</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-UI-017</td> <td>verified</td> <td>When the effective training mode is QUESTIONNAIRE, the draft surface shall present a training section with an author-ga…</td> <td>STR-025, STR-007; ADR-0070, ADR-0007</td> <td>api/e2e/training-questionnaire.spec.ts</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-UI-018</td> <td>verified</td> <td>The system shall present a per-scope QMS-configuration surface (route /scope-config, reached via a gear affordance next…</td> <td>STR-007, STR-003; ADR-0073, ADR-0030, ADR-0007, ADR-0091, ADR-0084</td> <td>api/api/ScopeConfigReadResourceTest.kt<br>api/api/ValidationJourneyTest.kt<br>api/e2e/scope-config.spec.ts</td> <td>PQ: station 3 (Requiring a read acknowledgement for the procedure type)<br>PQ: station 9 (Defining a recurring duty)<br>PQ: station 13 (Reading the setup health and signing out)</td> <td>—</td> <td><code>bfd379ec</code> docs(requirements): prepare the v1.9 delta — Stage C valida…<br><code>2c3b51f2</code> docs(requirements): prepare the v1.8 delta — obligations, D…</td> </tr> <tr> <td>REQ-UI-019</td> <td>verified</td> <td>The system shall present a personal "My training" page (document-training obligations and external entries with mode/st…</td> <td>STR-025, STR-007; ADR-0071, ADR-0007</td> <td>api/e2e/my-training.spec.ts<br>api/e2e/traceability-training.spec.ts</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-UI-020</td> <td>verified</td> <td>The version detail shall offer a "Download PDF" affordance on post-working versions (RELEASED, REVOKED) that retrieves…</td> <td>STR-007, STR-011; ADR-0074, ADR-0007</td> <td>api/api/ValidationJourneyTest.kt<br>api/e2e/pdf-export.spec.ts</td> <td>PQ: station 7 (Releasing the effective version)</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-UI-021</td> <td>verified</td> <td>The revise flow shall require a reason for change and accept an optional impact note (REQ-DOC-031); the version detail…</td> <td>STR-007, STR-009; ADR-0001, ADR-0007</td> <td>api/e2e/change-reason.spec.ts</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-UI-022</td> <td>verified</td> <td>The traceability page shall be a WORKSPACE: an overview hub whose tiles each show a headline metric + status (e.g.</td> <td>STR-007, STR-011, STR-027; ADR-0080, ADR-0071, ADR-0007, ADR-0084</td> <td>api/e2e/gspr-conformity.spec.ts<br>api/e2e/traceability-hub.spec.ts<br>api/e2e/traceability-training.spec.ts<br>api/e2e/traceability.spec.ts<br>api/e2e/validation-matrix.spec.ts</td> <td>—</td> <td>—</td> <td><code>bfd379ec</code> docs(requirements): prepare the v1.9 delta — Stage C valida…<br><code>f2b93b49</code> docs(requirements): prepare the v1.7 delta — trace/risk/aud…</td> </tr> <tr> <td>REQ-UI-023</td> <td>verified</td> <td>Risk-analysis-capable documents shall offer a TABLE-SHAPED authoring and reading surface over their risk items in which…</td> <td>STR-001, STR-007, STR-027; ADR-0082, ADR-0079, ADR-0057, ADR-0007</td> <td>api/e2e/risk-grid.spec.ts</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-UI-024</td> <td>verified</td> <td>The scope's documents surface shall offer a scope-level export menu for the audit pack (REQ-DOC-037): the merged review…</td> <td>STR-007, STR-011; ADR-0083, ADR-0074, ADR-0007</td> <td>api/api/ValidationJourneyTest.kt<br>api/e2e/audit-pack.spec.ts</td> <td>PQ: station 11 (Exporting the project as an audit pack)</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-UI-025</td> <td>verified</td> <td>The toolbar scope switcher (a scope id or ALL, persisted) shall be the application's single scope-filter state; per-vie…</td> <td>STR-007, STR-003; ADR-0093, ADR-0080, ADR-0007</td> <td>api/e2e/scope-context.spec.ts</td> <td>—</td> <td>—</td> <td><code>bfd379ec</code> docs(requirements): prepare the v1.9 delta — Stage C valida…<br><code>f0691e82</code> docs(requirements): v1.8 delta PREPARED — 9 rows, all verif…<br><code>2c3b51f2</code> docs(requirements): prepare the v1.8 delta — obligations, D…</td> </tr> <tr> <td>REQ-UI-026</td> <td>verified</td> <td>GSPR/applicability documents shall offer a TABLE-SHAPED authoring and reading surface over their regulatory-ref items i…</td> <td>STR-001, STR-007, STR-027; ADR-0084, ADR-0082, ADR-0057, ADR-0007</td> <td>api/e2e/regulatory-axis.spec.ts</td> <td>—</td> <td>—</td> <td><code>84a5198f</code> docs(requirements): v1.9 delta PREPARED — Stage C rows, all…<br><code>bfd379ec</code> docs(requirements): prepare the v1.9 delta — Stage C valida…</td> </tr> <tr> <td>REQ-UI-027</td> <td>GAP</td> <td>The user manual shall ship inside the application, versioned with it; help affordances on a surface shall open the topi…</td> <td>STR-030; ADR-0099</td> <td>—</td> <td>—</td> <td>—</td> <td><code>25fe83b2</code> docs(requirements): baseline v2.0 — the five post-v1.9 func…</td> </tr> </tbody> </table> <h3 id="req-usr">REQ-USR<a class="headerlink" href="#req-usr" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-USR-001</td> <td>verified</td> <td>A user shall be a unique individual identity anchored to a stable OIDC subject (issuer + subject); email and display na…</td> <td>STR-016, STR-018; ADR-0013, ADR-0063</td> <td>identity/identity/UserSchemaTest.kt</td> <td>—</td> <td>persistence/V003__app_user.sql<br>persistence/V042__user_identity_subject_only.sql</td> <td><code>7070565a</code> test(traceability): backfill REQ citations for 5 impl-untes…<br><code>4138cbee</code> feat(identity): app_user entity + identity module (Phase 2,…<br><code>ceab7252</code> docs(arch): accept ADR-0013 user identity lifecycle</td> </tr> <tr> <td>REQ-USR-002</td> <td>verified</td> <td>An administrator with MANAGE_USERS may pre-provision (invite) a user before first login (by email/IdP identifier) and a…</td> <td>STR-018; ADR-0013, ADR-0011, ADR-0012</td> <td>api/api/AdminUserResourceTest.kt<br>catalog/catalog/UserAdminServiceTest.kt</td> <td>—</td> <td>api/src/app/core/lqms-api.ts<br>api/src/app/core/models.ts<br>catalog/catalog/person/service/UserAdminService.kt<br>identity/identity/UserRepository.kt<br>persistence/V003__app_user.sql<br>persistence/V042__user_identity_subject_only.sql</td> <td><code>619d859b</code> feat(catalog,identity,api,webui): admin user lifecycle — in…</td> </tr> <tr> <td>REQ-USR-003</td> <td>verified</td> <td>A user authenticating with no matching invited or existing record shall be JIT-provisioned, with no access until assign…</td> <td>STR-018; ADR-0013, ADR-0011</td> <td>identity/identity/UserProvisioningTest.kt</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-USR-004</td> <td>verified</td> <td>Email shall be the matching key only for not-yet-bound invited records, and only when the authentication token asserts…</td> <td>STR-018; ADR-0013, ADR-0011</td> <td>identity/identity/UserProvisioningTest.kt</td> <td>—</td> <td>—</td> <td><code>9db4f401</code> docs(req): release requirements-v1.4 baseline<br><code>f9544324</code> feat(identity): require verified email for invite binding;…</td> </tr> <tr> <td>REQ-USR-005</td> <td>verified</td> <td>A user shall have a lifecycle state (invited, active, deactivated); deactivation shall block authentication and authori…</td> <td>STR-003, STR-018; ADR-0013</td> <td>api/api/AdminUserResourceTest.kt<br>api/api/DeactivatedUserAccessTest.kt<br>catalog/catalog/UserAdminServiceTest.kt<br>identity/identity/UserSchemaTest.kt</td> <td>—</td> <td>api/src/app/features/admin/invite-eligibility.ts<br>catalog/catalog/membership/service/MembershipService.kt<br>catalog/catalog/person/service/UserAdminService.kt<br>persistence/V089__external_person.sql</td> <td>—</td> </tr> <tr> <td>REQ-USR-006</td> <td>verified</td> <td>Deactivation shall be a state change, never deletion: the user's authorship, approvals, and audit events shall remain i…</td> <td>STR-009, STR-018; ADR-0013, REQ-AUD-001</td> <td>api/api/AdminUserResourceTest.kt<br>catalog/catalog/UserAdminServiceTest.kt</td> <td>—</td> <td>api/src/app/core/lqms-api.ts<br>api/src/app/core/models.ts<br>catalog/catalog/person/service/UserAdminService.kt</td> <td><code>619d859b</code> feat(catalog,identity,api,webui): admin user lifecycle — in…</td> </tr> <tr> <td>REQ-USR-007</td> <td>verified</td> <td>A deactivated user shall be reactivatable, reusing the same record (no duplicate identity).</td> <td>STR-018; ADR-0013</td> <td>catalog/catalog/UserAdminServiceTest.kt</td> <td>—</td> <td>api/src/app/core/lqms-api.ts<br>catalog/catalog/person/service/UserAdminService.kt</td> <td><code>2da77f9a</code> test(traceability): backfill REQ citations + add REQ-LC-014…<br><code>619d859b</code> feat(catalog,identity,api,webui): admin user lifecycle — in…</td> </tr> <tr> <td>REQ-USR-008</td> <td>accepted-gap</td> <td>Shared/generic human accounts shall not be permitted; each human user is a distinct individual identity. <em>(One-human-one-identity is enforced by the unique (issuer,subject) key (tested under REQ-USR-001); prohibiting shared/generic accounts is IdP/organizational policy (ADR-0013), not app-enforceable.)</em></td> <td>STR-009, STR-018; ADR-0013, REQ-AUTH-011</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> <tr> <td>REQ-USR-009</td> <td>future</td> <td>On deactivation the user's pending obligations (required-approver in open reviews, owned drafts) shall be surfaced to a… <em>(Surfacing pending obligations (open approvals, owned drafts) on deactivation is not built (ADR-0013 pending-obligations intent); the deactivation flow itself is tested under REQ-USR-005/006. The former screenshot citation was narrowed to USR-010 — it showed the assignment surface, not this behavior.)</em></td> <td>STR-007, STR-018; ADR-0013</td> <td>—</td> <td>—</td> <td>api/src/app/core/lqms-api.ts<br>api/src/app/features/admin/assignments-dialog.ts</td> <td><code>b6f5d429</code> fix(webui): assignment role picker offers only the scope's…<br><code>97c08195</code> test(traceability): implemented-untested backfill — 5 of 7…<br><code>7070565a</code> test(traceability): backfill REQ citations for 5 impl-untes…</td> </tr> <tr> <td>REQ-USR-010</td> <td>verified</td> <td>User lifecycle actions (invite, bind, deactivate, reactivate) and role-assignment changes shall produce audit events.</td> <td>STR-009, STR-018; ADR-0013, REQ-AUD-001</td> <td>api/e2e/screenshots.spec.ts<br>catalog/catalog/UserAdminServiceTest.kt<br>identity/identity/UserProvisioningTest.kt</td> <td>—</td> <td>api/src/app/core/lqms-api.ts<br>api/src/app/features/admin/assignments-dialog.ts<br>identity/identity/UserProvisioning.kt</td> <td><code>2c3b51f2</code> docs(requirements): prepare the v1.8 delta — obligations, D…<br><code>dcb018f8</code> feat(identity): USER_BOUND audit event on invite binding (R…<br><code>2fc5936e</code> feat(identity): audit USER_BOUND on invite→first-login bind…</td> </tr> <tr> <td>REQ-USR-011</td> <td>future</td> <td>Erasure of a user's personal data shall be governed by the retention/data-protection decision (GAP-06); deactivation is… <em>(User personal-data erasure follows the DPR erasure capability (REQ-DPR-007), Later per release-plan.md; ADR-0016/ADR-0013. Deactivation-is-not-erasure is realized (status change, record retained).)</em></td> <td>STR-018; ADR-0013</td> <td>—</td> <td>—</td> <td>—</td> <td>—</td> </tr> </tbody> </table> <h3 id="req-val">REQ-VAL<a class="headerlink" href="#req-val" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>ID</th> <th>Status</th> <th>Requirement</th> <th>Trace</th> <th>Test evidence</th> <th>PQ evidence</th> <th>Impl citations</th> <th>Commits</th> </tr> </thead> <tbody> <tr> <td>REQ-VAL-001</td> <td>verified</td> <td>A user need shall be a keyed trace item (node userNeed, fence :::user-need) inside a controlled document — the top of t…</td> <td>STR-001, STR-027; ADR-0084, ADR-0078, ADR-0057</td> <td>api/e2e/validation-axis.spec.ts<br>document/document/PdfExportServiceTest.kt<br>document/document/ValidationAxisRegistryTest.kt<br>document/document/ValidationAxisSaveTest.kt</td> <td>—</td> <td>—</td> <td><code>bfd379ec</code> docs(requirements): prepare the v1.9 delta — Stage C valida…</td> </tr> <tr> <td>REQ-VAL-002</td> <td>verified</td> <td>A validation case shall be a keyed trace item (node validationCase, fence :::validation-case) carrying the single FIXED…</td> <td>STR-001, STR-027; ADR-0084, ADR-0078</td> <td>api/e2e/validation-axis.spec.ts<br>document/document/PdfExportServiceTest.kt<br>document/document/ValidationAxisRegistryTest.kt<br>document/document/ValidationAxisSaveTest.kt</td> <td>—</td> <td>—</td> <td><code>bfd379ec</code> docs(requirements): prepare the v1.9 delta — Stage C valida…</td> </tr> <tr> <td>REQ-VAL-003</td> <td>verified</td> <td>A design element shall be a keyed trace item (node designElement, fence :::design-element) — the architecture/design *h…</td> <td>STR-001, STR-027; ADR-0084, ADR-0078</td> <td>api/e2e/validation-axis.spec.ts<br>document/document/PdfExportServiceTest.kt<br>document/document/ValidationAxisRegistryTest.kt<br>document/document/ValidationAxisSaveTest.kt</td> <td>—</td> <td>—</td> <td><code>bfd379ec</code> docs(requirements): prepare the v1.9 delta — Stage C valida…</td> </tr> <tr> <td>REQ-VAL-004</td> <td>verified</td> <td>A design element's designKind shall be constrained to a STRICT per-scope value set.</td> <td>STR-003, STR-027; ADR-0084, ADR-0078</td> <td>api/e2e/validation-axis.spec.ts<br>document/document/ValidationAxisSaveTest.kt<br>scope/scope/DesignKindVocabularyRlsSeparationTest.kt</td> <td>—</td> <td>—</td> <td><code>bfd379ec</code> docs(requirements): prepare the v1.9 delta — Stage C valida…</td> </tr> <tr> <td>REQ-VAL-005</td> <td>verified</td> <td>The system shall derive, per scope, a live VALIDATION MATRIX read model (VIEW_TRACEABILITY-gated, RLS-scoped, nothing s…</td> <td>STR-011, STR-027; ADR-0084, ADR-0088, ADR-0080</td> <td>api/api/ValidationMatrixResourceTest.kt<br>api/e2e/validation-matrix.spec.ts<br>document/document/PdfExportServiceTest.kt<br>document/document/ValidationMatrixLogicTest.kt</td> <td>—</td> <td>—</td> <td><code>bfd379ec</code> docs(requirements): prepare the v1.9 delta — Stage C valida…</td> </tr> </tbody> </table> </article> </div> <script>var target=document.getElementById(location.hash.slice(1));target&&target.name&&(target.checked=target.name.startsWith("__tabbed_"))</script> </div> <button type="button" class="md-top md-icon" data-md-component="top" hidden> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M13 20h-2V8l-5.5 5.5-1.42-1.42L12 4.16l7.92 7.92-1.42 1.42L13 8z"/></svg> Back to top </button> </main> <footer class="md-footer"> <nav class="md-footer__inner md-grid" aria-label="Footer" > <a href="../" class="md-footer__link md-footer__link--prev" aria-label="Previous: Requirements Traceability"> <div class="md-footer__button md-icon"> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11z"/></svg> </div> <div class="md-footer__title"> <span class="md-footer__direction"> Previous </span> <div class="md-ellipsis"> Requirements Traceability </div> </div> </a> <a href="../../validation/" class="md-footer__link md-footer__link--next" aria-label="Next: Validation documentation — the tool / instance rule"> <div class="md-footer__title"> <span class="md-footer__direction"> Next </span> <div class="md-ellipsis"> Validation documentation — the tool / instance rule </div> </div> <div class="md-footer__button md-icon"> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M4 11v2h12l-5.5 5.5 1.42 1.42L19.84 12l-7.92-7.92L10.5 5.5 16 11z"/></svg> </div> </a> </nav> <div class="md-footer-meta md-typeset"> <div class="md-footer-meta__inner md-grid"> <div class="md-copyright"> <div class="md-copyright__highlight"> Built from <code>v0.9.56-4-g06c7f811</code> (commit <code>06c7f811</code>, 2026-09-09) — the same Markdown the repository ships. </div> </div> </div> </div> </footer> </div> <div class="md-dialog" data-md-component="dialog"> <div class="md-dialog__inner md-typeset"></div> </div> <script id="__config" type="application/json">{"base": "../..", "features": ["navigation.instant", "navigation.tracking", "navigation.top", "navigation.footer", "navigation.indexes", "toc.follow", "search.suggest", "search.highlight", "content.code.copy", "content.action.edit"], "search": "../../assets/javascripts/workers/search.6ce7567c.min.js", "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}}</script> <script src="../../assets/javascripts/bundle.83f73b43.min.js"></script> </body> </html>