@oimlsmart/primmel-packages 0.4.0 → 0.6.0

package/oiml-cs/framework/documents/cid-01/abstract-processes.prl

@@ -0,0 +1,112 @@
+# OIML-CS DOCUMENT MODULE CID-01 — ABSTRACT PROCESSES
+# -----------------------------------------------------------------------------
+# The CID-01 Edition 6 clarifications pinned as INVARIANT-CARRYING
+# abstract processes (TODO.roadmap/43):
+#
+#   test_report_issuance        — the TL issues the OIML test report
+#   evaluation_report_issuance  — the IA issues the OIML type evaluation
+#                                 report
+#   ia_scope_support            — the IA's scope is TL-supported at all
+#                                 times and it issues only within it
+#
+# These processes have no workflow of their own (no sequence): each pins a
+# cross-cutting IDENTITY rule the Edition-6 clarifications state, binding
+# it as invariants over the scheme's issuance records — the rules
+# themselves stay owned by the clarified documents (B 18 3.40 Note 3 /
+# PD-03 5.1 / PD-05 4.3 & 5.3; MECE — see the requirements.prl header).
+# The cross-corpus consistency proof (the PD-05 process model's testing
+# step is TL-executed, its evaluation/issue steps IA-executed) lives in
+# the consumer's cs-scheme-governance tests.
+#
+# TODO.roadmap/45 REALIZED the pins: realized_by binds the concrete Core
+# processes whose execution makes each identity rule hold by construction
+# (compile_test_report / compile_evaluation_report — the TL issues the
+# test report, the IA the evaluation report; issue_certificate +
+# record_participant_declaration — the signing gate checks the IA's
+# Declaration scope at every issuance).
+#
+# This file is the single source of truth; the consumer's
+# data/oiml-cs/documents/cid-01/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 test_report_issuance {
+  name "OIML test report issuance"
+  summary "An OIML test report is issued by an OIML Test Laboratory — regardless of whether the Recommendation carries the test report format as a separate Part (B 6-1:2023 ≥ four-part layout) or combined with the type evaluation report format (the old three-part layout). The scheme process model realizes this as the TL-executed testing step (evaluation/abstract-processes.yaml testing — roles [test_laboratory], out: [testReports])."
+  validate_provision {
+    /req/cs/cid-01/test-report-issued-by-tl
+  }
+  signature {
+    out { testReports }
+  }
+  invariants {
+    "[test_report].issued_by_kind = 'test_laboratory'"
+    "[test_report].recommendation_part_layout = 'combined' implies [test_report].issued_by_kind = 'test_laboratory'"
+  }
+  activity_kind { attestation }
+  participant_kinds { test_laboratory }
+  evidence {
+    issued_test_report { description "The issued OIML test report, identifying the issuing Test Laboratory." required true }
+  }
+  realized_by { compile_test_report }
+  executor actor
+  source { doc "CID-01, 3.1 (B 18, 4.2)" clause "" }
+}
+
+process evaluation_report_issuance {
+  name "OIML type evaluation report issuance"
+  summary "An OIML type evaluation report is issued by an OIML Issuing Authority — never by a Test Laboratory (B 18:2025 3.40 Note 3) — regardless of the Recommendation's part structure. The scheme process model realizes this as the IA-executed evaluation step (evaluation/abstract-processes.yaml evaluation — roles [issuing_authority], out: [evaluationReports])."
+  validate_provision {
+    /req/cs/cid-01/evaluation-report-issued-by-ia
+  }
+  signature {
+    in { testReports }
+    out { evaluationReports }
+  }
+  invariants {
+    "[evaluation_report].issued_by_kind = 'issuing_authority'"
+    "[evaluation_report].issued_by_kind = 'test_laboratory' implies false"
+  }
+  activity_kind { attestation }
+  participant_kinds { issuing_authority }
+  evidence {
+    issued_evaluation_report { description "The issued OIML type evaluation report, identifying the issuing OIML Issuing Authority." required true }
+  }
+  realized_by { compile_evaluation_report }
+  executor actor
+  source { doc "CID-01, 3.1 (B 18, 4.2)" clause "" }
+}
+
+process ia_scope_support {
+  name "IA scope support and issuance discipline"
+  summary "At all times the OIML Issuing Authority's scope is supported by an approved Test Laboratory listed in its Declaration for each category in the scope — an application needs an existing or accompanying TL application; an unsupported scope is amended. The IA issues certificates and evaluation reports only within that scope, using test data of a TL in its own Declaration or of a (non-MTL) TL in another IA's Declaration."
+  validate_provision {
+    /req/cs/cid-01/ia-scope-tl-supported
+    /req/cs/cid-01/ia-issuance-within-scope
+  }
+  signature {
+    in { declarations }
+    out { evaluationReports }
+  }
+  invariants {
+    "[issuing_authority].scope.count >= 1 implies [issuing_authority].declaration.tl_ids.count >= 1"
+    "[certificate].category is not null implies [declaration].supports_category([certificate].category) = true"
+    "[test_data].tl_declaration_ia <> [issuing_authority].id implies [test_data].tl_kind <> 'manufacturer'"
+  }
+  participant_kinds { issuing_authority test_laboratory }
+  evidence {
+    scope_support_record { description "The Declaration listing the approved Test Laboratory(ies) supporting each category of the Issuing Authority's scope." required true }
+  }
+  realized_by { issue_certificate record_participant_declaration }
+  executor actor
+  source { doc "CID-01, 3.3 (PD-03, 5.1; PD-05, 4.3/5.3)" clause "" }
+}
+
+document_module cid-01 {
+  document "OIML-CS CID-01"
+  title "Clarifications and Interpretations of OIML-CS Documents"
+  edition "6"
+  year 2024
+  namespace /req/cs/cid-01
+}

package/oiml-cs/framework/documents/cid-01/requirements.prl

@@ -0,0 +1,99 @@
+# OIML-CS DOCUMENT MODULE CID-01 — NORMATIVE PROVISIONS (/req/cs/cid-01/*)
+# -----------------------------------------------------------------------------
+# OIML-CS CID-01 Edition 6 (approved 2024-09-19, MC online vote) — the
+# single point of reference for MC-agreed clarifications of B 18:2022,
+# OD-01/02 and PD-01…PD-08, prepared by the Executive Secretary and
+# approved by the MC (the Maintenance Group develops them; rank 2 of the
+# governing-document hierarchy — framework/documents.prl).
+#
+# NATURE (clause 2.2, verbatim-faithful): the clarifications "are
+# intended as guidance and additional information and do not supersede
+# the text in the current edition of the relevant OIML-CS document" —
+# they are folded into future editions. The provisions below therefore
+# PIN the clarified RULES (each of which restates an already-normative
+# rule of the clarified document); the non-superseding nature itself is
+# the statement-level provision clarifications-non-superseding.
+#
+# Edition-6 content (three entries; Table 4 — OD-01/OD-02 — is empty):
+# 3.1 B 18, 4.2 — an OIML TEST REPORT IS ISSUED BY AN OIML TEST
+# LABORATORY and an OIML TYPE EVALUATION REPORT IS ISSUED BY AN OIML
+# ISSUING AUTHORITY, regardless of the Recommendation's structure;
+# 3.3 PD-03/PD-04 5.2.2 & 5.2.3.5 — the COVID contingencies were REVOKED
+# as of 2024-01-15; 3.3 PD-03, 5.1 and PD-05, 4.3 & 5.3 — an IA's scope
+# must be TL-supported at all times (its own Declaration's TL or another
+# IA's, never an MTL of another Declaration); an unsupported scope is
+# amended.
+#
+# MECE: the issuance-identity rules restate B 18:2025 3.40 Note 3 (the
+# framework participants.prl test_laboratory definition carries it) and
+# the PD-05 process discipline (the scheme process model's testing step
+# is TL-executed, evaluation/issue IA-executed — evaluation/
+# abstract-processes.prl); this module PINS them as machine-checkable
+# invariants (abstract-processes.prl), never re-owning the content. The
+# TL-support rule is the PD-03 ≥ 1-TL precondition's in-operation twin
+# (/req/cs/pd-03/tl-application-precondition — referenced, not restated).
+#
+# NUMBERING: VERIFIED against the official published PDF
+# (reference-docs/cs/docs/oiml-cs-clarifications-interpretations-cid-01-
+# edition6.pdf — 3.1 B 18 table, 3.2 empty OD table, 3.3 PD table). The
+# regenerated local XML (data/oiml-cs-cid-01/) 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/cid-01/requirements.yaml is its GENERATED YAML twin
+# (cd browser && npm run gen:data).
+requirement_class /req/cs/cid-01 {
+  title "OIML-CS clarification provisions"
+  name "Clarifications and Interpretations of OIML-CS Documents (CID-01)"
+  description "The Edition-6 clarifications of OIML-CS CID-01 pinned as provisions. Per CID-01 clause 2.2 the clarifications are guidance and additional information that do not supersede the current editions' text; each provision below restates a rule that is already normative in the clarified document (B 18 / PD-03 / PD-04 / PD-05). Enforced by the invariant-pinning abstract processes of this module (abstract-processes.yaml)."
+  subject "OIML-CS agreed clarifications — issuance identity, TL support, revoked contingencies"
+}
+
+requirement /req/cs/cid-01/test-report-issued-by-tl {
+  name "Test report issued by a Test Laboratory"
+  statement "Regardless of the structure of an OIML Recommendation (the old three-part layout with the combined test-report and evaluation- report Part, or the B 6-1:2023 ≥ four-part layout with the two report formats as separate Parts), an OIML test report is issued by an OIML Test Laboratory (CID-01, 3.1 clarifying B 18, 4.2; MC Meeting 8, Action Item 8.8)."
+  obligation shall
+  verification { method inspection description "The issuance-identity invariant (abstract process test_report_issuance)." }
+  source { doc "CID-01, 3.1 (B 18, 4.2)" clause "" }
+}
+
+requirement /req/cs/cid-01/evaluation-report-issued-by-ia {
+  name "Evaluation report issued by an Issuing Authority"
+  statement "Regardless of the structure of an OIML Recommendation, an OIML type evaluation report is issued by an OIML Issuing Authority — never by a Test Laboratory (CID-01, 3.1 clarifying B 18, 4.2; B 18:2025 3.40 Note 3)."
+  obligation shall
+  verification { method inspection description "The issuance-identity invariant (abstract process evaluation_report_issuance)." }
+  source { doc "CID-01, 3.1 (B 18, 4.2)" clause "" }
+}
+
+requirement /req/cs/cid-01/covid-contingencies-revoked {
+  name "COVID assessment contingencies revoked"
+  statement "The COVID contingencies agreed at the Fourth MC Meeting (June 2020) — the use of accreditation-body experts in place of Legal Metrology Experts, and remote assessments of OIML Issuing Authorities and Test Laboratories — were revoked as of 2024-01-15; all assessment activities are conducted in accordance with the rules and requirements of the relevant accreditation body and the OIML-CS, PD-03/PD-04 having been amended to retain flexibility for future international travel restrictions (CID-01, 3.3)."
+  obligation statement
+  verification { method deferred description "Verified by assessment of the scheme corpus (the revocation is an MC decision of 2024-01-15; the amended PD-03/PD-04 rules are the task-42 modules')." }
+  source { doc "CID-01, 3.3 (PD-03 5.2.2/5.2.3.5; PD-04 5.2.2/5.2.3.5)" clause "" }
+}
+
+requirement /req/cs/cid-01/ia-scope-tl-supported {
+  name "IA scope supported by a Test Laboratory at all times"
+  statement "At all times, the scope of an OIML Issuing Authority must be supported by an approved Test Laboratory — listed in the Issuing Authority's Declaration — for each category of measuring instrument included within that scope; every Issuing Authority application must therefore be supported by an existing Test Laboratory or an accompanying Test Laboratory application (internal, third-party or Manufacturer Test Laboratory); if at any time the scope is not so supported for a category, the scope must be amended accordingly (CID-01, 3.3 clarifying PD-03, 5.1 — the in-operation twin of the application-time precondition /req/cs/pd-03/tl-application- precondition)."
+  obligation shall
+  verification { method inspection description "The TL-support invariant (abstract process ia_scope_support)." }
+  source { doc "CID-01, 3.3 (PD-03, 5.1)" clause "" }
+}
+
+requirement /req/cs/cid-01/ia-issuance-within-scope {
+  name "IA issues within its TL-supported scope"
+  statement "An OIML Issuing Authority is only permitted to issue OIML certificates and OIML type evaluation reports in accordance with its scope; it may use test data from a Test Laboratory listed in its own Declaration, or from a Test Laboratory (other than a Manufacturer Test Laboratory) listed in the Declaration of another OIML Issuing Authority; in either case its scope must be supported by an approved Test Laboratory listed in its own Declaration for each category within the scope (CID-01, 3.3 clarifying PD-05, 4.3 & 5.3)."
+  obligation shall
+  verification { method inspection description "The issuance-scope invariant (abstract process ia_scope_support)." }
+  source { doc "CID-01, 3.3 (PD-05, 4.3/5.3)" clause "" }
+}
+
+requirement /req/cs/cid-01/clarifications-non-superseding {
+  name "Clarifications do not supersede"
+  statement "The clarifications and interpretations of CID-01 are intended as guidance and additional information and do not supersede the text in the current edition of the relevant OIML-CS document; they may be incorporated into future editions (CID-01, 2.2 — the document's rank in the governing-document hierarchy is framework/documents.yaml, rank 2)."
+  obligation statement
+  verification { method deferred description "Verified by assessment of the scheme corpus (the nature of the CID-01 document itself — framework/documents.yaml, rank 2)." }
+  source { doc "CID-01, 2.2" clause "" }
+}
+

package/oiml-cs/framework/documents/od-01/abstract-processes.prl

@@ -0,0 +1,157 @@
+# OIML-CS DOCUMENT MODULE OD-01 — ABSTRACT PROCESSES
+# -----------------------------------------------------------------------------
+# The OD-01 Edition 4 operational disciplines as ABSTRACT processes
+# (TODO.roadmap/43):
+#
+#   rc_recommendation_governance   (5.6/5.7 + 7.3 — the RC's segregation,
+#                                   confidentiality and two-thirds validity)
+#   mc_annual_reporting            (8.1/8.2 — the annual report to the CIML
+#                                   with the a–k content census)
+#   scheme_monitoring              (12.1/12.2 — the measurement mechanisms
+#                                   feeding the report)
+#   expert_list_maintenance        (13.2/13.4 — the competence criteria and
+#                                   the 3-yearly list review)
+#
+# There is no linear chain — these are the standing governance disciplines
+# of the MC/RC, not a pipeline. The organs and the MC's voting thresholds
+# REFERENCE the task-40 framework model (framework/participants.prl;
+# framework/governance.prl ia-tl-participation-decisions, which OD-01 7.8
+# applies) — never restate it; the consumer's linker rule R26 resolves
+# every reference. The expert competence criteria (13.2.1/13.2.2) are the
+# delegation TARGET of the PD-02 pipeline (documents/pd-02/ — the expert
+# registers are PD-02's lme_register/mse_register, maintained under the
+# discipline this module pins).
+#
+# TODO.roadmap/44–45 REALIZED the pipeline where the platform executes it
+# (the participant-approval set; see the pd-03 header); the standing
+# reporting/monitoring disciplines stay documentary 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/od-01/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 rc_recommendation_governance {
+  name "RC recommendation discipline"
+  summary "The Review Committee recommends to the Management Committee — through the Executive Secretary — on IA/TL approval or rejection incl. scope changes, on periodic review, and on expert approval or rejection (5.6), with the segregation rule: no member contributes to a recommendation concerning an IA/TL they assessed (peer or accreditation assessment); own-country contribution subject to 5.6.3. Confidentiality: members sign the BIML NDA; application documents are destroyed after the recommendation (5.7); accreditation and peer assessment reports are never made public (7.3). Validity: no formal voting — a recommendation is valid at TWO-THIRDS of the opinions in favour; a lower level is reported to the MC as the actual consensus (7.9)."
+  validate_provision {
+    /req/cs/od-01/rc-recommendations
+    /req/cs/od-01/rc-confidentiality
+    /req/cs/od-01/assessment-reports-confidential
+    /req/cs/od-01/rc-recommendation-validity
+  }
+  signature {
+    out { recommendations }
+  }
+  invariants {
+    "[recommendation].consensus_level is not null"
+    "[recommendation].valid = ([recommendation].opinions_in_favour_ratio >= 0.667)"
+    "[recommendation].valid = false implies [recommendation].reported_consensus = [recommendation].opinions_in_favour_ratio"
+    "[rc_member].assessed_subject = true implies [rc_member].contributed = false"
+  }
+  activity_kind { review }
+  organs { review_committee executive_secretary }
+  evidence {
+    recommendation_report { description "The RC's recommendation report to the MC with the level of consensus reached (7.9)." required true }
+    confidentiality_records { description "The members' BIML non-disclosure agreements and the destruction of the application documents after the recommendation (5.7)." required true }
+  }
+  realized_by { recommend_participation }
+  segregation {
+    constraint rc_assessor_bar_ia {
+      kind case_personnel_disjoint
+      clause "OD-01, 5.6"
+      pair { rc_recommendation_governance ia_assessment }
+      statement "Members of the Review Committee shall not contribute (by comment or opinion) to recommendations concerning a potential or existing OIML Issuing Authority or Test Laboratory where they participated in the peer assessment or accreditation assessment of that Issuing Authority or Test Laboratory (OD-01, 5.6) — the RC's personnel for the recommendation are disjoint from the IA assessment's personnel (documents/pd-03/ ia_assessment)."
+    }
+    constraint rc_assessor_bar_tl {
+      kind case_personnel_disjoint
+      clause "OD-01, 5.6"
+      pair { rc_recommendation_governance tl_assessment }
+      statement "The same bar against the Test Laboratory assessment's personnel (documents/pd-04/ tl_assessment — OD-01, 5.6)."
+    }
+  }
+  executor actor
+  source { doc "OD-01, 5.6/5.7, 7.3, 7.9" clause "" }
+}
+
+process mc_annual_reporting {
+  name "Annual report to the CIML"
+  summary "The Management Committee reports annually to the CIML — prepared by the Executive Secretary, presented by the Chairperson at the CIML's annual meeting, reviewed by the MC before submission (8.1) — on its activities and on the monitoring of the operation and effectiveness of the OIML-CS, with the 8.2 content census a)–k): MC/WG activities incl. document changes; categories and their Scheme; the system's functioning (certificates issued; certificates/reports not accepted, with reasons); IA/TL appointments, rejections, suspensions; IA and Utilizer counts with scopes; continuing compliance; expert appointments; the appeals summary (privacy-preserving); promotional activities; finances; the outlook."
+  validate_provision {
+    /req/cs/od-01/annual-report
+    /req/cs/od-01/mc-composition-appointment
+    /req/cs/od-01/member-voting-obligation
+    /req/cs/od-01/mc-voting-rules
+  }
+  signature {
+    out { annualReports }
+  }
+  invariants {
+    "[annual_report].content_sections.count >= 11"
+    "[annual_report].mc_reviewed = true"
+    "[annual_report].presented_to_ciml = true"
+  }
+  organs { management_committee executive_secretary ciml }
+  evidence {
+    annual_report { description "The annual report in the website template, covering the 8.2 a–k content, with the MC's review record and the CIML presentation." required true }
+  }
+  executor actor
+  source { doc "OD-01, 8.1/8.2" clause "" }
+}
+
+process scheme_monitoring {
+  name "Monitoring of operation and effectiveness"
+  summary "The Management Committee establishes mechanisms for measuring key activities and outcomes (the measurable activities are the 8.2 census, 12.2), seeks stakeholder and user feedback, and reports the monitoring of the operation and effectiveness of the OIML-CS to the CIML as part of the annual report; benchmarking may support it (12.3)."
+  validate_provision {
+    /req/cs/od-01/scheme-monitoring
+  }
+  signature {
+    out { monitoringRecords }
+  }
+  invariants {
+    "[monitoring].metrics_source = 'annual_report_8.2'"
+    "[monitoring].feeds_annual_report = true"
+  }
+  organs { management_committee executive_secretary }
+  evidence {
+    monitoring_record { description "The measurement of the 8.2 activities with the stakeholder feedback record, feeding the annual report." required true }
+  }
+  executor actor
+  source { doc "OD-01, 12.1/12.2" clause "" }
+}
+
+process expert_list_maintenance {
+  name "Expert criteria and list maintenance"
+  summary "The Management Committee specifies the competence criteria for Legal Metrology Experts (13.2.1) and Management System Experts (13.2.2) — the criteria the PD-02 approval pipeline applies. The Executive Secretary maintains and publishes the expert lists; the MC reviews the list on a 3-yearly basis — the Executive Secretary contacting each expert — confirming continued listing, scope changes, and continued fulfilment of the criteria incl. participation in relevant activities, with the Review Committee's advice incorporated (13.4)."
+  validate_provision {
+    /req/cs/od-01/expert-competence-criteria
+    /req/cs/od-01/expert-list-maintenance
+  }
+  signature {
+    in { expertRegisters }
+    out { expertRegisters }
+  }
+  invariants {
+    "[expert].list_review_due = true implies [expert].contacted_by_executive_secretary = true"
+    "[review].rc_advice is not null"
+  }
+  activity_kind { surveillance }
+  organs { management_committee executive_secretary review_committee }
+  participant_kinds { legal_metrology_expert management_system_expert }
+  evidence {
+    list_review_record { description "The 3-yearly list review record — per expert: remain/scope-change confirmation, continued-criteria fulfilment, the RC's advice." required true }
+  }
+  realized_by { publish_participant_register }
+  executor actor
+  source { doc "OD-01, 13.2/13.4" clause "" }
+}
+
+document_module od-01 {
+  document "OIML-CS OD-01"
+  title "Management Committee"
+  edition "4"
+  year 2022
+  namespace /req/cs/od-01
+}

package/oiml-cs/framework/documents/od-01/requirements.prl

@@ -0,0 +1,138 @@
+# OIML-CS DOCUMENT MODULE OD-01 — NORMATIVE PROVISIONS (/req/cs/od-01/*)
+# -----------------------------------------------------------------------------
+# OIML-CS OD-01 Edition 4 (approved 2022-09-09; published 2022-11-14) —
+# the Operational Rules of the Management Committee: composition and
+# appointment, the Review Committee's rules (including the TWO-THIRDS
+# recommendation validity), the principles of operation, and the annual
+# report to the CIML.
+#
+# NUMBERING: clause anchors VERIFIED against the official published PDF
+# (reference-docs/cs/docs/oiml-cs-od-01-edition-4.pdf, retrieved
+# 2026-07-24; task 46). The 7.6+ reconstruction is CONFIRMED against the
+# body text: 7.6 MC meetings · 7.7 RC/WG meetings · 7.8 MC voting · 7.9 RC
+# recommendations (two-thirds validity; ≤ 1 proxy) · 7.10 WG
+# recommendations · 7.11 timelines · 8 interaction with the CIML (8.2
+# annual-report content a–k, h = appeals summary) · 9 strategy and policy
+# · 10 promotion and awareness raising · 11 documents · 12 monitoring
+# (12.1/12.2) · 13 experts (13.2.1/13.2.2 criteria, 13.4 list maintenance/
+# publication + 3-yearly review) · 14 TLF interface · 15 references. NOTE
+# — OD-01's own printed CONTENTS is defective: it skips 7.2 (Obligations
+# of Review Committee Members), so every TOC entry from "7.2" onward is
+# body−1; the BODY numbering followed here (and by every internal
+# cross-reference in the CS corpus: PD-02's "OD-01, 13.4", the 7.8/7.9
+# gates) is authoritative. The local presentation XML
+# (data/oiml-cs-od-01/) is a defective build (0.x renumbering) and is
+# never cited.
+#
+# 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. This module records OD-01's own text
+# (3-yearly list review); documents/pd-02 records PD-02's text
+# (four-year review) — the two cycles are separately anchored to their
+# sources (a CID-01 candidate). 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/od-01/requirements.yaml is its GENERATED YAML twin
+# (cd browser && npm run gen:data).
+requirement_class /req/cs/od-01 {
+  title "OIML-CS Management Committee operational rules"
+  name "Management Committee (OD-01)"
+  description "Provisions of OIML-CS OD-01 Edition 4: the operational rules of the Management Committee and its Review Committee, the annual reporting and monitoring of the scheme, and the expert criteria and lists. Enforced by the abstract processes of this module (abstract-processes.yaml); the organs and their decision rules are the task-40 framework model (framework/)."
+  subject "OIML-CS governance — MC/RC operation, reporting, experts"
+}
+
+requirement /req/cs/od-01/mc-composition-appointment {
+  name "MC composition and appointment"
+  statement "The CIML Member of an OIML Member State that has at least one OIML Issuing Authority or Utilizer may designate up to four representatives to participate in the Management Committee; one of the representatives shall be designated as the \"Management Committee Member\" for the purposes of voting (OD-01, 4.2.1). The Chairperson serves a three-year CIML-appointed term with one renewal (4.2.3); the Executive Secretary is an independent BIML staff member, never a country representative (4.2.6)."
+  obligation shall
+  verification { method inspection description "MC composition evidence (framework participants; abstract process mc_annual_reporting's organ bindings)." }
+  source { doc "OD-01, 4.2.1" clause "" }
+}
+
+requirement /req/cs/od-01/rc-recommendations {
+  name "RC recommendations and member segregation"
+  statement "The Management Committee seeks, through the Executive Secretary, Review Committee recommendations on a) the approval or rejection of candidate OIML Issuing Authorities and their Test Laboratories, including scope changes, b) their periodic review, and c) the approval or rejection of Legal Metrology Experts and Management System Experts (OD-01, 5.6). A Review Committee member shall not contribute (by comment or opinion) to recommendations concerning an Issuing Authority or Test Laboratory whose peer assessment or accreditation assessment they participated in; members may contribute to recommendations concerning their own country and organization, subject to the exception of 5.6.3."
+  obligation shall
+  verification { method inspection description "The RC recommendation discipline (abstract process rc_recommendation_governance; its invariants)." }
+  source { doc "OD-01, 5.6" clause "" }
+}
+
+requirement /req/cs/od-01/rc-confidentiality {
+  name "RC confidentiality"
+  statement "Review Committee members sign a non-disclosure agreement with the BIML; application documents are destroyed after the recommendation has been made (OD-01, 5.7)."
+  obligation shall
+  verification { method inspection description "The confidentiality discipline (abstract process rc_recommendation_governance)." }
+  source { doc "OD-01, 5.7" clause "" }
+}
+
+requirement /req/cs/od-01/member-voting-obligation {
+  name "Member voting obligation"
+  statement "A Management Committee Member shall vote when called upon; where the obligation process is exhausted without resolution, the country loses its vote within the Management Committee and is classified as an Observer — the Executive Secretary informs the CIML Member, who may designate another Management Committee Member; full membership and voting rights are regained when the Management Committee Member attends the next meeting, and the CIML Member may appeal the reclassification (OD-01, 7.1; the same mechanism binds Review Committee members, 7.2)."
+  obligation shall
+  verification { method inspection description "The voting-obligation discipline (abstract process mc_annual_reporting's obligations evidence)." }
+  source { doc "OD-01, 7.1/7.2" clause "" }
+}
+
+requirement /req/cs/od-01/assessment-reports-confidential {
+  name "Assessment reports never public"
+  statement "Accreditation and peer assessment reports shall never be made public (OD-01, 7.3); the MC works by correspondence with the MC Workspace on the OIML-CS website, and its approval, suspension and scope decisions are confidential until effected (7.3/7.4)."
+  obligation shall
+  verification { method inspection description "The confidentiality rule (abstract process rc_recommendation_governance; its invariants)." }
+  source { doc "OD-01, 7.3" clause "" }
+}
+
+requirement /req/cs/od-01/mc-voting-rules {
+  name "MC voting rules"
+  statement "Management Committee voting follows the rules of OIML B 18, 11.4 (OD-01, 7.8 — the framework's ia-tl-participation-decisions rule): a member unable to be present may give a proxy to another representative of their own country or to another Management Committee Member from an OIML Member State, under the stated conditions (maximum two proxies held per member; abstentions not counted)."
+  obligation shall
+  verification { method inspection description "The voting rule binding (framework governance; abstract process mc_annual_reporting)." }
+  source { doc "OD-01, 7.8" clause "" }
+}
+
+requirement /req/cs/od-01/rc-recommendation-validity {
+  name "RC recommendation validity — two-thirds"
+  statement "There is no formal voting in the Review Committee, but it shall report its recommendations to the Management Committee with the level of consensus reached; a recommendation is valid when TWO-THIRDS of the opinions given are in favour — a lower level of support may ground a recommendation, in which case the actual level is reported to the Management Committee, which votes on the basis of the recommendation (OD-01, 7.9; RC proxies limited to one per member, two where needed for quorum)."
+  obligation shall
+  verification { method inspection description "The validity threshold (abstract process rc_recommendation_governance; its invariants)." }
+  source { doc "OD-01, 7.9" clause "" }
+}
+
+requirement /req/cs/od-01/annual-report {
+  name "Annual report to the CIML"
+  statement "The Management Committee reports annually to the CIML on its activities and on the monitoring of the operation and effectiveness of the OIML-CS; the Executive Secretary prepares the report, the Chairperson presents it at the CIML's annual meeting, and the Management Committee reviews and comments before submission (OD-01, 8.1). The report contains information relating, but not limited, to (8.2): a) activities of the MC and its Working Groups, including changes to ODs, PDs, guidance, forms and templates; b) the categories of measuring instruments in the system and their Scheme; c) the functioning of the system — e.g. the number of OIML certificates issued and the number of certificates (and evaluation/ test reports) not accepted, with the reasons for non-acceptance; d) appointment, rejection and suspension of IAs and TLs; e) the number of IAs and Utilizers and their scopes; f) continuing compliance of IAs and TLs with the rules; g) appointment of Legal Metrology Experts and Management System Experts; h) a summary of appeals — content, nature and resolution, to the greatest extent possible consistent with the parties' privacy; i) promotional activities; j) the finances (income and expenditure) of the OIML-CS; k) the outlook for the next year. A template is provided on the OIML-CS pages of the OIML website."
+  obligation shall
+  verification { method inspection description "The annual-reporting process (abstract process mc_annual_reporting; its invariants name the a–k content)." }
+  source { doc "OD-01, 8.1/8.2" clause "" }
+}
+
+requirement /req/cs/od-01/scheme-monitoring {
+  name "Monitoring of operation and effectiveness"
+  statement "The Management Committee shall establish mechanisms for measuring key activities and outcomes, and shall seek feedback from stakeholders and users of the OIML-CS to identify improvements; the monitoring of the operation and effectiveness of the OIML-CS is reported to the CIML as part of the annual report (OD-01, 12.1; the measurable activities are those of 8.2 — 12.2; benchmarking may support the monitoring, 12.3)."
+  obligation shall
+  verification { method inspection description "The monitoring mechanism (abstract process scheme_monitoring)." }
+  source { doc "OD-01, 12.1/12.2" clause "" }
+}
+
+requirement /req/cs/od-01/expert-competence-criteria {
+  name "Expert competence criteria"
+  statement "The competence criteria for Legal Metrology Experts (13.2.1) and for Management System Experts (13.2.2) are specified by the Management Committee — performance-oriented criteria (education, knowledge, experience, personal and auditing skills) judged case by case. These are the criteria OIML-CS PD-02, 5/6 defer to (the delegation pinned by documents/pd-02/requirements.yaml lme-competence-criteria / mse-competence-criteria)."
+  obligation shall
+  verification { method inspection description "The criteria home (abstract process expert_list_maintenance; the PD-02 pipeline applies them)." }
+  source { doc "OD-01, 13.2.1/13.2.2" clause "" }
+}
+
+requirement /req/cs/od-01/expert-list-maintenance {
+  name "Expert list maintenance and review"
+  statement "The list of Legal Metrology Experts and Management System Experts approved to serve as assessors per instrument category is maintained by the Executive Secretary and available on the OIML-CS pages of the OIML website; the list is reviewed on a 3-yearly basis by the Management Committee — the Executive Secretary first contacting each expert — confirming a) whether the expert wishes to remain on the list, b) any requested change of scope, and c) whether the expert continues to fulfil the 13.2.1/13.2.2 criteria, including participation in relevant activities; the Executive Secretary seeks the Review Committee's advice on continued suitability, incorporated into the review (OD-01, 13.4; see the header's verified discrepancy with PD-02, 11's four-year cycle)."
+  obligation shall
+  verification { method inspection description "The list-maintenance cycle (abstract process expert_list_maintenance; its invariants)." }
+  source { doc "OD-01, 13.4" clause "" }
+}
+

package/oiml-cs/framework/documents/od-02/abstract-processes.prl

@@ -0,0 +1,119 @@
+# OIML-CS DOCUMENT MODULE OD-02 — ABSTRACT PROCESSES
+# -----------------------------------------------------------------------------
+# The OD-02 Edition 3 operational disciplines as ABSTRACT processes
+# (TODO.roadmap/43):
+#
+#   tlf_representation                        (4.2/5.3 — participation and
+#                                              the Executive Secretary's
+#                                              secretariat)
+#   interlaboratory_comparison_encouragement  (5.1 — the ILC role per
+#                                              ISO/IEC 17043:2023)
+#   tlf_recommendation                        (6.3–6.5 — meetings, the
+#                                              consensus rule, the TC/SC
+#                                              interface)
+#
+# There is no linear chain — these are the TLF's standing disciplines, not
+# a pipeline. The TLF organ and its advisory tasks REFERENCE the task-40
+# framework model (framework/participants.prl test_laboratories_forum;
+# framework/governance.prl tlf-advisory-tasks) — never restate it; the
+# consumer's linker rule R26 resolves every reference.
+#
+# TODO.roadmap/45: the TLF stays UNREALIZED — an advisory organ with no
+# executive acts on the platform (its outputs are recommendations); every
+# process is a justified named gap 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/od-02/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 tlf_representation {
+  name "TLF participation and secretariat"
+  summary "One representative per Test Laboratory listed in an Issuing Authority's Declaration participates in the TLF (per category where a laboratory covers several); the Management Committee Members notify the representative names and changes to the Executive Secretary, who maintains the representative list and provides the TLF's secretariat — convening and chairing meetings, reporting to the Management Committee."
+  validate_provision {
+    /req/cs/od-02/tlf-participation
+    /req/cs/od-02/tlf-secretariat
+  }
+  signature {
+    out { tlfRepresentatives }
+  }
+  invariants {
+    "[tlf_representative].tl_id is not null"
+    "[tlf_representative].tl_listed_in_ia_declaration = true"
+    "[tlf_representative].count_for_tl([tlf_representative].tl_id, [tlf_representative].category) <= 1"
+  }
+  organs { test_laboratories_forum executive_secretary management_committee }
+  participant_kinds { test_laboratory }
+  evidence {
+    representative_notification { description "The Management Committee Member's notification of the TLF representative name(s) — one per Test Laboratory listed in an Issuing Authority's Declaration, per category where the laboratory covers several." required true }
+    representative_list { description "The Executive Secretary's up-to-date list of TLF representatives (the register below)." required true }
+  }
+  executor actor
+  source { doc "OD-02, 4.2/5.3" clause "" }
+}
+
+process interlaboratory_comparison_encouragement {
+  name "Inter-laboratory comparison encouragement"
+  summary "The TLF encourages inter-laboratory comparison programs amongst OIML Issuing Authorities and their Test Laboratories — regionally, with the support of the relevant Regional Legal Metrology Organization — applying the applicable requirements of ISO/IEC 17043:2023 (the proficiency-testing standard — referenced, never restated). This is the provenance of the intercomparison- results evidence item of the TL application (PD-04, 5.1 i)."
+  validate_provision {
+    /req/cs/od-02/intercomparison-encouragement
+  }
+  signature {
+    out { intercomparisonPrograms }
+  }
+  invariants {
+    "[program].participant_tl_ids.count >= 2"
+    "[program].iso_17043_applied = true"
+  }
+  organs { test_laboratories_forum }
+  participant_kinds { test_laboratory issuing_authority }
+  evidence {
+    program_record { description "The encouraged inter-laboratory comparison program record — participating IAs/TLs, the regional/RLMO frame where applicable, and the ISO/IEC 17043:2023 conformity basis." required true }
+  }
+  executor actor
+  source { doc "OD-02, 5.1" clause "" }
+}
+
+process tlf_recommendation {
+  name "TLF recommendations and TC/SC interface"
+  summary "The TLF works primarily by correspondence; meetings follow the 3-month notice / 2-month agenda discipline with at most three participants per Management Committee Member simultaneously present, minutes going to the Management Committee (6.1/6.3). Recommendations issue BY CONSENSUS; where consensus fails the matter is referred to the Management Committee or the relevant OIML TC/SC (6.4). Proposals to revise a Recommendation's testing requirements go from the TLF via the Executive Secretary to the TC/SC, the Management Committee Chairperson notified (6.5)."
+  validate_provision {
+    /req/cs/od-02/tlf-meetings
+    /req/cs/od-02/tlf-consensus
+    /req/cs/od-02/tlf-tc-interface
+  }
+  signature {
+    out { tlfRecommendations }
+  }
+  invariants {
+    "[recommendation].consensus = true or [recommendation].referred_to is not null"
+    "[meeting].notice_days >= 90 or [meeting].shorter_period_agreed = true"
+    "[meeting].agenda_days >= 60 or [meeting].shorter_period_agreed = true"
+    "[meeting].participants_per_mc_member <= 3"
+    "[recommendation].kind = 'testing_requirements_revision' implies [recommendation].mc_chair_notified = true"
+  }
+  organs { test_laboratories_forum executive_secretary }
+  evidence {
+    recommendation_record { description "The consensus recommendation with its meeting minutes (3-month notice, 2-month agenda, ≤ 3 participants per MC Member) — or the referral record to the MC / OIML TC/SC where consensus failed (6.4); for testing-requirement revisions, the proposal to the TC/SC with the MC Chairperson's notification (6.5)." required true }
+  }
+  decision { rule tlf-advisory-tasks clause "OD-02, 6.4" }
+  executor actor
+  source { doc "OD-02, 6.3/6.4/6.5" clause "" }
+}
+
+document_module od-02 {
+  document "OIML-CS OD-02"
+  title "Test Laboratories Forum"
+  edition "3"
+  year 2024
+  namespace /req/cs/od-02
+  register tlf_representative_register {
+    label "TLF representative list"
+    clause "OD-02, 4.2"
+    maintainer executive_secretary
+    published "Maintained by the Executive Secretary (TLF Workspace on the OIML-CS website)"
+    entries "Per Test Laboratory listed in an OIML Issuing Authority's Declaration: the representative name(s) — one representative, or one per measuring instrument category where the laboratory covers several — with the notifying Management Committee Member."
+  }
+}