@oimlsmart/primmel-packages 0.2.1 → 0.4.0

package/iso-iec-17067/specification/scheme-types.prl

@@ -0,0 +1,292 @@
+# ISO/IEC 17067:2013 — PRODUCT-CERTIFICATION SCHEME TYPES (TODO.roadmap/39d)
+# -----------------------------------------------------------------------------
+# The clause-5 scheme-type taxonomy of ISO/IEC 17067:2013 as a STRUCTURED,
+# MACHINE-QUERYABLE REGISTER — the resolution register for the
+# `scheme_type` facet a scheme layer declares in its manifest (today:
+# data/oiml-cs declares `scheme_type: type_1a`, B 18:2025 §1.3). checkUses
+# (the composition registry) resolves a declared type against the register
+# of a layer composed earlier; task 43's oiml-cs→17067 coverage gate reads
+# the facets to discharge type-conditioned provisions (a type-1a scheme
+# carries NO surveillance — the
+# /req/iso-17067/scheme-content/surveillance-procedures provision and the
+# VI-activity content are N/A with the 5.3.1 justification).
+#
+# The register encodes clause 5 INCLUDING Table 1 ("Building a product
+# certification scheme", 5.2):
+#   family common         Table-1 rows I–IV — X for every scheme type
+#                       (5.3.1: "All types of product certification schemes
+#                       involve selection, determination, review, decision
+#                       and attestation"); row I includes sampling, as
+#                       applicable.
+#   family determination  Table-1 row II a)–e) — "as applicable" for every
+#                       type; the scheme selects per its purpose and scope
+#                       (6.5.1 c).
+#   family attestation    Table-1 row V a)–d) — attestation and licensing;
+#                       the per-type `attestation` list carries the X-marks.
+#   family surveillance   Table-1 row VI a)–d) — the surveillance menu; the
+#                       per-type `surveillance.activities` list carries the
+#                       X-marks.
+#   scheme_type           the seven named types (5.3.2–5.3.8), each with
+#                       its defining-subclause anchor, a verbatim-faithful
+#                       description, the attestation object, the
+#                       attestation/licensing X-marks, and the SURVEILLANCE
+#                       facet — `required` is the 5.3.1 machine query ("For
+#                       scheme types 1a and 1b, no surveillance is required
+#                       since the attestation relates only to the product
+#                       items which have been subjected to the
+#                       determination activities").
+#
+# Table-1 notes carried by the register (5.2): NOTE c — a scheme includes
+# at least the activities I, II, III, IV and V a) (hence issue_statement
+# is on every type's attestation list); NOTE a — the activities can be
+# coupled with initial audit and surveillance audit of the applicant's
+# management system (an example is given in ISO/IEC Guide 53), the order
+# defined within the scheme; NOTE b — ISO/IEC Guide 28 is the often-used,
+# well-tried model corresponding to scheme type 5; NOTE d — the table's
+# "N" column marks an undefined number of possible OTHER schemes based on
+# different activities: a placeholder, deliberately NOT a register entry
+# (a scheme_type value must name one of the seven defined types).
+#
+# X-MARK VERIFICATION: every per-type attestation/surveillance list was
+# transcribed from the Metanorma AsciiDoc Table-1 rows (see layer.yaml
+# editions.source) and cross-checked against the 5.3.x defining
+# subclauses. One divergence from the corpus audit's summary table
+# (analysis/oiml-cs-corpus-audit-2026-07.md, Corpus D §2.2): Table 1's
+# raw V d) row marks X for type 6 (cells: 1a blank, X for 1b/2/3/4/5/6,
+# N absent) — the audit's "type 6 has a)+b)" omits it. The raw table is
+# authoritative; type 6 carries mark_licensing.
+#
+# X for row V d) is conditioned by the standard itself: "granting the
+# right to use marks of conformity (licensing) is based on surveillance
+# (VI) or certification of a batch" — type 1a (no surveillance, no batch)
+# carries no mark licensing, matching the table.
+#
+# Cross-references (the per-type determination/attestation/surveillance
+# ids against the activity-kind menus; a scheme manifest's scheme_type
+# against this register when composed) are checked package-side by the
+# kernel's C122 scheme-type-resolves (per-register gated).
+#
+# This file is the single source of truth; the consumer's
+# data/iso-iec-17067/specification/scheme-types.yaml is its GENERATED YAML
+# twin (cd browser && npm run gen:data; schema data/schemas/scheme-types.yaml).
+scheme_activity_kind selection {
+  family common
+  row "I"
+  label "Selection, including planning and preparation activities, specification of requirements, e.g. normative documents, and sampling, as applicable"
+}
+
+scheme_activity_kind determination {
+  family common
+  row "II"
+  label "Determination of characteristics, as applicable, by: a) testing; b) inspection; c) design appraisal; d) assessment of services or processes; e) other determination activities, e.g. verification"
+}
+
+scheme_activity_kind review {
+  family common
+  row "III"
+  label "Review — Examining the evidence of conformity obtained during the determination stage to establish whether the specified requirements have been met"
+}
+
+scheme_activity_kind decision {
+  family common
+  row "IV"
+  label "Decision on certification — Granting, maintaining, extending, reducing, suspending, withdrawing certification"
+}
+
+scheme_activity_kind testing {
+  family determination
+  row "II a)"
+  label "testing"
+}
+
+scheme_activity_kind inspection {
+  family determination
+  row "II b)"
+  label "inspection"
+}
+
+scheme_activity_kind design_appraisal {
+  family determination
+  row "II c)"
+  label "design appraisal"
+}
+
+scheme_activity_kind service_process_assessment {
+  family determination
+  row "II d)"
+  label "assessment of services or processes"
+}
+
+scheme_activity_kind other_determination {
+  family determination
+  row "II e)"
+  label "other determination activities, e.g. verification"
+}
+
+scheme_activity_kind issue_statement {
+  family attestation
+  row "V a)"
+  label "issuing a certificate of conformity or other statement of conformity (attestation)"
+}
+
+scheme_activity_kind grant_use_of_statement {
+  family attestation
+  row "V b)"
+  label "granting the right to use certificates or other statements of conformity"
+}
+
+scheme_activity_kind batch_certificate {
+  family attestation
+  row "V c)"
+  label "issuing a certificate of conformity for a batch of products"
+}
+
+scheme_activity_kind mark_licensing {
+  family attestation
+  row "V d)"
+  label "granting the right to use marks of conformity (licensing) — based on surveillance (VI) or certification of a batch"
+}
+
+scheme_activity_kind market_sampling {
+  family surveillance
+  row "VI a)"
+  label "testing or inspection of samples from the open market"
+}
+
+scheme_activity_kind factory_sampling {
+  family surveillance
+  row "VI b)"
+  label "testing or inspection of samples from the factory"
+}
+
+scheme_activity_kind production_assessment {
+  family surveillance
+  row "VI c)"
+  label "assessment of the production, the delivery of the service or the operation of the process"
+}
+
+scheme_activity_kind management_system_audit {
+  family surveillance
+  row "VI d)"
+  label "management system audits combined with random tests or inspections"
+}
+
+scheme_type type_1a {
+  label "scheme type 1a"
+  clause "5.3.2"
+  description "In this scheme, one or more samples of the product are subjected to the determination activities. A certificate of conformity or other statement of conformity (e.g. a letter) is issued for the product type, the characteristics of which are detailed in the certificate or a document referred to in the certificate. Subsequent production items are not covered by the certification body's attestation of conformity. The samples are representative of subsequent production items which could be referred to by the manufacturer as being manufactured in accordance with the certified type. The certification body may grant to the manufacturer the right to use the type certificate or other statement of conformity (e.g. letter) as a basis for the manufacturer to declare that subsequent production items conform to the specified requirements."
+  sampling "One or more samples of the product are subjected to the determination activities; the samples are representative of subsequent production items which could be referred to by the manufacturer as being manufactured in accordance with the certified type (5.3.2)."
+  attestation_object product_type
+  determination { testing inspection design_appraisal service_process_assessment other_determination }
+  attestation { issue_statement grant_use_of_statement }
+  surveillance {
+    required false
+  }
+  notes {
+    "No surveillance is required (5.3.1): the attestation relates only to the product items which have been subjected to the determination activities. Subsequent production items are NOT covered by the certification body's attestation of conformity."
+    "The OIML-CS case (B 18:2025 §1.3): the type certificate attests the TYPE — which is precisely why metrological verification exists as a separate pathway for production items, outside the product-certification frame."
+  }
+}
+
+scheme_type type_1b {
+  label "scheme type 1b"
+  clause "5.3.3"
+  description "This scheme type involves the certification of a whole batch of products, following selection and determination as specified in the scheme. The proportion to be tested, which can include testing of all the units in the batch (100 % testing), would be based, for example, on the homogeneity of the items in the batch and the application of a sampling plan, where appropriate. If the outcome of the determination, review and decision is positive, all items in the batch may be described as certified and may have a mark of conformity affixed, if that is included in the scheme."
+  sampling "The proportion of the batch to be tested — which can include testing of all the units in the batch (100 % testing) — is based, for example, on the homogeneity of the items in the batch and the application of a sampling plan, where appropriate (5.3.3)."
+  attestation_object batch
+  determination { testing inspection design_appraisal service_process_assessment other_determination }
+  attestation { issue_statement grant_use_of_statement batch_certificate mark_licensing }
+  surveillance {
+    required false
+  }
+  notes {
+    "No surveillance is required (5.3.1): the attestation relates only to the product items which have been subjected to the determination activities — here the whole batch."
+  }
+}
+
+scheme_type type_2 {
+  label "scheme type 2"
+  clause "5.3.4"
+  description "The surveillance part of this scheme involves periodically taking samples of the product from the market and subjecting them to determination activities to check that items produced subsequent to the initial attestation fulfil the specified requirements. While this scheme may identify the impact of the distribution channel on conformity, the resources it requires can be extensive. Also, when significant nonconformities are found, effective corrective measures may be limited since the product has already been distributed to the market."
+  sampling "Surveillance samples are taken periodically from the market (5.3.4; Table 1, VI a)."
+  attestation_object ongoing_production
+  determination { testing inspection design_appraisal service_process_assessment other_determination }
+  attestation { issue_statement grant_use_of_statement mark_licensing }
+  surveillance {
+    required true
+    activities { market_sampling }
+  }
+  notes {
+    "May identify the impact of the distribution channel on conformity, but corrective measures can be limited once nonconforming product has already been distributed (5.3.4)."
+  }
+}
+
+scheme_type type_3 {
+  label "scheme type 3"
+  clause "5.3.5"
+  description "The surveillance part of this scheme involves periodically taking samples of the product from the point of production and subjecting them to determination activities to check that items produced subsequent to the initial attestation fulfil the specified requirements. The surveillance includes periodic assessment of the production process. This scheme does not provide any indication of the impact the distribution channel plays on conformity. When serious nonconformities are found, the opportunity may exist to resolve them before widespread market distribution occurs."
+  sampling "Surveillance samples are taken periodically from the point of production (5.3.5; Table 1, VI b)."
+  attestation_object ongoing_production
+  determination { testing inspection design_appraisal service_process_assessment other_determination }
+  attestation { issue_statement grant_use_of_statement mark_licensing }
+  surveillance {
+    required true
+    activities { factory_sampling production_assessment }
+  }
+  notes {
+    "Provides no indication of the distribution channel's impact on conformity, but serious nonconformities may be resolved before widespread market distribution occurs (5.3.5)."
+  }
+}
+
+scheme_type type_4 {
+  label "scheme type 4"
+  clause "5.3.6"
+  description "The surveillance part of this scheme allows for the choice between periodically taking samples of the product from the point of production, or from the market, or from both, and subjecting them to determination activities to check that items produced subsequent to the initial attestation fulfil the specified requirements. The surveillance includes periodic assessment of the production process. This scheme can both indicate the impact the distribution channel plays on conformity and provide a premarket mechanism to identify and resolve serious nonconformities. Significant duplication of effort may take place for those products whose conformity is not affected during the distribution process."
+  sampling "Surveillance samples are taken periodically from the point of production, or from the market, or from both — the choice is defined within the scheme (5.3.6; Table 1, VI a + b)."
+  attestation_object ongoing_production
+  determination { testing inspection design_appraisal service_process_assessment other_determination }
+  attestation { issue_statement grant_use_of_statement mark_licensing }
+  surveillance {
+    required true
+    activities { market_sampling factory_sampling production_assessment }
+  }
+  notes {
+    "Combines the type-2 and type-3 indications (distribution-channel impact AND a premarket mechanism), at the price of possible duplicated effort for products whose conformity is not affected during distribution (5.3.6)."
+  }
+}
+
+scheme_type type_5 {
+  label "scheme type 5"
+  clause "5.3.7"
+  description "The surveillance part of this scheme allows for the choice between periodically taking samples of the product either from the point of production, or from the market, or from both, and subjecting them to determination activities to check that items produced subsequent to the initial attestation fulfil the specified requirements. The surveillance includes periodic assessment of the production process, or audit of the management system, or both. The extent to which the four surveillance activities are conducted may be varied for a given situation, as defined in the scheme. If the surveillance includes audit of the management system, an initial audit of the management system will be needed."
+  sampling "Surveillance samples are taken periodically from the point of production, or from the market, or from both — the extent of the four surveillance activities may be varied for a given situation, as defined in the scheme (5.3.7; Table 1, VI a–d)."
+  attestation_object ongoing_production
+  determination { testing inspection design_appraisal service_process_assessment other_determination }
+  attestation { issue_statement grant_use_of_statement mark_licensing }
+  surveillance {
+    required true
+    activities { market_sampling factory_sampling production_assessment management_system_audit }
+  }
+  notes {
+    "If the surveillance includes audit of the management system, an initial audit of the management system will be needed (5.3.7)."
+    "ISO/IEC Guide 28 is the often-used and well-tried model for a product certification scheme corresponding to scheme type 5 (Table 1, Note b)."
+  }
+}
+
+scheme_type type_6 {
+  label "scheme type 6"
+  clause "5.3.8"
+  description "This scheme is mainly applicable to certification of services and processes. Although services are considered as being generally intangible, the determination activities are not limited to the evaluation of intangible elements (e.g. effectiveness of an organization's procedures, delays and responsiveness of the management). In some situations, the tangible elements of a service can support the evidence of conformity indicated by the assessment of processes, resources and controls involved. For both services and processes, the surveillance part of this scheme should include periodic audits of the management system and periodic assessment of the service or process."
+  sampling "Determination activities are not limited to the evaluation of intangible elements — the tangible elements of a service can support the evidence of conformity (e.g. inspection of the cleanliness of vehicles for the quality of public transportation); for processes, determination can include testing and inspection of samples of the resultant product (e.g. welds), if applicable (5.3.8)."
+  attestation_object service_or_process
+  determination { testing inspection design_appraisal service_process_assessment other_determination }
+  attestation { issue_statement grant_use_of_statement mark_licensing }
+  surveillance {
+    required true
+    activities { production_assessment management_system_audit }
+  }
+  notes {
+    "Mainly applicable to certification of services and processes (5.3.8). Table 1's V d) row marks X for type 6 (mark licensing based on the VI surveillance) — the corpus audit's summary table omits this mark; the raw table is authoritative."
+  }
+}
+

package/oiml-cs/framework/declarations.prl

@@ -0,0 +1,145 @@
+# OIML-CS FRAMEWORK — THE DECLARATION MODEL (B 18:2025 §5.5–5.6; PD-08)
+# -----------------------------------------------------------------------------
+# The OIML-CS Declaration as a first-class model (TODO.roadmap/40): the
+# participation register of the scheme (PD-08 clause 4 — every IA, Utilizer
+# and Associate shall sign a Declaration; the Executive Secretary records
+# them). Three declaration kinds, their content slots, the status model
+# (PD-08 cl. 5: a Declaration is initiated, signed, kept current through
+# scope extensions/reductions and periodic-review changes, and recorded by
+# the Executive Secretary), and the SIGNING-GATE invariant (PD-08 clause 5):
+# an OIML Issuing Authority must have signed its Declaration before issuing
+# any OIML certificate or OIML type evaluation report.
+#
+# This file closes the §4.6.7 documented exclusion of
+# 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).
+#
+# Declaration semantics (PD-08, verified against the corpus audit
+# analysis/oiml-cs-corpus-audit-2026-07.md, corpus C):
+#   - IA Declaration scope = instrument categories × Schemes (certificates
+#     and type evaluation reports under Scheme A and/or B — PD-08 cl. 4 a);
+#   - Utilizer/Associate Declaration scope = acceptance per Scheme PLUS any
+#     additional national requirements (3.2) deviating from the
+#     Recommendation (PD-08 cl. 4 b; B 18:2025 §5.6.1–5.6.2);
+#   - Utilizers/Associates specify from which IAs and TLs they accept
+#     reports/test data and whether they accept MTL-based reports
+#     (§5.6.3 — MTL acceptance is voluntary and need not be justified);
+#   - acceptance of legacy MAA certificates + conditions SHALL be detailed
+#     in the Declaration (PD-08 cl. 6; B 18:2025 §15.10), Basic-certificate
+#     acceptance is voluntary (§15.11).
+#
+# Numbering: official published PDF (reference-docs/cs/docs/b018-e25.pdf).
+#
+# This file is the single source of truth; the consumer's
+# data/oiml-cs/framework/declarations.yaml is its GENERATED YAML twin
+# (cd browser && npm run gen:data; schema data/schemas/framework-declarations.yaml).
+# Cross-references (holder kinds, the gate's declaration edge) are checked
+# package-side by the kernel's C120 framework-references-resolve; the
+# consumer's linker R25 still guards the regenerated YAML (incl. the
+# signing-gate's blocks against the abstract-process ids). The gate
+# calculus lives in browser/src/data/framework.ts; the seeded rejection
+# proof in browser/src/__tests__/cs-framework.test.ts.
+declaration_kind issuing_authority_declaration {
+  label "OIML Issuing Authority Declaration"
+  holder issuing_authority
+  clause "5.5.1"
+  procedure "PD-08"
+  definition "Declaration signed by an OIML Issuing Authority accepted for participation in the OIML-CS, indicating its scope for issuing OIML certificates and OIML type evaluation reports under Scheme A and/or Scheme B (§5.5.1)."
+  scope_model categories_x_schemes
+  scheme_a_obligation "When an OIML Issuing Authority is accepted under Scheme A, the OIML Member State shall designate at least one Utilizer for each instrument category concerned, unless the category is not regulated in that Member State (§5.5.1; PD-08 cl. 4 Note 2 — a written explanation to the Executive Secretary)."
+  source {
+    doc "urn:oiml:pub:b:18:2025"
+    clause "5.5.1"
+  }
+}
+
+declaration_kind utilizer_declaration {
+  label "Utilizer Declaration"
+  holder utilizer
+  clause "5.6.1"
+  procedure "PD-08"
+  definition "Declaration signed by a Utilizer indicating its scope of acceptance of OIML certificates and/or OIML type evaluation reports issued under Scheme A and/or Scheme B (§5.6.1)."
+  scope_model categories_x_schemes
+  content additional_national_requirements {
+    clause "5.6.1"
+    description "Additional national requirements (3.2) deviating from the Recommendation — the Utilizer may specify them; acceptance of additional-national-requirement test data is at the Utilizer's discretion and must be stated in the Declaration (PD-09, 4.1)."
+  }
+  content accepted_participants {
+    clause "5.6.3"
+    description "The OIML Issuing Authorities and Test Laboratories from which the Utilizer accepts evaluation reports, test reports and test data for additional national requirements (§5.6.3)."
+  }
+  content mtl_acceptance_policy {
+    clause "5.6.3"
+    description "Whether the Utilizer accepts OIML certificates and/or type evaluation reports issued on the basis of test reports from a Manufacturer's Test Laboratory (§5.6.3) — acceptance is voluntary and requires no justification (PD-08 cl. 6)."
+  }
+  content maa_certificate_acceptance {
+    clause "15.10"
+    description "Conditions for the acceptance of legacy OIML MAA certificates — SHALL be detailed in the Declaration when accepted (PD-08 cl. 6; §15.10). Legacy OIML Basic certificates remain valid and their acceptance is voluntary (§15.11)."
+  }
+  source {
+    doc "urn:oiml:pub:b:18:2025"
+    clause "5.6.1"
+  }
+}
+
+declaration_kind associate_declaration {
+  label "Associate Declaration"
+  holder associate
+  clause "5.6.2"
+  procedure "PD-08"
+  definition "Declaration signed by an Associate indicating its scope of acceptance of OIML certificates and/or OIML type evaluation reports issued under Scheme A and/or Scheme B (§5.6.2) — the same content slots as the Utilizer Declaration."
+  scope_model categories_x_schemes
+  content additional_national_requirements {
+    clause "5.6.2"
+    description "Additional national requirements (3.2), as for the Utilizer Declaration."
+  }
+  content accepted_participants {
+    clause "5.6.3"
+    description "The OIML Issuing Authorities and Test Laboratories from which the Associate accepts reports and test data (§5.6.3)."
+  }
+  content mtl_acceptance_policy {
+    clause "5.6.3"
+    description "Whether the Associate accepts MTL-based certificates/reports (§5.6.3) — voluntary, no justification needed (PD-08 cl. 6)."
+  }
+  content maa_certificate_acceptance {
+    clause "15.10"
+    description "Conditions for the acceptance of legacy OIML MAA certificates (PD-08 cl. 6; §15.10); Basic-certificate acceptance is voluntary (§15.11)."
+  }
+  source {
+    doc "urn:oiml:pub:b:18:2025"
+    clause "5.6.2"
+  }
+}
+
+declaration_status draft {
+  description "Initiated, not yet signed by the participant."
+}
+
+declaration_status signed {
+  description "Signed by the participant and recorded by the Executive Secretary — the only status that discharges the signing gate."
+}
+
+declaration_status suspended {
+  description "The participant is suspended by the Management Committee (§11.4) — no new applications (PD-03 cl. 8)."
+}
+
+declaration_status withdrawn {
+  description "Participation withdrawn; the Declaration no longer grounds issuance or acceptance."
+}
+
+declaration_gate declaration-signed-before-issuance {
+  clause "PD-08 cl. 5"
+  statement "An OIML Issuing Authority shall not issue any OIML certificate or OIML type evaluation report before its Declaration covering the instrument category and Scheme is signed (PD-08 clause 5; B 18:2025 §5.5.1). Evaluation and testing for an application received beforehand may proceed only after the Review Committee has made a positive, unconditional recommendation to the Management Committee — but the certificate/report still cannot be issued until the Declaration is signed or updated (PD-08 clause 5)."
+  holder issuing_authority
+  declaration issuing_authority_declaration
+  blocks { issue evaluation }
+  blocks_note "The gated abstract processes of the scheme process model (evaluation/abstract-processes.yaml): issue (certificate issuance) and evaluation (the OIML type evaluation report — its compilation and release are part of the evaluation step)."
+  scope_checked { category scheme }
+  source {
+    doc "urn:oiml:pub:b:18:2025"
+    clause "5.5.1"
+  }
+}
+

package/oiml-cs/framework/documents.prl

@@ -0,0 +1,118 @@
+# OIML-CS FRAMEWORK — GOVERNING-DOCUMENT HIERARCHY + AUTO-INCLUSION
+# -----------------------------------------------------------------------------
+# The governing-document hierarchy of the OIML-CS (B 18:2025, clause 6)
+# with its precedence rule, and the automatic-inclusion conditions of
+# clause 4 (§4.2): when a category of measuring instrument enters the
+# OIML-CS — the precondition the scheme lifecycle's automatic Scheme B
+# entry keys on (framework/schemes.prl, §15.1).
+#
+# The per-document models of the corpus (PD-01…PD-09, CID-01, OD-01/02)
+# are tasks 42–43; this file models the HIERARCHY and the entry conditions
+# only. PD-05 (the certification process) already has its model in this
+# package (specification/requirements/cs.prl + the consumer's
+# evaluation/abstract-processes.yaml + execution/test-report-checklist.yaml).
+#
+# Numbering: official published PDF (reference-docs/cs/docs/b018-e25.pdf).
+#
+# This file is the single source of truth; the consumer's
+# data/oiml-cs/framework/documents.yaml is its GENERATED YAML twin
+# (cd browser && npm run gen:data; schema data/schemas/framework-documents.yaml).
+# The approved_by organ edges are checked package-side by the kernel's
+# C120 framework-references-resolve; the consumer's linker R25 still
+# guards the regenerated YAML.
+framework_document b18 {
+  rank 1
+  doc "OIML B 18"
+  title "Framework for the OIML Certification System (OIML-CS)"
+  approved_by ciml
+  clause "6 a)"
+  source {
+    doc "urn:oiml:pub:b:18:2025"
+    clause "6"
+  }
+}
+
+framework_document cid-01 {
+  rank 2
+  doc "OIML-CS CID-01"
+  title "Clarification and Interpretation Document"
+  approved_by management_committee
+  clause "6 b)"
+  note "Clarifications and interpretations of OIML-CS documents intended as guidance and additional information; they do not supersede the text of the current editions (CID-01, clause 2)."
+  source {
+    doc "urn:oiml:pub:b:18:2025"
+    clause "6"
+  }
+}
+
+framework_document od {
+  rank 3
+  doc "OIML-CS OD-xx"
+  title "Operational Documents"
+  approved_by management_committee
+  clause "6 c)"
+  source {
+    doc "urn:oiml:pub:b:18:2025"
+    clause "6"
+  }
+}
+
+framework_document pd {
+  rank 4
+  doc "OIML-CS PD-xx"
+  title "Procedural Documents"
+  approved_by management_committee
+  clause "6 d)"
+  source {
+    doc "urn:oiml:pub:b:18:2025"
+    clause "6"
+  }
+}
+
+framework_document guidance {
+  rank 5
+  doc "OIML-CS Guidance, Forms and Templates"
+  title "Guidance, Forms and Templates"
+  approved_by management_committee
+  clause "6 e)"
+  source {
+    doc "urn:oiml:pub:b:18:2025"
+    clause "6"
+  }
+}
+
+document_precedence higher_position_prevails {
+  clause "6"
+  statement "In the event of a conflict, contradiction or inconsistency between the provisions of one of the governing documents and the provisions of another, the provisions of the document listed in a higher position take precedence over the provisions of the document listed in a lower position (clause 6)."
+  source {
+    doc "urn:oiml:pub:b:18:2025"
+    clause "6"
+  }
+}
+
+auto_inclusion auto_inclusion {
+  clause "4.2"
+  statement "Categories of measuring instruments (including families of instruments, modules, or families of modules) are automatically included in the OIML-CS when the relevant OIML Recommendation specifies all of the following (§4.2); the initial placement is Scheme B (§4.3, §15.1)."
+  condition metrological-technical-requirements {
+    clause "4.2 a)"
+    description "The Recommendation specifies the metrological and technical requirements for the category."
+  }
+  condition test-procedures {
+    clause "4.2 b)"
+    description "The Recommendation specifies the test procedures, including (where applicable) the selection of the instrument(s) or module(s) to be tested from the family (§4.4 — what counts as a family/module and the applicable requirements/test procedures for them)."
+  }
+  condition test-report-format {
+    clause "4.2 c)"
+    description "The Recommendation specifies the OIML test report format."
+  }
+  condition evaluation-report-format {
+    clause "4.2 d)"
+    description "The Recommendation specifies the OIML type evaluation report format."
+  }
+  note "The two report formats (conditions c and d) may be specified in separate Parts of a Recommendation or combined in one Part (§4.2 Note). The BIML maintains the list of the categories in the OIML-CS with references to the relevant Recommendations on the OIML website (§4.5)."
+  source {
+    doc "urn:oiml:pub:b:18:2025"
+    clause "4.2"
+  }
+}
+