Skip to content
LQMS
The setup wizard: what the three lanes are, and what it actually writes
Initializing search
nburri/lqms
LQMS
nburri/lqms
Home
Evaluate LQMS
Evaluate LQMS
LQMS Known Limits
LQMS Security Posture
Architecture
Architecture
1. Introduction and Goals
2. Architecture Constraints
3. Context and Scope
4. Solution Strategy
5. Building Block View
6. Runtime View
7. Deployment View
8. Crosscutting Concepts
9. Architecture Decisions
10. Quality Requirements
11. Risks and Technical Debt
12. Glossary
The arrival bundle format
Decisions (ADRs)
Decisions (ADRs)
ADR-0001: Content-Addressed Document Storage with PostgreSQL as Source of Truth
ADR-0002: Single Instance with Scope Hierarchy and Copy-on-Derive
ADR-0003: Fixed Life Cycle States with Configurable Review Processes
ADR-0004: Global Catalogs for Roles and Document Types with Per-Scope Activation
ADR-0005: Modular Monolith
ADR-0006: Three-Layer Search with In-Database Index and Pluggable LLM
ADR-0007: Angular Frontend with Server-Side-Only Enforcement
ADR-0008: Flyway Migrations and jOOQ Codegen from the Migrated Schema
ADR-0009: RLS Enforcement via a Session-Scoped Authorized Scope Set
ADR-0010: Self-Managed QMS via an Internal Mandator
ADR-0011: Authentication via OIDC SSO with Server-Side (BFF) Sessions
ADR-0012: Permission-Based Authorization and System Bootstrap
ADR-0013: User Identity Lifecycle
ADR-0014: Electronic Signatures (Part 11 / Annex 11-Capable)
ADR-0015: Document Effectivity, Periodic Review & Validity
ADR-0016: Data Retention, Disposal & Privacy (FADP / GDPR)
ADR-0017: Multi-Part Version Content
ADR-0018: Non-Functional Targets (Capacity, Availability, Security)
ADR-0019: Notifications & Tasks
ADR-0020: Internationalization (Content Language, Time Zones, Formatting)
ADR-0021: General Typed Document Relationships
ADR-0022: Read-Acknowledgement & Questionnaires
ADR-0023: Migration / Import — Current Released State
ADR-0024: Draft / In-Review Cancellation
ADR-0025: Disposal & Erasure Mechanics (Storage, Index, Backups)
ADR-0026: RLS Runtime Safety — Connection-Pool Scope Isolation
ADR-0027: RLS Boundary — Content-Plane vs Control-Plane
ADR-0028: Stateless Encrypted Token-State Cookie (no server-side session store)
ADR-0029: Document Content Model — Draft-Freeze, Content-Table RLS, Append-Only Audit
ADR-0030: Review & Life-Cycle Realization Model
ADR-0031: Released-base readability enforcement & copy-on-derive mechanics
ADR-0032: Frontend realization — Quinoa, Angular Material, i18n & E2E
ADR-0033: CSRF control for the BFF session — SameSite + JSON content-type
ADR-0034: Notification realization — in-process domain events + system-context fan-out
ADR-0035: Fan-out contract as shipped — gate semantics, count disclosure, audit protocol
ADR-0036: Repository layer — services carry rules, repositories carry jOOQ
ADR-0037: Task scheduler — in-process tick, advisory-lock election, SQL sweep
ADR-0038: Periodic-review realization — derived due date, policy-gated confirmation
ADR-0039: Sweep & periodic-review contract as shipped — grants, guards, addressing
ADR-0040: Disposal-due surfacing — closure-anchored retention, scope-level legal hold
ADR-0041: Email channel & notification i18n — notification-as-outbox, structured messages
ADR-0042: Disposal execution — document tombstoning, single-actor hard-gated destruction
ADR-0043: Disposal blob deletion is post-commit, GC-backstopped
ADR-0044: Search FTS baseline — event-indexed, RLS-scoped search_index
ADR-0045: Image Attachments as Content Parts (Rich-Content Slice R2)
ADR-0046: Four-Eyes — Submitter Excluded from Approval
ADR-0047: Four-Eyes — Submitter-Only Exclusion
ADR-0048: Document Organization — Folder Tree per Scope
ADR-0049: Content Model Round 2 — Type Categories, Template Instantiation, Trace Relations, Completeness Rules
ADR-0050: Live Frontend — SSE State Push, CodeMirror 6, Draft Presence
ADR-0051: In-Text Document Links (doc: Scheme)
ADR-0052: Addressees & Read-Acknowledgement (REQ-TRN Realization)
ADR-0053: Addressees Per Document + Process Owner (amends ADR-0052 K-1)
ADR-0054: Process Owner Is a Role (amends ADR-0053 P-3)
ADR-0055: WYSIWYG Editing Mode over Markdown (editor step R4)
ADR-0056: Visual-Editor Chrome via Milkdown Crepe (gated adoption)
ADR-0057: Content Record Is the ProseMirror Document Tree; Markdown Becomes a Derived Projection
ADR-0058: PM_DOC Is the Only Content Format (pre-production cut; amends ADR-0057 §5)
ADR-0059: Editor Engine Switches to TipTap (spike-gated; supersedes the Milkdown/Crepe choice)
ADR-0060: Backup & Restore — Scripted Ordered Backup with Automated Restore Rehearsal
ADR-0061: CSV — Generated Validation Package per Release
ADR-0062: SBOM — CycloneDX over the Production Layers, Validated Against the Artifact
ADR-0063: User Identity Binds on Subject Only (Issuer Becomes Provenance)
ADR-0064: Per-Document Workflow Role Bindings (Author / Reviewer / Releaser), Enforced
ADR-0065: Diagrams — Excalidraw as the Manual Layer, Mermaid Stays for Text-First/UML
ADR-0066: WITHDRAW — the Author Side May Reclaim a Version from Review
ADR-0067: Review Comments — Anchored, Immutable, Resolvable
ADR-0068: Confluence/Jira QMS Import — Staged, Read-Only, Repeatable
ADR-0069: Arbitrary File Attachments — Download-Only Confinement
ADR-0070: Training Questionnaires — Versioned, Auto-Scored, Release-Gated
ADR-0071: Training Plans — Document Obligations + External Trainings & Certifications
ADR-0072: Diagrams — Self-Hosted draw.io Replaces Excalidraw
ADR-0073: Per-Scope QMS Configuration Surface
ADR-0074: PDF Export of Released Documents — Server-Side via Apache FOP over the Canonical Projection
ADR-0075: Source History Import — Continuity Without Forged Audit
ADR-0076: Periodic-review status visibility (completing MVP gap #2)
ADR-0077: Requirement Items — Keyed Blocks Inside Controlled Documents
ADR-0078: Generalized Trace Items (Traceability Model — Stage A)
ADR-0079: Risk & Risk-Control Items (Traceability Model — Stage B)
ADR-0080: Traceability Workspace — Hub, Sub-Pages, and Role-Gated Views
ADR-0081: Draft-Only Trace-Structure Changes, Server-Enforced
ADR-0082: Table-Shaped Risk Authoring over Risk Blocks
ADR-0083: The TD Dossier — a Versioned, Cross-Scope, Regulatory-Structured Deliverable
ADR-0084: Validation & Regulatory Axes (Traceability Model — Stage C)
ADR-0085: Relation-Layer Consolidation — One Trace Vocabulary, One Surface
ADR-0086: Requirement Traceability Chains — End-to-End Path View + Flat Path Export
ADR-0087: The Scope Traceability Report — One Derived Overview Artifact, Never a Controlled Document
ADR-0088: Verification Evidence Classes — Planned vs. Verified, Derived at the Read Layer
ADR-0089: Recurring Obligations — Periodic Tasks With Record Evidence, Not Calendar Series
ADR-0090: Release & Versioning Policy — Deliberate Releases, One Auditor-Facing Number
ADR-0091: Release Modes — Single-Person Record Release With a Structural Four-Eyes Floor
ADR-0092: Orphan-Blob Garbage Collection With a Quarantine Bin
ADR-0093: One Scope Context — the Toolbar Switcher Is the Only Scope Selector
ADR-0094: Calendar-Anchored Obligation Schedules (Clamped, Never Too Late)
ADR-0095: Key-Rule Governance — Free Until First Use, Then Frozen
ADR-0096: Transition Permissions — Always Visible, Deny Unless Granted
ADR-0097: A Governed Provisioning Surface — MANAGE_SCOPES
ADR-0098: Org Chart × Role System — Marriage at the Evidence Level, Never in Authorization
ADR-0099: The User Manual is an In-App Topic Reference, Not a Document
ADR-0100: LQMS Is the Living Quality Management System
ADR-0101: The Executable Validation Journey (PQ Evidence That Cannot Drift)
ADR-0102: Typed Template Variables (text | date | number — and Deliberately No Enum)
ADR-0103: npm audit Joins the Verification Gate as a Second Standing Input
ADR-0104: The Issued Dossier Is a Persisted Artifact of Record — and Clones to a New Draft
ADR-0105: Navigation Information Architecture — Group by Moment-of-Use
ADR-0106: The Client Reflection Follows Assignments, Not Only Content Reach
ADR-0107: The Audit Append Gate Follows Assignment Reach, Not Content Reach
ADR-0108: Mandator Membership — Invite-Accept, with Pre-Assigned Responsibilities
ADR-0109: Organization Founding Is Its Own Process
ADR-0110: The Audit Trail Is Not a Read Model
ADR-0111: The Imported-Person Model, and Project Portability's First Doctrines
ADR-0112: The Element-Kind Catalog — Semantics in the Model, Not Only in the Code
ADR-0113: Project Arrival Import — Records Arrive as They Are, People Arrive as They Were
ADR-0114: The Operating Model Arrives — Roles as Functions, Names as Words, People as This Instance's Decision
ADR-0115: Collaborative Draft Editing — Two Carets, One Truth, Honest Credit
ADR-0116: The System Maintenance Surface — the App Backs Itself Up, the Host Keeps One Dumb Job
ADR-0117: Role Documentation — a Link, a Finding, Per-Source Recognizers; Substitution Rejected
ADR-0118: The Offline QMS Copy — the Repo Carries the Audit Pack, Not a Second Renderer
ADR-0119: Module-Internal Package Structure — Capabilities First, Layers Second, the Root Is the Surface
ADR-0120: The Shared Kernel — the Domain-Exception Vocabulary Leaves the Authorization Module
ADR-0121: The Project Administrator Role — Per-Scope Administration With Read Access, Seeded in the Base Catalog
ADR-0122: Organization-Level Administration — the Cascade Stays, Becomes Visible, and Founds Projects
ADR-0123: Draft Save-Points — Every Save Restorable, Kept for the Life of the Version
ADR-0124: The Birth Path Completes Without Borrowing Content Clothes
ADR-0125: The Export Twin — Export Emits an Arrival Bundle
ADR-0126: Project Dissolution — the Un-Birth of an Unused Scope
ADR-0127: The Base-QMS Layers — One Library, Derived Adaptations, Local Records
ADR-0128: The GLOBAL Cascade Carries Administration, Never Content
ADR-0129: Role Identity from a GLOBAL Assignment Acts in GLOBAL Alone
ADR-0130: Break-Glass — the Project Administrator's Escalation Is a First-Class, Witnessed, Self-Expiring Act
ADR-0131: Role Substitution as Declared Adoption Edges — Emergency Cover Is Governed, Own-Name, Timed Staffing
ADR-0132: Dual-Hat Reviewer Satisfaction Is a Declared Policy Choice — the Strict Floor Stays the Default
ADR-NNNN:
</span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_5" > <div class="md-nav__link md-nav__container"> <a href="../../../requirements/" class="md-nav__link "> <span class="md-ellipsis"> Requirements </span> </a> <label class="md-nav__link " for="__nav_5" id="__nav_5_label" tabindex="0"> <span class="md-nav__icon md-icon"></span> </label> </div> <nav class="md-nav" data-md-level="1" aria-labelledby="__nav_5_label" aria-expanded="false"> <label class="md-nav__title" for="__nav_5"> <span class="md-nav__icon md-icon"></span> Requirements </label> <ul class="md-nav__list" data-md-scrollfix> <li class="md-nav__item"> <a href="../../../requirements/stakeholder_requirements/" class="md-nav__link"> <span class="md-ellipsis"> Stakeholder Requirements </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/gap-analysis/" class="md-nav__link"> <span class="md-ellipsis"> Requirements Gap Analysis </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_admin/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Administration, Permissions & Onboarding </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_api_ui/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: API & User Interface </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_audit_reporting/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Audit Trail & Regulatory Reporting </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_auth/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Authentication & Session </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_backup/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Backup & Restore </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_catalogs/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Catalogs, Roles & Users </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_data_protection/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Data Protection, Retention & Disposal </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_documents/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Documents, Versions & Storage </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_dossiers/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Technical Documentation Dossiers </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_effectivity/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Effectivity, Periodic Review & Validity </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_gspr/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Regulatory Conformity (GSPR / Essential Principles) </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_i18n/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Internationalization </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_lifecycle/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Life Cycle & Reviews </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_memberships/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Mandator Membership & Invitations </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_migration/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Migration & Import </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_nfr/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Non-Functional </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_notifications/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Notifications & Tasks </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_obligations/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Recurring Obligations </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_relationships/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Document Relationships </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_risk/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Risk Management (ISO 14971 Hazards & Controls) </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_sbom/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Software Bill of Materials & Supply-Chain Assurance </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_search/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Search </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_separation/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Scopes, Mandators & Separation </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_signatures/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Electronic Signatures </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_training/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Read-Acknowledgement & Questionnaires </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_users/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: User Identity & Lifecycle </span> </a> </li> <li class="md-nav__item"> <a href="../../../requirements/req_validation/" class="md-nav__link"> <span class="md-ellipsis"> Software Requirements: Design Validation & the Validation Traceability Axis </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_6" > <div class="md-nav__link md-nav__container"> <a href="../../../process/" class="md-nav__link "> <span class="md-ellipsis"> Process (IEC 62304) </span> </a> <label class="md-nav__link " for="__nav_6" id="__nav_6_label" tabindex="0"> <span class="md-nav__icon md-icon"></span> </label> </div> <nav class="md-nav" data-md-level="1" aria-labelledby="__nav_6_label" aria-expanded="false"> <label class="md-nav__title" for="__nav_6"> <span class="md-nav__icon md-icon"></span> Process (IEC 62304) </label> <ul class="md-nav__list" data-md-scrollfix> <li class="md-nav__item"> <a href="../../../process/configuration_management_plan/" class="md-nav__link"> <span class="md-ellipsis"> Configuration Management Plan </span> </a> </li> <li class="md-nav__item"> <a href="../../../process/problem_resolution/" class="md-nav__link"> <span class="md-ellipsis"> Problem Resolution Process </span> </a> </li> <li class="md-nav__item"> <a href="../../../process/risk_management/" class="md-nav__link"> <span class="md-ellipsis"> Risk Management </span> </a> </li> <li class="md-nav__item"> <a href="../../../process/software_development_plan/" class="md-nav__link"> <span class="md-ellipsis"> Software Development Plan </span> </a> </li> <li class="md-nav__item"> <a href="../../../process/verification_plan/" class="md-nav__link"> <span class="md-ellipsis"> Verification Plan </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--nested"> <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_7" > <label class="md-nav__link" for="__nav_7" id="__nav_7_label" tabindex="0"> <span class="md-ellipsis"> Operations </span> <span class="md-nav__icon md-icon"></span> </label> <nav class="md-nav" data-md-level="1" aria-labelledby="__nav_7_label" aria-expanded="false"> <label class="md-nav__title" for="__nav_7"> <span class="md-nav__icon md-icon"></span> Operations </label> <ul class="md-nav__list" data-md-scrollfix> <li class="md-nav__item"> <a href="../../../operations/genesis-installation/" class="md-nav__link"> <span class="md-ellipsis"> Genesis: Birthing an LQMS Installation with a Base Library </span> </a> </li> <li class="md-nav__item"> <a href="../../../operations/deployment/" class="md-nav__link"> <span class="md-ellipsis"> LQMS Deployment Guide </span> </a> </li> <li class="md-nav__item"> <a href="../../../operations/server-deployment/" class="md-nav__link"> <span class="md-ellipsis"> LQMS Server Deployment (single Linux host, public HTTPS) </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item md-nav__item--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--active md-nav__item--nested"> <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_11" checked> <div class="md-nav__link md-nav__container"> <a href="../../" 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="true"> <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="../../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="../../administration/" class="md-nav__link"> <span class="md-ellipsis"> Administering an LQMS Installation </span> </a> </li> <li class="md-nav__item"> <a href="../../diagrams/" class="md-nav__link"> <span class="md-ellipsis"> Diagrams </span> </a> </li> <li class="md-nav__item"> <a href="../../documents-lifecycle/" class="md-nav__link"> <span class="md-ellipsis"> Documents & the Lifecycle </span> </a> </li> <li class="md-nav__item"> <a href="../../exports/" class="md-nav__link"> <span class="md-ellipsis"> PDF Exports & the Audit Pack </span> </a> </li> <li class="md-nav__item"> <a href="../../obligations/" class="md-nav__link"> <span class="md-ellipsis"> Recurring Obligations </span> </a> </li> <li class="md-nav__item"> <a href="../../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="../../review-comments/" class="md-nav__link"> <span class="md-ellipsis"> Review Comments </span> </a> </li> <li class="md-nav__item"> <a href="../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="../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="../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="../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="../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="../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="../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="../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="../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="../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="../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 md-nav__item--active"> <input class="md-nav__toggle md-toggle" type="checkbox" id="__toc"> <label class="md-nav__link md-nav__link--active" for="__toc"> <span class="md-ellipsis"> The setup wizard: the lanes, and what it writes </span> <span class="md-nav__icon md-icon"></span> </label> <a href="./" class="md-nav__link md-nav__link--active"> <span class="md-ellipsis"> The setup wizard: the lanes, and what it writes </span> </a> <nav class="md-nav md-nav--secondary" aria-label="Table of contents"> <label class="md-nav__title" for="__toc"> <span class="md-nav__icon md-icon"></span> Table of contents </label> <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix> <li class="md-nav__item"> <a href="#1-the-lane-is-the-one-choice-that-shapes-everything" class="md-nav__link"> <span class="md-ellipsis"> 1. The lane is the one choice that shapes everything </span> </a> <nav class="md-nav" aria-label="1. The lane is the one choice that shapes everything"> <ul class="md-nav__list"> <li class="md-nav__item"> <a href="#which-one-to-pick" class="md-nav__link"> <span class="md-ellipsis"> Which one to pick </span> </a> </li> <li class="md-nav__item"> <a href="#the-qms-lane-has-no-trace-axis-at-all" class="md-nav__link"> <span class="md-ellipsis"> The QMS lane has no trace axis at all </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item"> <a href="#2-what-the-wizard-writes" class="md-nav__link"> <span class="md-ellipsis"> 2. What the wizard writes </span> </a> </li> <li class="md-nav__item"> <a href="#3-what-it-honestly-hands-over" class="md-nav__link"> <span class="md-ellipsis"> 3. What it honestly hands over </span> </a> </li> <li class="md-nav__item"> <a href="#4-two-modes-on-the-configuration-step" class="md-nav__link"> <span class="md-ellipsis"> 4. Two modes on the configuration step </span> </a> </li> <li class="md-nav__item"> <a href="#5-the-last-step-checks-it-does-not-gate" class="md-nav__link"> <span class="md-ellipsis"> 5. The last step checks, it does not gate </span> </a> </li> <li class="md-nav__item"> <a href="#6-the-chip-monitors-the-wizard-remediates" class="md-nav__link"> <span class="md-ellipsis"> 6. The chip monitors; the wizard remediates </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item"> <a href="../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="../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="../../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="../../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="../../traceability-workspace/" class="md-nav__link"> <span class="md-ellipsis"> The Traceability Workspace </span> </a> </li> <li class="md-nav__item"> <a href="../../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="#1-the-lane-is-the-one-choice-that-shapes-everything" class="md-nav__link"> <span class="md-ellipsis"> 1. The lane is the one choice that shapes everything </span> </a> <nav class="md-nav" aria-label="1. The lane is the one choice that shapes everything"> <ul class="md-nav__list"> <li class="md-nav__item"> <a href="#which-one-to-pick" class="md-nav__link"> <span class="md-ellipsis"> Which one to pick </span> </a> </li> <li class="md-nav__item"> <a href="#the-qms-lane-has-no-trace-axis-at-all" class="md-nav__link"> <span class="md-ellipsis"> The QMS lane has no trace axis at all </span> </a> </li> </ul> </nav> </li> <li class="md-nav__item"> <a href="#2-what-the-wizard-writes" class="md-nav__link"> <span class="md-ellipsis"> 2. What the wizard writes </span> </a> </li> <li class="md-nav__item"> <a href="#3-what-it-honestly-hands-over" class="md-nav__link"> <span class="md-ellipsis"> 3. What it honestly hands over </span> </a> </li> <li class="md-nav__item"> <a href="#4-two-modes-on-the-configuration-step" class="md-nav__link"> <span class="md-ellipsis"> 4. Two modes on the configuration step </span> </a> </li> <li class="md-nav__item"> <a href="#5-the-last-step-checks-it-does-not-gate" class="md-nav__link"> <span class="md-ellipsis"> 5. The last step checks, it does not gate </span> </a> </li> <li class="md-nav__item"> <a href="#6-the-chip-monitors-the-wizard-remediates" class="md-nav__link"> <span class="md-ellipsis"> 6. The chip monitors; the wizard remediates </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/user-guide/topics/setup-wizard-lanes.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="the-setup-wizard-the-lanes-and-what-it-writes">The setup wizard: the lanes, and what it writes<a class="headerlink" href="#the-setup-wizard-the-lanes-and-what-it-writes" title="Permanent link">¶</a></h1> <p><em>Audience: a quality manager creating a new project or configuring an existing one.</em></p> <p><strong>Project setup</strong> (Admin → Project setup) walks a project's configuration in four steps: <strong>Project → Lane → Configuration → Apply & verify</strong>. Its subtitle states the deal plainly — <em>"the house-validated configuration, editable before it is written."</em> Nothing is written until the last step, and every proposal on the way is editable.</p> <h2 id="1-the-lane-is-the-one-choice-that-shapes-everything">1. The lane is the one choice that shapes everything<a class="headerlink" href="#1-the-lane-is-the-one-choice-that-shapes-everything" title="Permanent link">¶</a></h2> <p>Step 2 asks which kind of scope this is. There are three, and they differ in kind, not in degree:</p> <table> <thead> <tr> <th>Lane</th> <th>What it is</th> </tr> </thead> <tbody> <tr> <td><strong>Supplier lane (IEC 62304)</strong></td> <td>Software supplier: requirements, design, tests and the risk file — verification against the customer's requirements. No validation or GSPR axis.</td> </tr> <tr> <td><strong>Manufacturer lane (ISO 13485)</strong></td> <td>Legal manufacturer: everything the supplier lane carries plus stakeholder needs, the validation axis and the GSPR applicability matrix.</td> </tr> <tr> <td><strong>QMS / process scope (ISO 13485)</strong></td> <td>The organisation's own QMS: SOPs, work instructions, templates and records — no product traceability.</td> </tr> </tbody> </table> <p><img alt="The lane step" src="scene:setup-wizard-2-lane" /></p> <h3 id="which-one-to-pick">Which one to pick<a class="headerlink" href="#which-one-to-pick" title="Permanent link">¶</a></h3> <p>Ask what the scope <em>documents</em>, not what your company is:</p> <ul> <li><strong>Supplier lane</strong> — the scope is a <strong>software project you build</strong>, and your duty is <em>verification</em>: requirements, design, tests, the risk file, evidence that what was built matches what was asked for. This is the IEC 62304 side of the house.</li> <li><strong>Manufacturer lane</strong> — the scope is a <strong>device the organisation puts its name on</strong>, and it carries the legal manufacturer's duties: stakeholder needs, <em>validation</em> (does it meet the user's actual need, not just the specification), and regulatory applicability. This is the ISO 13485 product side.</li> <li><strong>QMS / process lane</strong> — the scope is <strong>one of the organisation's own process areas</strong>, and its documents are procedures rather than product artefacts. Note that this is not only for engineering processes: a marketing or sales process area with its own SOPs and records is a QMS scope exactly like document control or supplier management is.</li> </ul> <p><strong>When in doubt between the two product lanes, take the manufacturer lane.</strong> It is the superset — it carries everything the supplier lane carries plus the validation and regulatory axes — so a project that turns out to need only verification simply has axes it does not use, whereas a supplier-lane project that turns out to carry the manufacturer's duty needs types, special elements and folders added by hand later. A project that both supplies the software and holds the manufacturer's validation duty is the manufacturer case, not a hybrid.</p> <p>None of this is a classification you are stuck with: the lane is a <strong>starting proposal</strong>. Every type, grant, prefix and folder it puts on the configuration step is editable before <em>Apply</em>, and nothing is written until then.</p> <p>The lane decides three things: which <strong>document types</strong> are proposed, which <strong>special elements</strong> the project declares (and under which key prefixes), and which <strong>folder skeleton</strong> is created.</p> <ul> <li><strong>Supplier</strong>: SOP, SWREQ, SWDSN, SWTEST, RA, VERREP, REC, INFRA. Special elements requirement <code>REQ-</code>, design element <code>DE-</code>, risk <code>RISK-</code>, risk control <code>RC-</code>. Folders <em>Procedures / Requirements / Design / Verification / Records</em>.</li> <li><strong>Manufacturer</strong>: the supplier list plus SR (stakeholder requirements), VALP (validation plan), GSPR (applicability matrix), TPL and VALREP. Special elements add user need <code>UN-</code>, validation case <code>VAL-</code>, regulatory reference <code>GSPR-</code>. Folders add <em>Stakeholder needs / Validation / Regulatory</em>.</li> <li><strong>QMS / process</strong>: QM, SOP, WI, DOC, TPL, REC. Folders are the ISO 13485 chapter tree (<em>4 Quality management system</em> … <em>8 Measurement, analysis and improvement</em>).</li> </ul> <p>A lane can no longer propose an <strong>incoherent</strong> vocabulary. The product's element catalog records what each kind depends on — risk and risk control are a mutual pair, a validation case needs a user need, which needs a system requirement, and a stakeholder requirement needs one too — and a lane's selection is checked against it. That is why the supplier lane's four come as <em>system requirement, design element, risk, risk control</em> and never as "risk controls, no risks": see <a href="../key-rules/">special elements</a>.</p> <h3 id="the-qms-lane-has-no-trace-axis-at-all">The QMS lane has no trace axis at all<a class="headerlink" href="#the-qms-lane-has-no-trace-axis-at-all" title="Permanent link">¶</a></h3> <p>This is structural, not a gap. A QMS scope documents the organisation's processes; it does not trace a product, so <strong>no type may define trace items and no element kind is declared</strong>. Where the product lanes arrive with four or eight rows ticked, the QMS lane arrives with none — and says why: <em>"This lane traces no product, so it proposes no special elements — a process scope documents the organisation."</em> The rows are still listed and still tickable, because a process scope that DOES key something must not be argued out of it by its lane.</p> <p>What the QMS lane carries instead:</p> <ul> <li><strong>Periodic-review cadences</strong> — Quality Manual and SOP every 365 days, Work Instruction every 730, QMS Document every 1095. A template carries none (a template is instantiated, not reviewed).</li> <li><strong>Read-acknowledgement proposals</strong> on the read-and-understand types (QM, SOP, WI), addressed to the author and reviewer roles. Templates and records propose none — nobody is trained on a blank checklist.</li> </ul> <p><img alt="The QMS lane configured" src="scene:setup-wizard-qms-2-config" /></p> <h2 id="2-what-the-wizard-writes">2. What the wizard writes<a class="headerlink" href="#2-what-the-wizard-writes" title="Permanent link">¶</a></h2> <p>Step 3 pre-fills everything from the lane; step 4 applies it <strong>one act at a time</strong>, each reporting its own outcome (<em>Pending / Running… / Done / Already there / Failed</em>). A failure stops the run there and leaves it resumable — <em>"Nothing after it ran; fix the cause and resume."</em></p> <p>Written for any caller holding the matching permission <strong>in the project</strong>:</p> <ul> <li>the per-type <strong>review policy</strong> — the complete grant set, including all three standing permissions (see <a href="../review-policies/">review policies</a>);</li> <li>the per-type <strong>may-define</strong> rights (which special elements documents of that type may mint) — edited on the per-kind row of the Special elements section, and governed by catalog activation <em>in the project</em>, which is a different right from the installation-shaping one below;</li> <li>the per-type <strong>read-acknowledgement policy</strong> where the lane proposes one;</li> <li>the <strong>folder skeleton</strong>.</li> </ul> <p>Written only for a caller holding <strong>MANAGE_SCOPES</strong> at the installation level (see <a href="../provisioning-birth-path/">the birth path</a>):</p> <ul> <li>creating a <strong>project</strong> — inside an organization that already exists. Founding the organization itself is a separate act with a right of its own since ADR-0109 (<a href="../provisioning-birth-path/">the birth path, §1a</a>); this wizard cannot do it;</li> <li><strong>activating</strong> a document type in the project;</li> <li><strong>activating</strong> a role in the project — this makes the role bindable and assignable; <em>it staffs nobody</em>;</li> <li>declaring the project's <strong>special elements</strong> — its element kinds, each with the project's own name for it and its key prefix, and the prerequisites the declaration pulls in with it (<a href="../key-rules/">special elements</a>).</li> </ul> <h2 id="3-what-it-honestly-hands-over">3. What it honestly hands over<a class="headerlink" href="#3-what-it-honestly-hands-over" title="Permanent link">¶</a></h2> <p>Three things stay a hand-off even with every permission, and the wizard names each rather than skipping it silently:</p> <ul> <li><strong>A type or role this installation's catalog does not carry at all.</strong> Creating catalog entries is catalog administration (Admin → Roles, document-type defaults) — the wizard can activate what exists, not invent vocabulary.</li> <li><strong>The periodic-review interval</strong> a lane recommends. The interval lives on the document <em>type</em> for the whole installation, not on your project, so the wizard displays the cadence and says where it is set.</li> <li><strong>Staffing.</strong> People come from your identity provider and are staffed through the user administration surface (<a href="../staffing-and-assignments/">staffing & assignments</a>).</li> </ul> <h2 id="4-two-modes-on-the-configuration-step">4. Two modes on the configuration step<a class="headerlink" href="#4-two-modes-on-the-configuration-step" title="Permanent link">¶</a></h2> <ul> <li><strong>A new project</strong> renders the lane's type list — there is nothing else to render yet.</li> <li><strong>An existing project</strong> renders <em>its own</em> activated types first, pre-filled from the lane where the prefixes match, and only then the lane types it has yet to activate.</li> </ul> <p>A type the lane knows nothing about — an imported vocabulary, a house type, another lane's type — gets a <em>"not in this lane"</em> marker, <strong>honestly empty grant rows</strong>, and starts <em>out</em> of the commit. Turn it on and fill the rows in yourself. The wizard will not invent a policy for a type nobody asked about.</p> <p><img alt="Configuring a project with its own vocabulary" src="scene:setup-wizard-existing-config" /></p> <h2 id="5-the-last-step-checks-it-does-not-gate">5. The last step checks, it does not gate<a class="headerlink" href="#5-the-last-step-checks-it-does-not-gate" title="Permanent link">¶</a></h2> <p><em>Apply & verify</em> re-reads the project's setup status against what was just written and lists what the system will still flag. It enforces nothing: <strong>unstaffed roles are normal on day one</strong> — invited people bind on first login — and the point is that you see what will block, and where, instead of meeting it as a surprise at the first submit.</p> <h2 id="6-the-chip-monitors-the-wizard-remediates">6. The chip monitors; the wizard remediates<a class="headerlink" href="#6-the-chip-monitors-the-wizard-remediates" title="Permanent link">¶</a></h2> <p>These are two different tools, and confusing them wastes time in both directions.</p> <p><strong>The setup-status chip is the monitor.</strong> <em>Setup complete</em> / <em>"N setup gaps"</em> on the project configuration is always on, always current, and it is the thing that tells you a project has drifted or was never finished. You do not need the wizard to <em>find out</em> whether a project is in order — that is the chip's job, and re-running the wizard as a routine health check is ceremony that tells you nothing the chip has not already said.</p> <p><strong>Wizard re-entry is the remediation tool.</strong> Pointing the wizard at an existing project (§4's second mode) does one thing the chip cannot: it <strong>compares the project against a lane</strong> and offers the whole difference as a single editable, reviewable batch. The chip reports <em>"this type has no review policy"</em>, one finding at a time, with a fix link per finding; the wizard says <em>"here is the lane's shape, here is yours, here is everything missing — check what you want and apply it in one pass"</em>. Nothing is written until <em>Apply</em>, so opening it to look costs nothing.</p> <p>Reach for re-entry when:</p> <ul> <li><strong>a project was configured by hand or arrived through an import</strong> and you want to see how far it is from a house lane;</li> <li><strong>new document types were activated</strong> in it and they need policies, may-define flags and acknowledgement policies — the wizard fills all three from the lane rather than you visiting three tabs per type;</li> <li><strong>you are adopting a lane's shape late</strong> — the project pre-dates the lane, or you decided its lane was the wrong one.</li> </ul> <p>Re-entry is safe: acts that are already satisfied report as <em>Already there</em> rather than being re-applied, and re-declaring an element kind the wizard itself declared is a no-op that does not trip the <a href="../key-rules/">freeze</a>. A type the lane does not know starts <em>out</em> of the commit (§4), so re-entry never quietly reshapes a house type.</p> <hr /> <p><em>Governing decisions: ADR-0097 (the governed provisioning surface — what the wizard may create), ADR-0096 (deny-unless-granted transition permissions — why every preset grant set is complete), ADR-0112 (the element-kind catalog a lane selects from), ADR-0095 (its freeze governance), ADR-0091 (release modes — the direct record release the INFRA type uses), ADR-0052 (read-acknowledgement policies), ADR-0049 (document categories — why only prescriptive types are periodically reviewed). Regulatory frame: IEC 62304 (supplier lane), ISO 13485 §§4–8 (the QMS lane's chapter tree).</em></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="../review-policies/" class="md-footer__link md-footer__link--prev" aria-label="Previous: What a review policy controls, and what an empty grant means"> <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"> What a review policy controls, and what an empty grant means </div> </div> </a> <a href="../staffing-and-assignments/" class="md-footer__link md-footer__link--next" aria-label="Next: Staffing people into roles, and the accountable holder"> <div class="md-footer__title"> <span class="md-footer__direction"> Next </span> <div class="md-ellipsis"> Staffing people into roles, and the accountable holder </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>