@oimlsmart/primmel-packages 0.4.0 → 0.6.0

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

@@ -0,0 +1,162 @@
+# OIML-CS DOCUMENT MODULE PD-03 — NORMATIVE PROVISIONS (/req/cs/pd-03/*)
+# -----------------------------------------------------------------------------
+# OIML-CS PD-03 Edition 5 (2025-12-24) — the participant-competence
+# pipeline for OIML Issuing Authorities: application (with the ≥ 1-TL-
+# application precondition), competence demonstration (accreditation via
+# the IAF MLA or peer assessment), RC review, the MC 80 % vote, the
+# Declaration and the IA register.
+#
+# NUMBERING: clause anchors VERIFIED against the official published PDF
+# (reference-docs/cs/docs/oiml-cs-pd-03-edition-5-20251224.pdf, retrieved
+# 2026-07-24; task 46). The audit's reconstruction is CONFIRMED in full:
+# top-level clauses 1–13 and 4.1/4.2/4.3, 5.1 (items a–i)/5.2/5.3,
+# 5.2.1–5.2.3, 5.3.1/5.3.2 (5.3.2.1–5.3.2.6 — the list update is
+# 5.3.2.6), 6.1/6.2 (6.2.2 = 5.3.2 minus 5.3.2.5), 7, 8, 9 (9.7 the
+# new-edition gap-analysis route), 10 (10.1 Scheme A — 10.1.1 annual
+# summary report + four-yearly reassessment review, 10.2 Scheme B), 11,
+# 12. The clause-10 split (10.1/10.2) exists in the body (the printed
+# Contents lists only 10.1/10.2 at clause level). The local presentation
+# XML (data/oiml-cs-pd-03/) is a defective build (official-PDF − 1
+# numbering) and is NEVER cited.
+#
+# Competence content is DELEGATED (MECE): ISO/IEC 17065 per OIML D 32 —
+# the iso-iec-17065 package + this module's annex-d032.prl.
+#
+# This file is the single source of truth; the consumer's
+# data/oiml-cs/documents/pd-03/requirements.yaml is its GENERATED YAML twin
+# (cd browser && npm run gen:data).
+requirement_class /req/cs/pd-03 {
+  title "OIML-CS IA approval requirements"
+  name "Application and approval of OIML Issuing Authorities (PD-03)"
+  description "Provisions of OIML-CS PD-03 Edition 5 governing the application, assessment, approval and continued participation of OIML Issuing Authorities. Enforced by the abstract pipeline of this module (abstract-processes.yaml); the organ actors, decision rules and Declaration model it binds are the task-40 framework model (framework/)."
+  subject "OIML-CS participant governance — Issuing Authority approval"
+}
+
+requirement /req/cs/pd-03/competence-basis {
+  name "Competence basis — ISO/IEC 17065 applied per D 32"
+  statement "The OIML Issuing Authority shall comply with ISO/IEC 17065:2012, applied in accordance with the guidance of OIML D 32:2018 (PD-03, 4.3). The competence requirements themselves are those of ISO/IEC 17065 — single-sourced in the iso-iec-17065 reference package (/req/iso-17065/*, TODO.roadmap/39b); this provision pins the delegation, it does not restate the standard. The method of DEMONSTRATING compliance is the accreditation or peer-assessment path of 5.2."
+  obligation shall
+  verification { method inspection description "Assessment report review in the approval pipeline (abstract process ia_assessment)." }
+  source { doc "PD-03, 4.3" clause "" }
+}
+
+requirement /req/cs/pd-03/tl-application-precondition {
+  name "Test Laboratory application precondition"
+  statement "An application to become an OIML Issuing Authority shall be accompanied by at least one associated Test Laboratory application in accordance with OIML-CS PD-04 (PD-03, 4.1). An IA application without an associated TL application is incomplete and does not enter assessment."
+  obligation shall
+  verification { method inspection description "Application completeness check (abstract process ia_application, invariant)." }
+  source { doc "PD-03, 4.1" clause "" }
+}
+
+requirement /req/cs/pd-03/application-contents {
+  name "Application contents"
+  statement "The application shall be made on the CIML-endorsed Application Form (reference-docs/cs/application-forms/oiml-issuing-authority- application-form.pdf) and shall include (PD-03, 5.1 items a–i): the competency-assessment information; the designation and contact details; the scope (instrument categories with their OIML Recommendations and Schemes); the list of associated Test Laboratories with the tests/examinations each performs; the MTL supervision procedures where a Manufacturer Test Laboratory is used (PD-04, 7.1); the accreditation certificate(s) with the latest assessment report, or the peer assessment report; the most recent OIML type evaluation report per category where the body was previously an IA; and the latest internal audit against ISO/IEC 17065 with D 32. The application commits the Member State to designate at least one Utilizer per category (PD-09) unless the category is not regulated in that Member State."
+  obligation shall
+  verification { method inspection description "Executive-Secretary completeness review (abstract process ia_application)." }
+  source { doc "PD-03, 5.1" clause "" }
+}
+
+requirement /req/cs/pd-03/assessment-accreditation {
+  name "Competence demonstration by accreditation"
+  statement "Where competence is demonstrated by accreditation, the accreditation body shall be a signatory of a mutual recognition arrangement (e.g. the IAF MLA) and the assessment team shall include at least one MC-approved Legal Metrology Expert (PD-03, 5.2.2). Substitution of the LME by an accreditation-body expert is permitted only for an existing IA, on written request, after consultation of the Executive Secretary, the MC Chairperson and the RC Chairperson, with the RC informed and an LME taking part at the next opportunity. The assessment shall address impartiality, shall record the D 32 evidence in its report, and may use remote techniques where integrity is not compromised (Joint IAF-OIML procedure)."
+  obligation shall
+  verification { method inspection description "Accreditation path of the assessment step (abstract process ia_assessment)." }
+  source { doc "PD-03, 5.2.2" clause "" }
+}
+
+requirement /req/cs/pd-03/assessment-peer {
+  name "Competence demonstration by peer assessment"
+  statement "Where competence is demonstrated by peer assessment, the assessment team shall be led by a Management System Expert and include at least one Legal Metrology Expert, all MC-approved and impartial; the applicant IA arranges the team from the approved-experts list (PD-02, 9) and bears the cost; the visit assesses against ISO/IEC 17065 with D 32 and is recorded on the OIML Issuing Authority Peer Assessment Report form; non-compliances shall be resolved to the satisfaction of the assessment team (PD-03, 5.2.3)."
+  obligation shall
+  verification { method inspection description "Peer-assessment path of the assessment step (abstract process ia_assessment)." }
+  source { doc "PD-03, 5.2.3" clause "" }
+}
+
+requirement /req/cs/pd-03/approval-process {
+  name "Approval process — RC recommendation and MC vote"
+  statement "The Executive Secretary shall review the application documentation (PD-03, 5.3.1); the complete documentation is reviewed and the Review Committee makes a recommendation to the Management Committee; the Management Committee decides the approval by vote — the 80 % participation decision of B 18:2025 §11.4.2 on RC recommendation (PD-03, 5.3.2) — and the applicant is notified of the outcome."
+  obligation shall
+  verification { method inspection description "The review and decision steps of the pipeline (abstract processes ia_rc_review, ia_mc_decision)." }
+  source { doc "PD-03, 5.3" clause "" }
+}
+
+requirement /req/cs/pd-03/declaration-before-issuance {
+  name "Declaration signed before any issuance"
+  statement "Before issuing any OIML certificate or OIML type evaluation report, the approved OIML Issuing Authority shall have signed its Declaration in accordance with OIML-CS PD-08 (PD-03, 5.3.2). This is the scheme's signing-gate invariant — the gate itself is single-sourced in the task-40 framework model (framework/declarations.yaml, signing_gate; calculus browser/src/data/framework.ts); the terminal step of this module's pipeline discharges it."
+  obligation shall
+  verification { method inspection description "Terminal step of the pipeline (abstract process ia_declaration_signing, discharges_gate)." }
+  source { doc "PD-03, 5.3.2; PD-08 cl. 5" clause "" }
+}
+
+requirement /req/cs/pd-03/scheme-b-self-declaration {
+  name "Scheme B application by self-declaration"
+  statement "An application to be an IA under Scheme B shall comprise a self-declaration with supporting evidence and the most recent OIML type evaluation report per category, or a report template where the body has not previously issued one (PD-03, 6.1); the application is processed by the 5.3.2 review-and-decision procedure without its assessment-report step (PD-03, 6.2)."
+  obligation shall
+  verification { method inspection description "Scheme B branch of the pipeline (abstract process ia_scheme_b_application)." }
+  source { doc "PD-03, 6.1" clause "" }
+}
+
+requirement /req/cs/pd-03/appeals-procedures {
+  name "Documented appeals procedures"
+  statement "The OIML Issuing Authority shall have documented procedures for accepting, considering and resolving appeals against its decisions (PD-03, 7). (Appeals against MC participation decisions are the Board of Appeal's procedure — framework/governance.yaml boa-appeal-rulings and PD-01, task 43.)"
+  obligation shall
+  verification { method inspection description "IA body procedures, verified at assessment and periodic review." }
+  source { doc "PD-03, 7" clause "" }
+}
+
+requirement /req/cs/pd-03/suspension-process {
+  name "Suspension process"
+  statement "Where an IA is alleged to have failed over time to abide by the rules of the OIML-CS, the Executive Secretary shall contact the IA with the supporting evidence and, failing a satisfactory response, report the alleged non-compliance to the Review Committee; the RC may require an action plan and, if the IA does not evidence the action, recommend suspension to the Management Committee, which decides by vote — a PARTIAL suspension of scope is possible (PD-03, 8). A suspended IA shall not start any new applications and may complete ongoing applications only under conditions defined by the MC."
+  obligation shall
+  verification { method inspection description "Off-sequence suspension flow (abstract process ia_suspension)." }
+  source { doc "PD-03, 8" clause "" }
+}
+
+requirement /req/cs/pd-03/scope-change {
+  name "Extension or reduction of scope"
+  statement "An IA may apply to extend its scope (extended TL capabilities, an added Test Laboratory — processed per PD-04, an added instrument category, or an added Recommendation edition) on the Application Form with supporting competence evidence, processed by the clause-5 procedures as appropriate. A reduction of scope is effected by notification to the Executive Secretary, who amends the IA's Declaration accordingly and notifies the MC — no MC approval is required for a reduction (PD-03, 9)."
+  obligation shall
+  verification { method inspection description "Off-sequence scope-change flow (abstract process ia_scope_change)." }
+  source { doc "PD-03, 9" clause "" }
+}
+
+requirement /req/cs/pd-03/periodic-review {
+  name "Periodic review of participation"
+  statement "IAs and their associated Test Laboratories shall undergo the maintenance process (PD-03, 10): an internal summary report is submitted to the Executive Secretary and reviewed by the Management Committee once a year (covering comparison results, personnel/ structure/organisation changes, management reviews, internal audits, accreditation surveillance where applicable, complaints, and the numbers of type evaluation reports, test reports and certificates issued — the OIML Issuing Authority Report template); and every four years the accreditation assessment reports and/or peer assessment reports are submitted (PD-03, 10.1.1), reviewed by the Executive Secretary, recommended on by the Review Committee, and voted on by the Management Committee — on rejection the IA may submit additional information and the MC reconsiders."
+  obligation shall
+  verification { method inspection description "Off-sequence maintenance flow (abstract process ia_periodic_review)." }
+  source { doc "PD-03, 10 (10.1.1)" clause "" }
+}
+
+requirement /req/cs/pd-03/periodic-review-lme-participation {
+  name "LME participation per accreditation renewal cycle"
+  statement "Within the maintenance process, an MC-approved Legal Metrology Expert shall participate in the IA's assessment at least once per accreditation renewal cycle, at a maximum interval of five years (PD-03, 10.1 — the audit's structural reconstruction; the sub-number is not in-text verified)."
+  obligation shall
+  verification { method inspection description "Assessment-team composition across the renewal cycle (abstract process ia_periodic_review)." }
+  source { doc "PD-03, 10 (10.1)" clause "" }
+}
+
+requirement /req/cs/pd-03/scheme-b-annual-evidence {
+  name "Scheme B — annual evidence supporting the self-declaration"
+  statement "A Scheme B IA shall submit every year the evidence supporting its self-declaration — the Scheme B counterpart of the Scheme A four-yearly accreditation/peer-assessment report cycle (PD-03, 10.2 — the audit's structural reconstruction; the sub-number is not in-text verified)."
+  obligation shall
+  verification { method inspection description "Annual Scheme B evidence of the maintenance flow (abstract process ia_periodic_review)." }
+  source { doc "PD-03, 10 (10.2)" clause "" }
+}
+
+requirement /req/cs/pd-03/withdrawal {
+  name "Withdrawal"
+  statement "An IA withdrawing from the OIML-CS (or reducing its scope) shall give notice to the Executive Secretary and shall meet all current obligations to customers before the withdrawal takes effect; where the withdrawal is at the proposal of the Management Committee, ongoing applications are completed under MC-defined conditions. The Executive Secretary notifies the Utilizers and Associates, who shall accept and utilise or recognise the OIML certificates and OIML type evaluation reports issued and registered prior to the withdrawal (PD-03, 11)."
+  obligation shall
+  verification { method inspection description "Off-sequence withdrawal flow (abstract process ia_withdrawal)." }
+  source { doc "PD-03, 11" clause "" }
+}
+
+requirement /req/cs/pd-03/notification-of-changes {
+  name "Notification of changes"
+  statement "The IA shall immediately inform the Executive Secretary of an essential organisational or technical change (e.g. key staff, location) that could impact its compliance with ISO/IEC 17065; the Executive Secretary consults the Review Committee for a recommendation on the appropriate action, e.g. a temporary suspension of scope (PD-03, 12)."
+  obligation shall
+  verification { method inspection description "Off-sequence change-notification flow (abstract process ia_notification_of_changes)." }
+  source { doc "PD-03, 12" clause "" }
+}
+

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

@@ -0,0 +1,295 @@
+# OIML-CS DOCUMENT MODULE PD-04 — ABSTRACT PROCESSES
+# -----------------------------------------------------------------------------
+# The PD-04 Edition 5 Test-Laboratory approval pipeline as ABSTRACT
+# processes (TODO.roadmap/42):
+#
+#   application → assessment → RC review → MC 80 % vote
+#               → IA-Declaration update → TL-list publication
+#
+# plus the off-sequence flows: Scheme B application, MTL controlled
+# supervision, scope change, withdrawal. 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 resolves every reference. The periodic review of a TL rides on
+# the IA's maintenance cycle (PD-03, 10 covers "IAs and their associated
+# Test Laboratories") — modelled once in documents/pd-03 (MECE).
+#
+# The terminal invariant: ia_declaration_update carries discharges_gate
+# declaration-signed-before-issuance — the same task-40 signing gate as
+# the PD-03 pipeline: the updated IA Declaration (now listing the TL) must
+# be SIGNED before the IA may issue anything on the basis of this TL's
+# test data (PD-08 cl. 5).
+#
+# TODO.roadmap/44–45 REALIZED the pipeline (the participant-approval set;
+# see the pd-03 header). 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-04/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 tl_application {
+  name "TL application"
+  summary "A Test Laboratory — internal, third-party or Manufacturer (the kinds of framework/participants.yaml) — applies on the Application Form ENDORSED BY an OIML Issuing Authority and made in conjunction with the IA's own application (PD-03, 4.1), with the 5.1 a–j accompanying information: TL kind, tests/examinations per Recommendation, type-testing capabilities incl. sites outside permanent control (ISO/IEC 17025, 6.3.5), MTL supervision procedures where applicable, accreditation or peer-assessment evidence, the internal audit against ISO/IEC 17025 with D 30, intercomparison results, and the latest OIML test report per category (or a template)."
+  validate_provision {
+    /req/cs/pd-04/ia-endorsement
+    /req/cs/pd-04/application-contents
+  }
+  signature {
+    out { participantApplications }
+  }
+  invariants {
+    "[tl_application].endorsing_ia_id is not null"
+    "[tl_application].tl_kind is not null"
+  }
+  activity_kind { selection }
+  organs { executive_secretary }
+  participant_kinds { test_laboratory issuing_authority }
+  evidence {
+    application_form { description "The IA-endorsed Application Form with the 5.1 a–j accompanying information." required true }
+    ia_endorsement { description "The endorsing IA's designation of the TL and the link to the IA's own application (PD-03, 4.1)." required true }
+  }
+  realized_by { submit_participant_application }
+  executor actor
+  source { doc "PD-04, 5.1" clause "" }
+}
+
+process tl_assessment {
+  name "TL competence assessment"
+  summary "The candidate TL's compliance with ISO/IEC 17025:2017 applied per OIML D 30 is demonstrated by accreditation and/or peer assessment (a combination is permitted): accreditation by an ILAC-MRA-signatory body with one MC-approved Legal Metrology Expert per instrument category in the team (5.2.2), or peer assessment led by a Management System Expert with one LME per category, arranged by the endorsing IA from the approved-experts list, recorded on the Test Laboratory Peer Assessment Report form with corrective actions closed by the team leader (5.2.3). Every report names the OIML experts involved (5.2.1)."
+  validate_provision {
+    /req/cs/pd-04/competence-basis
+    /req/cs/pd-04/assessment-general
+    /req/cs/pd-04/assessment-accreditation
+    /req/cs/pd-04/assessment-peer
+    /req/cs/pd-02/unapproved-expert-use
+  }
+  signature {
+    in { participantApplications }
+    out { participantAssessments }
+  }
+  invariants {
+    "[assessment].path = 'accreditation' or [assessment].path = 'peer_assessment' or [assessment].path = 'combined'"
+    "[assessment].team.lme_per_category.count = [tl_application].scope.categories.count"
+    "[assessment].path = 'peer_assessment' implies [assessment].team.mse_team_leader is not null"
+  }
+  activity_kind { accreditation peer_assessment }
+  participant_kinds { test_laboratory legal_metrology_expert management_system_expert }
+  evidence {
+    assessment_report { description "The accreditation certificate with scope and the latest assessment report, or the Test Laboratory Peer Assessment Report — naming the OIML experts and recording the corrective- action closure." required true }
+    expert_approval_evidence { description "Evidence that every expert in the team is MC-approved — one LME per instrument category assessed." required true }
+  }
+  realized_by { assess_participant_competence }
+  executor actor
+  source { doc "PD-04, 5.2" clause "" }
+}
+
+process tl_rc_review {
+  name "RC review and recommendation"
+  summary "The Review Committee reviews the complete TL application documentation and makes its recommendation on the approval to the Management Committee."
+  validate_provision {
+    /req/cs/pd-04/approval-process
+  }
+  signature {
+    in { participantApplications participantAssessments }
+    out { participantApplications }
+  }
+  invariants {
+    "[tl_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 TL's approval." required true }
+  }
+  realized_by { recommend_participation }
+  executor actor
+  source { doc "PD-04, 5.3.2" clause "" }
+}
+
+process tl_mc_decision {
+  name "MC approval vote"
+  summary "The Management Committee decides the TL'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)."
+  validate_provision {
+    /req/cs/pd-04/approval-process
+  }
+  signature {
+    in { participantApplications }
+    out { participantApplications }
+  }
+  invariants {
+    "[tl_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 TL and the endorsing IA." required true }
+  }
+  decision { rule ia-tl-participation-decisions clause "PD-04, 5.3.2" }
+  realized_by { decide_participation }
+  executor actor
+  source { doc "PD-04, 5.3.2" clause "" }
+}
+
+process ia_declaration_update {
+  name "IA Declaration update"
+  summary "The Declaration of the designating IA(s) is updated to list the approved Test Laboratory (and, for an MTL, to identify the IA responsible for its controlled supervision, 7.1). This is the pipeline's TERMINAL INVARIANT: the updated Declaration must be SIGNED before the IA may issue any certificate or type evaluation report on the basis of this TL's test data — the task-40 signing gate (framework/declarations.yaml, PD-08 cl. 5) blocks the IA's issue/evaluation abstract processes until then."
+  validate_provision {
+    /req/cs/pd-04/approval-process
+  }
+  signature {
+    in { participantApplications declarations }
+    out { declarations }
+  }
+  invariants {
+    "[declaration].test_laboratory_ids contains [tl_application].test_laboratory_id"
+    "[declaration].status = 'signed'"
+  }
+  activity_kind { declaration }
+  organs { executive_secretary }
+  participant_kinds { issuing_authority test_laboratory }
+  evidence {
+    updated_declaration { description "The IA's Declaration updated with the approved TL (and the MTL supervision identification where the TL is a Manufacturer Test Laboratory), recorded by the Executive Secretary." required true }
+  }
+  declaration { kind issuing_authority_declaration action update }
+  discharges_gate declaration-signed-before-issuance
+  realized_by { record_participant_declaration }
+  executor actor
+  source { doc "PD-04, 5.3.2" clause "" }
+}
+
+process tl_list_publication {
+  name "TL list publication"
+  summary "The approved TL is added to the Test Laboratory list on the OIML-CS pages of the OIML website — the public register of who may test for the scheme."
+  signature {
+    in { declarations }
+    out { participantRegisters }
+  }
+  invariants {
+    "[register_entry].test_laboratory_id is not null"
+  }
+  organs { biml executive_secretary }
+  evidence {
+    register_entry { description "The TL's entry in the published TL register (designation, kind, tests/examinations per Recommendation, designating IAs)." required true }
+  }
+  realized_by { publish_participant_register }
+  executor actor
+  source { doc "PD-04, 5.3.2" clause "" }
+}
+
+process tl_scheme_b_application {
+  name "Scheme B TL application"
+  summary "A Scheme B TL application comprises a self-declaration with the capability defined in terms of tests/examinations, supported by internal-assessment evidence (6.1), reviewed by the 5.3.2 procedure (6.2)."
+  validate_provision {
+    /req/cs/pd-04/scheme-b-self-declaration
+  }
+  signature {
+    out { participantApplications }
+  }
+  invariants {
+    "[tl_application].scheme = 'B' implies [tl_application].self_declaration is not null"
+  }
+  activity_kind { selection }
+  organs { executive_secretary review_committee management_committee }
+  participant_kinds { test_laboratory issuing_authority }
+  evidence {
+    self_declaration { description "The self-declaration defining the capability in tests/ examinations, with the internal-assessment evidence." required true }
+  }
+  decision { rule ia-tl-participation-decisions clause "PD-04, 6.2" }
+  realized_by { submit_participant_application }
+  executor actor
+  source { doc "PD-04, 6" clause "" }
+}
+
+process mtl_supervision {
+  name "MTL controlled supervision"
+  summary "A Manufacturer Test Laboratory operates under the controlled supervision of at least one IA identified in its Declaration, with the 7.1 a–f safeguards: documented instructions for the test program and the EUT (and for EUT failure mid-program), start/finish notification, short-notice witness visits, post-test re-tests (spot checks), and no subcontracting by the MTL. The effectiveness of the supervision is audited — within the supervising IA's Scheme A assessments, or under Scheme B within internal audits — and the MTL's parent organisation embeds mandatory impartiality provisions in its quality manual. When testing for other parties than its parent company the MTL is treated as a third-party TL (framework/participants.yaml)."
+  validate_provision {
+    /req/cs/pd-04/mtl-controlled-supervision
+    /req/cs/pd-04/mtl-safeguards
+    /req/cs/pd-04/mtl-supervision-audit
+  }
+  signature {
+    in { declarations }
+    out { participantAssessments }
+  }
+  invariants {
+    "[mtl].supervising_ia_ids.count >= 1"
+    "[mtl].subcontracts_testing = false"
+  }
+  activity_kind { surveillance }
+  participant_kinds { test_laboratory issuing_authority }
+  evidence {
+    supervision_procedures { description "The IA's documented supervision instructions for the MTL (test program, EUT failure) — also part of the IA's PD-03, 5.1 application content." required true }
+    supervision_records { description "The running supervision records: start/finish notifications, witness-visit records, spot-check re-test results." required true }
+  }
+  realized_by { record_participant_declaration }
+  executor actor
+  source { doc "PD-04, 7.1" clause "" }
+}
+
+process tl_scope_change {
+  name "TL scope extension or reduction"
+  summary "A TL extends its scope on the IA-endorsed Application Form, processed by the clause-5 procedures — for a new edition of a Recommendation already in scope a gap analysis suffices, no new assessment. A reduction is notified via the IA to the Executive Secretary, who amends the TL's scope on the OIML-CS pages and notifies the MC — no MC approval for a reduction."
+  validate_provision {
+    /req/cs/pd-04/scope-change
+  }
+  signature {
+    in { declarations }
+    out { declarations }
+  }
+  invariants {
+    "[scope_change].kind = 'extension' implies [scope_change].ia_endorsement is not null"
+  }
+  activity_kind { review }
+  organs { executive_secretary }
+  participant_kinds { test_laboratory issuing_authority }
+  evidence {
+    scope_change_record { description "The endorsed extension application (with the gap analysis where a new Recommendation edition is added), or the reduction notification with the amended register entry." required true }
+  }
+  realized_by { record_participant_declaration }
+  executor actor
+  source { doc "PD-04, 8" clause "" }
+}
+
+process tl_withdrawal {
+  name "TL withdrawal"
+  summary "A TL withdraws by notice via the relevant IA to the Executive Secretary after meeting all current obligations to customers; an MC-proposed withdrawal completes ongoing applications under MC-defined conditions."
+  validate_provision {
+    /req/cs/pd-04/withdrawal
+  }
+  signature {
+    in { declarations }
+    out { declarations }
+  }
+  invariants {
+    "[tl_application].status = 'withdrawn' implies [tl_application].withdrawal_record is not null"
+  }
+  activity_kind { withdrawal }
+  organs { executive_secretary }
+  participant_kinds { test_laboratory issuing_authority }
+  evidence {
+    withdrawal_record { description "The withdrawal notice via the IA and the evidence of met customer obligations." required true }
+  }
+  realized_by { record_participant_declaration }
+  executor actor
+  source { doc "PD-04, 9" clause "" }
+}
+
+document_module pd-04 {
+  document "OIML-CS PD-04"
+  title "Assessment and approval of Test Laboratories"
+  edition "5"
+  year 2025
+  namespace /req/cs/pd-04
+  sequence { tl_application tl_assessment tl_rc_review tl_mc_decision ia_declaration_update tl_list_publication }
+  register tl_register {
+    label "List of Test Laboratories"
+    clause "PD-04, 5.3.2"
+    maintainer biml
+    published "The OIML-CS pages of the OIML website"
+    entries "Per Test Laboratory: designation, kind (internal / third-party / manufacturer), the tests/examinations it performs per OIML Recommendation, the designating OIML Issuing Authorities, and participation status."
+  }
+}

package/oiml-cs/framework/documents/pd-04/annex-d030.prl

@@ -0,0 +1,54 @@
+# OIML-CS DOCUMENT MODULE PD-04 — INFORMATIVE ANNEX: OIML D 30 (2020)
+# -----------------------------------------------------------------------------
+# D 30 is the application guide PD-04, 4.3 invokes for the ISO/IEC 17025
+# competence basis ("compliance with ISO/IEC 17025:2017, applied per OIML
+# D 30"). INFORMATIVE only: the normative provisions are this module's
+# requirements.prl; the competence model itself lives in the iso-iec-17025
+# package (/req/iso-17025/*, TODO.roadmap/39c) — 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-d030/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/
+# d030-e20.pdf, retrieved 2026-07-24; task 46).
+informative_annex d_30 {
+  document {
+    id "D 30"
+    title "OIML D 30 — Guide for the application of ISO/IEC 17025 to the assessment of Testing Laboratories involved in legal metrology"
+    edition 2020
+    year 2020
+    role informative
+    source "data/oiml-d030/document.presentation.xml"
+  }
+  applies_to iso-iec-17025
+  applied_by "PD-04, 4.3"
+  scope "Guidance for assessing testing laboratories involved in legal metrology against ISO/IEC 17025 — clause-by-clause application notes (the G-series) on the impartiality, structural, resource, process and management-system requirements, read together with the standard when a TL's competence is assessed under PD-04, 5.2 (accreditation and/or peer assessment) and when the TL keeps its internal audit current (PD-04, 5.1)."
+  numbering_caution "The local text source (data/oiml-d030/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.8.6.1-1), VERIFIED against the official published PDF (reference-docs/oiml-d/d030-e20.pdf, task 46, 2026-07-24): G.6.3.5-1, G.6.3.3-1, G.7.7.2-1, G.7.8.6.1-1 (+ its single Note) and G.7.8.1.2-1 all confirmed."
+  highlight testing_outside_permanent_control {
+    clause "G.6.3.5-1"
+    title "Facility requirements apply at customer and field sites"
+    statement "The facility and environmental-condition requirements also apply when the testing laboratory performs tests at the customer's (manufacturer's) or other facilities (D 30, G.6.3.5-1, applying ISO/IEC 17025 6.3.5); outdoor-test conditions (rain, wind, …) shall be recorded (G.6.3.3-1)."
+    discharged_by "PD-04, 5.1 makes the capability explicit in the TL application (tests at sites outside the laboratory's permanent control — e.g. belt weighers, rail-weighbridges — usable in OIML test reports per PD-05); per-rec field-test content is the design.field metadata of the conformance tests (the test-design convention, TODO.refactor/09)."
+  }
+  highlight interlaboratory_comparisons {
+    clause "G.7.7.2-1"
+    title "Ensuring validity via inter-laboratory comparisons"
+    statement "Ensuring the validity of results may include participation in inter-laboratory comparisons organised by the BIML (D 30, G.7.7.2-1, applying ISO/IEC 17025 7.7)."
+    discharged_by "The TLF's intercomparison programme (framework/governance.yaml tlf-advisory-tasks, B 18:2025 12.2 d) and the PD-04, 5.1 application content (intercomparison results); the pilot lab's intercomparison evidence is its implementation-package content (data/lab-*/ , TODO.roadmap/23)."
+  }
+  highlight decision_rule_per_recommendation {
+    clause "G.7.8.6.1-1"
+    title "Statement of conformity per the Recommendation's decision rule"
+    statement "A statement of conformity (e.g. pass/fail) for an individual test shall be made in accordance with the decision rule specified for that test in the relevant OIML Recommendation; OIML G 1-106 and G 19 give general guidance on decision rules and measurement uncertainty (D 30, G.7.8.6.1-1 + Note, applying ISO/IEC 17025 7.8.6.1)."
+    discharged_by "The platform's acceptance decision-rule convention (TODO.refactor/10): every requirement limit and characteristic carries its declared `acceptance:` (shared_risk default / guarded with guard bands, the R 91-2 criterion taxonomy), single-sourced per rec in specification/requirements and model/characteristics — the decision rule is Recommendation content, evaluated by the one verdict chain."
+  }
+  highlight partial_test_reports {
+    clause "G.7.8.1.2-1"
+    title "Multiple laboratories — partial test reports"
+    statement "Where more than one testing laboratory contributes to an evaluation, each testing laboratory issues a partial test report and/or an additional test report for its part (D 30, G.7.8.1.2-1, applying ISO/IEC 17025 7.8.1.2)."
+    discharged_by "The PD-05 multiple-laboratories rule — /req/cs/ multiple-test-laboratories (specification/requirements/cs.yaml) and the platform's per-TL test-report chain (test request → assignment → test report per laboratory)."
+  }
+}