Skip to content
LQMS
5. Building Block View
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
5. Building Block View
Table of contents
5.1 Whitebox Overall System
5.2 Content record architecture (tree record + projection)
5.3 Level 2
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--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="#51-whitebox-overall-system" class="md-nav__link"> <span class="md-ellipsis"> 5.1 Whitebox Overall System </span> </a> </li> <li class="md-nav__item"> <a href="#52-content-record-architecture-tree-record--projection" class="md-nav__link"> <span class="md-ellipsis"> 5.2 Content record architecture (tree record + projection) </span> </a> </li> <li class="md-nav__item"> <a href="#53-level-2" class="md-nav__link"> <span class="md-ellipsis"> 5.3 Level 2 </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/architecture/05_building_block_view.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="5-building-block-view">5. Building Block View<a class="headerlink" href="#5-building-block-view" title="Permanent link">¶</a></h1> <h2 id="51-whitebox-overall-system">5.1 Whitebox Overall System<a class="headerlink" href="#51-whitebox-overall-system" title="Permanent link">¶</a></h2> <p>LQMS is a modular monolith (<a href="../../decisions/adr-0005-modular-monolith/">ADR-0005</a>): one Kotlin/Quarkus application plus a separate Angular frontend.</p> <pre class="mermaid"><code>graph TD FE["Angular frontend<br/>(separate application)"] subgraph Backend["Quarkus application (single deployable)"] API["api<br/>REST + DTOs, SSE, DI wiring,<br/>bootstrap, schedulers,<br/>SPA hosting, future MCP"] DOC["document<br/>documents, versions, IDs,<br/>derive; lifecycle state machine,<br/>release gate, review comments,<br/>attachments, PDF export"] LC["lifecycle<br/>contracts: domain events +<br/>publisher, approvals, review-policy<br/>& workflow-role repositories"] CAT["catalog<br/>roles, document types,<br/>activations, retention,<br/>user/role admin"] SCOPE["scope<br/>mandators, scopes,<br/>tenancy/RLS,<br/>authorization resolution"] IDENT["identity<br/>OIDC-subject users,<br/>invite/JIT provisioning"] STOR["storage<br/>blob store interface<br/>(FS now, S3 later)"] SEARCH["search<br/>indexing & retrieval<br/>(extraction candidate)"] BAK["backup<br/>in-app pg_dump + blob archive,<br/>backup evidence, job heartbeats"] AUD["audit<br/>append-only events"] NOTIF["notification<br/>tasks & inbox, delivery<br/>channels, event fan-out"] PERS["persistence<br/>Flyway migrations +<br/>generated jOOQ classes"] COMMON["common<br/>shared kernel: the domain-exception<br/>vocabulary + requireValid/checkState"] end DB[("PostgreSQL")] FS[("blob store<br/>file system / S3")] FE --> API API --> DOC & CAT & SCOPE & LC & SEARCH & BAK & NOTIF & IDENT & AUD & STOR DOC --> SCOPE & CAT & LC & SEARCH & STOR & AUD CAT --> SCOPE & IDENT & AUD BAK --> SCOPE & STOR & AUD SEARCH --> SCOPE & STOR & AUD NOTIF --> SCOPE & LC & AUD IDENT --> AUD AUD --> SCOPE DOC -. publishes events .-> NOTIF DOC & CAT & LC & SCOPE & IDENT & SEARCH & BAK & NOTIF & AUD & API --> PERS DOC & CAT & SCOPE & SEARCH & BAK & NOTIF & AUD & API --> COMMON PERS --> DB STOR --> FS</code></pre> <blockquote> <p><strong>Diagram currency — re-derived 2026-08-22, with the ADR-0120 shared-kernel split.</strong> Every <strong>solid</strong> edge above is a <em>real compile-time dependency</em>, derived by expanding the <code>import ch.lqms.*</code> statements of every module's <code>src/main</code> — not an intention sketch. The solid set is exactly the 48 module→module import edges the source exercises: no edge is asserted that the code does not have, and none is omitted. It is no longer a claim anybody has to re-check by hand — <code>ModuleDiagramTest</code> (<code>backend/architecture-tests</code>) parses this very Mermaid block on every build and diffs it against the imports in both directions. The single <strong>dotted</strong> edge (<code>document ⇢ notification</code>) is deliberately <em>not</em> a compile edge — it is the ADR-0034 runtime event flow: <code>document</code> publishes through the <code>lifecycle</code> publisher, <code>notification</code> subscribes to the <code>lifecycle</code> event types, and <code>api</code> wires the subscription at startup. Emitting modules never reference consumers.</p> <p><strong>The 2026-08-22 delta (ADR-0120).</strong> The eight <code>… → common</code> edges are new, and they are the whole change: extracting the shared domain-exception vocabulary out of <code>scope</code> <strong>added</strong> edges and removed none, because every module that reached into <code>scope</code> for a <code>NotFoundException</code> also reaches into it for <code>AuthorizedRequestContext</code> or <code>EffectiveAuthzRepository</code>. What the split bought is not a thinner graph but an honest one — a <code>… → scope</code> edge now means <em>authorization</em>, and the count behind it fell accordingly (<code>api → scope</code> 22 importing files → 5, <code>audit → scope</code> 3 → 1). <code>common</code> itself imports nothing: it is a leaf, so it can never participate in a cycle.</p> <p>Two Gradle-declared dependencies are deliberately <strong>not</strong> drawn because no source uses them: <code>lifecycle → {scope, catalog, audit}</code> and <code>backup → document</code> (KDoc links only). <code>lifecycle</code>'s only real outbound edge is <code>persistence</code> — the visual proof of the contracts-only split described in the note below. <code>test-support</code> and the test-only <code>architecture-tests</code> module are omitted (no production edges).</p> <p><strong>Pending delta of 2026-08-18 — APPLIED 2026-08-22.</strong> The paragraph that stood here predicted that <code>PooledConnections.kt</code> (then uncommitted) would make the <code>api → persistence</code> edge real and invalidate the <code>persistence</code> row's "no hand-written Kotlin". It landed in <code>d646b6da</code> — an ancestor of the very commit that corrected this diagram — and the delta sat unapplied until <code>ModuleDiagramTest</code> (the durable §5 checker, built 2026-08-22 from the Fable re-check's finding 1) failed on it during its first run. Both statements are now corrected on this page. The ADR-0036 question the old paragraph flagged was ruled by Nicolas on 2026-08-21 (fix-log decision 6): <code>PooledConnections</code> STAYS in <code>persistence</code> — it holds no queries, native or jOOQ, only JDBC connection lifecycle — while <code>RlsScopeContext</code> deliberately stays in <code>scope</code>, because those 76 lines are the tenant-separation rule expressed as code, not plumbing. From this date the diagram is enforced against the source graph by the checker, so the next drift fails the build instead of waiting for a reader.</p> </blockquote> <table> <thead> <tr> <th>Module</th> <th>Responsibility</th> <th>Notes</th> </tr> </thead> <tbody> <tr> <td><code>scope</code></td> <td>Mandators, scopes, scope codes, capability flags, tenancy/RLS integration (<code>RlsScopeContext</code>, <code>AuthorizedRequestContext</code>) and the effective-authorization resolution (<code>EffectiveAuthzRepository</code>) — <strong>authorization and tenancy only</strong> since <a href="../../decisions/adr-0120-shared-kernel-module/">ADR-0120</a> moved the shared domain-exception set out to <code>common</code>. <code>RlsScopeContext</code> and <code>TransactionPostCommit</code> deliberately stay here (fix-log decision 6: those 76 lines are the separation rule as code, not plumbing)</td> <td>Core of separation (ADR-0002, ADR-0026); depends only on <code>common</code> and <code>persistence</code></td> </tr> <tr> <td><code>identity</code></td> <td>User identities (stable OIDC subject), invite/JIT provisioning, activate/deactivate</td> <td>ADR-0011/0013; global (no RLS); extends the ADR-0005 module set</td> </tr> <tr> <td><code>catalog</code></td> <td>Role/document-type catalogs, per-scope activations & assignments, directory lookups, retention rules & legal holds, user/role administration</td> <td>ADR-0004, ADR-0016</td> </tr> <tr> <td><code>document</code></td> <td>Documents, versions, document IDs, provenance, derive & instantiate; the tree-record content model (PM_DOC tree + derived projection, server-side <code>PmDocText</code> extraction); <strong>and the lifecycle state machine</strong> (<code>LifecycleService</code>, incl. the DIRECT single-person <code>directRelease</code> transition, state-conditional transitions in <code>VersionRepository</code>, <code>ReleaseGate</code>), <strong>review comments</strong> (<code>CommentService</code>), PDF export (<code>PdfExportService</code>/Apache FOP), attachments, acknowledgements, questionnaires, periodic review, coverage rules, disposal, the training plan/compliance read models, the <strong>derived traceability read models</strong> (<code>RequirementChainService</code>, <code>RiskTraceabilityService</code>, the <code>TraceCoverage</code> edge-type-set engine, <code>TraceabilityReportService</code>, and — since Stage C, <a href="../../decisions/adr-0084-validation-regulatory-axes/">ADR-0084</a> — the validation & regulatory axes' <code>ValidationMatrixService</code> + <code>GsprConformityService</code> plus the per-scope design-kind vocabulary <code>DesignKindService</code>), <strong>recurring obligations</strong> (<code>RecurringObligationService</code>; the next-due rule itself is the shared SQL function <code>lqms_obligation_next_due</code>, V070 — one encoding for the oversight derivation and both sweep passes, a fold over the completion history), and <strong>orphan-blob GC</strong> (<code>BlobGcSweepService</code>/<code>BlobGcRepository</code>). Since 2026-07 <code>DocumentService</code> is split: the metadata cluster lives in <code>DocumentMetadataService</code>, and one <code>WorkflowActionEvaluator</code> seam computes both the <code>getVersion</code> action reflection and the transition enforcement (§8.10)</td> <td>ADR-0001/0002, ADR-0003, ADR-0057/0058, ADR-0074, ADR-0084, ADR-0085/0086/0087/0088, ADR-0089/0091/0092/0094</td> </tr> <tr> <td><code>lifecycle</code></td> <td><strong>Contracts only</strong>, no state machine and no comments: the domain-event types + <code>DomainEventPublisher</code> (ADR-0034), the append-only approval repository, and the review-policy + per-document workflow-role binding repositories/resolvers that <code>document</code>'s state machine consumes — the resolved policy now carries the STANDARD/DIRECT <code>release_flow</code> (ADR-0091), an axis orthogonal to the AUTOMATIC/EXPLICIT <code>release_mode</code></td> <td>ADR-0003, ADR-0030, ADR-0034, ADR-0064, ADR-0091</td> </tr> <tr> <td><code>storage</code></td> <td>Content-addressed blob store behind an interface (<code>ContentStore</code> + FS implementation); the interface also enumerates a scope's stored blobs (<code>list(scope)</code> / <code>listScopes()</code>) so the orphan-blob GC can compute stored-minus-referenced (ADR-0092)</td> <td>Extraction-ready (FS → S3); no module dependencies</td> </tr> <tr> <td><code>search</code></td> <td>Full-text indexing, retrieval, and disposal-driven purge</td> <td>Designated extraction candidate</td> </tr> <tr> <td><code>backup</code></td> <td>The in-app system-maintenance surface (<a href="../../decisions/adr-0116-system-maintenance-surface/">ADR-0116</a>): the EXPORT_BACKUP-gated backup act, executed asynchronously one-at-a-time as an image-pinned <code>pg_dump -Fc</code> plus a blob archive into the app's own volume (<code>BackupService</code>, <code>PgDumpExecutor</code>/<code>ProcessPgDumpExecutor</code>), the backup evidence read model and <code>NO_VERIFIED_BACKUP</code> finding (<code>BackupRecordRepository</code>, V102), and scheduled-job heartbeats (<code>SystemJobHeartbeatService</code>)</td> <td>ADR-0116, ADR-0060, ADR-0018; <strong>shipped</strong> v0.9.12 (~1,027 main-source lines; REQ-BAK-006/-007 verified, REQ-ADM-012). <strong>Restore stays deploy-level</strong> by decision — the <code>deploy/</code> scripts remain the restore and rehearsal path (ADR-0060); per-scope export (REQ-BAK-005) is still future</td> </tr> <tr> <td><code>audit</code></td> <td>Append-only audit events; the shared <code>AuditChanges</code> before/after builder</td> <td></td> </tr> <tr> <td><code>notification</code></td> <td>Tasks & inbox; pluggable delivery channels; acknowledgement/training fan-out — a <em>consumer</em> of the <code>lifecycle</code> domain events (compile-time dependency on <code>lifecycle</code> for the event types + <code>LifecycleTaskHandler</code> subscriber — the ADR-0005-legal edge blessed in ADR-0034)</td> <td>ADR-0019/0034/0035; event-driven</td> </tr> <tr> <td><code>api</code></td> <td>REST resources + request/response DTOs, exception mappers, security headers, CDI producers, SSE push/presence, bootstrap & deployment checks, the scheduled sweeps & GC (four advisory-lock-elected schedulers — task-sweep + notification delivery, certification-renewal, recurring-obligation, and orphan-blob GC; §8.4), and SPA hosting (Quarkus Quinoa); future MCP extension point</td> <td>Only externally reachable module; depends on all other backend modules</td> </tr> <tr> <td><code>persistence</code></td> <td>Technical module: Flyway migrations + jOOQ classes generated from the migrated schema, plus exactly one hand-written file — <code>PooledConnections.kt</code>, the physical connection-eviction helper (no queries; JDBC lifecycle only, decision 6 of the 2026-08-18 fix log)</td> <td>ADR-0008; exposes the jOOQ API to domain modules</td> </tr> <tr> <td><code>common</code></td> <td>The <strong>shared kernel</strong> (<a href="../../decisions/adr-0120-shared-kernel-module/">ADR-0120</a>): the cross-module domain-exception vocabulary in one file — <code>PermissionDeniedException</code>, <code>NotFoundException</code>, <code>GlobalScopeMissingException</code>, <code>InvalidStateException</code>, <code>DomainValidationException</code> — plus the <code>requireValid</code>/<code>checkState</code> guards that raise the last two. Nothing else lives here</td> <td>Depends on <strong>nothing</strong> (not even <code>persistence</code>), so any module may depend on it without a cycle; the api layer maps each type to its HTTP status in ONE place (<code>ScopeExceptionMappers</code>)</td> </tr> <tr> <td><code>test-support</code></td> <td>Test fixture module (<code>LqmsTestDb</code>): one PostgreSQL container + one migration pass per JVM, per-boot pristine clones via <code>CREATE DATABASE … TEMPLATE …</code></td> <td>Main source set, consumed via <code>testImplementation</code>; closes the parked F33 item (2026-07-16)</td> </tr> </tbody> </table> <p>Dependency rules are build-enforced (Gradle module graph) and verified by architecture tests; see ADR-0005. The authoritative rule set lives in the build configuration; the diagram above shows the edges the source actually exercises, which is the tighter set (see the currency note).</p> <blockquote> <p><strong>Note (2026-07-16, arc42-currency sweep):</strong> ADR-0005's initial decomposition placed the state machine, review policies, approvals, and comments in <code>lifecycle</code>. As the code grew, the transaction-heavy state machine and comments settled in <code>document</code> (they operate directly on versions and content), while <code>lifecycle</code> distilled down to the <em>contracts</em> those flows depend on — event types, approvals, and policy/workflow-role bindings — keeping the <code>document → lifecycle</code> edge one-directional and cycle-free. This section is the authoritative current split (ADR-0005 §Consequences delegates the living decomposition to arc42 §5).</p> <p><strong>Open code-comment defect, re-verified 2026-08-18 — still present.</strong> The KDoc on <code>backend/lifecycle/src/main/kotlin/ch/lqms/lifecycle/LifecycleModule.kt</code> still describes the module as <em>"life-cycle state machine, review policies, approvals, review comments"</em>, repeating the superseded ADR-0005 ownership claim: the state machine and comments live in <code>document</code>. First flagged here on 2026-07-16 and <strong>open for 33 days</strong>; the fix is a Kotlin edit and is therefore out of scope for a docs sweep. Registered as D6 in <a href="https://github.com/nburri/lqms/blob/main/docs/planning/review-2026-08-18-architecture.md">review-2026-08-18-architecture.md</a>. Until it lands, <strong>this section — not the KDoc — is authoritative</strong> on the <code>document</code>/<code>lifecycle</code> split.</p> </blockquote> <p>A test-only module <code>backend/architecture-tests</code> (not a production building block) enforces, via Konsist, the boundary rules the compile graph cannot express: production code resides under <code>ch.lqms</code>; only <code>api</code> declares JAX-RS resources; only <code>storage</code> performs file-system access; no module depends on <code>api</code>. The check always re-runs (Konsist reads sources off disk, invisible to Gradle's up-to-date tracking).</p> <h2 id="52-content-record-architecture-tree-record--projection">5.2 Content record architecture (tree record + projection)<a class="headerlink" href="#52-content-record-architecture-tree-record--projection" title="Permanent link">¶</a></h2> <p>The document content model is format <code>PM_DOC</code> only (<a href="../../decisions/adr-0057-tree-as-record/">ADR-0057</a>, <a href="../../decisions/adr-0058-v2-only-pre-production/">ADR-0058</a>; see §8.1 for the full concept). The authoritative content is a ProseMirror document <strong>tree</strong>; markdown is a derived <strong>projection</strong> computed by ONE shared projection function. That function is JavaScript and lives with the frontend, split browser/Node for bundle hygiene:</p> <ul> <li><code>webui/fidelity/projection.mjs</code> — browser-safe: <code>importMarkdown</code> / <code>projectMarkdown</code> / <code>canonicalizeTree</code> / <code>extractText</code>; the editor and reader import it.</li> <li><code>webui/fidelity/projection-node.mjs</code> — jsdom-backed <code>createProjection</code>, harness/seed only (kept out of the app bundle); the demo seed wraps it via <code>deploy/md-to-tree.mjs</code>, and <code>webui/fidelity/verify-stored-trees.mjs</code> is the offline projection-integrity audit (ADR-0057 §4).</li> </ul> <p>The backend <code>document</code> module owns the format-versioned storage (V039/V040), validates the submitted tree, and computes the search extraction server-side (<code>PmDocText</code>, the Kotlin port of <code>extractText</code>) — it never depends on the client projection for search (ADR-0057 §3). The reading view renders PM_DOC from the tree via a headless <code>DOMSerializer</code> behind the unchanged policy layer (<code>content-policy.ts</code>); the markdown-it path is retained only for transient instantiation-born MARKDOWN drafts (ADR-0058).</p> <h2 id="53-level-2">5.3 Level 2<a class="headerlink" href="#53-level-2" title="Permanent link">¶</a></h2> <p><strong>TBD — and the premise of the original placeholder has expired.</strong> This section said the Level-2 views would follow "once the modules take shape during implementation"; they have long since taken shape. As of 2026-08-18 the backend is 31.6k lines in <code>document</code> alone (98 files), 10.4k in <code>api</code> (81 files) and 7.2k in <code>catalog</code> (19 files), while the other eight production modules are each under 1.1k lines.</p> <p>So this is a <strong>real documentation gap, not a not-yet</strong>: the only module that genuinely needs a whitebox view is <code>document</code> — 57% of the backend, ~20 responsibility clusters in one flat package (the §5.1 table row is currently doing that job in prose, and is straining). The remaining modules are small enough that the §5.1 table plus their ADRs suffice, so a full Level-2 sweep would be make-work. Registered as D6/S1 in <a href="https://github.com/nburri/lqms/blob/main/docs/planning/review-2026-08-18-architecture.md">review-2026-08-18-architecture.md</a>; the decomposition of <code>document</code> is a design question (how it <em>should</em> be split), not a transcription job, so it is deliberately not answered here by a docs sweep.</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="../04_solution_strategy/" class="md-footer__link md-footer__link--prev" aria-label="Previous: 4. Solution Strategy"> <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"> 4. Solution Strategy </div> </div> </a> <a href="../06_runtime_view/" class="md-footer__link md-footer__link--next" aria-label="Next: 6. Runtime View"> <div class="md-footer__title"> <span class="md-footer__direction"> Next </span> <div class="md-ellipsis"> 6. Runtime View </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>