@oimlsmart/primmel-packages 0.4.0 → 0.5.0

package/oiml-cs/framework/documents/pd-02/requirements.prl

@@ -0,0 +1,126 @@
+# OIML-CS DOCUMENT MODULE PD-02 — NORMATIVE PROVISIONS (/req/cs/pd-02/*)
+# -----------------------------------------------------------------------------
+# OIML-CS PD-02 Edition 3 (2022-11-14) — the approval pipeline for the
+# experts the PD-03/PD-04 assessment teams are drawn from: nomination, RC
+# recommendation, MC approval, the BIML non-disclosure agreement, and the
+# ILAC-IAF-OIML expert lists.
+#
+# NUMBERING: PD-02's clause anchors are VERIFIED against the official
+# published PDF (reference-docs/cs/docs/oiml-cs-pd-02-edition-3.pdf,
+# retrieved 2026-07-24; task 46) — the local presentation XML
+# (data/oiml-cs-pd-02/) is a defective build (0.x renumbering) and is
+# never cited. Application forms:
+# reference-docs/cs/application-forms/{legal-metrology-expert,ms-expert}-
+# application-form.pdf.
+#
+# SOURCE DISCREPANCY (verified, task 46, 2026-07-24): PD-02 Ed 3, 11.1
+# reads verbatim "As outlined in OD-01, 13.4 [2], the on-going competence
+# and suitability of experts shall be reviewed at least once every four
+# years.", while OD-01 Ed 4, 13.4 itself reads verbatim "The list of
+# experts will be reviewed on a 3-yearly basis by the Management
+# Committee…". Both texts verified against the official PDFs — the
+# sources genuinely disagree (a CID-01 candidate). This module records
+# PD-02's own text (four-year review); documents/od-01 records OD-01's
+# text (3-yearly list review). Editorial note: OD-01, 13.4's internal
+# cross-reference "In accordance with PD-02, 10.2 [11]…" is itself an
+# error in OD-01 — the RC-advice discipline on continued suitability is
+# PD-02, 11.3 (PD-02, 10.2 is scope extension).
+#
+# This file is the single source of truth; the consumer's
+# data/oiml-cs/documents/pd-02/requirements.yaml is its GENERATED YAML twin
+# (cd browser && npm run gen:data).
+requirement_class /req/cs/pd-02 {
+  title "OIML-CS expert approval requirements"
+  name "Approval of Legal Metrology Experts and Management System Experts (PD-02)"
+  description "Provisions of OIML-CS PD-02 Edition 3 governing the nomination, approval, publication and monitoring of Legal Metrology Experts and Management System Experts (Team Leaders). Enforced by the abstract pipeline of this module (abstract-processes.yaml); the organ actors and decision mechanics it binds are the task-40 framework model (framework/)."
+  subject "OIML-CS participant governance — expert approval and lists"
+}
+
+requirement /req/cs/pd-02/lme-competence-criteria {
+  name "LME competence criteria"
+  statement "A Legal Metrology Expert shall satisfy the competence criteria of OD-01, 13.2.1 (PD-02, 5 defers; performance-oriented criteria — education, knowledge, experience, personal and auditing skills — judged case by case). The criteria themselves are OD-01 content (task 43); this provision pins the delegation."
+  obligation shall
+  verification { method inspection description "Expert application review (abstract process expert_rc_review)." }
+  source { doc "PD-02, 5" clause "" }
+}
+
+requirement /req/cs/pd-02/mse-competence-criteria {
+  name "MSE competence criteria"
+  statement "A Management System Expert (Team Leader) shall satisfy the competence criteria of OD-01, 13.2.2 (PD-02, 6 defers). The criteria themselves are OD-01 content (task 43); this provision pins the delegation."
+  obligation shall
+  verification { method inspection description "Expert application review (abstract process expert_rc_review)." }
+  source { doc "PD-02, 6" clause "" }
+}
+
+requirement /req/cs/pd-02/lme-nomination {
+  name "LME nomination"
+  statement "A Legal Metrology Expert candidate applies individually on the \"LME Application Form\" to the Executive Secretary, for one or multiple measuring instrument categories with their corresponding OIML Recommendations (PD-02, 7.1)."
+  obligation shall
+  verification { method inspection description "Nomination step of the pipeline (abstract process expert_nomination)." }
+  source { doc "PD-02, 7.1" clause "" }
+}
+
+requirement /req/cs/pd-02/mse-nomination-accreditation-body {
+  name "MSE nomination by an accreditation body"
+  statement "A Management System Expert may be nominated by an accreditation body that is an ILAC MRA signatory for the scope \"Testing ISO/IEC 17025\" (for TL peer assessments) or an IAF MLA signatory for \"Product Certification ISO/IEC 17065\" or an ILAC signatory for \"Inspection ISO/IEC 17020\" (for IA assessments), with evidence of understanding of the OIML-CS and of OIML D 32, D 30 and D 37 (PD-02, 7.2.1)."
+  obligation shall
+  verification { method inspection description "Nomination step of the pipeline (abstract process expert_nomination)." }
+  source { doc "PD-02, 7.2.1" clause "" }
+}
+
+requirement /req/cs/pd-02/mse-nomination-individual {
+  name "MSE nomination by an individual"
+  statement "A Management System Expert candidate may alternatively apply individually on the \"MSE Application Form\" (PD-02, 7.2.2)."
+  obligation shall
+  verification { method inspection description "Nomination step of the pipeline (abstract process expert_nomination)." }
+  source { doc "PD-02, 7.2.2" clause "" }
+}
+
+requirement /req/cs/pd-02/review-and-decision {
+  name "Review and decision"
+  statement "The Executive Secretary reviews the application and the Review Committee makes a recommendation (PD-02, 8.1); the Management Committee votes — approval or rejection with reasons — and the applicant is notified (PD-02, 8.2). Expert approval is an \"other proposal\" in the MC's voting mechanics (the 80 % threshold of B 18:2025 §11.4.2 is reserved to IA/TL participation decisions)."
+  obligation shall
+  verification { method inspection description "The review and decision steps of the pipeline (abstract processes expert_rc_review, expert_mc_decision)." }
+  source { doc "PD-02, 8.1/8.2" clause "" }
+}
+
+requirement /req/cs/pd-02/nda {
+  name "Non-disclosure agreement"
+  statement "An approved expert shall sign a non-disclosure agreement with the BIML before being added to the lists of experts (PD-02, 8.2)."
+  obligation shall
+  verification { method inspection description "The NDA step of the pipeline (abstract process expert_nda)." }
+  source { doc "PD-02, 8.2" clause "" }
+}
+
+requirement /req/cs/pd-02/unapproved-expert-use {
+  name "Use of not-yet-approved experts at applicant risk"
+  statement "A not-yet-approved expert may be used in an IA or TL assessment when the expert's approval application accompanies the IA/TL application, at the applicant's risk: if the expert is not subsequently approved, the assessment may have to be repeated (PD-02, 8.3 — the hook PD-03, 5.2.2/5.2.3 and PD-04, 5.2.2/5.2.3 invoke)."
+  obligation may
+  verification { method inspection description "Assessment-team composition evidence of the PD-03/PD-04 pipelines." }
+  source { doc "PD-02, 8.3" clause "" }
+}
+
+requirement /req/cs/pd-02/publication {
+  name "Publication of the lists of experts"
+  statement "The approved experts shall be added to the ILAC-IAF-OIML lists of experts published on the OIML-CS pages of the OIML website; ILAC and the IAF are notified for Management System Experts (PD-02, 9)."
+  obligation shall
+  verification { method inspection description "The publication step of the pipeline (abstract process expert_list_publication; registers below)." }
+  source { doc "PD-02, 9" clause "" }
+}
+
+requirement /req/cs/pd-02/change-of-scope {
+  name "Change of scope"
+  statement "An expert may extend or reduce their scope (instrument categories with their Recommendations, assessment scopes): extensions are processed by the review procedure of 8.1/8.2; reductions and removals are effected by notification only (PD-02, 10)."
+  obligation shall
+  verification { method inspection description "Off-sequence scope-change flow (abstract process expert_scope_change)." }
+  source { doc "PD-02, 10" clause "" }
+}
+
+requirement /req/cs/pd-02/monitoring {
+  name "Monitoring of experts"
+  statement "The on-going competence and suitability of every expert shall be reviewed at least once every four years (per OD-01, 13.4): the Review Committee recommends on continued competence; removal from the lists may also occur without a formal review (PD-02, 11; see the header's verified discrepancy — OD-01, 13.4 itself reads 3-yearly)."
+  obligation shall
+  verification { method inspection description "Off-sequence monitoring flow (abstract process expert_monitoring)." }
+  source { doc "PD-02, 11" clause "" }
+}
+

package/oiml-cs/framework/documents/pd-03/abstract-processes.prl

@@ -0,0 +1,348 @@
+# OIML-CS DOCUMENT MODULE PD-03 — ABSTRACT PROCESSES
+# -----------------------------------------------------------------------------
+# The PD-03 Edition 5 Issuing-Authority approval pipeline as ABSTRACT
+# processes (TODO.roadmap/42):
+#
+#   application → assessment → RC review → MC 80 % vote
+#               → Declaration signing → IA-list publication
+#
+# plus the off-sequence lifecycle flows: Scheme B application, periodic
+# review (maintenance), scope change, suspension, withdrawal, and
+# notification of changes. The pipeline's organ actors, its MC 80 %
+# decision rule and its Declaration model REFERENCE the task-40 framework
+# model (framework/) — never restate it; the consumer's linker rule R26
+# (document-pipeline-references) resolves every reference.
+#
+# The terminal invariant: ia_declaration_signing carries
+# discharges_gate declaration-signed-before-issuance — the task-40 signing
+# gate (framework/declarations.prl, PD-08 cl. 5) wired as this pipeline's
+# terminal invariant. Until the Declaration is signed the gate blocks the
+# IA's issue/evaluation abstract processes; the seeded end-to-end
+# rejection proof lives in the consumer's cs-participant-approval tests.
+#
+# TODO.roadmap/44–45 REALIZED the pipeline: realized_by binds the concrete
+# Core processes (the participant-approval set) that the task-44 registry
+# runtime executes (browser/src/data/participant-registry.ts); the
+# signature stores are the runtime's cs-participants entity classes.
+# Processes left unrealized are named gaps in the unified coverage report
+# (browser/build/cs-coverage.ts).
+#
+# This file is the single source of truth; the consumer's
+# data/oiml-cs/documents/pd-03/abstract-processes.yaml is its GENERATED YAML
+# twin (cd browser && npm run gen:data; schema data/schemas/abstract-processes.yaml).
+# The realized_by edges name CONCRETE processes of the rec packages —
+# unresolvable under the standalone package check, covered by the one glob
+# allowlist entry (C121; dies when the gates check composed).
+process ia_application {
+  name "IA application"
+  summary "A certification/inspection body of an OIML Member State applies on the CIML-endorsed Application Form, endorsed by its CIML Member, with the 5.1 a–i accompanying information — scope (categories × Recommendations × Schemes), the associated Test Laboratory list, MTL supervision procedures, the accreditation or peer-assessment evidence, and the latest internal audit against ISO/IEC 17065 with D 32. The application is valid only with at least one associated Test Laboratory application per PD-04 (PD-03, 4.1)."
+  validate_provision {
+    /req/cs/pd-03/tl-application-precondition
+    /req/cs/pd-03/application-contents
+  }
+  signature {
+    out { participantApplications }
+  }
+  invariants {
+    "[ia_application].tl_application_ids.count >= 1"
+    "[ia_application].scope.count >= 1"
+  }
+  activity_kind { selection }
+  organs { executive_secretary }
+  participant_kinds { issuing_authority }
+  evidence {
+    application_form { description "The endorsed Application Form with the 5.1 a–i accompanying information (designation, scope, TL list, assessment evidence, internal audit)." required true }
+    tl_application_link { description "The at-least-one associated Test Laboratory application per PD-04 (the 4.1 precondition)." required true }
+  }
+  realized_by { submit_participant_application }
+  executor actor
+  source { doc "PD-03, 5.1" clause "" }
+}
+
+process ia_assessment {
+  name "IA competence assessment"
+  summary "The candidate IA's compliance with ISO/IEC 17065:2012 applied per OIML D 32 is demonstrated by one of two paths: accreditation by an IAF-MLA-signatory accreditation body with at least one MC-approved Legal Metrology Expert in the assessment team (5.2.2), or peer assessment led by a Management System Expert with at least one LME, arranged by the applicant from the approved-experts list at its own cost and recorded on the OIML Issuing Authority Peer Assessment Report form (5.2.3). A not-yet-approved expert may be used only with the expert's PD-02 application accompanying the IA application, at the applicant's risk (PD-02, 8.3)."
+  validate_provision {
+    /req/cs/pd-03/competence-basis
+    /req/cs/pd-03/assessment-accreditation
+    /req/cs/pd-03/assessment-peer
+    /req/cs/pd-03/appeals-procedures
+    /req/cs/pd-02/unapproved-expert-use
+  }
+  signature {
+    in { participantApplications }
+    out { participantAssessments }
+  }
+  invariants {
+    "[assessment].path = 'accreditation' or [assessment].path = 'peer_assessment'"
+    "[assessment].team.lme_count >= 1"
+    "[assessment].path = 'peer_assessment' implies [assessment].team.mse_team_leader is not null"
+  }
+  activity_kind { accreditation peer_assessment }
+  participant_kinds { issuing_authority legal_metrology_expert management_system_expert }
+  evidence {
+    assessment_report { description "The accreditation certificate with the latest assessment report, or the OIML Issuing Authority Peer Assessment Report — recording the D 32 evidence, the team composition (MC-approved LME/MSE), and the resolution of any non-compliances." required true }
+    expert_approval_evidence { description "Evidence that every expert in the team is MC-approved — or, for a not-yet-approved expert, the accompanying PD-02 approval application (at the applicant's risk)." required true }
+  }
+  realized_by { assess_participant_competence }
+  executor actor
+  source { doc "PD-03, 5.2" clause "" }
+}
+
+process ia_rc_review {
+  name "RC review and recommendation"
+  summary "The Review Committee reviews the complete application documentation (application, assessment report, internal audit) and makes its recommendation on the approval to the Management Committee."
+  validate_provision {
+    /req/cs/pd-03/approval-process
+  }
+  signature {
+    in { participantApplications participantAssessments }
+    out { participantApplications }
+  }
+  invariants {
+    "[ia_application].rc_recommendation is not null"
+  }
+  activity_kind { review }
+  organs { review_committee }
+  evidence {
+    rc_recommendation { description "The Review Committee's recommendation to the Management Committee on the IA's approval." required true }
+  }
+  realized_by { recommend_participation }
+  executor actor
+  source { doc "PD-03, 5.3.2" clause "" }
+}
+
+process ia_mc_decision {
+  name "MC approval vote"
+  summary "The Management Committee decides the IA's approval on the Review Committee's recommendation — the 80 % participation vote of B 18:2025 §11.4.2/§11.4.3 (framework/governance.yaml ia-tl-participation-decisions); the applicant is notified of the outcome."
+  validate_provision {
+    /req/cs/pd-03/approval-process
+  }
+  signature {
+    in { participantApplications }
+    out { participantApplications }
+  }
+  invariants {
+    "[ia_application].mc_decision is not null"
+  }
+  activity_kind { decision }
+  organs { management_committee }
+  evidence {
+    mc_decision_record { description "The MC decision record (vote result on the RC recommendation) and the notification to the applicant." required true }
+  }
+  decision { rule ia-tl-participation-decisions clause "PD-03, 5.3.2" }
+  realized_by { decide_participation }
+  executor actor
+  source { doc "PD-03, 5.3.2" clause "" }
+}
+
+process ia_declaration_signing {
+  name "Declaration signing"
+  summary "The approved IA signs its Declaration (scope: instrument categories × Schemes) in accordance with OIML-CS PD-08; the Executive Secretary records it. This is the pipeline's TERMINAL INVARIANT: until the Declaration is signed, the task-40 signing gate blocks every issuance of the IA (framework/declarations.yaml signing_gate blocks the issue/evaluation abstract processes of the scheme process model)."
+  validate_provision {
+    /req/cs/pd-03/declaration-before-issuance
+  }
+  signature {
+    in { participantApplications }
+    out { declarations }
+  }
+  invariants {
+    "[declaration].status = 'signed'"
+    "[declaration].kind = 'issuing_authority_declaration'"
+  }
+  activity_kind { declaration }
+  organs { executive_secretary }
+  participant_kinds { issuing_authority }
+  evidence {
+    signed_declaration { description "The IA's signed Declaration (PD-08 cl. 4 a — scope as categories × Schemes), recorded by the Executive Secretary." required true }
+  }
+  declaration { kind issuing_authority_declaration action sign }
+  discharges_gate declaration-signed-before-issuance
+  realized_by { record_participant_declaration }
+  executor actor
+  source { doc "PD-03, 5.3.2; PD-08 cl. 5" clause "" }
+}
+
+process ia_list_publication {
+  name "IA list publication"
+  summary "The new IA is added to the list of OIML Issuing Authorities maintained by the BIML on the OIML-CS pages of the OIML website (B 18:2025 §5.1.4) — the public register of who may issue."
+  signature {
+    in { declarations }
+    out { participantRegisters }
+  }
+  invariants {
+    "[register_entry].issuing_authority_id is not null"
+  }
+  organs { biml executive_secretary }
+  evidence {
+    register_entry { description "The IA's entry in the published IA register (designation, Member State, scope, associated Test Laboratories)." required true }
+  }
+  realized_by { publish_participant_register }
+  executor actor
+  source { doc "PD-03, 5.3.2" clause "" }
+}
+
+process ia_scheme_b_application {
+  name "Scheme B IA application"
+  summary "A Scheme B application comprises a self-declaration with supporting evidence and the most recent OIML type evaluation report per category (or a report template), processed by the 5.3.2 review-and-decision procedure without its assessment-report step (6.2)."
+  validate_provision {
+    /req/cs/pd-03/scheme-b-self-declaration
+  }
+  signature {
+    out { participantApplications }
+  }
+  invariants {
+    "[ia_application].scheme = 'B' implies [ia_application].self_declaration is not null"
+  }
+  activity_kind { selection }
+  organs { executive_secretary review_committee management_committee }
+  participant_kinds { issuing_authority }
+  evidence {
+    self_declaration { description "The self-declaration with supporting evidence and the latest type evaluation report or report template per category." required true }
+  }
+  decision { rule ia-tl-participation-decisions clause "PD-03, 6.2" }
+  realized_by { submit_participant_application }
+  executor actor
+  source { doc "PD-03, 6" clause "" }
+}
+
+process ia_periodic_review {
+  name "Periodic review of participation"
+  summary "The maintenance cycle of an approved IA and its associated Test Laboratories: the MC reviews the IA's internal summary report once a year, and every four years the accreditation and/or peer assessment reports are submitted to the Executive Secretary (10.1.1), reviewed, recommended on by the RC, and voted on by the MC — continued participation is re-decided, with a reconsideration round on rejection. An MC-approved Legal Metrology Expert participates in the assessment at least once per accreditation renewal cycle (maximum interval five years); a Scheme B IA instead submits annual evidence supporting its self-declaration (10.2)."
+  validate_provision {
+    /req/cs/pd-03/periodic-review
+    /req/cs/pd-03/periodic-review-lme-participation
+    /req/cs/pd-03/scheme-b-annual-evidence
+  }
+  signature {
+    in { declarations }
+    out { participantApplications }
+  }
+  invariants {
+    "[review_cycle].annual_report_count >= 1"
+    "[review_cycle].reassessment_due = true implies [review_cycle].reassessment_reports.count >= 1"
+  }
+  activity_kind { surveillance }
+  organs { executive_secretary review_committee management_committee }
+  participant_kinds { issuing_authority test_laboratory }
+  evidence {
+    annual_summary_report { description "The IA's internal summary report (OIML Issuing Authority Report template): comparisons, personnel/structure changes, management reviews, internal audits, accreditation surveillance, complaints, issuance counts." required true }
+    reassessment_reports { description "The four-yearly accreditation assessment reports and/or peer assessment reports of the IA and its Test Laboratories (10.1.1)." required true }
+  }
+  decision { rule ia-tl-participation-decisions clause "PD-03, 10" }
+  executor actor
+  source { doc "PD-03, 10" clause "" }
+}
+
+process ia_scope_change {
+  name "IA scope extension or reduction"
+  summary "An IA extends its scope (TL capabilities, an added Test Laboratory — processed per PD-04, an added category, an added Recommendation edition) on the Application Form with competence evidence, processed by the clause-5 procedures; a reduction is effected by notification to the Executive Secretary, who amends the Declaration and notifies the MC — no MC approval for a reduction."
+  validate_provision {
+    /req/cs/pd-03/scope-change
+  }
+  signature {
+    in { declarations }
+    out { declarations }
+  }
+  invariants {
+    "[scope_change].kind = 'extension' implies [scope_change].competence_evidence is not null"
+  }
+  activity_kind { review }
+  organs { executive_secretary }
+  participant_kinds { issuing_authority }
+  evidence {
+    scope_change_record { description "The extension application with competence evidence, or the reduction notification with the amended Declaration." required true }
+  }
+  declaration { kind issuing_authority_declaration action update }
+  realized_by { record_participant_declaration }
+  executor actor
+  source { doc "PD-03, 9" clause "" }
+}
+
+process ia_suspension {
+  name "IA suspension"
+  summary "On evidence-supported allegation of persistent non-compliance, the Executive Secretary contacts the IA and reports to the RC; the RC may require an action plan and recommends suspension to the MC, which decides by vote — possibly a PARTIAL suspension of scope. A suspended IA starts no new applications and completes ongoing ones only under MC-defined conditions."
+  validate_provision {
+    /req/cs/pd-03/suspension-process
+  }
+  signature {
+    in { declarations }
+    out { declarations }
+  }
+  invariants {
+    "[declaration].status = 'suspended' implies [declaration].suspension_record is not null"
+  }
+  activity_kind { suspension }
+  organs { executive_secretary review_committee management_committee }
+  evidence {
+    suspension_record { description "The non-compliance report, the action plan and its follow-up, the RC recommendation, the MC vote and the suspension notification with the conditions for ongoing applications." required true }
+  }
+  decision { rule ia-tl-participation-decisions clause "PD-03, 8" }
+  realized_by { decide_participation }
+  executor actor
+  source { doc "PD-03, 8" clause "" }
+}
+
+process ia_withdrawal {
+  name "IA withdrawal"
+  summary "An IA withdraws by notice to the Executive Secretary after meeting all current obligations to customers; an MC-proposed withdrawal completes ongoing applications under MC-defined conditions. The Executive Secretary notifies the Utilizers and Associates, who continue to accept the certificates and reports issued and registered before the withdrawal."
+  validate_provision {
+    /req/cs/pd-03/withdrawal
+  }
+  signature {
+    in { declarations }
+    out { declarations }
+  }
+  invariants {
+    "[declaration].status = 'withdrawn' implies [declaration].withdrawal_record is not null"
+  }
+  activity_kind { withdrawal }
+  organs { executive_secretary }
+  participant_kinds { issuing_authority }
+  evidence {
+    withdrawal_record { description "The withdrawal notice, the evidence of met customer obligations, and the notification to Utilizers and Associates." required true }
+  }
+  realized_by { record_participant_declaration }
+  executor actor
+  source { doc "PD-03, 11" clause "" }
+}
+
+process ia_notification_of_changes {
+  name "IA notification of changes"
+  summary "The IA immediately informs the Executive Secretary of essential organisational or technical changes impacting its ISO/IEC 17065 compliance; the Executive Secretary consults the RC for a recommendation on the appropriate action (e.g. temporary suspension of scope)."
+  validate_provision {
+    /req/cs/pd-03/notification-of-changes
+  }
+  signature {
+    in { declarations }
+    out { declarations }
+  }
+  invariants {
+    "[change_notification].received_at is not null"
+  }
+  activity_kind { review }
+  organs { executive_secretary review_committee }
+  participant_kinds { issuing_authority }
+  evidence {
+    change_notification { description "The change notification and the RC consultation outcome." required true }
+  }
+  realized_by { record_participant_declaration }
+  executor actor
+  source { doc "PD-03, 12" clause "" }
+}
+
+document_module pd-03 {
+  document "OIML-CS PD-03"
+  title "Application and approval of OIML Issuing Authorities"
+  edition "5"
+  year 2025
+  namespace /req/cs/pd-03
+  sequence { ia_application ia_assessment ia_rc_review ia_mc_decision ia_declaration_signing ia_list_publication }
+  register ia_register {
+    label "List of OIML Issuing Authorities"
+    clause "PD-03, 5.3.2"
+    maintainer biml
+    published "The OIML-CS pages of the OIML website (B 18:2025 §5.1.4)"
+    entries "Per OIML Issuing Authority: designation, Member State, scope (instrument categories × OIML Recommendations × Schemes), associated Test Laboratories, and participation status (approved / suspended / withdrawn)."
+  }
+}

package/oiml-cs/framework/documents/pd-03/annex-d032.prl

@@ -0,0 +1,48 @@
+# OIML-CS DOCUMENT MODULE PD-03 — INFORMATIVE ANNEX: OIML D 32 (2018)
+# -----------------------------------------------------------------------------
+# D 32 is the application guide PD-03, 4.3 invokes for the ISO/IEC 17065
+# competence basis ("compliance with ISO/IEC 17065:2012, applied per OIML
+# D 32"). INFORMATIVE only: the normative provisions are this module's
+# requirements.prl; the competence model itself lives in the iso-iec-17065
+# package (/req/iso-17065/*, TODO.roadmap/39b) — this annex REFERENCES it,
+# never restates it (MECE, grep-proven by the consumer's
+# cs-participant-approval tests).
+#
+# WARNING — DEFECTIVE LOCAL NUMBERING (permanent): the local
+# data/oiml-d032/document.presentation.xml is a defective conversion
+# (regenerated XMLs are numbered official-PDF − 1 — the build drops the
+# Introduction clause) and is NEVER cited for numbering. Clause anchors
+# here follow the official published PDF (reference-docs/oiml-d/
+# d032-e18.pdf, retrieved 2026-07-24; task 46).
+informative_annex d_32 {
+  document {
+    id "D 32"
+    title "OIML D 32 — Guide for the application of ISO/IEC 17065 to assessment of certification bodies in legal metrology"
+    edition 2018
+    year 2018
+    role informative
+    source "data/oiml-d032/document.presentation.xml"
+  }
+  applies_to iso-iec-17065
+  applied_by "PD-03, 4.3"
+  scope "Guidance for assessing certification bodies in legal metrology against ISO/IEC 17065 — clause-by-clause application notes (the G-series) on the structural, resource, process and management-system requirements, read together with the standard when an IA's competence is assessed under PD-03, 5.2 (accreditation or peer assessment) and when the IA keeps its internal audit current (PD-03, 5.1 i)."
+  numbering_caution "The local text source (data/oiml-d032/document.presentation.xml) is a defective conversion (official-PDF − 1 numbering) and is never cited for numbering; the note anchors cited here follow the guide's own stable in-text note ids (e.g. G.7.1.1-3), VERIFIED against the official published PDF (reference-docs/oiml-d/d032-e18.pdf, task 46, 2026-07-24): G.7.1.1-1/-2/-3/-6, G.7.1.2-1 and G.7.1.3-1 all confirmed. NOTE — the official D 32:2018 PDF itself skips G.7.1.1-4 (the printed sequence runs -3 → -5; an editorial gap in the source document, not a conversion drop — corpus C's speculation is corrected)."
+  highlight design_evaluation_checklist {
+    clause "G.7.1.1-3"
+    title "Type evaluation includes design evaluation"
+    statement "Type evaluation includes design evaluation, in particular for the following aspects: suitability for use; sealing; marking; checking facilities (D 32, G.7.1.1-3, applying ISO/IEC 17065 7.1.1)."
+    discharged_by "The Recommendations' own examination-documentation requirements: each rec's examination-docs content (the M7 module data/modules/examination-docs/ + the recs' report-row examination requirements — the report-row-coverage linker convention) is what a rec declares for the sealing/marking/checking-facilities design evaluation of its instruments, so the IA assessment verifies the rec-level discharge rather than re-modelling the checklist here. Neighbour notes: G.7.1.1-1/2 (the scheme relates to type approval and OIML certification; no market sampling) and G.7.1.1-6 (non-legal-metrology matters, e.g. electrical safety, are out of scope) are scope statements the scheme model already realizes (framework/schemes.yaml; per-rec applicability)."
+  }
+  highlight oiml_cs_procedural_documents_apply {
+    clause "G.7.1.3-1"
+    title "OIML certification applies the OIML-CS procedural documents"
+    statement "For OIML Certificates the provisions of OIML-CS PD-05 (Processing an OIML Type Evaluation Report and OIML Certificate) shall be applied (D 32, G.7.1.3-1, applying ISO/IEC 17065 7.1.3)."
+    discharged_by "The PD-05 content is single-sourced in this package (specification/requirements/cs.yaml + evaluation/abstract-processes.yaml, TODO.roadmap/15/41) — the certification process the IA is assessed against."
+  }
+  highlight public_requirements {
+    clause "G.7.1.2-1"
+    title "Requirements result from publicly accessible documents"
+    statement "The certification requirements shall result from documents accessible to the public — laws, regulations, OIML publications, standards (D 32, G.7.1.2-1, applying ISO/IEC 17065 7.1.2): for OIML certification, the OIML Recommendations and the OIML-CS documents."
+    discharged_by "The YAML single-source discipline of this repository: every rec's requirements carry clause-URN provenance to the published Recommendation; the governing-document hierarchy is framework/documents.yaml."
+  }
+}