@oimlsmart/primmel-packages 0.1.0

package/acme-rs180/model/rs180.prl

@@ -0,0 +1,236 @@
+# ─────────────────────────────────────────────────────────────────────
+# ACME RS-180 — the product model (TODO.roadmap/36; doctrine ch. 15
+# §15.2; the acme-lc500 pattern). *** FICTIONAL DEMO PRODUCT. *** A
+# manufacturer authors their product model exactly as any subject
+# model — the full IS/HAS/DOES anatomy:
+#   IS   design parameters, the classification values stated on R 91's
+#        category axes (5.1–5.5) and the D 11 environment classes (6.17)
+#        as designed conditions, promises, the endpoint declaration,
+#        metadata, provenance (the type-evaluation certificate — the
+#        promises-as-verified provenance, §15.2);
+#   HAS  exhibited attributes, the characteristics the standard's tests
+#        compute, the operational state, the serve bindings;
+#   DOES the emission behavior (the Doppler spectrum) and the self-test
+#        (the checking facility, R 91-1, 7.5).
+#
+# Quantity-typed design parameters carry their literal as the qualifier
+# string "<value> <unit>" — the design-time vocabulary a consumer's
+# abstract import validates against (§15.3 mode 1, computed by the
+# platform's product-coverage gate).
+#
+# The product is STATIONARY-only (R 91-1, 5.1.a): no ego speed meter,
+# no moving-MPE class — the A/B class dimension (6.15.1) does not apply
+# and is honestly absent, not hidden.
+# ─────────────────────────────────────────────────────────────────────
+
+quantity_register si {
+  kind speed { dimensions { L 1 T -1 } si_unit "m/s" description "Speed of the target vehicle." }
+  unit kmh { symbol "km/h" label "kilometres per hour" kind speed factor 0.277778 }
+  kind frequency { dimensions { T -1 } si_unit "Hz" description "Frequency of the emitted microwave radiation." }
+  unit GHz { symbol "GHz" label "gigahertz" kind frequency factor 1000000000 }
+  kind power { dimensions { L 2 M 1 T -3 } si_unit "W" description "Emitted microwave power." }
+  unit mW { symbol "mW" label "milliwatt" kind power factor 0.001 }
+  kind angle { si_unit "rad" description "Beam width / measurement angle." }
+  unit deg { symbol "°" label "degree" kind angle factor 0.0174533 }
+  kind temperature { dimensions { Θ 1 } si_unit "K" description "Temperature." }
+  unit degC { symbol "°C" label "degree Celsius" kind temperature offset 273.15 }
+  kind length { dimensions { L 1 } si_unit "m" description "Distance to the target vehicle." }
+  unit m { symbol "m" label "metre" kind length factor 1 }
+  kind ratio { si_unit "1" description "Relative quantity." }
+  unit % { symbol "%" label "percent" kind ratio factor 0.01 }
+  kind dimensionless { si_unit "1" }
+  unit dB { symbol "dB" label "decibel" kind dimensionless }
+  unit dimensionless { label "dimensionless" kind dimensionless }
+}
+
+attribute_definition indication {
+  symbol "v"
+  name "Indicated speed"
+  definition "The indicated speed of the target vehicle — the served live reading, an integer km/h value (the product's answer to R 91-1, 6.2)."
+  quantity_kind speed
+  unit "km/h"
+  value_type QuantityValue
+  origin measured
+  scope sample
+  category metrological
+}
+
+attribute_definition high_res_speed {
+  symbol "v_hr"
+  name "High-resolution speed value"
+  definition "Speed value with further decimal digits, read via the test interface (the product's answer to R 91-1, 6.3 — metrologically relevant in linearity/influence/disturbance tests)."
+  quantity_kind speed
+  unit kmh
+  value_type QuantityValue
+  origin measured
+  scope sample
+  category metrological
+}
+
+attribute_definition reference_speed {
+  symbol "v_ref"
+  name "Reference speed"
+  definition "Reference measured speed by the reference speed meter or simulator, read from the twin's test context (R 91-3 symbols)."
+  quantity_kind speed
+  unit kmh
+  value_type QuantityValue
+  origin design-fixed
+  scope sample
+  category metrological
+}
+
+attribute_definition simulated_speed {
+  symbol "v_sim"
+  name "Simulated speed (self-check)"
+  definition "Simulated speed value produced by the checking facility's independent frequency source during self-check (the product's answer to R 91-1, 7.5)."
+  quantity_kind speed
+  unit kmh
+  value_type QuantityValue
+  origin measured
+  scope sample
+  category metrological
+}
+
+state_machine rs_operational {
+  kind operational
+  initial off
+  states { off warming ready measuring fault }
+  transition off -> warming action power_on
+  transition warming -> ready action warmed
+  transition ready -> measuring action start_measurement
+  transition measuring -> ready action stop_measurement
+  transition [off, warming, ready, measuring] -> fault action fault_detected
+}
+
+behavior radar_emission {
+  kind temporal
+  stimulus time
+  response "The emitted K-band microwave spectrum: the frequency peaks hold the specified band, drift ≤ ±0.2 % over 2 years, and the side lobes stay ≤ −20 dB below the main beam and are never used for measurement (the product's answer to R 91-1, 6.10)."
+}
+
+behavior self_test {
+  kind procedural
+  stimulus invoke
+  response "The instrument runs its checking facility — an independent frequency source simulating speed over the whole measurement chain from detection to display/storage (the product's answer to R 91-1, 7.5); a detected error, defect or significant fault gives an error message, inhibits further measurements and drives the operational state machine to fault (R 91-1, 6.18.4)."
+}
+
+subject RS180 {
+  is {
+    metadata {
+      name "RS-180 radar speed meter model"
+      designation "RS-180 stationary Doppler radar speed meter (K-band, tripod-mounted, manual triggering)"
+    }
+    provenance {
+      manufacturer "ACME Traffic Systems GmbH (FICTIONAL — demo manufacturer)"
+      certificate "R91/2025-DE-25-018"
+      type_evaluation_report "ACME-TE-2025-033"
+      promises_as_verified "stationary MPE over 20–180 km/h and −10…+50 °C (the certificate's content — the claims as verified, distinct from the claims as declared, §15.2)"
+    }
+    design_parameters {
+      v_min_range : "20 km/h"
+      v_max_range : "180 km/h"
+      f_band : "24.125 GHz"
+      p_radar : "10 mW"
+      bw_h : "12 deg"
+      bw_v : "6 deg"
+      side_lobe : "-24 dB"
+      freq_drift_2y : "0.1 %"
+      speed_res : "1 km/h"
+      d_max_ident : "600 m"
+      t_min : "-10 degC"
+      t_max : "50 degC"
+      t_smin : "-25 degC"
+      t_smax : "70 degC"
+    }
+    designed_conditions {
+      climatic_environment_class H3
+      mechanical_environment_class M2
+      electromagnetic_environment_class E2
+      note "The rated environment classes per OIML D 11 (R 91-1, 6.17): H3 open air moderate zones, M2 static incl. mobile, E2 AC-mains/DC-standalone supply — declared values, never re-modelled axes."
+    }
+    promises {
+      mpe_within {
+        target error_hold
+        level symbolic stationary-mpe
+        conditions ocl{self.temperature >= rated.t_min and self.temperature <= rated.t_max}
+        statement "Holds the stationary MPE — ±3 km/h up to and including 100 km/h, ±3 % above (R 91-1, 6.4) — across the rated operating conditions."
+        verified_by { oiml-r91#/req/metrological/mpe-stationary }
+      }
+      linearity_within {
+        target linearity_hold
+        level symbolic linearity-limit
+        statement "The high-resolution error stays within the linearity limit — ±1 km/h up to and including 100 km/h, ±1 % above (R 91-1, 6.5)."
+        verified_by { oiml-r91#/req/metrological/linearity-limit }
+      }
+      temp_envelope {
+        target error_hold
+        level range { min -10 max 50 unit degC }
+        conditions "over the rated temperature range"
+        statement "The rated temperature envelope spans −10…+50 °C operating, −25…+70 °C storage (R 91-1, 6.16 Table 1)."
+        verified_by { oiml-r91#/req/metrological/operating-conditions-minimum }
+      }
+      spectrum_holds {
+        target radar_emission
+        statement "The emitted frequency spectrum stays within the specified 24.125 GHz band (R 91-1, 6.10)."
+        verified_by { oiml-r91#/req/category-doppler-radar/frequency-spectrum }
+      }
+      spectrum_stable_2y {
+        target radar_emission
+        level { value 0.2 unit % }
+        statement "The frequency peaks drift no more than ±0.2 % within 2 years (R 91-1, 6.10); the design budget is 0.1 %."
+        verified_by { oiml-r91#/req/category-doppler-radar/spectrum-stability }
+      }
+      side_lobe_guard {
+        target radar_emission
+        level { value -20 unit dB }
+        statement "Side lobes stay below −20 dB relative to the main beam (design value −24 dB) and are never used for measurement (R 91-1, 6.10)."
+        verified_by { oiml-r91#/req/category-doppler-radar/side-lobe }
+      }
+      self_check_within {
+        target self_test
+        level { value 1 unit % }
+        statement "The self-check holds ±1 % of the simulated speed for all values (R 91-1, 7.5 — the only pure-relative, tierless error limit); it runs at every power-on and at least once per day."
+        verified_by { oiml-r91#/req/technical/checking-facilities }
+      }
+      fault_annunciation {
+        target self_test
+        statement "Significant faults are detected and annunciated — the instrument gives an error message, inhibits further measurements, produces no evidence file, and drives its operational state to fault (R 91-1, 6.18.4)."
+        verified_by { oiml-r91#/req/metrological/disturbances }
+      }
+    }
+    endpoint rs180_api {
+      operation get_indication { kind query serves { indication } payload { quantity_kind speed unit km/h timestamp true } }
+      operation watch_state { kind subscribe serves { state environmental_context } payload { quantity_kind state unit dimensionless timestamp true } }
+      operation run_self_test { kind invoke does { self_test } payload { quantity_kind diagnostic_report unit dimensionless timestamp true } }
+      access { public { get_indication } registered { watch_state } authority { run_self_test } }
+      profile rest_json
+    }
+  }
+  has {
+    attributes {
+      indication : speed test_dependent
+      high_res_speed : speed test_dependent
+      reference_speed : speed test_dependent
+      simulated_speed : speed test_dependent
+    }
+    dimensions {
+      mode_of_use : stationary
+      installation_principle : mobile
+      working_principle : doppler-radar
+      triggering : manual
+      cosine_compensation : along-the-road
+    }
+    characteristics {
+      error_hold dv = ocl{self.indication - self.reference_speed}
+      linearity_hold dv_hr = ocl{self.high_res_speed - self.reference_speed}
+    }
+    state rs_operational
+    serve sample.indication via get_indication { fresh_within 5s }
+    serve sample.state via watch_state { fresh_within 1s }
+    serve sample.environmental_context via watch_state { fresh_within 1s }
+  }
+  does {
+    behavior radar_emission
+    behavior self_test
+  }
+}

package/acme-rs180/package.primmel

@@ -0,0 +1,47 @@
+# ─────────────────────────────────────────────────────────────────────
+# ACME RS-180 — the product reference package (TODO.roadmap/36; doctrine
+# ch. 15, the model supply chain; the acme-lc500 pattern applied to
+# R 91 territory — the radar speed meter's half of "R 91 also needs
+# simulated SMART digital twin and full model", 2026-07-28).
+#
+# *** FICTIONAL DEMO MANUFACTURER — NO REAL PRODUCT. ***
+# "ACME Traffic Systems GmbH" is an invented company (the qms-ref/
+# isms-ref/acme-lc500 demo spirit); the RS-180 is an invented reference
+# Doppler radar speed meter. Every value below is plausible demo
+# content, not a real instrument's data sheet.
+#
+# The manufacturer side of the supply chain: ACME's RS-180 radar speed
+# meter model as a SUBJECT model (the oiml-rec methodology applied by
+# the manufacturer — full IS/HAS/DOES anatomy), with every conformance-
+# relevant aspect and promise mapped aspect-by-aspect to R 91
+# (model/r91-map.prl). The mapping is the manufacturer's conformance
+# claim made computable: "our v_min/v_max range is your measuring
+# interval; our emission behavior answers your Doppler-radar spectrum
+# requirements" (§15.2). R 91 is radar SPEED measurement (Doppler,
+# 20–180 km/h per R 91-1, 6.1) — never level gauging.
+#
+# The package is a REFERENCE model — it states what the product is and
+# claims; it is not derived from the Recommendation and composes nothing
+# from it (no uses edge): the two are related by mapping only. Consumers
+# use it in the §15.3 modes (abstract import version-pinned per C83;
+# live integration over the declared endpoint — the sim-instruments
+# twin-schema generator reads the serve declarations IN PLACE, never
+# copied, via the .prl adapter).
+#
+# The twin-cert program's R 91 expansion (oiml-twin-cert maps_to
+# oiml-r60 today) is a SEPARATE leg — not this package.
+# ─────────────────────────────────────────────────────────────────────
+package {
+  id acme-rs180
+  kind product_reference
+  manufacturer "ACME Traffic Systems GmbH (FICTIONAL — demo manufacturer)"
+  product "RS-180"
+  title "ACME RS-180 Doppler radar speed meter — product reference model (FICTIONAL demo)"
+  version "2025"
+  editions { 2025 }
+  status current
+  validity { from 2025-06-01 }
+  maps_to { oiml-r91 }
+  default_spelling eng-Latn
+  description "ACME's RS-180 stationary Doppler radar speed meter (20–180 km/h per R 91-1, 6.1; K-band 24.125 GHz; climatic/mechanical/electromagnetic classes H3/M2/E2 per OIML D 11) as a product reference model: the full subject anatomy, the rs180_api twin endpoint, and the aspect-by-aspect mapping to OIML R 91 — the manufacturer's conformance claim made computable (TODO.roadmap/36, doctrine ch. 15). FICTIONAL demo manufacturer, clearly marked."
+}

package/ims-demo/model/ims.prl

@@ -0,0 +1,23 @@
+# ─────────────────────────────────────────────────────────────────────
+# ims-demo — the integrated management system's own processes
+# (TODO.v2/02 VL-3; view-lens-design.md Q4).
+#
+# *** FICTIONAL TEACHING MODEL. *** Five invented operating processes.
+# The mappings that read them against the toy references live in
+# qms-map.prl / isms-map.prl (one map_profile per reference); this file
+# declares only the implementation's own anatomy.
+#
+#   PolicyAndObjectives — fulfils TWO qms-ref components (multi-target).
+#   InternalAudit       — the SHARED process: fulfils qms-ref AND
+#                         isms-ref ("write once, comply twice").
+#   RiskProcess         — maps the isms-ref PARENT (inheritance).
+#   AccessAndIncidents  — fulfils one isms-ref gateway branch.
+#   LogisticsOutsourcing— mapped NOWHERE on purpose: the composed
+#                         report's uncovered-implementation row.
+# ─────────────────────────────────────────────────────────────────────
+
+process PolicyAndObjectives { name "Policy and objectives" }
+process InternalAudit { name "Internal audit" }
+process RiskProcess { name "Risk process" }
+process AccessAndIncidents { name "Access and incidents" }
+process LogisticsOutsourcing { name "Logistics outsourcing" }

package/ims-demo/model/isms-map.prl

@@ -0,0 +1,60 @@
+# ─────────────────────────────────────────────────────────────────────
+# ims-demo ⇒ isms-ref — the ISMS lens (TODO.v2/02 VL-3;
+# view-lens-design.md Q4). FICTIONAL teaching content — isms-ref is a
+# toy reference, no ISO/IEC 27001 content.
+#
+# The `isms-ref#…` declarations below are LOCAL ALIASES of the reference
+# elements this model maps to (the C21 alias discipline) — a NESTED
+# ALIAS FOREST so the linter's C23 fallback tree is the real reference
+# shape (the gateway-parent alias re-declares `child_composition
+# gateway`). Aliases are cited, never content-merged.
+#
+# The mapping makes the deterministic ISMS table: RiskProcess maps the
+# RiskManagement PARENT — both children covered by INHERITANCE (full,
+# inheritedFrom RiskManagement) and two INHERITED proposals fire; the
+# treatment child additionally carries its own direct pair from the
+# SHARED InternalAudit process (a direct pair wins over the inherited
+# cover). One IsmsOperation branch fulfilled ⇒ the gateway parent
+# aggregates to minimal, the other branch stays none. Result: full 4 /
+# minimal 1 / none 1 (+2 inherited proposals) — pinned by the coverage
+# block (C23 tripwires; coverage is COMPUTED, never authored).
+# ─────────────────────────────────────────────────────────────────────
+
+process isms-ref#RiskManagement {
+  name "alias: isms-ref Risk management"
+  process isms-ref#RiskAssessment { name "alias: isms-ref Risk assessment" }
+  process isms-ref#RiskTreatment { name "alias: isms-ref Risk treatment" }
+}
+
+process isms-ref#IsmsOperation {
+  name "alias: isms-ref ISMS operation"
+  child_composition gateway
+  process isms-ref#AccessControl { name "alias: isms-ref Access control" }
+  process isms-ref#IncidentResponse { name "alias: isms-ref Incident response" }
+}
+
+map_profile isms-ref {
+  description "The IMS read against the toy ISMS reference: the integrated risk process fulfils the whole risk-management subtree (inheritance), the SHARED internal audit directly fulfils risk treatment (write once, comply twice), and the access-and-incidents operation fulfils one gateway branch."
+  mapping {
+    InternalAudit -> isms-ref#RiskTreatment {
+      description "Audit findings raise risk-treatment actions and follow them up."
+      justification "The same audit programme that drives QMS corrective action also tracks the ISMS risk-treatment plan — write once, comply twice."
+    }
+    RiskProcess -> isms-ref#RiskManagement {
+      description "The IMS's single risk process runs the whole ISMS risk-management cycle."
+      justification "One integrated risk process performs assessment and treatment as sub-activities, so the pair is asserted at the parent and covers the subprocess tree by inheritance."
+    }
+    AccessAndIncidents -> isms-ref#AccessControl {
+      description "The access-and-incidents operation enforces access control day to day."
+      justification "The operation administers access rights and reviews them on the ISMS schedule."
+    }
+  }
+  coverage {
+    isms-ref#RiskManagement full
+    isms-ref#RiskAssessment full
+    isms-ref#RiskTreatment full
+    isms-ref#IsmsOperation minimal
+    isms-ref#AccessControl full
+    isms-ref#IncidentResponse none
+  }
+}

package/ims-demo/model/qms-map.prl

@@ -0,0 +1,73 @@
+# ─────────────────────────────────────────────────────────────────────
+# ims-demo ⇒ qms-ref — the QMS lens (TODO.v2/02 VL-3;
+# view-lens-design.md Q4). FICTIONAL teaching content — qms-ref is a
+# toy reference, no ISO 9001 content.
+#
+# The `qms-ref#…` declarations below are LOCAL ALIASES of the reference
+# elements this model maps to (the C21 alias discipline, the
+# acme-lc500/quarry-belt-scale precedent) — declared as a NESTED ALIAS
+# FOREST so the linter's C23 fallback tree is the real reference shape
+# (an alias of a gateway parent re-declares `child_composition
+# gateway`). Aliases are cited, never content-merged.
+#
+# The mapping makes the deterministic QMS table: both PlanQms children
+# fulfilled by ONE multi-target source ⇒ PlanQms aggregates to full and
+# a CLOSURE proposal fires; one ImproveQms branch fulfilled ⇒ the
+# gateway parent aggregates to minimal, the other branch stays none.
+# Result: full 4 / minimal 1 / none 1 (+1 closure proposal) — pinned by
+# the coverage block (C23 tripwires; coverage is COMPUTED, the block
+# only asserts what the calculus already proves).
+# ─────────────────────────────────────────────────────────────────────
+
+process qms-ref#PlanQms {
+  name "alias: qms-ref Plan the QMS"
+  process qms-ref#QualityPolicy { name "alias: qms-ref Quality policy" }
+  process qms-ref#QualityObjectives { name "alias: qms-ref Quality objectives" }
+}
+
+process qms-ref#ImproveQms {
+  name "alias: qms-ref Improve the QMS"
+  child_composition gateway
+  process qms-ref#CorrectiveAction { name "alias: qms-ref Corrective action" }
+  process qms-ref#ContinualImprovement { name "alias: qms-ref Continual improvement" }
+}
+
+map_profile qms-ref {
+  description "The IMS read against the toy QMS reference: the integrated policy process fulfils both planning children (multi-target), the shared internal audit fulfils one improvement branch — the auditor-facing half of the two-reference demonstration."
+  mapping {
+    PolicyAndObjectives -> qms-ref#QualityPolicy {
+      description "The IMS's single policy process issues and maintains the quality policy."
+      justification "One integrated policy process is operated for the whole management system; the quality policy is one of its standing outputs."
+    }
+    PolicyAndObjectives -> qms-ref#QualityObjectives {
+      description "The same policy process cascades the quality objectives and reviews them."
+      justification "Objectives are set, tracked and reviewed inside the one integrated policy-and-objectives cycle."
+    }
+    InternalAudit -> qms-ref#CorrectiveAction {
+      description "Audit findings open corrective actions and track them to closure."
+      justification "The integrated audit programme is the trigger and the tracking mechanism the QMS corrective-action process requires."
+    }
+  }
+  coverage {
+    qms-ref#PlanQms full
+    qms-ref#QualityPolicy full
+    qms-ref#QualityObjectives full
+    qms-ref#ImproveQms minimal
+    qms-ref#CorrectiveAction full
+    qms-ref#ContinualImprovement none
+  }
+}
+
+# The role-scoped sub-lens (the kernel applyView second filter). READ-
+# ONLY: a view selects implementation voices, it never edits the
+# mapping (C26). Roles are DISPLAY-ONLY metadata — rendered as badges,
+# never gated (controller decision 1). NOTE the bracketed roles
+# spelling: `roles [qms-manager]` — the kernel's list tokenizer strips
+# the wrapping characters unconditionally, so the bare spelling
+# `roles qms-manager` would silently mis-tokenize (the VL-1 quirk).
+view_profile QmsLeadership {
+  description "The QMS leadership lens: only the policy-and-objectives and internal-audit voices are audible; the rest of the IMS is filtered out."
+  roles [qms-manager]
+  visible { PolicyAndObjectives InternalAudit }
+  against qms-ref
+}

package/ims-demo/package.primmel

@@ -0,0 +1,42 @@
+# ─────────────────────────────────────────────────────────────────────
+# ims-demo — a FICTIONAL integrated management system (IMS) and the
+# worked example of multi-reference mapping (TODO.v2/02 VL-3, feeding
+# TODO.v2/03; the analysis view-lens-design.md Q4 skeleton).
+#
+# *** FICTIONAL TEACHING MODEL. *** One small organization runs five
+# invented operating processes and reads them against TWO toy reference
+# models — qms-ref and isms-ref (themselves fictional, no ISO content)
+# — via one map_profile per reference. The mapping design is enumerated
+# so every calculus rule fires deterministically (the per-reference
+# tables: QMS full 4 / minimal 1 / none 1 + 1 closure proposal; ISMS
+# full 4 / minimal 1 / none 1 + 2 inherited proposals):
+#
+#   PolicyAndObjectives — fulfils TWO QMS components (multi-target).
+#   InternalAudit       — the SHARED process: fulfils qms-ref AND
+#                         isms-ref — "write once, comply twice" made
+#                         visible (the composed report's shared source).
+#   RiskProcess         — maps the isms-ref PARENT (inheritance down).
+#   AccessAndIncidents  — fulfils one ISMS branch (gateway minimum).
+#   LogisticsOutsourcing— mapped NOWHERE: the deliberately unmapped
+#                         element feeding the composed report's
+#                         uncovered-implementation row.
+#
+# The package IMPORTS NOTHING (no uses): the two references are related
+# to this implementation by MAPPING only — a map_profile namespace is
+# never an import (C24). Package kind: NONE declared — reference and
+# implementation are ROLES at the ends of a mapping chain, not manifest
+# kinds (view-lens-design.md Q4; the quarry-belt-scale precedent).
+#
+# Authored-native: PRL is the only source form (excluded by name in
+# browser/scripts/ssot-guard.ts AUTHORED_NATIVE; guarded by
+# `primmel check` via the from-packages proof). Never generated into
+# the data trees.
+# ─────────────────────────────────────────────────────────────────────
+package {
+  id ims-demo
+  title "Toy integrated management system (fictional) — the multi-reference mapping worked example"
+  version "1.0.0"
+  editions { 1.0.0 }
+  default_spelling eng-Latn
+  description "A tiny FICTIONAL integrated management system: five invented processes read against the two toy references qms-ref and isms-ref through one map_profile each, plus one role-scoped view_profile. The deterministic worked example for the view/lens calculus and the multi-reference composition fold (TODO.v2/02 VL-3, view-lens-design.md Q4; feeds TODO.v2/03)."
+}

package/isms-ref/model/isms.prl

@@ -0,0 +1,34 @@
+# ─────────────────────────────────────────────────────────────────────
+# isms-ref — the toy ISMS process tree (TODO.v2/02 VL-3;
+# view-lens-design.md Q4).
+#
+# *** FICTIONAL TEACHING MODEL — NO ISO/IEC 27001 CONTENT. *** These
+# are invented processes, not clauses of any real standard.
+#
+# The tree is deliberately the smallest shape that exercises every
+# calculus rule when ims-demo maps into it:
+#
+#   RiskManagement — a SERIAL parent and the INHERITANCE target: ims-demo
+#                    maps the PARENT, so both children are covered by
+#                    downward inheritance (full, inheritedFrom
+#                    RiskManagement) and INHERITED proposals fire for
+#                    both descendants. One child additionally carries its
+#                    own direct pair — a direct pair wins over the
+#                    inherited cover.
+#   IsmsOperation  — a GATEWAY parent: one child mapped-full, the other
+#                    untouched ⇒ the parent aggregates to MINIMAL and the
+#                    untouched child stays NONE (the visible ISMS gap).
+# ─────────────────────────────────────────────────────────────────────
+
+process RiskManagement {
+  name "Risk management"
+  process RiskAssessment { name "Risk assessment" }
+  process RiskTreatment { name "Risk treatment" }
+}
+
+process IsmsOperation {
+  name "ISMS operation"
+  child_composition gateway
+  process AccessControl { name "Access control" }
+  process IncidentResponse { name "Incident response" }
+}

package/isms-ref/package.primmel

@@ -0,0 +1,35 @@
+# ─────────────────────────────────────────────────────────────────────
+# isms-ref — a FICTIONAL toy information-security-management-system
+# reference model (TODO.v2/02 VL-3; the analysis view-lens-design.md Q4
+# worked example).
+#
+# *** FICTIONAL TEACHING MODEL — NO ISO/IEC 27001 CONTENT. ***
+# This package is a tiny invented process tree that merely EXERCISES the
+# coverage calculus (downward inheritance from a mapped parent, the
+# gateway minimum, inherited-pair discovery). It is not, and does not
+# derive from, ISO/IEC 27001 or any other real management-system
+# standard (controller decision 2: toy references — licensing and
+# maintenance both avoided; the calculus mechanics are what's being
+# proven). Any resemblance to a real standard's clause structure is
+# coincidental and unintentional.
+#
+# Package kind: NONE declared (absent = the ordinary default) — per the
+# design (view-lens-design.md Q4), "reference" and "implementation" are
+# ROLES at the ends of a mapping chain, not manifest kinds (the
+# quarry-belt-scale precedent; none of core/module/rec/
+# product_reference/certification_program applies to fictional teaching
+# content).
+#
+# Authored-native: PRL is the only source form (excluded by name in
+# browser/scripts/ssot-guard.ts AUTHORED_NATIVE; guarded by
+# `primmel check` via the from-packages proof). Never generated into
+# the data trees.
+# ─────────────────────────────────────────────────────────────────────
+package {
+  id isms-ref
+  title "Toy ISMS reference model (fictional — teaching model for the view/lens calculus)"
+  version "2026"
+  editions { 2026 }
+  default_spelling eng-Latn
+  description "A tiny FICTIONAL information-security-management-system reference tree (no ISO/IEC 27001 content): one serial parent (the inheritance target) and one gateway parent with two children each — just enough structure for the coverage calculus to inherit downward, apply the gateway minimum, and propose inherited pairs. The reference end of the ims-demo ⇒ isms-ref lens (TODO.v2/02, view-lens-design.md Q4)."
+}

package/iso-iec-17000/package.primmel

@@ -0,0 +1,8 @@
+package {
+  id iso-iec-17000
+  kind core
+  title "OIML SMART iso-iec-17000 layer package"
+  description "ISO/IEC 17000:2020 reference package — the CASCO conformity-assessment vocabulary (clause-referenced terms) and the functional-approach activity taxonomy as a register of classifiable activity kinds (selection, determination + testing/inspection/audit/validation/verification/peer assessment, review, decision, attestation + declaration/certification/ accreditation, surveillance + suspension/withdrawal/expiry/restoration/ appeal/complaint). The resolution register for the activity_kind facet on abstract processes. Composed into each Recommendation via `uses: [iso-iec-17000]` ahead of oiml-cs."
+  provides { iso-iec-17000 ca-terminology-17000 }
+  default_spelling eng-Latn
+}