Skip to content
LQMS
Software Requirements
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--active md-nav__item--nested"> <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_5" checked> <div class="md-nav__link md-nav__container"> <a href="./" class="md-nav__link md-nav__link--active"> <span class="md-ellipsis"> Requirements </span> </a> <label class="md-nav__link md-nav__link--active" 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="true"> <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="stakeholder_requirements/" class="md-nav__link"> <span class="md-ellipsis"> Stakeholder Requirements </span> </a> </li> <li class="md-nav__item"> <a href="gap-analysis/" class="md-nav__link"> <span class="md-ellipsis"> Requirements Gap Analysis </span> </a> </li> <li class="md-nav__item"> <a href="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="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="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="req_auth/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Authentication & Session </span> </a> </li> <li class="md-nav__item"> <a href="req_backup/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Backup & Restore </span> </a> </li> <li class="md-nav__item"> <a href="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="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="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="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="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="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="req_i18n/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Internationalization </span> </a> </li> <li class="md-nav__item"> <a href="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="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="req_migration/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Migration & Import </span> </a> </li> <li class="md-nav__item"> <a href="req_nfr/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Non-Functional </span> </a> </li> <li class="md-nav__item"> <a href="req_notifications/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Notifications & Tasks </span> </a> </li> <li class="md-nav__item"> <a href="req_obligations/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Recurring Obligations </span> </a> </li> <li class="md-nav__item"> <a href="req_relationships/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Document Relationships </span> </a> </li> <li class="md-nav__item"> <a href="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="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="req_search/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Search </span> </a> </li> <li class="md-nav__item"> <a href="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="req_signatures/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Electronic Signatures </span> </a> </li> <li class="md-nav__item"> <a href="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="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="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--nested"> <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_8" > <div class="md-nav__link md-nav__container"> <a href="../traceability/" 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="false"> <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"> <a href="../traceability/matrix/" class="md-nav__link"> <span class="md-ellipsis"> Requirements Traceability Matrix </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_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="#baseline-history" class="md-nav__link"> <span class="md-ellipsis"> Baseline history </span> </a> </li> <li class="md-nav__item"> <a href="#the-v20-delta-detail" class="md-nav__link"> <span class="md-ellipsis"> The v2.0 delta (detail) </span> </a> </li> <li class="md-nav__item"> <a href="#the-v19-delta-detail" class="md-nav__link"> <span class="md-ellipsis"> The v1.9 delta (detail) </span> </a> </li> <li class="md-nav__item"> <a href="#structure" class="md-nav__link"> <span class="md-ellipsis"> Structure </span> </a> </li> <li class="md-nav__item"> <a href="#conventions" class="md-nav__link"> <span class="md-ellipsis"> Conventions </span> </a> </li> <li class="md-nav__item"> <a href="#traceability" class="md-nav__link"> <span class="md-ellipsis"> Traceability </span> </a> </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/requirements/README.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="software-requirements">Software Requirements<a class="headerlink" href="#software-requirements" title="Permanent link">¶</a></h1> <ul> <li><strong>Status: released</strong> — baseline <code>requirements-v2.1</code>, reviewed by Nicolas Burri, 2026-08-16 (the tag defines the exact v2.1 content). Changes require change control per the <a href="../process/configuration_management_plan/#document-baselines-and-change-control">configuration management plan</a>.</li> </ul> <h3 id="baseline-history">Baseline history<a class="headerlink" href="#baseline-history" title="Permanent link">¶</a></h3> <table> <thead> <tr> <th>Baseline</th> <th>Date</th> <th>Reviewer</th> <th>Contents / changes</th> </tr> </thead> <tbody> <tr> <td><code>requirements-v1.0</code></td> <td>2026-06-04</td> <td>Nicolas Burri</td> <td>Initial set: 14 STR + 59 software requirements (8 groups).</td> </tr> <tr> <td><code>requirements-v1.1</code></td> <td>2026-06-17</td> <td>Nicolas Burri</td> <td>Tier-1 gap resolutions (GAP-23/01/03/02/04/05/06, ADR-0010..0016): added STR-015..021; new groups REQ-AUTH, REQ-ADM, REQ-USR, REQ-SIG, REQ-EFF, REQ-DPR plus REQ-SEP-008/009 and REQ-REP-004; refined REQ-LC-010 and REQ-SIG-004.</td> </tr> <tr> <td><code>requirements-v1.2</code></td> <td>2026-06-18</td> <td>Nicolas Burri</td> <td>Tier-2 & Tier-3 gap resolutions (GAP-07..22, ADR-0017..0023): added STR-022..026; new groups REQ-NFR, REQ-NOT, REQ-I18N, REQ-REL, REQ-TRN, REQ-MIG, plus REQ-DOC-014/015/016, REQ-SEP-010, REQ-LC-012/013/014, REQ-SRCH-010, REQ-UI-005/006, REQ-REP-005/006; refined REQ-DOC-005, REQ-SEP-005, REQ-SIG-001, REQ-REP-001; adopted the MoSCoW priority convention. GAP-22 closed (all gaps resolved).</td> </tr> <tr> <td><code>requirements-v1.3</code></td> <td>2026-06-18</td> <td>Nicolas Burri</td> <td>Spec-hardening round from the <a href="https://github.com/nburri/lqms/blob/main/docs/planning/spec-review-2026-06-18.md">2026-06-18 spec review</a> (Tier-B, ADR-0024..0026): CANCELLED state (REQ-LC-001/002/015); disposal/erasure mechanics — storage delete, index purge, bounded backups, manifest-as-blob (REQ-DOC-015/018, REQ-SRCH-011, REQ-DPR-011); RLS connection-pool isolation (REQ-SEP-011); field-level audit + inspection copy (REQ-AUD-001/005/006); change description on versions (REQ-DOC-017); doc-ID uniqueness/LLM-ordering/re-auth clarifications (REQ-DOC-002, REQ-SRCH-007, REQ-SIG-006); dev-plan §2 safety-classification decision.</td> </tr> <tr> <td><code>requirements-v1.4</code></td> <td>2026-06-30</td> <td>Nicolas Burri</td> <td>Implementation-round changes (ADR-0027/0028/0029, Phase 2–3): REQ-SEP-012 (RLS guards content-bearing tables; scope/mandator & catalogs/identity/authz are control-plane, permission-governed); REQ-AUTH-004/006 reworked for the stateless encrypted token-state cookie (no server-side session store; revocation by per-request re-evaluation + bounded access-token lifetime/silent refresh + key rotation; compromised-cookie residual risk accepted, RISK-003); REQ-USR-004 invite-binding requires a verified email; REQ-SIG-006 deactivation denial at next signing/step-up via per-request re-evaluation.</td> </tr> <tr> <td><code>requirements-v1.5</code></td> <td>2026-07-05</td> <td>Nicolas Burri</td> <td>Demo-feedback-round changes (ADR-0044..0047): REQ-LC-005 superseded by REQ-LC-016 (four-eyes exclusion moves from the version's creator to the round's submitter — attester ≠ approver; accepted residual recorded); REQ-UI-007 added (version diff: added/removed/changed); REQ-DOC-005 annotated + ADR-0045 trace (Markdown + image attachment parts), REQ-DOC-014 ADR-0045 trace; realized REQ-SRCH-001/004/009/011 trace ADR-0044. First generated traceability snapshot accompanies the baseline (docs/traceability/matrix.md).</td> </tr> <tr> <td><code>requirements-v1.6</code></td> <td>2026-07-07</td> <td>Nicolas Burri</td> <td>Feature-wave changes (ADR-0048..0051): REQ-DOC-019..025 (folder tree, type categories, template variables + instantiation, in-text doc: links); REQ-REL-005/006 (relation CRUD vocabulary, freeze-time fromText sync; REL-001/002 refined by annotation); REQ-REP-007/008 (declarative coverage rules, released-evidence completeness); REQ-UI-008..014 (tree navigation, category tabs, References section, traceability page, CM6 editor, [[ authoring, live-refresh/presence UI); REQ-NOT-010/011 (post-commit scope-filtered SSE push, ephemeral presence with no-clobber); REQ-SRCH-012 (label-fragment lookup); REQ-EFF-003 annotated for categories. All 21 new rows landed traceability-verified at baseline.</td> </tr> </tbody> </table> <p>| <code>requirements-v1.7</code> | 2026-07-20 | Nicolas Burri | Three prepared waves folded into one baseline: <strong>(1) ADR-0064..0070 arcs</strong> — REQ-LC-017..026 (per-document workflow role bindings; withdraw-from-review; review comments incl. the resolution release gate), REQ-DOC-026..030 (FILE attachments; diagram content-part pair), REQ-UI-015..017, REQ-TRN-007/008 (questionnaires), REQ-MIG-004/005 (importer as developer tooling) + annotations. <strong>(2) ADR-0071..0075 arcs</strong> — REQ-TRN-009..011 (training plans, due-window compliance), REQ-DOC-031..033 (change reason/impact; source-history continuity; PDF export), REQ-EFF-009, REQ-UI-018..021, REQ-MIG-006; draw.io as annotations (engine swap, requirements unchanged). <strong>(3) ADR-0077..0083 + ADR-0062</strong> — REQ-DOC-034..037 (requirement/trace items; PDF navigation; scope audit pack), REQ-REL-007/008 (item links; server-enforced draft-only), REQ-REP-009 (registry + verifies-OR-satisfies coverage), new group REQ-RISK-001..003 (ISO 14971 items, recorded-not-computed scores), REQ-UI-022..024, REQ-ADM-010 (per-view traceability permissions), REQ-MIG-007, new group REQ-SBOM-001..005 (ADR-0062 D-5), STR-027 (machine-verifiable traceability); ADR-0060/0063 annotation pass (ADR-0061 checked, not applicable to REQ-REP). 53 new software requirements + STR-027 + two new groups; product rows enter the matrix GAP-flagged pending the citation backfill (worklists below), no-code-carrier rows curated <code>accepted-gap</code>/<code>future</code> with reasons. |</p> <p>| <code>requirements-v1.8</code> | 2026-07-24 | Nicolas Burri | Delta for the post-v1.7 ADR-first arcs (ADR-0087..0094): new group REQ-OBL-001..004 (recurring obligations: config object, released-record completion + sweep-derivation parity, VIEW_OBLIGATIONS oversight, calendar schedules with the clamp rule), REQ-LC-027 (DIRECT release flow with the structural RECORD-only floor), REQ-DOC-038 (two-phase quarantine-bin GC, one-place reference inventory), REQ-UI-025 (one scope context), REQ-REP-010 (derived traceability report), REQ-API-006 (product version on wire + UI); annotations on REQ-LC-003, REQ-DOC-013, REQ-UI-018, REQ-REP-009 (ADR-0088 evidence classes). All 9 new rows landed traceability-VERIFIED at baseline (the arcs shipped with cited tests — no backfill worklist needed); group naming (REQ-OBL vs folding into TRN) reviewed and confirmed. |</p> <p>| <code>requirements-v1.9</code> | 2026-07-26 | Nicolas Burri | Stage C — the Validation & Regulatory axes (ADR-0084, five waves): new group <strong>REQ-VAL</strong>-001..005 (user-need / validation-case / design-element trace-item types, the <code>validates</code> edge, the strict per-scope <code>designKind</code> set, the derived validation matrix + CSV); new group <strong>REQ-GSP</strong>-001..002 (regulatory-ref type, the <code>complies-with</code> edge, the GSPR conformity view with NA_WITHOUT_JUSTIFICATION a HARD gap); REQ-UI-026 (GSPR authoring grid); annotations on REQ-REL-007, REQ-REP-010, REQ-UI-018/022/025. 276→284 rows, every new row traceability-VERIFIED at preparation (0 GAP). Delta detail + verified-by-test mapping below. |</p> <p>| <code>requirements-v2.0</code> | 2026-08-08 | Nicolas Burri | The five function families that shipped after v1.9 with no requirement representation, minted from the <a href="https://github.com/nburri/lqms/blob/main/docs/planning/review-2026-08-08-membership-spec.md">2026-08-08 spec review</a> (S5/S7) and its draft: new group <strong>REQ-MEM</strong>-001..006 (membership as a first-class recorded state; acceptance-gated entry carrying pre-assigned responsibilities; membership ≠ access with non-membership answered as nonexistence; anti-enumeration invitation with IdP-only credential minting; single-use, digest-stored, expiring links; membership end that never touches the person — ADR-0108); new group <strong>REQ-TD</strong>-001..003 (pinned assembly, issue-once-and-persist with hash identity, the partial copy marked as not the record, forward-only correction — ADR-0083, ADR-0104); REQ-UI-027 (the in-app manual shipped and versioned with the release, surface↔topic bidirectionality build-enforced — ADR-0099); REQ-CAT-008 (catalog bootstrap out of a guided setup as an explicit audited catalog act); REQ-ADM-011 (a fresh installation fully operable from its bootstrap administrator — ADR-0106, ADR-0107). STR-028..030 added (27 → 30 stakeholder requirements); 284 → 296 software-requirement rows. <strong>Unlike the v1.8/v1.9 rows, these enter with coverage GAPS expected</strong>: the five families ship verified by tests and the PQ walk, but their new ids are not yet cited in tests or journey station declarations, so the matrix GAP count goes 0 → 12 at this baseline. The citation/journey adoption is the registered follow-up, not a claim made here. Delta detail below. | | <code>requirements-v2.1</code> | 2026-08-16 | Nicolas Burri | The ADR-0116 maintenance-surface delta (shipped in v0.9.12): <strong>REQ-BAK-006</strong> (the in-app EXPORT_BACKUP-gated backup act — asynchronous single-flight with a named refusal on concurrency, audited at both ends with failed runs recorded never silent, archive byte-compatible with the deploy-side producer so one restore drill covers both, attachment-hardened download; restore stays exclusively deploy-level), <strong>REQ-BAK-007</strong> (backup evidence on the admin System surface incl. the 7-day no-verified-backup installation finding in the setup-finding grammar), <strong>REQ-ADM-012</strong> (the admin System page: per-gate sections, the audited search-reindex act, honest read-only job heartbeats). 296 → 299 software-requirement rows; all three entered the matrix <strong>VERIFIED at minting</strong> (the v1.8 discipline — no backfill worklist). Sign-off given by Nicolas in-session 2026-08-16 and recorded on his behalf. |</p> <h3 id="the-v20-delta-detail">The v2.0 delta (detail)<a class="headerlink" href="#the-v20-delta-detail" title="Permanent link">¶</a></h3> <p><strong>BASELINED 2026-08-08</strong> — review record: Nicolas's sign-off on the draft and this review pair ("I read both files and agree with all your points"). The rows are PROMOTED verbatim from <a href="https://github.com/nburri/lqms/blob/main/docs/planning/requirements-v2.0-draft.md"><code>docs/planning/requirements-v2.0-draft.md</code></a> (now marked historical); the trigger is finding <strong>S7</strong> of the <a href="https://github.com/nburri/lqms/blob/main/docs/planning/review-2026-08-08-membership-spec.md">membership spec review</a> — the validation report's coverage derived from v1.9 while five function families were already in the product. <strong>12 new software requirements</strong> in <strong>two new groups</strong> plus three appended rows, and <strong>three new stakeholder requirements</strong>:</p> <ul> <li><strong>Memberships (ADR-0108; new group REQ-MEM):</strong> REQ-MEM-001 (invited → accepted / declined / removed as recorded state, each act audited at the mandator's own scope — the invitation <em>is</em> a record), REQ-MEM-002 (acceptance is what starts membership; pre-assigned responsibilities are an offer applied at acceptance, degrading to a visible gap rather than failing), REQ-MEM-003 (membership grants no content access, and a non-member sees nonexistence, not refusal — the ADR-0012 admin ≠ content line held at the tenant boundary), REQ-MEM-004 (no enumeration oracle to the inviter; credentials only via the IdP, never through LQMS — ADR-0063), REQ-MEM-005 (link hygiene: single-use, unguessable, digest-only at rest, expiring, indistinguishable failure answers), REQ-MEM-006 (ending a membership is a tenant act; existence elsewhere is untouched — only installation administration deactivates a person). A NEW group because belonging to a mandator is a distinct concern from REQ-ADM's permission/assignment machinery and REQ-USR's person lifecycle: both of those already existed while membership had no representation at all.</li> <li><strong>Technical dossiers (ADR-0083, ADR-0104; new group REQ-TD):</strong> REQ-TD-001 (frozen pins in, one render at issue, stored bytes out under a recorded hash — the artifact of record), REQ-TD-002 (a reader missing pinned elements gets a freshly rendered partial copy visibly marked as not the record; unmarked ⇒ record), REQ-TD-003 (issued dossiers are undeletable, correction is forward-only, draft exports watermarked). A NEW group because the dossier is a deliverable assembled <em>over</em> documents, not a document behaviour: REQ-DOC's rows govern the versions it pins.</li> <li><strong>In-app manual (ADR-0099):</strong> REQ-UI-027 — the manual ships inside the application and is versioned with it, help affordances open the topic documenting their surface, and the build fails on a missing topic, scene capture or surface link (bidirectionality enforced, not aspired to). Renumbered from the draft's <code>REQ-UI-0xx</code>.</li> <li><strong>Catalog bootstrap:</strong> REQ-CAT-008 — a guided setup that needs an absent catalog entry offers its one-click creation to a catalog administrator as an explicit audited catalog act (types complete with their definition, roles with the standard permission sets), and hands off honestly to callers without the permission instead of misaddressing them. Renumbered from <code>REQ-CAT-0xx</code>.</li> <li><strong>Fresh-install completion (ADR-0106, ADR-0107, ADR-0108):</strong> REQ-ADM-011 — the property the 0106/0107 arcs were built for, previously only <em>partially</em> implied by existing REQ-ADM rows: a fresh installation is fully operable from its bootstrap administrator with no out-of-band data manipulation, and every guided path is walkable to its end. Renumbered from <code>REQ-ADM-0xx</code>.</li> <li><strong>Stakeholder level:</strong> STR-028 (invitation-and-acceptance membership, separate from access, with no cross-organization effect — ADR-0108), STR-029 (an issued dossier is a persisted, byte-stable, hash-identified record; a non-record copy says so — ADR-0083, ADR-0104), STR-030 (the system carries its own versioned user documentation — ADR-0099). The house STR table carries no trace column, so those ADR references live here rather than in the row.</li> </ul> <p><strong>Coverage honesty at this baseline (the difference from v1.8/v1.9):</strong> those two deltas backfilled citations in the same pass and landed at GAP zero. This one does not — the twelve new ids enter the matrix as GAPs because no test or journey station cites them <em>yet</em>, while the behaviour itself is covered (the ADR-0108 arc, the dossier arc, the manual lint, the 0106/0107 arcs all shipped with tests, and the PQ walk's station 14 exercises the membership half). What is missing is the citation, not the verification. Registered follow-up, in order: cite the new ids in the tests that already exercise them, adopt them in the journey station declarations (the dossier station and station 14, per the draft's own note), and bring the validation report's §4 intended-use narrative current with dossiers and membership.</p> <h3 id="the-v19-delta-detail">The v1.9 delta (detail)<a class="headerlink" href="#the-v19-delta-detail" title="Permanent link">¶</a></h3> <p><strong>BASELINED 2026-07-26</strong> — sign-off given by Nicolas in-session and recorded on his behalf at his explicit request (the tag annotation carries the same provenance). Delta for <strong>Stage C — the Validation & Regulatory axes</strong> (ADR-0084, all five waves merged 2026-07-24), which closes the two remaining trace axes of the traceability model and brings the trace web to all five axes at item level (requirements, risk, design, validation, regulatory). <strong>8 new software requirements</strong> in <strong>two new groups</strong> plus one new REQ-UI row and five annotations. Like the v1.8 preparation (and unlike v1.7), the citations were backfilled in the SAME pass, so every new row lands <code>verified</code> at preparation — the matrix GAP count stays ZERO and no new override was needed (every arc shipped with dedicated tests):</p> <ul> <li><strong>Validation axis (ADR-0084 Waves 2-3):</strong> new group <strong>REQ-VAL</strong> — REQ-VAL-001 (the <code>user-need</code> trace-item type, attr <code>source</code>, the <code>validates</code> target), REQ-VAL-002 (the <code>validation-case</code> type, attr <code>intendedUseRef</code>,</li> <li>the new <code>validates</code> edge, item- AND document-level), REQ-VAL-003 (the <code>design-element</code> type, attr <code>designKind</code>, + design-element as a new <code>satisfies</code> SOURCE), REQ-VAL-004 (the STRICT per-scope <code>designKind</code> value set — shipped default <code>architecture|interface|component|unit</code>, per-scope override, server 422 on an unknown value, RLS — the OQ-3 decision), REQ-VAL-005 (the derived validation-matrix view + flat CSV + the three gap flags + the design-realization leg, reusing the ADR-0088 evidence classing).</li> <li><strong>Regulatory axis (ADR-0084 Waves 4-5):</strong> new group <strong>REQ-GSP</strong> — REQ-GSP-001 (the <code>regulatory-ref</code> type with the hash-frozen attrs <code>source | clause | applicability | justification</code>, GSPR-as-content per ADR-0061 D-5, + the new <code>complies-with</code> edge from a requirement AND a design-element), REQ-GSP-002 (the derived GSPR conformity view + flat CSV + the four gap verdicts, with <strong>NA_WITHOUT_JUSTIFICATION a HARD gap</strong> per OQ-8). Two groups (not one) mirror the RISK-is-its-own-domain-group precedent and ADR-0084's explicit two-axis framing: design validation (ISO 13485 §7.3) and regulatory conformity (MDR Annex I / GSPR) are distinct regulatory bases, and the regulatory axis will grow (the Annex II §4 dossier consumes the conformity view later, ADR-0083 note). <code>design-element</code> sits in REQ-VAL (its Wave-2 home) though it sources both axes.</li> <li><strong>GSPR authoring grid (OQ-7 — Nicolas's deliberate override of the defer lean):</strong> REQ-UI-026, the table-shaped authoring/reading surface over regulatory-ref items, each row IS a <code>:::regulatory-ref</code> block (mirrors the risk grid REQ-UI-023).</li> <li><strong>Annotations (no new row):</strong> REQ-REL-007 (the trace-link vocabulary gains <code>validates</code> + <code>complies-with</code>, and <code>satisfies</code> gains the design-element source); REQ-REP-010 (the derived traceability report now composes a validation-matrix and a GSPR-conformity section with matching digest lines — the two axes ride the one report and its single audit-pack entry, so <strong>no separate audit-pack artifact/row</strong>); REQ-UI-022 (the reserved validation / GSPR hub tiles are now live); REQ-UI-018 (the per-scope design-kind vocabulary editor landed as an ACTIVATE_CATALOG_ENTRIES field on the Document-types tab per the "new knobs land as fields" rule); REQ-UI-025 (the validation-matrix and GSPR-conformity pages join the one-scope-context list).</li> </ul> <p>Deliberately NOT given rows (checked this pass; judgment rule 3): the <strong>Wave-1 schema-driven attribute UI</strong> (the dialog collapse onto <code>TraceItemDialog</code>, −316 lines) is a behavior-frozen frontend refactor (projection byte-identical, engines zero-diff) with no new user-visible behavior — it is the mechanism the new type rows author through, covered by REQ-DOC-035's additive-registration principle, not a requirement of its own; the <strong>may-define extension to the six/seven types</strong> rides REQ-DOC-034's existing per-(scope, type) flag mechanism (each new type row states its gate, exactly as REQ-RISK-002 does), so no new row; the <strong>report-section + audit-pack integration</strong> rides the REQ-REP-010 annotation above (the sections are part of the one derived report). No new schema content COLUMN ships (trace-item attributes live inside the tree, ADR-0057; the only DB touch is the <code>trace_link</code> CHECK + the <code>design_kind_vocabulary</code> config table, V067), so the schema-extension lifecycle audit fires only for RLS-separation-per-new-type — covered by <code>DesignKindVocabularyRlsSeparationTest</code> and <code>RegulatoryLinkRlsSeparationTest</code>.</p> <p>Verified-by-test mapping for the v1.9 delta (each id cited at the most specific carrier):</p> <table> <thead> <tr> <th>Requirement</th> <th>Verifying test(s)</th> </tr> </thead> <tbody> <tr> <td>REQ-VAL-001</td> <td><code>ValidationAxisRegistryTest</code> (user-need registration + fence + content-hash contract); <code>ValidationAxisSaveTest</code> (per-(scope,type) may-define gate); <code>PdfExportServiceTest</code> (the user-need fence renders formatted, not a raw literal); <code>validation-axis.spec.ts</code> (slash-gating + dialog authoring)</td> </tr> <tr> <td>REQ-VAL-002</td> <td><code>ValidationAxisRegistryTest</code>; <code>ValidationAxisSaveTest</code> (the <code>validates</code> edge — item-level AND document-level); <code>PdfExportServiceTest</code> (validation-case fence); <code>validation-axis.spec.ts</code></td> </tr> <tr> <td>REQ-VAL-003</td> <td><code>ValidationAxisRegistryTest</code>; <code>ValidationAxisSaveTest</code> (design-element saves; satisfies gains the design-element source); <code>PdfExportServiceTest</code> (design-element fence); <code>validation-axis.spec.ts</code></td> </tr> <tr> <td>REQ-VAL-004</td> <td><code>DesignKindVocabularyRlsSeparationTest</code> (cross-scope isolation of the value set at the DB level); <code>ValidationAxisSaveTest</code> (default OK / unset OK / unknown → 422 / override changes the set / clear reverts); <code>validation-axis.spec.ts</code> (designKind enum resolved from the scope's set)</td> </tr> <tr> <td>REQ-VAL-005</td> <td><code>ValidationMatrixLogicTest</code> (derivation, the three gap flags, ADR-0088 classing, RLS degradation); <code>ValidationMatrixResourceTest</code> (JSON + CSV matrix + VIEW_TRACEABILITY 403 + cross-scope separation); <code>validation-matrix.spec.ts</code> (sub-page + hub tile + one-scope-context)</td> </tr> <tr> <td>REQ-GSP-001</td> <td><code>RegulatoryAxisRegistryTest</code> (regulatory-ref registration + hash-frozen attr order); <code>RegulatoryAxisSaveTest</code> (may-define gate; empty-justification N/A saves; <code>complies-with</code> from a requirement AND a design-element); <code>RegulatoryLinkRlsSeparationTest</code> (the <code>complies-with</code> edge RLS separation); <code>PdfExportServiceTest</code> (regulatory-ref fence); <code>regulatory-axis.spec.ts</code> (slash-gating + dialog)</td> </tr> <tr> <td>REQ-GSP-002</td> <td><code>GsprConformityLogicTest</code> (the four gap verdicts incl. NA_WITHOUT_JUSTIFICATION as a HARD gap, ADR-0088 classing, clause ordering, RLS degradation); <code>GsprConformityResourceTest</code> (JSON + gap verdicts + CSV + VIEW_TRACEABILITY 403); <code>gspr-conformity.spec.ts</code> (sub-page + hub tile + the unjustified-N/A hard-gap chip)</td> </tr> <tr> <td>REQ-UI-026</td> <td><code>regulatory-axis.spec.ts</code> (the GSPR grid authors a row and a cell edit round-trips to the prose block)</td> </tr> </tbody> </table> <p><strong>Still without rows at this preparation (checked, deferred):</strong> the ADR-0086 requirement trace chains + CSV path export and the ADR-0085 relation-layer consolidation — Stage C's two views COMPOSE the chains read model (<code>RequirementChainLogic</code>) but add no rows for it; those pre-Stage-C arcs remain the "known later-increment candidates" below for a dedicated coverage audit, out of this Stage-C-scoped delta.</p> <!-- The v1.8 delta below was released 2026-07-24; retained context: --> <p><strong>Released 2026-07-24 (was: prepared).</strong> Delta for the arcs that landed ADR-first after the v1.7 baseline (ADR-0087..0094); <strong>9 new software requirements</strong> in <strong>one new group</strong> plus annotations, bringing the baseline back to covering the shipped system. Unlike the v1.7 preparation, the citations were backfilled in the SAME pass, so every new row lands <code>verified</code> (matrix GAP unchanged at zero) — no new override was needed, all arcs shipped with dedicated tests:</p> <ul> <li><strong>Recurring obligations (ADR-0089; calendar schedules ADR-0094):</strong> new group <strong>REQ-OBL</strong> — REQ-OBL-001 (per-scope obligation config, RECORD completion type, CONFIGURE_REVIEW_POLICY CRUD, RLS), REQ-OBL-002 (completion-by-released-record; derived-never-stored status; the self-contained sweep raises/reconciles the non-manually-resolvable <code>OBLIGATION_DUE</code> task; sweep–derivation parity), REQ-OBL-003 (<code>VIEW_OBLIGATIONS</code> oversight roll-up), REQ-OBL-004 (INTERVAL/MONTHLY/YEARLY kinds, the never-too-late clamp, occurrence-after-anchor next-due, calendar parity). A NEW group because recurring QMS-operations duties (ISO 13485 §6.3) are a distinct concern from REQ-TRN's person-and-document read-acknowledgement.</li> <li><strong>DIRECT release flow (ADR-0091):</strong> REQ-LC-027 (STANDARD/DIRECT release flow — single-person DRAFT→RELEASED for RECORD-category types only, releaser-gated, guardrails preserved); REQ-LC-003 annotated (the release-flow axis, orthogonal to REQ-LC-007's release mode); REQ-UI-018 annotated (the knob landed as a Review-policies field per its own rule).</li> <li><strong>Orphan-blob quarantine bin (ADR-0092):</strong> REQ-DOC-038 (two-phase quarantine→purge, 30-day bin, registry-not-file-move, the column-inventory architecture test, self-healing), refining REQ-DOC-013 (annotated; the base GC row itself flipped GAP→<code>verified</code> in the same wave).</li> <li><strong>One scope context (ADR-0093):</strong> REQ-UI-025 (the toolbar switcher is the only scope filter; neutral picker on ALL for per-scope views; display-filter-only — the server still authorizes).</li> <li><strong>Scope traceability report (ADR-0087):</strong> REQ-REP-010 (the derived per-scope gap-digest PDF, <code>VIEW_TRACEABILITY</code>-gated, hub download + permission-conditional audit-pack entry).</li> <li><strong>Product version (ADR-0090 §3):</strong> REQ-API-006 (<code>productVersion</code> via <code>/api/version</code> + the UI build/version display; <code>EXPORTED</code>-event tool version).</li> <li><strong>Verification evidence classes (ADR-0088):</strong> no new row — a refinement annotated on REQ-REP-009 (verified vs planned <code>verifies</code> classes, reported as separate counts; the fully-verified roll-up).</li> </ul> <p>Already covered (checked this pass, no row needed): OpenAPI generation (REQ-API-004 — <code>verified</code> via <code>OpenApiSpecTest</code>); USER_BOUND invite-binding audit (REQ-USR-010 — <code>verified</code> via <code>UserProvisioningTest</code>). Deliberately NOT given rows: the ADR-0089 §5 optional trace-tie and the ADR-0088 §5 freshness-as-a-rule (optional / not built).</p> <p>Verified-by-test mapping for the v1.8 delta (each id cited at the most specific carrier):</p> <table> <thead> <tr> <th>Requirement</th> <th>Verifying test(s)</th> </tr> </thead> <tbody> <tr> <td>REQ-OBL-001</td> <td><code>RecurringObligationTest</code> (RLS separation; CONFIGURE_REVIEW_POLICY CRUD gate); <code>RecurringObligationResourceTest</code>; <code>obligations.spec.ts</code> (scope-config Obligations tab)</td> </tr> <tr> <td>REQ-OBL-002</td> <td><code>RecurringObligationTest</code> (derived status: no-execution/fresh/due-soon/overdue, completion-anchored); <code>RecurringObligationSweepTest</code> (raise/idempotent/auto-resolve)</td> </tr> <tr> <td>REQ-OBL-003</td> <td><code>RecurringObligationTest</code> (<code>VIEW_OBLIGATIONS</code> oversight gate); <code>RecurringObligationResourceTest</code> (oversight 403); <code>obligations.spec.ts</code> (oversight page + route guard)</td> </tr> <tr> <td>REQ-OBL-004</td> <td><code>ObligationScheduleTest</code> (kinds, clamp, next-due parity, per-kind validation)</td> </tr> <tr> <td>REQ-LC-027</td> <td><code>DirectReleaseTest</code> (happy path, non-releaser 403, comments gate, STANDARD refuses direct, action reflection); <code>direct-release.spec.ts</code>; <code>obligations.spec.ts</code> (release-flow control, RECORD-only)</td> </tr> <tr> <td>REQ-DOC-038</td> <td><code>BlobGcSweepServiceTest</code> (quarantine→purge round trip, never-delete-referenced, rescue, purge-time re-verify); <code>BlobHashColumnInventoryTest</code> (column-inventory architecture test)</td> </tr> <tr> <td>REQ-UI-025</td> <td><code>scope-context.spec.ts</code> (one context; neutral picker; deep link)</td> </tr> <tr> <td>REQ-REP-010</td> <td><code>TraceabilityReportResourceTest</code> (PDF + hardening headers + <code>VIEW_TRACEABILITY</code>/cross-scope 403); <code>traceability-hub.spec.ts</code> (hub download delivery)</td> </tr> <tr> <td>REQ-API-006</td> <td><code>build-info.spec.ts</code> (product version leads the build stamps; pre-release "unreleased")</td> </tr> </tbody> </table> <p><strong>v1.7 citation-backfill worklist — COMPLETE.</strong> The 27 rows below (prepared GAP at v1.7) were promoted to <code>verified</code> by citing their ids in the named tests; the matrix now reports GAP ZERO. Retained as the provenance of that promotion:</p> <table> <thead> <tr> <th>Requirement</th> <th>Verifying test(s)</th> </tr> </thead> <tbody> <tr> <td>REQ-TRN-009</td> <td><code>TrainingPlanServiceTest</code> (self-record/four-eyes-confirm/supersede/evidence/renewal-sweep)</td> </tr> <tr> <td>REQ-TRN-010</td> <td><code>TrainingPlanServiceTest</code> (derived obligations); <code>my-training.spec.ts</code></td> </tr> <tr> <td>REQ-TRN-011</td> <td><code>TrainingComplianceServiceTest</code> (roll-up, overdue boundary, neutral-release anchor); <code>EndpointBodyBindingTest</code> (due-window)</td> </tr> <tr> <td>REQ-DOC-031</td> <td><code>DocumentServiceTest</code> (reason+impact ride the revision; <code>setChangeInfo</code> freeze/409/v1); <code>LifecycleServiceTest</code> (SUBMIT pins reason+impact); <code>EndpointBodyBindingTest</code></td> </tr> <tr> <td>REQ-DOC-032</td> <td><code>DocumentServiceTest</code> (startAtVersion continuity; source-history claims record; red-line audit actors); <code>DisposalServiceTest</code> (source_history severed)</td> </tr> <tr> <td>REQ-DOC-033</td> <td><code>PdfExportServiceTest</code> (stamped/audited PDF; DRAFT/IN_REVIEW 409; REVOKED + cross-scope 404; mermaid label; alt placeholder); <code>pdf-export.spec.ts</code></td> </tr> <tr> <td>REQ-EFF-009</td> <td><code>DocumentServiceTest</code> (effectiveStanding / listVersions over backdated effective_from) — backfill target</td> </tr> <tr> <td>REQ-UI-018</td> <td><code>ScopeConfigReadResourceTest</code> (type catalog); <code>scope-config.spec.ts</code> (tab gating, redirect)</td> </tr> <tr> <td>REQ-UI-019</td> <td><code>my-training.spec.ts</code> (plan render, record, dashboard, compliance/aging)</td> </tr> <tr> <td>REQ-UI-020</td> <td><code>pdf-export.spec.ts</code> (Download PDF on RELEASED/REVOKED; absent on DRAFT/IN_REVIEW)</td> </tr> <tr> <td>REQ-UI-021</td> <td><code>change-reason.spec.ts</code> (revise requires reason; IN_REVIEW prominence; v1 empty; editor edit)</td> </tr> <tr> <td>REQ-DOC-034</td> <td><code>RequirementLogicTest</code>, <code>RequirementRegistryServiceTest</code>; <code>requirement.spec.ts</code></td> </tr> <tr> <td>REQ-DOC-035</td> <td><code>TraceItemGeneralizationTest</code> (synthetic second type — registry/links/suspect/coverage, zero engine change)</td> </tr> <tr> <td>REQ-DOC-036</td> <td><code>PdfExportServiceTest</code> (bookmarks/anchors, context-dependent <code>doc:</code> links, merged ToC/chapters); <code>pdf-export.spec.ts</code></td> </tr> <tr> <td>REQ-DOC-037</td> <td><code>PdfExportServiceTest</code> (streamed zip, sha256 manifest, citation closure, completeness marker); <code>audit-pack.spec.ts</code></td> </tr> <tr> <td>REQ-REL-007</td> <td><code>RequirementLinkServiceTest</code> (edge vocabulary, suspect, dedupe/self-edge); <code>requirement-links.spec.ts</code></td> </tr> <tr> <td>REQ-REL-008</td> <td><code>RequirementLinkServiceTest</code> + <code>RelationServiceTest</code> (source-must-have-DRAFT 409; clearSuspect exempt)</td> </tr> <tr> <td>REQ-REP-009</td> <td><code>RequirementRegistryServiceTest</code>, <code>TraceMatrixTest</code> (verifies-OR-satisfies separate counts, uncovered list); <code>traceability.spec.ts</code></td> </tr> <tr> <td>REQ-RISK-001</td> <td><code>RiskTraceItemTest</code> (attribute set, recorded tokens); <code>risk.spec.ts</code></td> </tr> <tr> <td>REQ-RISK-002</td> <td><code>RiskTraceItemTest</code> (controlKind; mitigates/implemented-by/verifies edges)</td> </tr> <tr> <td>REQ-RISK-003</td> <td><code>RiskTraceItemTest</code> (gap flags, accepted-without-reduction, document implemented-by clears); <code>risk.spec.ts</code></td> </tr> <tr> <td>REQ-UI-022</td> <td><code>traceability-hub.spec.ts</code>, <code>traceability.spec.ts</code>, <code>traceability-training.spec.ts</code></td> </tr> <tr> <td>REQ-UI-023</td> <td><code>risk-grid.spec.ts</code></td> </tr> <tr> <td>REQ-UI-024</td> <td><code>audit-pack.spec.ts</code></td> </tr> <tr> <td>REQ-ADM-010</td> <td><code>TraceabilityPermissionSeparationTest</code>; <code>CoverageResourceTest</code>, <code>RelationResourceTest</code> (per-view server gate)</td> </tr> </tbody> </table> <p><strong>Known later-increment row candidates</strong> (arcs still without rows): periodic-review status visibility (ADR-0076/V054 — deferred at v1.7 preparation); the ADR-0083 dossier proper (SectionPin, regulatory skeletons, DRAFT→ISSUED) when built; the requirement trace chains + CSV path export (ADR-0086) and the relation-layer consolidation (ADR-0085) — their shipped slices need a coverage audit at the next preparation to decide whether they warrant their own rows or ride existing ones. (Single-person record release is now built — REQ-LC-027, this delta.)</p> <p>Requirements specification for LQMS, in <strong>two levels</strong>:</p> <ol> <li><strong>Stakeholder requirements</strong> (<code>STR-NNN</code>) — the intended use; what CSV <strong>validation</strong> validates against. One file: <a href="stakeholder_requirements/">stakeholder_requirements.md</a>.</li> <li><strong>Software requirements</strong> (<code>REQ-<GROUP>-NNN</code>) — testable system behavior; what <strong>verification</strong> tests against. Every software requirement traces to at least one STR and, where applicable, the deciding ADR.</li> </ol> <p>LQMS is a pure software product, so no separate "system requirements" level exists — the software level <em>is</em> the system level. (Requirement documents of user projects managed <em>inside</em> LQMS are QMS content and out of scope.)</p> <p>Known coverage gaps and ambiguities in the current baseline are tracked in <a href="gap-analysis/">gap-analysis.md</a> (a working document, not part of the baseline); they feed change-control rounds.</p> <h2 id="structure">Structure<a class="headerlink" href="#structure" title="Permanent link">¶</a></h2> <table> <thead> <tr> <th>File</th> <th>Group</th> <th>Prefix</th> </tr> </thead> <tbody> <tr> <td><a href="stakeholder_requirements/">stakeholder_requirements.md</a></td> <td>Intended use</td> <td><code>STR</code></td> </tr> <tr> <td><a href="req_documents/">req_documents.md</a></td> <td>Documents, versions & storage</td> <td><code>REQ-DOC</code></td> </tr> <tr> <td><a href="req_lifecycle/">req_lifecycle.md</a></td> <td>Life cycle & reviews</td> <td><code>REQ-LC</code></td> </tr> <tr> <td><a href="req_separation/">req_separation.md</a></td> <td>Scopes, mandators & separation</td> <td><code>REQ-SEP</code></td> </tr> <tr> <td><a href="req_auth/">req_auth.md</a></td> <td>Authentication & session</td> <td><code>REQ-AUTH</code></td> </tr> <tr> <td><a href="req_admin/">req_admin.md</a></td> <td>Administration, permissions & onboarding</td> <td><code>REQ-ADM</code></td> </tr> <tr> <td><a href="req_users/">req_users.md</a></td> <td>User identity & lifecycle</td> <td><code>REQ-USR</code></td> </tr> <tr> <td><a href="req_signatures/">req_signatures.md</a></td> <td>Electronic signatures</td> <td><code>REQ-SIG</code></td> </tr> <tr> <td><a href="req_effectivity/">req_effectivity.md</a></td> <td>Effectivity, periodic review & validity</td> <td><code>REQ-EFF</code></td> </tr> <tr> <td><a href="req_data_protection/">req_data_protection.md</a></td> <td>Data protection, retention & disposal</td> <td><code>REQ-DPR</code></td> </tr> <tr> <td><a href="req_catalogs/">req_catalogs.md</a></td> <td>Catalogs, roles & users</td> <td><code>REQ-CAT</code></td> </tr> <tr> <td><a href="req_search/">req_search.md</a></td> <td>Search</td> <td><code>REQ-SRCH</code></td> </tr> <tr> <td><a href="req_backup/">req_backup.md</a></td> <td>Backup & restore</td> <td><code>REQ-BAK</code></td> </tr> <tr> <td><a href="req_audit_reporting/">req_audit_reporting.md</a></td> <td>Audit trail & regulatory reporting</td> <td><code>REQ-AUD</code> / <code>REQ-REP</code></td> </tr> <tr> <td><a href="req_api_ui/">req_api_ui.md</a></td> <td>API & user interface</td> <td><code>REQ-API</code> / <code>REQ-UI</code></td> </tr> <tr> <td><a href="req_nfr/">req_nfr.md</a></td> <td>Non-functional (capacity, availability, security)</td> <td><code>REQ-NFR</code></td> </tr> <tr> <td><a href="req_notifications/">req_notifications.md</a></td> <td>Notifications & tasks</td> <td><code>REQ-NOT</code></td> </tr> <tr> <td><a href="req_i18n/">req_i18n.md</a></td> <td>Internationalization (content language, time zones)</td> <td><code>REQ-I18N</code></td> </tr> <tr> <td><a href="req_relationships/">req_relationships.md</a></td> <td>Document relationships</td> <td><code>REQ-REL</code></td> </tr> <tr> <td><a href="req_migration/">req_migration.md</a></td> <td>Migration & import</td> <td><code>REQ-MIG</code></td> </tr> <tr> <td><a href="req_training/">req_training.md</a></td> <td>Read-acknowledgement & questionnaires</td> <td><code>REQ-TRN</code></td> </tr> <tr> <td><a href="req_obligations/">req_obligations.md</a></td> <td>Recurring obligations (periodic QMS duties)</td> <td><code>REQ-OBL</code></td> </tr> <tr> <td><a href="req_risk/">req_risk.md</a></td> <td>Risk management (ISO 14971 hazards & controls)</td> <td><code>REQ-RISK</code></td> </tr> <tr> <td><a href="req_validation/">req_validation.md</a></td> <td>Design validation & the validation traceability axis</td> <td><code>REQ-VAL</code></td> </tr> <tr> <td><a href="req_gspr/">req_gspr.md</a></td> <td>Regulatory conformity (GSPR / essential principles)</td> <td><code>REQ-GSP</code></td> </tr> <tr> <td><a href="req_sbom/">req_sbom.md</a></td> <td>Software bill of materials & supply-chain assurance</td> <td><code>REQ-SBOM</code></td> </tr> <tr> <td><a href="req_memberships/">req_memberships.md</a></td> <td>Mandator membership & invitations</td> <td><code>REQ-MEM</code></td> </tr> <tr> <td><a href="req_dossiers/">req_dossiers.md</a></td> <td>Technical documentation dossiers</td> <td><code>REQ-TD</code></td> </tr> </tbody> </table> <h2 id="conventions">Conventions<a class="headerlink" href="#conventions" title="Permanent link">¶</a></h2> <ul> <li>IDs are never reused after deletion; superseded requirements are struck through with a pointer to their successor, not removed.</li> <li>Each software requirement is individually testable; the trace column lists the satisfied STRs and deciding ADRs.</li> <li>Requirement → test traceability is maintained per the <a href="../process/verification_plan/">verification plan</a>.</li> <li>Open details inside a requirement are marked <code>TBD:</code> like everywhere else in the docs.</li> <li>Requirements carry a <strong>MoSCoW priority</strong> (Must / Should / Could / Won't) to enable MVP sequencing (GAP-21); the initial classification is done as a dedicated pass when implementation is planned, rather than retrofitted to every requirement now.</li> </ul> <h2 id="traceability">Traceability<a class="headerlink" href="#traceability" title="Permanent link">¶</a></h2> <p>A generated requirements-traceability matrix links every requirement to its test, implementation, and commit evidence and flags untraced gaps — see <a href="https://github.com/nburri/lqms/tree/main/docs/traceability">../traceability/</a> (regenerate with <code>python3 scripts/generate-traceability.py</code>).</p> </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="../decisions/adr-template/" class="md-footer__link md-footer__link--prev" aria-label="Previous: ADR-NNNN: <Title>"> <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"> ADR-NNNN: <Title> </div> </div> </a> <a href="stakeholder_requirements/" class="md-footer__link md-footer__link--next" aria-label="Next: Stakeholder Requirements"> <div class="md-footer__title"> <span class="md-footer__direction"> Next </span> <div class="md-ellipsis"> Stakeholder Requirements </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>