@oimlsmart/primmel-packages 0.4.0 → 0.5.0

package/oiml-cs/.primmel-allowlist.prl

@@ -0,0 +1,7 @@
+# .primmel-allowlist.prl — GENERATED from primmel-allowlist.yaml (TODO.roadmap/17), do not edit.
+allowlist_entry {
+  rule C121
+  match "*realized_by \"*\" is not a declared process (abstract-process-references-resolve)*"
+  reason "The realized_by edges resolve against the COMPOSED model (the rec packages' concrete evaluation/processes.prl processes) by design — C121's merged-model semantics. The corpus's standalone check mode (no resolvePackage locator) cannot see them, and composing trips the pre-existing CASCO C28 (the include-transport migration, primmel-ts task 13). Content-level resolution is proven by the consumer's cs-coverage gate. Dies when the gates check composed (the STALE discipline)."
+  audit_ref "TODO.roadmap/42"
+}

package/oiml-cs/evaluation/abstract-processes.prl

@@ -0,0 +1,454 @@
+# OIML-CS REFERENCE PACKAGE — ABSTRACT PROCESS MODEL (PD-05)
+# -----------------------------------------------------------------------------
+# The OIML-CS certification process as ABSTRACT processes (TODO.roadmap/15;
+# abstract form per TODO.roadmap/02 — signature + invariants, no steps).
+# The 7-step usage flow (docs/oiml-cs-cert-workflow.md) plus BIML
+# registration: application → review → dispatch → testing → evaluation →
+# decision → issue → biml_registration. TODO.roadmap/41 (full PD-05
+# coverage) adds the off-sequence flows: revision (§8.1, pre-existing),
+# re_application (§4.5.7), registration_fee (§6.2–6.3),
+# incorrect_conclusions (§7.1), parallel_certificates (§8.2),
+# recommendation_update (§8.3) and scheme_a_certification (clause 5).
+# Processes with an empty realized_by have no concrete Core realization —
+# the coverage gate records them (and their provisions) as named gaps.
+#
+# Each abstract process declares:
+#   executor   machine | actor (task 02 executor typing)
+#   roles      role ids from data/core/evaluation/roles.yaml bound to this step
+#   signature  in/out — the workflow records the step consumes/produces,
+#              named by Core entity store (data/core/entities/*.yaml)
+#   evidence   evidence requirements — the records the step must produce or
+#              attach for the scheme's provisions to be inspectable
+#   invariants OCL-style booleans over the signature that hold on completion
+#              — paths name REAL Core entity fields (snake_case, references
+#              are the _id-suffixed fields, enum literals uppercase per the
+#              entity's enum_values, e.g. Application.status = 'REJECTED')
+#   provisions the /req/cs/* provisions (specification/requirements/cs.prl)
+#              this step enforces
+#   realized_by the CONCRETE Core process ids (data/core/evaluation/
+#              processes.yaml) that realize this abstract process in the
+#              platform's workflow skeleton — the documentary half of the
+#              mapping; the FORMAL mapping is the .prm
+#              (data/core/evaluation/platform-to-oiml-cs.prm,
+#              TODO.roadmap/16) and the coverage gate keeps the two
+#              consistent (a pair on one side only is a validation
+#              error); empty where the platform has no concrete process
+#              yet (dispatch — a named gap in the coverage report).
+#   approved_by the Core approval ids (data/core/evaluation/
+#              approvals.yaml) whose sign-off closes this step — the
+#              documentary half of the approval⇒abstract mapping; the
+#              coverage gate keeps it consistent with the .prm's
+#              approval-source pairs exactly as for realized_by (a pair
+#              on one side only is a validation error); empty where the
+#              step has no sign-off gate.
+#   activity_kind
+#              the ISO/IEC 17000 activity-kind ids (the iso-iec-17000
+#              package's evaluation/activity-archetypes.prl — TODO.roadmap/39)
+#              classifying this step in the functional approach; multi-kind
+#              is deliberate (evaluation = selection + determination per
+#              ISO/IEC 17065 3.3). Classification, not inheritance — the
+#              consumer's linker rule R23 (activity-kind-resolves) checks
+#              every id against the register. Untagged: dispatch — an
+#              OIML-CS platform addition (test-request logistics across
+#              eligible laboratories) with no 17000 functional-approach
+#              counterpart.
+#
+# Provenance: OIML-CS PD-05 Edition 6 (2024-03-11) + Amendment 1.
+#
+# This file is the single source of truth; the consumer's
+# data/oiml-cs/evaluation/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 that live in the rec
+# packages (evaluation/processes.prl) — unresolvable under the standalone
+# package check, so they ride one glob allowlist entry (C121; the
+# oiml-cs-dataspace composition-gap precedent — the entry dies when the
+# gates check composed).
+process application {
+  name "Application"
+  summary "The manufacturer (or its authorised representative) applies to an OIML Issuing Authority for a certificate covering a measuring instrument type (single model or model family)."
+  validate_provision {
+    /req/cs/application-contents
+  }
+  signature {
+    out { applications }
+  }
+  invariants {
+    "[application].issuing_authority_id is not null"
+    "[application].manufacturer_id is not null"
+  }
+  activity_kind { selection }
+  roles { applicant }
+  evidence {
+    application_record { description "The application record with the PD-05 §4.1.2 contents: applicant and manufacturer identity, no-concurrent-application statement, type description, operation description and documentation list, sample information, previous test reports where applicable." required true }
+    subject_definition { description "The instrument definition on the subject chain (model family / models / samples with classification, parameters, capabilities) the application references." required true }
+  }
+  realized_by { submit_application }
+  executor actor
+  source { doc "PD-05 §4.1" clause "" }
+}
+
+process review {
+  name "Application review"
+  summary "The Issuing Authority reviews the application for completeness, may request additional information or changes, and accepts (notifying samples, laboratories, fees and schedule) or rejects with reasons."
+  validate_provision {
+    /req/cs/application-completeness
+    /req/cs/rejection-reason
+    /req/cs/fee-estimate
+    /req/cs/sample-count
+    /req/cs/application-time-estimate
+  }
+  signature {
+    in { applications }
+    out { applications }
+  }
+  invariants {
+    "[application].ia_review_result is not null"
+    "[application].status = 'REJECTED' implies [application].rejection_reason is not null"
+  }
+  activity_kind { selection }
+  roles { issuing_authority }
+  evidence {
+    review_outcome { description "The review decision (accept / reject / request-changes) with reviewer, date and — on rejection — the stated reasons (PD-05 §4.2.2, §4.2.4)." required true }
+    acceptance_notice { description "On acceptance: the required sample count, the receiving Test Laboratory(ies), the fee estimate (PD-05 §4.2.8) and the approximate evaluation schedule (PD-05 §4.2.9)." }
+  }
+  realized_by { review_application accept_application reject_application }
+  approved_by { ia_accept_application }
+  executor actor
+  source { doc "PD-05 §4.2" clause "" }
+}
+
+process dispatch {
+  name "Test request dispatch"
+  summary "The Issuing Authority dispatches test report requests to one or more eligible Test Laboratories, each request carrying exactly the tests (forms) and samples that laboratory must perform."
+  validate_provision {
+    /req/cs/test-laboratory-eligibility
+  }
+  signature {
+    in { applications measuringInstrumentSamples }
+    out { testRequests testAssignments }
+  }
+  invariants {
+    "[test_request].assigned_laboratory_id is not null"
+    "[test_request].required_forms.count >= 1"
+  }
+  roles { issuing_authority }
+  evidence {
+    test_request { description "One test request per laboratory: request number, assigned laboratory, models, samples, required forms and test conditions." required true }
+    laboratory_eligibility { description "Evidence that every dispatched laboratory is listed in the OIML-CS Declaration of an OIML Issuing Authority for the assigned tests." required true }
+  }
+  executor actor
+  source { doc "PD-05 §4.3.1" clause "" }
+}
+
+process testing {
+  name "Testing and test reporting"
+  summary "The Test Laboratory receives the samples, performs the assigned tests and examinations per the Recommendation's procedures, signs the evidence, and compiles and authorises the OIML test report (PD-05 §4.4)."
+  validate_provision {
+    /req/cs/test-report-18-elements
+    /req/cs/test-report-authorization
+    /req/cs/multiple-test-laboratories
+    /req/cs/test-report-language
+    /req/cs/test-report-logo
+  }
+  signature {
+    in { testRequests testAssignments measuringInstrumentSamples }
+    out { testReports formInstances }
+  }
+  invariants {
+    "[test_report].laboratory_id is not null"
+    "[test_assignment].status = 'COMPLETED' implies [test_assignment].form_instance_id is not null"
+  }
+  activity_kind { testing }
+  roles { test_laboratory }
+  evidence {
+    form_evidence { description "The completed form instances for every required form, signed by the evaluator and supervisor (per-form sign-off)." required true }
+    test_report { description "The OIML test report covering the PD-05 §4.4.3 eighteen elements, dated, signed and uniquely identified by the responsible person (PD-05 §4.4.4)." required true }
+    custody_record { description "The sample custody chain from receipt through testing (sample status and custody events)." }
+  }
+  realized_by { conduct_tests compile_test_report }
+  approved_by { tl_authorize_test_report }
+  executor actor
+  source { doc "PD-05 §4.3" clause "" }
+}
+
+process evaluation {
+  name "Type evaluation"
+  summary "The Issuing Authority compiles the type evaluation report: every test report reviewed, a determination per evaluated provision, and a conformity conclusion for the type."
+  validate_provision {
+    /req/cs/evaluation-report-contents
+    /req/cs/evaluation-report-id
+    /req/cs/evaluation-report-logo
+    /req/cs/evaluation-report-language
+    /req/cs/sample-retention
+  }
+  signature {
+    in { applications testReports formInstances }
+    out { evaluationReports }
+  }
+  invariants {
+    "[evaluation_report].test_report_ids.count >= 1"
+    "[evaluation_report].test_report_determinations.count = [evaluation_report].test_report_ids.count"
+  }
+  activity_kind { selection determination }
+  roles { issuing_authority }
+  evidence {
+    evaluation_report { description "The type evaluation report with the PD-05 §4.5.1 contents: per-test- report determinations, the conclusion on the conformity of the type, and the responsible persons' signatures (PD-05 §4.5.2)." required true }
+  }
+  realized_by { compile_evaluation_report }
+  approved_by { ia_approve_evaluation_report }
+  executor actor
+  source { doc "PD-05 §4.5" clause "" }
+}
+
+process decision {
+  name "Conformity decision"
+  summary "The Issuing Authority decides on the conformity of the type: conforming types proceed to certificate issuance; on failure the applicant is informed in writing of the reasons."
+  validate_provision {
+    /req/cs/failure-notice
+  }
+  signature {
+    in { evaluationReports }
+    out { evaluationReports }
+  }
+  invariants {
+    "[evaluation_report].overall_decision is not null"
+    "[evaluation_report].overall_decision = 'REJECTED' implies [evaluation_report].review_notes is not null"
+  }
+  activity_kind { decision }
+  roles { issuing_authority }
+  evidence {
+    decision_record { description "The overall decision (conform / not conform) with conditions and review notes; on failure, the written reasons given to the applicant." required true }
+  }
+  realized_by { compile_evaluation_report }
+  executor actor
+  source { doc "PD-05 §4.5.6" clause "" }
+}
+
+process issue {
+  name "Certificate issuance"
+  summary "The Issuing Authority issues the OIML certificate for a conforming type: Annex-A format, responsible-person signature, OIML-CS logo, Annex-B certificate number, and delivery to the applicant with the evaluation and test reports."
+  validate_provision {
+    /req/cs/certificate-requirements
+    /req/cs/certificate-format
+    /req/cs/certificate-number
+    /req/cs/certificate-delivery
+  }
+  signature {
+    in { evaluationReports }
+    out { certificates }
+  }
+  invariants {
+    "[certificate].evaluation_report_id.overall_decision = 'APPROVED' or [certificate].evaluation_report_id.overall_decision = 'CONDITIONALLY_APPROVED'"
+    "[certificate].certificate_number is not null"
+  }
+  activity_kind { certification }
+  roles { issuing_authority }
+  evidence {
+    certificate { description "The issued certificate: type designation, applicant and manufacturer, certified characteristics, Annex-B number, date of issue and responsible-person signature." required true }
+    delivery_record { description "The hand-over of certificate, evaluation report and test reports to the applicant (owner), with the Issuing Authority's copies retained." required true }
+  }
+  realized_by { issue_certificate }
+  approved_by { ia_sign_certificate }
+  executor actor
+  source { doc "PD-05 §4.6" clause "" }
+}
+
+process biml_registration {
+  name "BIML registration"
+  summary "The Issuing Authority transmits the issued certificate to the BIML for registration; the registered certificate is visible in the public OIML-CS register."
+  validate_provision {
+    /req/cs/biml-registration
+  }
+  signature {
+    in { certificates }
+    out { certificates }
+  }
+  invariants {
+    "[certificate].biml_registration is not null"
+  }
+  activity_kind { attestation }
+  roles { issuing_authority biml }
+  evidence {
+    registration_record { description "The BIML registration record for the issued certificate (transmitted copy, registration date, public register entry)." required true }
+  }
+  realized_by { register_certificate }
+  approved_by { biml_register_certificate }
+  executor actor
+  source { doc "PD-05 clause 6" clause "" }
+}
+
+process revision {
+  name "Certificate revision"
+  summary "The Issuing Authority revises an issued and registered certificate — correcting an error, modifying the certified type, or transferring ownership — keeping the initial certificate number with a revision number and reason, and re-registers it with the BIML."
+  validate_provision {
+    /req/cs/certificate-revision
+    /req/cs/certificate-revision-mechanics
+  }
+  signature {
+    in { certificates }
+    out { certificates certificateAnnexes }
+  }
+  invariants {
+    "[certificate].revisions.count >= 1"
+  }
+  activity_kind { decision certification }
+  roles { issuing_authority }
+  evidence {
+    revision_record { description "The revision record: initial certificate number retained, revision number, the statement replacing the previous version(s) with the reason(s) for the revision, and the re-registration." required true }
+  }
+  realized_by { handle_revision }
+  approved_by { ia_approve_revision }
+  executor actor
+  source { doc "PD-05 §8.1" clause "" }
+}
+
+process re_application {
+  name "Re-application after failure"
+  summary "After a failed evaluation the applicant submits a new application with samples of a modified or newly identified type; new tests may be limited to the previously failed requirements only where the evidence supports that the modification did not affect the instrument's performance for all other requirements."
+  validate_provision {
+    /req/cs/re-application
+  }
+  signature {
+    in { applications evaluationReports }
+    out { applications }
+  }
+  invariants {
+    "[application].issuing_authority_id is not null"
+  }
+  activity_kind { selection }
+  roles { applicant issuing_authority }
+  evidence {
+    previous_failure_link { description "The link from the new application to the previous failed evaluation it follows (the failed type and its evaluation report)." required true }
+    retest_limitation_evidence { description "Where tests are limited to the previously failed requirements: the evidence supporting that the modification is not likely to have affected performance for all other requirements (PD-05 §4.5.7)." }
+  }
+  executor actor
+  source { doc "PD-05 §4.5.7" clause "" }
+}
+
+process registration_fee {
+  name "Registration fee and listing"
+  summary "The BIML invoices the registration fee (the certificate owner where national regulations bar the Issuing Authority's pass-through); the certificate is added to the list of registered certificates but withdrawn if payment is not received within 3 months of the invoice date (owner-invoiced certificates are listed on payment)."
+  validate_provision {
+    /req/cs/registration-fee
+    /req/cs/registration-withdrawal
+  }
+  signature {
+    in { certificates }
+    out { certificates }
+  }
+  invariants {
+    "[certificate].biml_registration is not null"
+  }
+  activity_kind { withdrawal }
+  roles { biml issuing_authority }
+  evidence {
+    fee_invoice { description "The BIML registration-fee invoice (to the Issuing Authority, or to the certificate owner per PD-05 §6.3) and its payment record." required true }
+    listing_withdrawal_record { description "The listing of the certificate in the registered list and, where payment is not received within 3 months of the invoice date, the withdrawal of the listing (PD-05 §6.2)." required true }
+  }
+  executor actor
+  source { doc "PD-05 §6.2–6.3" clause "" }
+}
+
+process incorrect_conclusions {
+  name "Incorrect-conclusions handling"
+  summary "On documented and substantiated evidence that the tests underlying an issued certificate were performed and/or interpreted incorrectly, the Executive Secretary consults the relevant Issuing Authority and the PD-01 clause 6 (complaints) procedure applies — up to deregistration of the certificate."
+  validate_provision {
+    /req/cs/incorrect-conclusions
+  }
+  signature {
+    in { certificates }
+    out { certificates }
+  }
+  invariants {
+    "[certificate].status = 'UNDER_INVESTIGATION' implies [certificate].investigation is not null"
+  }
+  activity_kind { complaint }
+  roles { biml issuing_authority }
+  evidence {
+    investigation_record { description "The documented and substantiated evidence, the Executive Secretary's consultation with the Issuing Authority, and the outcome under the PD-01 clause 6 procedure (resolve or deregister)." required true }
+  }
+  realized_by { handle_complaint deregister_certificate }
+  executor actor
+  source { doc "PD-05 §7.1" clause "" }
+}
+
+process parallel_certificates {
+  name "Parallel certificate issuance"
+  summary "A new applicant in possession of all the §4.1.2 technical documentation and the existing type evaluation report obtains a new certificate issued in parallel to the original; the Issuing Authority inquires into the validity of the application (e.g. the original applicant's permission) and the parallel certificate is registered per clause 6."
+  validate_provision {
+    /req/cs/parallel-certificates
+  }
+  signature {
+    in { certificates }
+    out { certificates }
+  }
+  invariants {
+    "[certificate].parallel_to is not null"
+    "[certificate].original_applicant is not null"
+  }
+  activity_kind { certification }
+  roles { applicant issuing_authority }
+  evidence {
+    documentation_possession { description "Evidence that the new applicant possesses all the §4.1.2 technical documentation and the existing OIML type evaluation report (PD-05 §8.2.1)." required true }
+    parallel_record { description "The parallel certificate itself: new sequential number, the original applicant and the source certificate recorded, and its clause-6 registration." required true }
+  }
+  realized_by { issue_certificate }
+  executor actor
+  source { doc "PD-05 §8.2" clause "" }
+}
+
+process recommendation_update {
+  name "Recommendation-revision certificate update"
+  summary "After a revision of the relevant OIML Recommendation, the certificate owner applies for an updated certificate on the basis of the revised Recommendation; the Issuing Authority determines whether the type complies and defines any additional tests and examinations, and on successful completion issues a new certificate and type evaluation report, registered per clause 6."
+  validate_provision {
+    /req/cs/recommendation-revision-updates
+  }
+  signature {
+    in { certificates }
+    out { evaluationReports certificates }
+  }
+  invariants {
+    "[certificate].edition_change is not null"
+    "[certificate].edition_change.new_evaluation_report_id is not null"
+  }
+  activity_kind { decision certification }
+  roles { applicant issuing_authority }
+  evidence {
+    update_determination { description "The Issuing Authority's determination under PD-05 §8.3.2: the previous and new editions, whether additional tests are required, and their definition (Certificate.edition_change)." required true }
+    updated_certificate { description "The new certificate and type evaluation report issued on successful completion of any additional tests, registered per clause 6 (PD-05 §8.3.3)." required true }
+  }
+  realized_by { handle_edition_change }
+  executor actor
+  source { doc "PD-05 §8.3" clause "" }
+}
+
+process scheme_a_certification {
+  name "Scheme A processing"
+  summary "Scheme A mirrors the clause-4 flow (its provisions apply via the clause-5 cross-references) with the Scheme-A deltas enforced as provisions: additional national requirements declared at application and tested/reported per the Utilizer/Associate Declarations (§5.1.4/§5.3.2/§5.4.2), Manufacturer Test Laboratory data flagged in the evaluation report (§5.3.1 b/§5.5.4/§5.5.5), and the validating ANR letter sent to the BIML with the certificate (§5.6.3)."
+  validate_provision {
+    /req/cs/scheme-a-national-requirements
+    /req/cs/scheme-a-mtl-test-data
+    /req/cs/scheme-a-anr-validation-letter
+  }
+  signature {
+    in { applications }
+    out { certificates }
+  }
+  invariants {
+    "[application].scheme = 'A' implies [certificate].scheme = 'A'"
+  }
+  activity_kind { selection determination certification }
+  roles { applicant issuing_authority }
+  evidence {
+    anr_declaration { description "The applicant's declaration of the additional national requirement tests applied for (PD-05 §5.1.4) — only where ANR tests are applied for." }
+    mtl_use_statement { description "The prominent statement of Manufacturer Test Laboratory use with the respective tests and the MTL designation at the head of the evaluation report (PD-05 §5.5.4) — only where MTL reports are utilised." }
+    anr_validation_letter { description "The Issuing Authority's letter validating conformity to the additional national requirements, sent to the BIML with the certificate (PD-05 §5.6.3) — only where ANR tests were conducted." }
+  }
+  realized_by { submit_application compile_test_report compile_evaluation_report issue_certificate register_certificate }
+  executor actor
+  source { doc "PD-05 clause 5" clause "" }
+}
+
+process_model certification_process {
+  sequence { application review dispatch testing evaluation decision issue biml_registration }
+}

package/oiml-cs/framework/declarations.prl

@@ -14,7 +14,7 @@
 # specification/requirements/cs.prl: the scheme-governance constraint
 # (who may certify what, and only after a signed Declaration) now has its
 # model home here — the gate references the abstract processes it blocks
-# (the consumer's evaluation/abstract-processes.yaml, still YAML-only).
+# (evaluation/abstract-processes.prl — the PD-05 certification process).
 #
 # Declaration semantics (PD-08, verified against the corpus audit
 # analysis/oiml-cs-corpus-audit-2026-07.md, corpus C):

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
+}