@oimlsmart/primmel-packages 0.4.0 → 0.6.0

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

@@ -0,0 +1,140 @@
+# OIML-CS DOCUMENT MODULE PD-04 — NORMATIVE PROVISIONS (/req/cs/pd-04/*)
+# -----------------------------------------------------------------------------
+# OIML-CS PD-04 Edition 5 (2025-12-24) — the participant-competence
+# pipeline for Test Laboratories of all three kinds (internal /
+# third-party / Manufacturer Test Laboratory): application endorsed by an
+# IA, competence demonstration (accreditation and/or peer assessment per
+# ISO/IEC 17025, applied per OIML D 30), RC review, the MC 80 % vote, the
+# IA-Declaration update and the TL register.
+#
+# NUMBERING: clause anchors VERIFIED against the official published PDF
+# (reference-docs/cs/docs/oiml-cs-pd-04-edition-5-20251224.pdf, retrieved
+# 2026-07-24; task 46). The audit's reconstruction is CONFIRMED in full:
+# top-level clauses 1–10 and 4.1/4.2/4.3, 5.1 (items a–j)/5.2/5.3,
+# 5.2.1–5.2.3, 5.3.1/5.3.2 (5.3.2.1–5.3.2.4 — the Declaration update + TL
+# list update is 5.3.2.4), 6.1/6.2, 7.1 (safeguards a–f)–7.5, 8 (8.3 the
+# new-edition gap-analysis route), 9 (9.2 ongoing applications completed
+# under MC-defined conditions). PD-04 Ed 5 has NO suspension clause (the
+# IA-side suspension process is PD-03, 8). The local presentation XML
+# (data/oiml-cs-pd-04/) is a defective build (official-PDF − 1 numbering)
+# and is NEVER cited.
+#
+# Competence content is DELEGATED (MECE): ISO/IEC 17025 per OIML D 30 —
+# the iso-iec-17025 package + this module's annex-d030.prl. The three TL
+# kinds are defined once in framework/participants.prl (test_laboratory
+# subkinds) and referenced via participant_kinds, never redefined.
+#
+# This file is the single source of truth; the consumer's
+# data/oiml-cs/documents/pd-04/requirements.yaml is its GENERATED YAML twin
+# (cd browser && npm run gen:data).
+requirement_class /req/cs/pd-04 {
+  title "OIML-CS TL approval requirements"
+  name "Assessment and approval of Test Laboratories (PD-04)"
+  description "Provisions of OIML-CS PD-04 Edition 5 governing the application, assessment, approval and continued participation of Test Laboratories — internal, third-party and Manufacturer Test Laboratories. 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 — Test Laboratory approval"
+}
+
+requirement /req/cs/pd-04/competence-basis {
+  name "Competence basis — ISO/IEC 17025 applied per D 30"
+  statement "The Test Laboratory shall comply with ISO/IEC 17025:2017, applied in accordance with the guidance of OIML D 30:2020 (PD-04, 4.3). The competence requirements themselves are those of ISO/IEC 17025 — single-sourced in the iso-iec-17025 reference package (/req/iso-17025/*, TODO.roadmap/39c); this provision pins the delegation, it does not restate the standard. The method of DEMONSTRATING compliance is the accreditation and/or peer- assessment path of 5.2."
+  obligation shall
+  verification { method inspection description "Assessment report review in the approval pipeline (abstract process tl_assessment)." }
+  source { doc "PD-04, 4.3" clause "" }
+}
+
+requirement /req/cs/pd-04/ia-endorsement {
+  name "Application endorsed by an Issuing Authority"
+  statement "The Test Laboratory application shall be endorsed by an OIML Issuing Authority and made in conjunction with that IA's own application (PD-04, 5.1; PD-03, 4.1 — an IA application is accompanied by at least one TL application). The application designates which of the three Test Laboratory kinds the applicant is: an internal TL of the IA, a third-party TL, or a Manufacturer Test Laboratory (the kinds themselves are defined in framework/participants.yaml test_laboratory.subkinds)."
+  obligation shall
+  verification { method inspection description "Application completeness check (abstract process tl_application)." }
+  source { doc "PD-04, 5.1" clause "" }
+}
+
+requirement /req/cs/pd-04/application-contents {
+  name "Application contents"
+  statement "The application shall be made on the Application Form (reference-docs/cs/application-forms/test-laboratory-application- form.pdf) and shall include (PD-04, 5.1 items a–j): the assessment information; the laboratory designation including the TL kind; the tests/examinations performed per OIML Recommendation; the type-testing capabilities, including testing at sites outside the laboratory's permanent control (ISO/IEC 17025, 6.3.5 — field or installed-site testing, e.g. belt weighers, rail-weighbridges, usable in OIML test reports per PD-05); the MTL supervision procedures where applicable; the accreditation certificate with scope and the latest assessment report, or the peer assessment report; the latest internal audit against ISO/IEC 17025 with D 30; intercomparison results; and the latest OIML test report per category (or a template where none exists)."
+  obligation shall
+  verification { method inspection description "Executive-Secretary completeness review (abstract process tl_application)." }
+  source { doc "PD-04, 5.1" clause "" }
+}
+
+requirement /req/cs/pd-04/assessment-general {
+  name "Assessment general rules"
+  statement "Competence shall be demonstrated by accreditation and/or peer assessment — a combination of the two is permitted — and every assessment report shall name the OIML experts involved (PD-04, 5.2.1)."
+  obligation shall
+  verification { method inspection description "The assessment step of the pipeline (abstract process tl_assessment)." }
+  source { doc "PD-04, 5.2.1" clause "" }
+}
+
+requirement /req/cs/pd-04/assessment-accreditation {
+  name "Competence demonstration by accreditation"
+  statement "Where competence is demonstrated by accreditation, the accreditation body shall be an ILAC MRA signatory and the assessment team shall include one MC-approved Legal Metrology Expert per instrument category assessed (PD-04, 5.2.2). Substitution of the LME by an accreditation-body expert follows the same conditions as for IA assessments (PD-03, 5.2.2 — existing participants only, written request, Executive Secretary + MC Chairperson + RC Chairperson consultation, RC informed, LME at the next opportunity). The Joint ILAC-OIML procedure applies."
+  obligation shall
+  verification { method inspection description "Accreditation path of the assessment step (abstract process tl_assessment)." }
+  source { doc "PD-04, 5.2.2" clause "" }
+}
+
+requirement /req/cs/pd-04/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 with one Legal Metrology Expert per instrument category, all MC-approved and impartial; the endorsing IA arranges the team from the approved- experts list and the IA or the TL bears the cost; the assessment is recorded on the Test Laboratory Peer Assessment Report form and corrective actions are closed out by the team leader (PD-04, 5.2.3)."
+  obligation shall
+  verification { method inspection description "Peer-assessment path of the assessment step (abstract process tl_assessment)." }
+  source { doc "PD-04, 5.2.3" clause "" }
+}
+
+requirement /req/cs/pd-04/approval-process {
+  name "Approval process — RC recommendation and MC vote"
+  statement "The Executive Secretary shall review the application documentation (PD-04, 5.3.1); the Review Committee reviews the documentation and recommends 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-04, 5.3.2); the Declaration of the designating IA(s) is updated with the approved TL; and the TL is added to the Test Laboratory list on the OIML-CS pages of the OIML website."
+  obligation shall
+  verification { method inspection description "The review, decision, Declaration-update and publication steps of the pipeline." }
+  source { doc "PD-04, 5.3" clause "" }
+}
+
+requirement /req/cs/pd-04/scheme-b-self-declaration {
+  name "Scheme B application by self-declaration"
+  statement "A Scheme B TL application shall comprise a self-declaration with the capability defined in terms of tests/examinations, supported by internal-assessment evidence (PD-04, 6.1); the application is reviewed by the 5.3.2 procedure (PD-04, 6.2)."
+  obligation shall
+  verification { method inspection description "Scheme B branch of the pipeline (abstract process tl_scheme_b_application)." }
+  source { doc "PD-04, 6" clause "" }
+}
+
+requirement /req/cs/pd-04/mtl-controlled-supervision {
+  name "MTL controlled supervision"
+  statement "To address potential conflicts of interest, a Manufacturer Test Laboratory shall operate under the controlled supervision of at least one OIML Issuing Authority identified in its Declaration (PD-04, 7.1). Where two or more IAs use the same MTL, this shall be stated in the MTL's Declaration and the IA responsible for the supervision shall be identified."
+  obligation shall
+  verification { method inspection description "The MTL supervision obligation (abstract process mtl_supervision; the MTL kind itself in framework/participants.yaml)." }
+  source { doc "PD-04, 7.1" clause "" }
+}
+
+requirement /req/cs/pd-04/mtl-safeguards {
+  name "MTL supervision safeguards"
+  statement "The controlled supervision shall include at least the safeguards (PD-04, 7.1): a) the IA has clear documented instructions (quality system procedures) for the MTL concerning the test program and the equipment under test; b) documented instructions for the case the EUT fails before the test program is finished; c) the IA is informed when the MTL starts and finishes the agreed tests; d) the IA or an authorised representative may make short-notice visits to witness tests at the MTL; e) after the tests the IA may request the EUT be submitted to its internal and/or subcontracting laboratory for re-tests (spot checks) — with the applicant's consent another IA's registered laboratory may be used; f) the MTL shall not subcontract testing."
+  obligation shall
+  verification { method inspection description "The supervision safeguards evidence of the MTL supervision obligation (abstract process mtl_supervision)." }
+  source { doc "PD-04, 7.1 a–f" clause "" }
+}
+
+requirement /req/cs/pd-04/mtl-supervision-audit {
+  name "MTL supervision audit and parent-organisation impartiality"
+  statement "The effectiveness of the controlled supervision shall be audited — within the Scheme A assessments of the supervising IA, or, under Scheme B, within internal audits (PD-04, 7.1). The MTL's parent organisation shall embed mandatory impartiality provisions covering the MTL's testing in its quality manual (PD-04, 7.1)."
+  obligation shall
+  verification { method inspection description "Supervision-effectiveness audit records and the parent quality manual (abstract process mtl_supervision)." }
+  source { doc "PD-04, 7.1" clause "" }
+}
+
+requirement /req/cs/pd-04/scope-change {
+  name "Extension or reduction of scope"
+  statement "A TL reduces its scope by notification — the relevant IA informs the Executive Secretary, who amends the TL's scope on the OIML-CS pages and notifies the MC; no MC approval is required for a reduction. A TL extends its scope on the Application Form endorsed by an IA, processed by the clause-5 procedures; where the TL adds a new edition of an OIML Recommendation already in its scope, a gap analysis suffices as competence evidence and no new accreditation or peer assessment is required (PD-04, 8)."
+  obligation shall
+  verification { method inspection description "Off-sequence scope-change flow (abstract process tl_scope_change)." }
+  source { doc "PD-04, 8" clause "" }
+}
+
+requirement /req/cs/pd-04/withdrawal {
+  name "Withdrawal"
+  statement "A TL withdrawing from the OIML-CS (or reducing its scope) shall give notice, via the relevant OIML Issuing Authority, 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 (PD-04, 9)."
+  obligation shall
+  verification { method inspection description "Off-sequence withdrawal flow (abstract process tl_withdrawal)." }
+  source { doc "PD-04, 9" clause "" }
+}
+

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

@@ -0,0 +1,152 @@
+# OIML-CS DOCUMENT MODULE PD-06 — ABSTRACT PROCESSES
+# -----------------------------------------------------------------------------
+# The PD-06 Edition 4 use/misuse discipline as ABSTRACT processes
+# (TODO.roadmap/43):
+#
+#   certificate_use                 (clause 4 — the owner's sanctioned uses)
+#   non_acceptance_justification    (4.8/4.9 — the acceptance discipline)
+#   misuse_handling                 (5.1 — evidence → consultation → warning)
+#   misuse_deregistration           (5.2/5.3 — appeal window → deregistration
+#                                    + public notice)
+#
+# There is no linear chain — all four are post-issuance flows keyed on a
+# registered certificate; hence no sequence. The certificate register and
+# the registered-copy validity principle REFERENCE the task-40 framework
+# model (framework/governance.prl biml-certificate-registration); the
+# deregistration acts through the BIML organ. The 4.8/5.2 appeal hooks are
+# PD-01's procedure (documents/pd-01/) — referenced, never restated; the
+# consumer's linker rule R26 resolves every framework reference.
+#
+# TODO.roadmap/45 REALIZED the acceptance discipline and the misuse track:
+# realized_by binds the concrete Core processes
+# (evaluate_certificate_acceptance, handle_misuse, deregister_certificate);
+# the signature stores are the runtime's cs-operations entity classes.
+# certificate_use stays unrealized (a named gap in the unified coverage
+# report — the owner's use discipline is not a platform act; the mapped
+# misuse track is the scheme's enforcement arm).
+#
+# This file is the single source of truth; the consumer's
+# data/oiml-cs/documents/pd-06/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 certificate_use {
+  name "Use of a registered certificate"
+  summary "The owner of a registered OIML certificate uses it and its associated OIML type evaluation report within the clause-4 discipline: the certificate bestows no legal international approval (4.1); the sanctioned uses are national/regional type-approval support with type-identity evidence on request (4.2 a), initial-verification support where type approval is not required (4.2 b), and buyer/user information (4.2 c); the complete evaluation report and test reports go to the Utilizer or Associate on request (4.3); the certificate is never proof of an individual instrument's conformity (4.4) and no OIML or OIML-CS logo is affixed to an instrument (4.4 — B 20); partial quotation is barred, full reproduction and the certificate number with the Issuing Authority's name excepted (4.5). National bodies should take the certificate into consideration (4.6) and Members are encouraged to recognize Scheme B certificates (4.7)."
+  validate_provision {
+    /req/cs/pd-06/no-legal-international-approval
+    /req/cs/pd-06/owner-uses
+    /req/cs/pd-06/report-provision-on-request
+    /req/cs/pd-06/certificate-not-instrument-proof
+    /req/cs/pd-06/no-logo-on-instruments
+    /req/cs/pd-06/no-partial-quotation
+    /req/cs/pd-06/national-consideration
+    /req/cs/pd-06/scheme-b-recognition
+  }
+  signature {
+    in { certificates }
+    out { certificates }
+  }
+  invariants {
+    "[certificate_use].claims_legal_international_approval = false"
+    "[certificate_use].claims_individual_instrument_conformity = false"
+    "[certificate_use].logo_affixed_to_instrument = false"
+    "[certificate_use].partial_quotation = false"
+    "[certificate_use].national_authority_request = true implies [certificate_use].complete_report_provided = true"
+  }
+  participant_kinds { certificate_owner utilizer associate }
+  evidence {
+    use_record { description "The owner's use of the certificate/report within the sanctioned uses (type-approval support, initial-verification support, buyer information), including the type-identity evidence given on request (4.2 a/b)." required true }
+    report_provision_record { description "The original or certified copy of the complete OIML type evaluation report and associated test reports provided to the Utilizer or Associate on the national authority's request (4.3)." }
+  }
+  executor actor
+  source { doc "PD-06, 4" clause "" }
+}
+
+process non_acceptance_justification {
+  name "Non-acceptance of test data"
+  summary "A Utilizer or Associate reviewing a received certificate and evaluation report first consults the Issuing Authority over any questions (4.8); if it then does not accept the test data, it sends WRITTEN JUSTIFICATION to the Issuing Authority, the manufacturer AND the Executive Secretary, and the Issuing Authority may appeal per PD-01. Non-acceptance of MTL-originated test results is voluntary and requires NO justification (4.9)."
+  validate_provision {
+    /req/cs/pd-06/non-acceptance-written-justification
+    /req/cs/pd-06/mtl-acceptance-voluntary
+  }
+  signature {
+    in { certificates }
+    out { acceptanceReviews }
+  }
+  invariants {
+    "[acceptance_review].consulted_ia = true"
+    "[acceptance_review].accepted = false and [acceptance_review].mtl_originated = false implies [acceptance_review].justification_addressees = ['issuing_authority', 'manufacturer', 'executive_secretary']"
+    "[acceptance_review].accepted = false and [acceptance_review].mtl_originated = true implies [acceptance_review].justification_addressees.count = 0"
+  }
+  organs { executive_secretary }
+  participant_kinds { utilizer associate issuing_authority }
+  evidence {
+    consultation_record { description "The Utilizer/Associate's consultation of the Issuing Authority over the questions raised during review (4.8)." required true }
+    written_justification { description "The written justification for the denial, addressed to the OIML Issuing Authority, the manufacturer AND the Executive Secretary (4.8) — not required for MTL-originated test data (4.9)." required true }
+  }
+  realized_by { evaluate_certificate_acceptance }
+  executor actor
+  source { doc "PD-06, 4.8/4.9" clause "" }
+}
+
+process misuse_handling {
+  name "Misuse of a certificate by its owner"
+  summary "On documented and substantiated evidence that the owner uses the certificate contrary to the clause-4 requirements, the Executive Secretary consults the CIML Member of the issuing Member State, informs the Management Committee, the other Member States, the Issuing Authority and interested parties, and warns the owner that continued misuse leads to corrective actions up to deregistration by the BIML (5.1)."
+  validate_provision {
+    /req/cs/pd-06/misuse-handling
+  }
+  signature {
+    in { certificates }
+    out { misuseCases }
+  }
+  invariants {
+    "[misuse_case].evidence is not null"
+    "[misuse_case].ciml_member_consulted = true"
+    "[misuse_case].owner_warned = true"
+  }
+  activity_kind { complaint }
+  organs { executive_secretary ciml management_committee }
+  participant_kinds { certificate_owner }
+  evidence {
+    misuse_evidence { description "The documented and substantiated evidence of use contrary to the clause-4 requirements (5.1)." required true }
+    owner_warning { description "The Executive Secretary's warning to the owner that continued misuse leads to corrective actions up to deregistration, with the CIML-Member consultation and the notifications (5.1)." required true }
+  }
+  realized_by { handle_misuse }
+  executor actor
+  source { doc "PD-06, 5.1" clause "" }
+}
+
+process misuse_deregistration {
+  name "Deregistration for misuse"
+  summary "The owner may appeal a deregistration proposal per PD-01 (5.2); if the appeal is not upheld, the BIML deregisters the certificate and the Executive Secretary notifies the owner, informs the Management Committee, the Member States, the Issuing Authority and interested parties, and publishes a notice in the OIML Bulletin and on the OIML website (5.3)."
+  validate_provision {
+    /req/cs/pd-06/misuse-deregistration
+  }
+  signature {
+    in { misuseCases certificates }
+    out { certificates }
+  }
+  invariants {
+    "[certificate].deregistered = true implies ([misuse_case].appeal_outcome = 'not_upheld' or [misuse_case].appeal_outcome is null)"
+    "[certificate].deregistered = true implies [deregistration].bulletin_notice_published = true"
+  }
+  activity_kind { withdrawal }
+  organs { biml executive_secretary }
+  participant_kinds { certificate_owner }
+  evidence {
+    deregistration_notice { description "The deregistration with the notifications (owner, MC, Member States, IA, interested parties) and the published notice in the OIML Bulletin and on the OIML website (5.3)." required true }
+  }
+  realized_by { deregister_certificate }
+  executor actor
+  source { doc "PD-06, 5.2/5.3" clause "" }
+}
+
+document_module pd-06 {
+  document "OIML-CS PD-06"
+  title "Use of OIML Type Evaluation Reports and OIML Certificates"
+  edition "4"
+  year 2024
+  namespace /req/cs/pd-06
+}

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

@@ -0,0 +1,122 @@
+# OIML-CS DOCUMENT MODULE PD-06 — NORMATIVE PROVISIONS (/req/cs/pd-06/*)
+# -----------------------------------------------------------------------------
+# OIML-CS PD-06 Edition 4 (approved 2024-03-06, 9th MC meeting; published
+# 2024-03-11) — the scheme's rules for using its outputs: an OIML
+# certificate bestows no rights beyond the documented uses; the acceptance
+# discipline (4.8/4.9); misuse handling and deregistration (5).
+#
+# NUMBERING: clause anchors VERIFIED against the official published PDF
+# (reference-docs/cs/docs/oiml-cs-pd-06-edition-4.pdf). NOTE — corpus C's
+# reconstruction numbers the non-acceptance clause 4.9 and the MTL clause
+# 4.10; the official PDF has the logo prohibition folded into 4.4, so the
+# official numbering is 4.8 (non-acceptance) and 4.9 (MTL) — this module
+# cites the official PDF (recorded for task 46). The regenerated local XML
+# (data/oiml-cs-pd-06/) is numbered official−1 (its build drops the
+# Introduction) and is never cited.
+#
+# This file is the single source of truth; the consumer's
+# data/oiml-cs/documents/pd-06/requirements.yaml is its GENERATED YAML twin
+# (cd browser && npm run gen:data).
+requirement_class /req/cs/pd-06 {
+  title "OIML-CS certificate and report use requirements"
+  name "Use of OIML Type Evaluation Reports and OIML Certificates (PD-06)"
+  description "Provisions of OIML-CS PD-06 Edition 4 governing the use of OIML certificates and OIML type evaluation reports by their owners and by accepting authorities, the acceptance/non-acceptance discipline, and the handling of certificate misuse up to deregistration. Enforced by the abstract processes of this module (abstract-processes.yaml)."
+  subject "OIML-CS outputs — use, acceptance and misuse"
+}
+
+requirement /req/cs/pd-06/no-legal-international-approval {
+  name "No legal international approval"
+  statement "An OIML certificate issued by an OIML Issuing Authority under Scheme A or B of the OIML-CS does not bestow any form of legal international approval (PD-06, 4.1)."
+  obligation shall
+  verification { method inspection description "The certificate-use discipline (abstract process certificate_use; its invariants)." }
+  source { doc "PD-06, 4.1" clause "" }
+}
+
+requirement /req/cs/pd-06/owner-uses {
+  name "Owner uses of a registered certificate"
+  statement "The owner may use a registered OIML certificate and its associated OIML type evaluation report (PD-06, 4.2): a) in support of an application for national or regional type approval — the applicant giving evidence on request that the type presented is identical to the certified one, and presenting the complete evaluation report with the certificate if the authority requests it; b) in support of the presentation of an individual instrument for initial verification in a country in which type approval is not required — with evidence on request that the instrument is of the certified type; c) to inform buyers, users and other interested parties that the type (represented by the tested samples) was found to conform to the relevant Recommendation — reference in catalogues and marketing literature permitted subject to 4.4 and 4.5."
+  obligation may
+  verification { method inspection description "The sanctioned-use register (abstract process certificate_use)." }
+  source { doc "PD-06, 4.2" clause "" }
+}
+
+requirement /req/cs/pd-06/report-provision-on-request {
+  name "Provision of the complete report on request"
+  statement "If requested by the regional or national issuing authority, the owner is responsible for providing the Utilizer or Associate with the original, or a certified copy of, the complete OIML type evaluation report and the associated test reports (PD-06, 4.3)."
+  obligation shall
+  verification { method inspection description "The on-request provision duty (abstract process certificate_use; its invariants)." }
+  source { doc "PD-06, 4.3" clause "" }
+}
+
+requirement /req/cs/pd-06/certificate-not-instrument-proof {
+  name "No proof of individual instrument conformity"
+  statement "An OIML certificate shall not be used as proof of conformity of an individual instrument with the requirements of the relevant Recommendation (PD-06, 4.4) — the certificate attests the TYPE, represented by the tested samples."
+  obligation shall
+  verification { method inspection description "The use discipline (abstract process certificate_use; its invariants)." }
+  source { doc "PD-06, 4.4" clause "" }
+}
+
+requirement /req/cs/pd-06/no-logo-on-instruments {
+  name "No OIML or OIML-CS logo on instruments"
+  statement "The OIML or OIML-CS logos shall not be affixed to an individual measuring instrument (PD-06, 4.4); the requirements regarding the use of the OIML and OIML-CS logos are specified in OIML B 20:2019 (delegated — the logo rules are B 20 content, never restated here)."
+  obligation shall
+  verification { method inspection description "The logo prohibition (abstract process certificate_use; its invariants)." }
+  source { doc "PD-06, 4.4" clause "" }
+}
+
+requirement /req/cs/pd-06/no-partial-quotation {
+  name "No partial quotation"
+  statement "Partial quotation of the OIML certificate or of the associated OIML type evaluation report is not permitted; they may be reproduced in full, and the OIML certificate number with the name of the OIML Issuing Authority that issued the certificate may be quoted (PD-06, 4.5)."
+  obligation shall
+  verification { method inspection description "The quotation discipline (abstract process certificate_use; its invariants)." }
+  source { doc "PD-06, 4.5" clause "" }
+}
+
+requirement /req/cs/pd-06/national-consideration {
+  name "Consideration by national bodies"
+  statement "The legal metrology service (or other responsible body) to which the application for national or regional type approval is made should take into consideration the OIML certificate and its associated OIML type evaluation report to the extent that is possible (PD-06, 4.6)."
+  obligation should
+  verification { method inspection description "The acceptance-encouragement discipline (abstract process certificate_use)." }
+  source { doc "PD-06, 4.6" clause "" }
+}
+
+requirement /req/cs/pd-06/scheme-b-recognition {
+  name "Recognition of Scheme B certificates"
+  statement "OIML Members are encouraged to adopt mechanisms to recognize and accept OIML certificates and their associated OIML type evaluation reports issued under Scheme B of the OIML-CS through appropriate measures (PD-06, 4.7)."
+  obligation should
+  verification { method inspection description "The Scheme-B recognition encouragement (abstract process certificate_use)." }
+  source { doc "PD-06, 4.7" clause "" }
+}
+
+requirement /req/cs/pd-06/non-acceptance-written-justification {
+  name "Non-acceptance requires written justification"
+  statement "When questions arise during the review of a received OIML certificate and OIML type evaluation report (including the test data), the Utilizer or Associate shall consult the relevant OIML Issuing Authority for clarification and take any further appropriate actions; in case the test data are not accepted, written justification for the denial shall be sent to the relevant OIML Issuing Authority, the manufacturer AND the Executive Secretary (PD-06, 4.8). The Issuing Authority may subsequently appeal the decision according to the PD-01 procedure (documents/pd-01/)."
+  obligation shall
+  verification { method inspection description "The non-acceptance discipline (abstract process non_acceptance_justification; its invariants)." }
+  source { doc "PD-06, 4.8" clause "" }
+}
+
+requirement /req/cs/pd-06/mtl-acceptance-voluntary {
+  name "MTL test data acceptance voluntary"
+  statement "OIML type evaluation reports that contain test results from a Manufacturer Test Laboratory (MTL) may be accepted by Utilizers and Associates on a voluntary basis; where MTL test results are not accepted, no justification or explanation is required (PD-06, 4.9). The Declaration-side record of this policy is the mtl_acceptance_policy content slot of framework/declarations.yaml (B 18:2025 §5.6.3) — referenced, never restated."
+  obligation may
+  verification { method inspection description "The MTL voluntary-acceptance rule (abstract process non_acceptance_justification; its invariants)." }
+  source { doc "PD-06, 4.9" clause "" }
+}
+
+requirement /req/cs/pd-06/misuse-handling {
+  name "Misuse handling — warning to corrective action"
+  statement "When documented and substantiated evidence is presented that an OIML certificate is being used by its owner in a manner contrary to the clause-4 requirements, the Executive Secretary shall consult the CIML Member of the Member State in which the certificate was issued; depending on the conclusions, the Executive Secretary shall inform the Management Committee, the other Member States, the OIML Issuing Authority and interested parties, and directly inform the owner that continued misuse will lead to corrective actions by the Management Committee that could result in deregistration of the certificate by the BIML (PD-06, 5.1)."
+  obligation shall
+  verification { method inspection description "The misuse track (abstract process misuse_handling)." }
+  source { doc "PD-06, 5.1" clause "" }
+}
+
+requirement /req/cs/pd-06/misuse-deregistration {
+  name "Deregistration for misuse with public notice"
+  statement "The owner of the OIML certificate may appeal a deregistration proposal according to the PD-01 procedure (PD-06, 5.2). If the appeal is not upheld and the certificate is to be deregistered, the Executive Secretary shall notify the owner, inform the Management Committee, the Member States, the OIML Issuing Authority and any other interested parties, and publish a notice in appropriate publications including the OIML Bulletin and the OIML website (PD-06, 5.3). The register act itself is the BIML's (framework/governance.yaml biml-certificate-registration)."
+  obligation shall
+  verification { method inspection description "The deregistration consequence (abstract process misuse_deregistration; its invariants)." }
+  source { doc "PD-06, 5.2/5.3" clause "" }
+}
+

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

@@ -0,0 +1,99 @@
+# OIML-CS DOCUMENT MODULE PD-07 — ABSTRACT PROCESSES
+# -----------------------------------------------------------------------------
+# The PD-07 Edition 4 transition discipline as ABSTRACT processes
+# (TODO.roadmap/43):
+#
+#   legacy_certificate_maintenance   (clause 4 — legacy validity, Annex
+#                                     limits, original-issuer routing)
+#   previous_test_data_acceptance    (5/6/7 — the IA's acceptability
+#                                     judgment over previous test data,
+#                                     with the documented-appraisal route)
+#
+# There is no linear chain — both are gates the IA applies within the
+# PD-05 certification processes (which stay the scheme process model's —
+# evaluation/abstract-processes.prl; PD-07 defers to PD-05 clauses 4/5).
+# The Review Committee's advice on previous test data is OD-01, 5.2
+# (documents/od-01/) — referenced, never restated; the per-category
+# Scheme B→A lifecycle machine is the task-40 framework's
+# (framework/schemes.prl), the consumer's linker rule R26 resolving every
+# reference.
+#
+# TODO.roadmap/45: previous_test_data_acceptance is REALIZED (the IA's
+# review step — the previous-reports acceptance judgment is recorded on
+# the Application); legacy_certificate_maintenance stays unrealized (a
+# named gap in the unified coverage report — no legacy MAA/Basic import
+# exists on the platform).
+#
+# This file is the single source of truth; the consumer's
+# data/oiml-cs/documents/pd-07/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 legacy_certificate_maintenance {
+  name "Legacy certificate status and Annexes"
+  summary "OIML Basic and MAA certificates remain valid (B 18, 15.10/15.11); since 2018-01-01 no new legacy certificates and no revisions — only an \"Annex\" by the original Issuing Authority/Participant to correct an error or transfer ownership, never to change technical or metrological characteristics (those require a new OIML certificate). Applications based on legacy certificates route to the ORIGINAL issuer, with the two stated exceptions (the original issuer is not an OIML Issuing Authority for the category, or cannot fulfil the process — the latter needing written permission from the original Issuing Authority or the Executive Secretary) (4.5)."
+  validate_provision {
+    /req/cs/pd-07/legacy-certificates-valid
+    /req/cs/pd-07/legacy-annex-limits
+    /req/cs/pd-07/original-issuer-application
+  }
+  signature {
+    out { legacyCertificates }
+  }
+  invariants {
+    "[annex].kind = 'error_correction' or [annex].kind = 'ownership_transfer'"
+    "[annex].changes_technical_characteristics = false"
+    "[application].routed_to_original_issuer = false implies [application].routing_exception is not null"
+  }
+  organs { executive_secretary }
+  participant_kinds { issuing_authority applicant }
+  evidence {
+    legacy_certificate { description "The existing OIML Basic or MAA certificate with its type evaluation report and previous test data (3.1)." required true }
+    annex_record { description "Where issued, the Annex — error correction or ownership transfer only, bearing the applicable logo and a unique number." }
+    routing_evidence { description "The application routing to the original issuer, or the exception evidence (other-IA eligibility for the category, or the written permission of the original Issuing Authority / Executive Secretary) (4.5)." required true }
+  }
+  executor actor
+  source { doc "PD-07, 4" clause "" }
+}
+
+process previous_test_data_acceptance {
+  name "Previous test data acceptance"
+  summary "The OIML Issuing Authority's acceptability judgment over previous test data (3.1) grounding an OIML certificate: the Scheme-B route (5.2/5.3 — facility satisfying ISO/IEC 17025 at the time by self-declaration, peer assessment or accreditation, representative sample, equivalent testing; documented appraisal where the facility did not qualify), the MAA→A route (6.1.2 — representative and equivalent; PD-05 clause 5 applies), the Basic→A route (6.2 — the certificate itself not directly usable; facility accreditation/peer assessment at the time or the documented appraisal of 6.2.3: facility/methodology against ISO/IEC 17025, data review, statement of continued acceptability, recorded in the evaluation report), and the Scheme B→A route after a category transition (7.1/7.2 — no new Scheme B certificates except original-IA revisions; the 7.2.1 conditions with the 7.2.2 appraisal). Review Committee advice is available (OD-01, 5.2). Every route identifies ALL test facilities and ALL reports/data used in the evaluation report, and reuses legacy data of a revised Recommendation edition only for unchanged requirements/tests — new or changed testing goes to a Test Laboratory listed in an Issuing Authority's Declaration."
+  validate_provision {
+    /req/cs/pd-07/previous-test-data-scheme-b
+    /req/cs/pd-07/previous-test-data-maa-scheme-a
+    /req/cs/pd-07/previous-test-data-basic-scheme-a
+    /req/cs/pd-07/scheme-b-to-a-transition
+  }
+  signature {
+    in { legacyCertificates }
+    out { previousTestDataAppraisals }
+  }
+  invariants {
+    "[acceptance].facility_qualified_at_time = false implies [acceptance].documented_appraisal is not null"
+    "[acceptance].sample_representative = true"
+    "[acceptance].testing_equivalent_to_edition = true"
+    "[acceptance].recommendation_edition_revised = true implies [acceptance].new_or_changed_tests_by_listed_tl = true"
+    "[evaluation_report].identifies_all_facilities_and_data = true"
+  }
+  activity_kind { review }
+  organs { review_committee }
+  participant_kinds { issuing_authority }
+  evidence {
+    acceptability_judgment { description "The Issuing Authority's documented judgment that the previous testing satisfies the applicable route's conditions (facility qualification at the time, representative sample, equivalence to the certified edition)." required true }
+    documented_appraisal { description "Where the facility did not qualify at the time: the documented appraisal — facility/methodology against ISO/IEC 17025, data review, statement of continued acceptability — recorded in the OIML type evaluation report (5.3/6.2.3/7.2.2)." }
+    data_identification { description "The evaluation report's identification of all test facilities and all reports/data used, with relevant explanations." required true }
+  }
+  realized_by { review_application }
+  executor actor
+  source { doc "PD-07, 5/6/7" clause "" }
+}
+
+document_module pd-07 {
+  document "OIML-CS PD-07"
+  title "Transition Arrangements under the OIML-CS"
+  edition "4"
+  year 2024
+  namespace /req/cs/pd-07
+}

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

@@ -0,0 +1,84 @@
+# OIML-CS DOCUMENT MODULE PD-07 — NORMATIVE PROVISIONS (/req/cs/pd-07/*)
+# -----------------------------------------------------------------------------
+# OIML-CS PD-07 Edition 4 (approved 2024-01-15; published 2024-01-16) —
+# the bridge from the legacy OIML Basic Certificate System and the OIML
+# MAA to the OIML-CS: legacy certificates remain valid; previous test data
+# is reusable under stated conditions.
+#
+# NUMBERING: clause anchors VERIFIED against the official published PDF
+# (reference-docs/cs/docs/oiml-cs-pd-07-edition-4.pdf, retrieved
+# 2026-07-24; task 46). Corpus C's reconstruction is CONFIRMED in full:
+# 4 (4.1–4.6 — 4.5 applications to the original IA), 5 Scheme B (5.1–5.9;
+# 5.2 conditions, 5.3 the documented-appraisal route, 5.4 "deemed to
+# fulfil PD-05, 4.3"), 6 Scheme A (6.1 MAA — 6.1.3 "deemed to fulfil
+# PD-05, 5.3"; 6.2 Basic — 6.2.2–6.2.9), 7 transition (7.1/7.2 — 7.2.3
+# "deemed to fulfil PD-05, 5.3.3"). The local presentation XML
+# (data/oiml-cs-pd-07/) is a defective build (0.x renumbering) and is
+# cited for TEXT only, never for numbering.
+#
+# This file is the single source of truth; the consumer's
+# data/oiml-cs/documents/pd-07/requirements.yaml is its GENERATED YAML twin
+# (cd browser && npm run gen:data).
+requirement_class /req/cs/pd-07 {
+  title "OIML-CS transition requirements"
+  name "Transition Arrangements under the OIML-CS (PD-07)"
+  description "Provisions of OIML-CS PD-07 Edition 4 governing the status and use of legacy OIML Basic and MAA certificates, the reuse of previous test data for OIML certificates under Scheme A or B, and the Scheme B → Scheme A transition of an instrument category. Enforced by the abstract processes of this module (abstract-processes.yaml)."
+  subject "OIML-CS legacy certificates and previous test data"
+}
+
+requirement /req/cs/pd-07/legacy-certificates-valid {
+  name "Legacy certificates remain valid"
+  statement "OIML Basic and OIML MAA certificates issued under the OIML Basic Certificate System and the OIML MAA are considered to remain valid (PD-07, 4; OIML B 18, 15.10/15.11 — the framework's legacy-certificate-validity rule). Utilizers and Associates may specify their acceptance of OIML MAA certificates and/or MAA type evaluation reports, with any associated conditions, in their Declarations (per PD-08); acceptance of OIML Basic certificates is voluntary and is not specified in the Declaration."
+  obligation shall
+  verification { method inspection description "The legacy-acceptance discipline (abstract process legacy_certificate_maintenance)." }
+  source { doc "PD-07, 4" clause "" }
+}
+
+requirement /req/cs/pd-07/legacy-annex-limits {
+  name "No new or revised legacy certificates — Annex limits"
+  statement "Since 2018-01-01 no new OIML Basic or MAA certificates may be issued and revisions to existing ones are no longer permitted; an \"Annex\" may be issued by the original Issuing Authority (Basic system) or original Issuing Participant (MAA) only a) to correct an error by the applicant or the Issuing Authority/Participant, or b) when ownership transfers to a new applicant — never to change the technical or metrological characteristics, which require a new OIML certificate under Scheme A or B (PD-07, 4). The Annex bears the applicable logo and a unique number."
+  obligation shall
+  verification { method inspection description "The Annex limits (abstract process legacy_certificate_maintenance; its invariants)." }
+  source { doc "PD-07, 4" clause "" }
+}
+
+requirement /req/cs/pd-07/original-issuer-application {
+  name "Applications route to the original issuer"
+  statement "An application for OIML certification based on an existing MAA or Basic certificate, its type evaluation report and previous test data shall be made to the ORIGINAL OIML Issuing Authority (the former MAA Issuing Participant or Basic Issuing Authority), except a) where the original issuer is not an OIML Issuing Authority for that category — the application may go to another Issuing Authority for the category; b) where the original Issuing Authority cannot fulfil the required certification process — a new application may go to another Issuing Authority with written permission from the original Issuing Authority or the Executive Secretary (PD-07, 4.5)."
+  obligation shall
+  verification { method inspection description "The application-routing rule (abstract process legacy_certificate_maintenance; its invariants)." }
+  source { doc "PD-07, 4.5" clause "" }
+}
+
+requirement /req/cs/pd-07/previous-test-data-scheme-b {
+  name "Previous test data under Scheme B"
+  statement "Where previous test data is used to issue a Scheme B OIML certificate and type evaluation report, the OIML Issuing Authority shall ensure (PD-07, 5.2): a) at the time of the original testing the test facility satisfied ISO/IEC 17025 — by self-declaration, peer assessment or accreditation with a scope covering the relevant Recommendation (accreditation body an ILAC MRA or recognized regional signatory for \"Testing ISO/IEC 17025\"; the peer team from the Joint OIML/ILAC/IAF list); b) the sample was representative of the current type; c) the testing is equivalent to the requirements of the Recommendation edition being certified. Where the facility did not satisfy a) at the time, the Issuing Authority shall include a documented appraisal of the testing — explaining why the data is acceptable under the OIML-CS — with b) and c) still applying (PD-07, 5.3). The PD-05 clause-4 procedures apply (data satisfying 5.2 is deemed to fulfil PD-05, 4.3); the evaluation report shall identify all test facilities and all reports/data used; Scheme B certificates issue only for Recommendation editions currently in the OIML-CS, unchanged tests of a revised edition may be reused, and all new or changed testing is conducted by a Test Laboratory listed in an Issuing Authority's Declaration."
+  obligation shall
+  verification { method inspection description "The Scheme-B legacy-data gate (abstract process previous_test_data_acceptance; its invariants)." }
+  source { doc "PD-07, 5.2/5.3" clause "" }
+}
+
+requirement /req/cs/pd-07/previous-test-data-maa-scheme-a {
+  name "Previous test data from the MAA under Scheme A"
+  statement "An applicant may use an existing OIML MAA certificate, its MAA type evaluation report and previous test data to issue a Scheme A OIML certificate and type evaluation report (PD-07, 6.1, with 4.5 applying). The Issuing Authority shall ensure (6.1.2): a) the testing was performed on a sample representative of the current type; b) the testing is equivalent to the requirements of the Recommendation edition being certified. The PD-05 clause-5 procedures apply (satisfying data is deemed to fulfil PD-05, 5.3); the evaluation report shall identify all test facilities and all reports/data used with relevant explanations; Scheme A certificates issue only for Recommendation editions currently in the OIML-CS; for a revised edition, unchanged requirements/tests may be supported by the MAA report while all new or changed testing is conducted by an approved Test Laboratory listed in an Issuing Authority's Declaration."
+  obligation shall
+  verification { method inspection description "The MAA→A legacy-data gate (abstract process previous_test_data_acceptance; its invariants)." }
+  source { doc "PD-07, 6.1" clause "" }
+}
+
+requirement /req/cs/pd-07/previous-test-data-basic-scheme-a {
+  name "Previous test data from a Basic certificate under Scheme A"
+  statement "An existing OIML Basic certificate and its type evaluation report cannot be used DIRECTLY to issue a Scheme A certificate, but their associated previous test data may be used under the conditions of 6.2.2–6.2.9 (PD-07, 6.2): at the time of the original testing the test facility was accredited or peer assessed to ISO/IEC 17025 with a scope covering the relevant Recommendation (the accreditation body an ILAC MRA or recognized regional signatory; the peer team comprising a lead assessor and technical/metrological experts from the Joint OIML/ILAC/IAF or MAA expert lists), the sample was representative of the current type, and the testing is equivalent to the certified edition (6.2.2). Where the facility did not so qualify, the Issuing Authority shall include a DOCUMENTED APPRAISAL of the previous testing (6.2.3): an assessment of the facility and methodology against ISO/IEC 17025 (traceability and calibration of reference standards, documented procedures and test methods, uncertainty estimation, staff competency and training, history of similar testing), a review of the data and its acceptability at the time, and a statement that the data continues to be acceptable under the OIML-CS — recording the use of the data in the evaluation report. The PD-05 clause-5 procedures apply with the same facility/data identification and revised-edition rules; Scheme A reports shall clearly specify whether they rest on Basic previous test data, and their acceptance by Utilizers and Associates is voluntary (declared per PD-08)."
+  obligation shall
+  verification { method inspection description "The Basic→A legacy-data gate with the documented appraisal (abstract process previous_test_data_acceptance; its invariants)." }
+  source { doc "PD-07, 6.2" clause "" }
+}
+
+requirement /req/cs/pd-07/scheme-b-to-a-transition {
+  name "Scheme B to Scheme A transition"
+  statement "When a category and its Recommendation transition from Scheme B to Scheme A (the framework/schemes.yaml lifecycle), no new Scheme B certificates may be issued for that category — except the revision of an existing Scheme B certificate by the original OIML Issuing Authority on the same Recommendation edition (PD-07, 7.1, with 4.5 applying). An existing Scheme B certificate may ground a Scheme A certificate when (7.2.1): a) the testing Test Laboratory is listed in an Issuing Authority's Declaration for the category; b) it was accredited/peer assessed to ISO/IEC 17025 with the relevant scope at the time; c) the sample was representative; d) the testing is equivalent — with the documented-appraisal route of 7.2.2 where a)/b) were not met, the PD-05 clause-5 procedures applying (the Scheme B type evaluation report deemed to fulfil PD-05, 5.3.3), the same facility/data identification and revised-edition rules as 6.x."
+  obligation shall
+  verification { method inspection description "The B→A transition gates (abstract process previous_test_data_acceptance; its invariants)." }
+  source { doc "PD-07, 7.1/7.2" clause "" }
+}
+