@oimlsmart/primmel-packages 0.4.0 → 0.5.0

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

@@ -0,0 +1,209 @@
+# OIML-CS DOCUMENT MODULE PD-01 — ABSTRACT PROCESSES
+# -----------------------------------------------------------------------------
+# The PD-01 Edition 3 remedy processes as ABSTRACT processes
+# (TODO.roadmap/43; abstract form per TODO.roadmap/02):
+#
+#   appeal_to_boa → boa_adjudication        (the 8 → 9 chain)
+#   complaint_handling                      (6.2/6.3/6.4 — off-sequence)
+#   certificate_deregistration              (6.2 consequence — off-sequence)
+#   dispute_escalation                      (7 — off-sequence)
+#
+# The BoA organ and its ruling rule REFERENCE the task-40 framework model
+# (framework/participants.prl board_of_appeal; framework/governance.prl
+# boa-appeal-rulings) — never restate it; the consumer's linker rule R26
+# (document-pipeline-references) resolves every reference. The
+# Executive-Secretary investigation a certificate issued on incorrect
+# conclusions undergoes here is the procedure PD-05 §7.1 defers to (the
+# abstract incorrect_conclusions flow of evaluation/abstract-processes.prl).
+#
+# TODO.roadmap/45 REALIZED the appeal chain, the complaint flow and the
+# deregistration consequence: realized_by binds the concrete Core
+# processes (handle_appeal, handle_complaint, deregister_certificate), the
+# signature stores are the runtime's cs-operations entity classes
+# (data/core/entities/cs-operations.yaml), and the one-month windows are
+# the structured windows facets below, executed by
+# browser/src/data/cs-operations.ts (never restated in TS).
+# dispute_escalation stays unrealized (a named gap in the unified coverage
+# report — the PD-01, 7 CIML-Member mediation is off-platform
+# correspondence).
+#
+# Clause anchors VERIFIED against the official published PDF
+# (reference-docs/cs/docs/oiml-cs-pd-01-edition-3.pdf; task 46,
+# 2026-07-24) — the local XML's 0.x numbering is never cited (see the
+# requirements.prl header for the 6.x/8.x reconstruction correction).
+#
+# This file is the single source of truth; the consumer's
+# data/oiml-cs/documents/pd-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 appeal_to_boa {
+  name "Appeal to the Board of Appeal"
+  summary "An applicant for OIML type evaluation and certification appeals against an OIML Issuing Authority's decision — but ONLY after exhausting that Issuing Authority's own appeal procedure, where applicable (8.2.1); an OIML Issuing Authority, Utilizer or Associate (including applicants for participation, 8.1 Note) appeals against a Management Committee decision (8.3). Both appeal in writing to the Executive Secretary WITHIN ONE MONTH — of being informed of the decision (8.2.2), or of concluding that no agreement can be reached (8.3) — setting out all reasons."
+  validate_provision {
+    /req/cs/pd-01/appeal-applicant-exhaustion
+    /req/cs/pd-01/appeal-participant-window
+  }
+  signature {
+    out { appeals }
+  }
+  invariants {
+    "[appeal].lodged_within_days <= 31"
+    "[appeal].appellant_kind = 'applicant' implies ([appeal].ia_appeal_outcome is not null or [appeal].ia_procedure_applicable = false)"
+    "[appeal].reasons is not null"
+  }
+  activity_kind { appeal }
+  organs { executive_secretary }
+  participant_kinds { applicant issuing_authority utilizer associate }
+  evidence {
+    written_appeal { description "The written appeal to the Executive Secretary setting out all reasons, dated within the one-month window." required true }
+    ia_procedure_exhaustion { description "For an applicant appeal: evidence that the Issuing Authority's own appeal procedure was used first (its outcome), or that the procedure is not applicable (8.2.1)." required true }
+  }
+  realized_by { handle_appeal }
+  windows {
+    window lodging_window {
+      kind max_elapsed
+      clause "PD-01, 8.2/8.3"
+      anchor informed_at
+      applies_to lodged_at
+      window { months 1 }
+      breach rule_inadmissible
+      description "The written appeal reaches the Executive Secretary WITHIN ONE MONTH — of the appellant being informed of the IA's decision (8.2.2), or of the participant concluding that no agreement can be reached (8.3). A late appeal is ruled inadmissible (the appeal_case machine's rule_inadmissible hop to INADMISSIBLE)."
+    }
+  }
+  executor actor
+  source { doc "PD-01, 8" clause "" }
+}
+
+process boa_adjudication {
+  name "BoA adjudication"
+  summary "The Board of Appeal considers the case — normally in person, online or by correspondence with all parties' consent; the Executive Secretary circulates all relevant information at least one month before the meeting; the case is confidential; the parties may use expert advisers; only the BoA and the Executive Secretary (non-voting secretary) are present. Decisions pass by simple majority with the Chairperson's casting vote; the written decision issues WITHIN ONE MONTH. A BoA decision upholding an appeal against a Management Committee decision is BINDING on the MC and cannot be appealed further; decisions are reported to the next MC meeting anonymized on request; the MC decides the steps when a participant ignores a BoA decision."
+  validate_provision {
+    /req/cs/pd-01/boa-composition
+    /req/cs/pd-01/boa-procedure
+    /req/cs/pd-01/boa-decision-binding
+  }
+  signature {
+    in { appeals }
+    out { appeals }
+  }
+  invariants {
+    "[appeal].information_circulated_days_before >= 31"
+    "[appeal].decision_issued_within_days <= 31"
+    "[appeal].upheld_against_mc_decision = true implies [appeal].binding_on_mc = true and [appeal].further_appeal_possible = false"
+    "[boa_case].mc_member_or_representative_in_panel = false"
+  }
+  activity_kind { decision }
+  organs { board_of_appeal executive_secretary }
+  evidence {
+    case_file { description "The complete case information circulated to the BoA and the parties at least one month before consideration." required true }
+    written_decision { description "The BoA's written decision, issued within one month of consideration, with the anonymized report to the next Management Committee meeting where requested." required true }
+  }
+  decision { rule boa-appeal-rulings clause "PD-01, 9" }
+  realized_by { handle_appeal }
+  windows {
+    window circulation_lead_time {
+      kind min_elapsed
+      clause "PD-01, 9"
+      anchor information_circulated_at
+      applies_to considered_at
+      window { months 1 }
+      description "All relevant information is circulated to the BoA Chairperson and members and to the parties AT LEAST ONE MONTH before the meeting at which the case is considered (9)."
+    }
+    window decision_window {
+      kind max_elapsed
+      clause "PD-01, 9"
+      anchor considered_at
+      applies_to decision_issued_at
+      window { months 1 }
+      description "The BoA gives its written decision WITHIN ONE MONTH after the case has been considered (9)."
+    }
+  }
+  executor actor
+  source { doc "PD-01, 9" clause "" }
+}
+
+process complaint_handling {
+  name "Complaint resolution"
+  summary "Three complaint kinds, all to the Executive Secretary with documented and substantiated evidence (6): incorrect technical conclusions or procedures underlying an issued OIML type evaluation report (6.2 — the owner and the MC are notified; the Executive Secretary investigates with the Review Committee's advice; upheld ⇒ the certificate is deregistered and the IA corrects the report); non-acceptance of reports/certificates by a Utilizer or Associate (6.3 — the MC may amend the Utilizer/Associate scope with consequential IA-scope amendments); expressions of dissatisfaction with the OIML-CS (6.4 — reported to the MC with recommended actions where upheld)."
+  validate_provision {
+    /req/cs/pd-01/complaint-incorrect-conclusions
+    /req/cs/pd-01/complaint-non-acceptance
+    /req/cs/pd-01/complaint-dissatisfaction
+  }
+  signature {
+    out { complaints }
+  }
+  invariants {
+    "[complaint].evidence is not null"
+    "[complaint].kind = 'incorrect_conclusions' implies [complaint].rc_advice is not null"
+    "[complaint].upheld = true implies [complaint].recommended_actions is not null"
+  }
+  activity_kind { complaint }
+  organs { executive_secretary review_committee management_committee }
+  evidence {
+    complaint_record { description "The complaint with its documented and substantiated evidence, the notification to the report owner / Utilizer / Associate and to the Management Committee." required true }
+    investigation_record { description "The Executive Secretary's investigation with the Review Committee's advice (6.2) and the recommended actions reported to the Management Committee." required true }
+  }
+  realized_by { handle_complaint }
+  executor actor
+  source { doc "PD-01, 6" clause "" }
+}
+
+process certificate_deregistration {
+  name "Deregistration for incorrect conclusions"
+  summary "The consequence of an upheld incorrect-conclusions complaint: the corresponding OIML certificate is deregistered from the OIML-CS website and the OIML Issuing Authority takes appropriate action to correct the OIML type evaluation report; the Issuing Authority may appeal the deregistration decision (8.3). This is the PD-01 half of the PD-05 §7.1 procedure (/req/cs/incorrect-conclusions — the Executive Secretary consults the IA, then this clause-6 procedure applies)."
+  validate_provision {
+    /req/cs/pd-01/complaint-incorrect-conclusions
+  }
+  signature {
+    in { complaints certificates }
+    out { certificates }
+  }
+  invariants {
+    "[certificate].deregistered = true implies [evaluation_report].correction_action is not null"
+  }
+  activity_kind { withdrawal }
+  organs { executive_secretary biml }
+  participant_kinds { issuing_authority }
+  evidence {
+    deregistration_record { description "The deregistration of the certificate from the OIML-CS website with the Issuing Authority's correction of the type evaluation report." required true }
+  }
+  realized_by { deregister_certificate }
+  executor actor
+  source { doc "PD-01, 6.2" clause "" }
+}
+
+process dispute_escalation {
+  name "Dispute resolution and escalation"
+  summary "A dispute — an applicant's over an OIML type evaluation report, or a participant's over the incorrect application of the OIML-CS rules and procedures (including non-acceptance without appropriate justification, 7.1 Note) — goes first to the parties with the appropriate CIML Member mediating; unresolved, the parties give the Executive Secretary a written explanation and the Executive Secretary raises it with the Board of Appeal."
+  validate_provision {
+    /req/cs/pd-01/dispute-resolution
+  }
+  signature {
+    out { disputes }
+  }
+  invariants {
+    "[dispute].escalated = true implies [dispute].written_explanation is not null"
+    "[dispute].escalated = true implies [dispute].mediation_attempted = true"
+  }
+  activity_kind { complaint }
+  organs { executive_secretary ciml board_of_appeal }
+  participant_kinds { applicant issuing_authority utilizer associate }
+  evidence {
+    dispute_record { description "The dispute notification to the Executive Secretary with the parties identified." required true }
+    written_explanation { description "The parties' written explanation when mediation fails — the escalation input to the Board of Appeal." required true }
+  }
+  executor actor
+  source { doc "PD-01, 7" clause "" }
+}
+
+document_module pd-01 {
+  document "OIML-CS PD-01"
+  title "Appeals, Resolution of Complaints and Disputes"
+  edition "3"
+  year 2024
+  namespace /req/cs/pd-01
+  sequence { appeal_to_boa boa_adjudication }
+}

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

@@ -0,0 +1,117 @@
+# OIML-CS DOCUMENT MODULE PD-01 — NORMATIVE PROVISIONS (/req/cs/pd-01/*)
+# -----------------------------------------------------------------------------
+# OIML-CS PD-01 Edition 3 (approved 2024-08-26, electronic ballot) — the
+# scheme's post-decision remedies: the Board of Appeal (BoA) composition
+# and procedure, the one-month appeal windows with the
+# IA-procedure-exhausted precondition, the binding force of BoA rulings on
+# the MC, complaint resolution (including deregistration of a certificate
+# whose type evaluation report rests on incorrect technical conclusions,
+# 6.2), and dispute handling.
+#
+# MECE: the BoA's IDENTITY and mandate live in the task-40 framework model
+# (framework/participants.prl board_of_appeal — B 18:2025 §13; the
+# boa-appeal-rulings decision rule in framework/governance.prl); this
+# module holds the PD-01 PROCEDURE, never restates the framework. The
+# Executive-Secretary investigation of a certificate issued on incorrect
+# conclusions (6.2) is the procedure PD-05 §7.1 defers to
+# (/req/cs/incorrect-conclusions); the PD-05-side provision stays in
+# specification/requirements/cs.prl.
+#
+# NUMBERING: clause anchors VERIFIED against the official published PDF
+# (reference-docs/cs/docs/oiml-cs-pd-01-edition-3.pdf, retrieved
+# 2026-07-24; task 46). CORRECTED 2026-07-24 — corpus C's reconstruction
+# numbered the complaint subclauses 6.1/6.2/6.3 and the appeal subclauses
+# 8.1/8.2; the official PDF numbers clause 6 with a 6.1 topic-list lead-in
+# (6.2 incorrect technical conclusions, 6.3 non-acceptance, 6.4 expressions
+# of dissatisfaction) and clause 8 with an 8.1 right-of-appeal lead-in
+# (8.2 appeals by applicants — 8.2.1 IA-procedure-first, 8.2.2 one-month
+# window; 8.3 appeals by IAs/Utilizers/Associates). The official notes:
+# one Note under 6.4 (suggestions for improvement), one under 7.1
+# (non-acceptance without appropriate justification), one under 8.1
+# (applicant organizations also have the right of appeal) — there is no
+# "Note 3" under clause 8. The local presentation XML
+# (data/oiml-cs-pd-01/) is a defective build (empty <sections>, body
+# renumbered) and is never cited.
+#
+# This file is the single source of truth; the consumer's
+# data/oiml-cs/documents/pd-01/requirements.yaml is its GENERATED YAML twin
+# (cd browser && npm run gen:data).
+requirement_class /req/cs/pd-01 {
+  title "OIML-CS appeals, complaints and disputes requirements"
+  name "Appeals, Resolution of Complaints and Disputes (PD-01)"
+  description "Provisions of OIML-CS PD-01 Edition 3 governing appeals against Management Committee and Issuing Authority decisions, the resolution of complaints (incorrect technical conclusions, non-acceptance, dissatisfaction) and disputes, and the operating procedure of the Board of Appeal. Enforced by the abstract processes of this module (abstract-processes.yaml); the BoA actor and its ruling rule are the task-40 framework model (framework/)."
+  subject "OIML-CS post-decision remedies — Board of Appeal, complaints, disputes"
+}
+
+requirement /req/cs/pd-01/boa-composition {
+  name "BoA composition and appointment"
+  statement "The Board of Appeal is composed per OIML B 18, 13.1 — a Chairperson and four members, all appointed by the CIML (PD-01, 4.1/4.2). Management Committee Members and representatives cannot be appointed; members serve three-year terms with one re-appointment; nobody serves in a case involving an OIML Issuing Authority or Test Laboratory of their own country; the Executive Secretary acts as the non-voting BoA secretary. CIML Members are given at least one month to review nominations ahead of the appointment vote."
+  obligation shall
+  verification { method inspection description "BoA composition evidence of the adjudication step (abstract process boa_adjudication)." }
+  source { doc "PD-01, 4.1/4.2" clause "" }
+}
+
+requirement /req/cs/pd-01/complaint-incorrect-conclusions {
+  name "Complaint of incorrect technical conclusions"
+  statement "A complaint may be submitted to the Executive Secretary with documented and substantiated evidence that an OIML type evaluation report was issued on the basis of incorrect technical conclusions or procedures (PD-01, 6.2). The Executive Secretary shall notify the report owner and the Management Committee, investigate, and seek the Review Committee's advice; if the complaint is upheld, the corresponding OIML certificate is deregistered from the OIML-CS website and the OIML Issuing Authority shall take appropriate action to correct the report. The Issuing Authority has the right to appeal the deregistration decision. (This is the procedure PD-05 §7.1 defers to — /req/cs/incorrect-conclusions.)"
+  obligation shall
+  verification { method inspection description "The incorrect-conclusions complaint flow (abstract process complaint_handling; deregistration consequence certificate_deregistration)." }
+  source { doc "PD-01, 6.2" clause "" }
+}
+
+requirement /req/cs/pd-01/complaint-non-acceptance {
+  name "Complaint of non-acceptance"
+  statement "A complaint may be submitted to the Executive Secretary with documented and substantiated evidence regarding a Utilizer's or Associate's decision not to accept an OIML test report, OIML type evaluation report and/or OIML certificate (PD-01, 6.3). The Executive Secretary shall notify the Utilizer or Associate and the Management Committee and investigate; the Management Committee may amend the scope of the Utilizer or Associate, with potential consequential amendments to the scope of the OIML Issuing Authority(ies) of the same Member State. The Utilizer or Associate has the right to appeal the Management Committee's decision."
+  obligation shall
+  verification { method inspection description "The non-acceptance complaint flow (abstract process complaint_handling)." }
+  source { doc "PD-01, 6.3" clause "" }
+}
+
+requirement /req/cs/pd-01/complaint-dissatisfaction {
+  name "Expression of dissatisfaction"
+  statement "An expression of dissatisfaction regarding the OIML-CS may be brought to the Management Committee Chairperson, the Deputy Chairperson, a Management Committee Member or the Executive Secretary; anyone other than the Executive Secretary shall notify the Executive Secretary, who investigates and — where the expression is upheld — reports to the Management Committee with recommended actions (PD-01, 6.4; the same process applies to suggestions for improvement, 6.4 Note)."
+  obligation shall
+  verification { method inspection description "The dissatisfaction flow (abstract process complaint_handling)." }
+  source { doc "PD-01, 6.4" clause "" }
+}
+
+requirement /req/cs/pd-01/dispute-resolution {
+  name "Dispute resolution"
+  statement "The Executive Secretary shall be contacted in the event of a dispute initiated by an applicant regarding an OIML type evaluation report, or by an OIML Issuing Authority, Utilizer or Associate regarding the incorrect application of the OIML-CS rules and procedures (PD-01, 7 — including non-acceptance without appropriate justification, 7.1 Note). The appropriate CIML Member may represent their participant and shall attempt to resolve the issue between the parties; where the issue cannot be resolved, the parties provide a written explanation to the Executive Secretary, who raises it with the Board of Appeal."
+  obligation shall
+  verification { method inspection description "The dispute flow (abstract process dispute_escalation)." }
+  source { doc "PD-01, 7" clause "" }
+}
+
+requirement /req/cs/pd-01/appeal-applicant-exhaustion {
+  name "Appeal by an applicant — IA procedure exhausted first"
+  statement "An applicant for OIML type evaluation and certification who wishes to appeal against a decision of an OIML Issuing Authority shall first appeal according to the appeal procedure of that Issuing Authority, where that procedure is applicable (PD-01, 8.2.1). Only if not satisfied with the outcome — and of the opinion that the decision goes against the OIML-CS rules and procedures — or if the Issuing Authority's appeal procedure is not applicable, may the applicant submit an appeal in writing to the Executive Secretary within one month after having been informed of the decision, setting out all reasons for the appeal."
+  obligation shall
+  verification { method inspection description "The applicant-appeal preconditions (abstract process appeal_to_boa; its invariants)." }
+  source { doc "PD-01, 8.2" clause "" }
+}
+
+requirement /req/cs/pd-01/appeal-participant-window {
+  name "Appeal by an Issuing Authority, Utilizer or Associate — one-month window"
+  statement "An OIML Issuing Authority, Utilizer or Associate wishing to appeal against a decision of the Management Committee shall do so in writing to the Executive Secretary within one month after having concluded that it cannot reach an agreement, setting out its reasons in full (PD-01, 8.3). Organizations that have applied to become an Issuing Authority, Utilizer or Associate have the same right of appeal (PD-01, 8.1 Note)."
+  obligation shall
+  verification { method inspection description "The participant-appeal window (abstract process appeal_to_boa; its invariants)." }
+  source { doc "PD-01, 8.3" clause "" }
+}
+
+requirement /req/cs/pd-01/boa-procedure {
+  name "BoA procedure"
+  statement "The BoA normally meets in person (online or by correspondence with the consent of all parties); all relevant information shall be circulated by the Executive Secretary to the BoA Chairperson and members and to the parties at least one month before the meeting; the case is dealt with confidentially; each party may use an expert adviser; only the BoA Chairperson, the four members and the Executive Secretary are present during adjudication; decisions are taken by simple majority with the Chairperson's casting vote on a tie; the BoA gives its decision in writing within one month after the case has been considered (PD-01, 9)."
+  obligation shall
+  verification { method inspection description "The adjudication discipline (abstract process boa_adjudication; its invariants)." }
+  source { doc "PD-01, 9" clause "" }
+}
+
+requirement /req/cs/pd-01/boa-decision-binding {
+  name "BoA decision binding on the MC"
+  statement "Where the BoA upholds an appeal against a Management Committee decision, the BoA decision is binding upon the Management Committee and cannot be subsequently appealed (PD-01, 9). BoA decisions are presented to the Management Committee at its next meeting without revealing the identity of the parties where any party so requests; when an OIML Issuing Authority, Utilizer or Associate does not follow a BoA decision, the Management Committee shall decide on the appropriate steps to be taken."
+  obligation shall
+  verification { method inspection description "The binding-ruling invariant (abstract process boa_adjudication; its invariants)." }
+  source { doc "PD-01, 9" clause "" }
+}
+

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

@@ -0,0 +1,217 @@
+# OIML-CS DOCUMENT MODULE PD-02 — ABSTRACT PROCESSES
+# -----------------------------------------------------------------------------
+# The PD-02 Edition 3 expert-approval pipeline as ABSTRACT processes
+# (TODO.roadmap/42):
+#
+#   nomination → RC review → MC vote → NDA → expert-list publication
+#
+# plus the off-sequence flows: change of scope and the four-year
+# monitoring cycle. The pipeline's organ actors and its MC decision
+# mechanics REFERENCE the task-40 framework model (framework/) — never
+# restate it; the consumer's linker rule R26 (document-pipeline-
+# references) resolves every reference. The expert KINDS (LME/MSE) are the
+# framework participant kinds (framework/participants.prl); the runtime
+# Expert entity hook stays in Core (data/core/entities/parties.yaml).
+#
+# No Declaration is signed here — the expert analogue of the participant
+# gate is the NDA (8.2): an expert enters the lists only after signing the
+# BIML non-disclosure agreement. The task-40 signing gate does not apply
+# to experts (its holder is the IA).
+#
+# TODO.roadmap/44–45: the pipeline is NOT executed by the runtime — the
+# participant-approval machinery (data/core/evaluation/processes.yaml;
+# browser/src/data/participant-registry.ts) operates IA/TL/Utilizer/
+# Associate cases only: ParticipantApplication.kind declares no expert
+# variant, so no expert nomination case can exist (task-45 review I-1).
+# Every process of this module is therefore a 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/pd-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 expert_nomination {
+  name "Expert nomination"
+  summary "An LME candidate applies individually on the LME Application Form for one or multiple instrument categories with their OIML Recommendations (7.1); an MSE candidate is nominated by an ILAC/IAF accreditation-body signatory of the matching scope (7.2.1 — Testing ISO/IEC 17025 for TL peer assessments, Product Certification ISO/IEC 17065 or Inspection ISO/IEC 17020 for IA assessments, with evidence of understanding the OIML-CS and D 32/D 30/D 37) or applies individually on the MSE Application Form (7.2.2)."
+  validate_provision {
+    /req/cs/pd-02/lme-nomination
+    /req/cs/pd-02/mse-nomination-accreditation-body
+    /req/cs/pd-02/mse-nomination-individual
+  }
+  signature {
+    out { expertApplications }
+  }
+  invariants {
+    "[expert_application].expert_kind is not null"
+    "[expert_application].expert_kind = 'legal_metrology_expert' implies [expert_application].categories.count >= 1"
+  }
+  activity_kind { selection }
+  organs { executive_secretary }
+  participant_kinds { legal_metrology_expert management_system_expert }
+  evidence {
+    application_form { description "The LME or MSE Application Form (individual), or the accreditation-body nomination with the scope evidence." required true }
+  }
+  executor actor
+  source { doc "PD-02, 7" clause "" }
+}
+
+process expert_rc_review {
+  name "RC review and recommendation"
+  summary "The Executive Secretary reviews the application and the Review Committee recommends on the candidate's approval — judging the performance-oriented competence criteria (OD-01, 13.2.1 for LMEs, 13.2.2 for MSEs) case by case."
+  validate_provision {
+    /req/cs/pd-02/lme-competence-criteria
+    /req/cs/pd-02/mse-competence-criteria
+    /req/cs/pd-02/review-and-decision
+  }
+  signature {
+    in { expertApplications }
+    out { expertApplications }
+  }
+  invariants {
+    "[expert_application].rc_recommendation is not null"
+  }
+  activity_kind { review }
+  organs { executive_secretary review_committee }
+  evidence {
+    rc_recommendation { description "The Review Committee's recommendation to the Management Committee on the expert's approval." required true }
+  }
+  executor actor
+  source { doc "PD-02, 8.1" clause "" }
+}
+
+process expert_mc_decision {
+  name "MC approval vote"
+  summary "The Management Committee votes on the expert's approval on the Review Committee's recommendation — an \"other proposal\" in the MC's voting mechanics (the 80 % threshold of B 18:2025 §11.4.2 is reserved to IA/TL participation decisions); rejection is with reasons and the applicant is notified. Appeals against expert decisions go to the Board of Appeal (framework/governance.yaml boa-appeal-rulings)."
+  validate_provision {
+    /req/cs/pd-02/review-and-decision
+  }
+  signature {
+    in { expertApplications }
+    out { expertApplications }
+  }
+  invariants {
+    "[expert_application].mc_decision is not null"
+    "[expert_application].mc_decision = 'REJECTED' implies [expert_application].rejection_reason is not null"
+  }
+  activity_kind { decision }
+  organs { management_committee }
+  evidence {
+    mc_decision_record { description "The MC decision record and the notification to the applicant (with reasons on rejection)." required true }
+  }
+  decision { rule ia-tl-participation-decisions clause "PD-02, 8.2" }
+  executor actor
+  source { doc "PD-02, 8.2" clause "" }
+}
+
+process expert_nda {
+  name "Non-disclosure agreement"
+  summary "The approved expert signs a non-disclosure agreement with the BIML — the precondition for entering the lists of experts."
+  validate_provision {
+    /req/cs/pd-02/nda
+  }
+  signature {
+    in { expertApplications }
+    out { expertApplications }
+  }
+  invariants {
+    "[expert_application].nda_signed = true"
+  }
+  organs { biml }
+  participant_kinds { legal_metrology_expert management_system_expert }
+  evidence {
+    signed_nda { description "The expert's non-disclosure agreement with the BIML." required true }
+  }
+  executor actor
+  source { doc "PD-02, 8.2" clause "" }
+}
+
+process expert_list_publication {
+  name "Expert list publication"
+  summary "The approved expert is added to the ILAC-IAF-OIML lists of experts published on the OIML-CS pages of the OIML website; ILAC and the IAF are notified for Management System Experts."
+  validate_provision {
+    /req/cs/pd-02/publication
+  }
+  signature {
+    in { expertApplications }
+    out { expertRegisters }
+  }
+  invariants {
+    "[register_entry].expert_id is not null"
+  }
+  organs { executive_secretary }
+  evidence {
+    register_entry { description "The expert's entry in the published ILAC-IAF-OIML lists (kind, instrument categories / assessment scopes), with the ILAC/IAF notification for MSEs." required true }
+  }
+  executor actor
+  source { doc "PD-02, 9" clause "" }
+}
+
+process expert_scope_change {
+  name "Expert change of scope"
+  summary "An expert extends or reduces their scope (instrument categories with their Recommendations, assessment scopes): extensions are processed by the 8.1/8.2 review procedure; reductions and removals are effected by notification only."
+  validate_provision {
+    /req/cs/pd-02/change-of-scope
+  }
+  signature {
+    in { expertRegisters }
+    out { expertRegisters }
+  }
+  invariants {
+    "[scope_change].kind = 'extension' implies [scope_change].rc_recommendation is not null"
+  }
+  activity_kind { review }
+  organs { executive_secretary review_committee }
+  participant_kinds { legal_metrology_expert management_system_expert }
+  evidence {
+    scope_change_record { description "The extension application (reviewed per 8.1/8.2) or the reduction notification with the amended list entry." required true }
+  }
+  executor actor
+  source { doc "PD-02, 10" clause "" }
+}
+
+process expert_monitoring {
+  name "Expert monitoring"
+  summary "The on-going competence and suitability of every listed expert is reviewed at least once every four years (OD-01, 13.4): the Review Committee recommends on continued competence; removal from the lists may also occur without a formal review."
+  validate_provision {
+    /req/cs/pd-02/monitoring
+  }
+  signature {
+    in { expertRegisters }
+    out { expertRegisters }
+  }
+  invariants {
+    "[expert].last_monitoring_review is not null"
+  }
+  activity_kind { surveillance }
+  organs { review_committee executive_secretary }
+  evidence {
+    monitoring_record { description "The four-year monitoring review record with the RC's continued- competence recommendation, or the removal note." required true }
+  }
+  executor actor
+  source { doc "PD-02, 11" clause "" }
+}
+
+document_module pd-02 {
+  document "OIML-CS PD-02"
+  title "Approval of Legal Metrology Experts and Management System Experts"
+  edition "3"
+  year 2022
+  namespace /req/cs/pd-02
+  sequence { expert_nomination expert_rc_review expert_mc_decision expert_nda expert_list_publication }
+  register lme_register {
+    label "ILAC-IAF-OIML list of Legal Metrology Experts"
+    clause "PD-02, 9"
+    maintainer executive_secretary
+    published "The OIML-CS pages of the OIML website (the ILAC-IAF-OIML lists of experts)"
+    entries "Per Legal Metrology Expert: identity, the instrument categories with their corresponding OIML Recommendations, and status."
+  }
+  register mse_register {
+    label "ILAC-IAF-OIML list of Management System Experts"
+    clause "PD-02, 9"
+    maintainer executive_secretary
+    published "The OIML-CS pages of the OIML website (the ILAC-IAF-OIML lists of experts; ILAC/IAF notified)"
+    entries "Per Management System Expert (Team Leader): identity, the assessment scopes (TL peer assessments per ISO/IEC 17025; IA assessments per ISO/IEC 17065 / ISO/IEC 17020), and status."
+  }
+}