Volume I: Primmel Kernel
Volume I, The Primmel Kernel
Section titled “Volume I, The Primmel Kernel”Foundation. This volume operationalizes the IS–HAS–DOES modelling system proven in Volume 0 (Foundation). Where Volume 0 proves the trichotomy is exhaustive, Volume I shows how Primmel turns it into a usable language. If a chapter here ever seems to introduce a ninth modelling term, it is a materialized view (Volume 0 §13), not a new primitive.
Primmel is a domain-specific language for representing SMART standards in an executable form. A Primmel-modelled standard is a structured artifact whose subjects, requirements, processes, data requirements and evidential requirements are defined precisely enough that a computer can validate them, query them, execute them, and reason about them.
Primmel v2 (formerly MMEL) established the four pillars, data,
process, compliance, measurement, and the artifact kinds
.prl / .prd / .prm / .pws. Primmel v3 keeps all of it and adds the
layer the compliance use-case always needed: the subject.
The v2 → v3 delta
Section titled “The v2 → v3 delta”| v2 (today) | v3 (this volume) |
|---|---|
| provisions as text + modality | subjects with a full anatomy (IS/HAS/DOES); requirements as constraints bound to subject aspects |
| processes as canvas nodes | processes as recursive subjects, abstract or executable, with state, registers, executors |
| one model kind | reference vs implementation model kinds, with mapping as the compliance relation |
| mapping coverage (full/minimal/partial) | same calculus, now machine-checked against typed anchor sets |
| data classes + registries | same, plus quantities/units, typed variables, tables/profiles, time primitives |
| models | packages with uses composition, modules, editions, model diff |
| references to clauses | clause + fragment provenance, document reconstruction, text-coverage audit |
| , | multilinguality (ISO 24229), interop projections (ReqIF, RDF/OWL, OpenCDD) |
The chapter map
Section titled “The chapter map”- Philosophy and tiers, why executable standards; the design principles; the tier system that organizes every model; the four artifact kinds.
- Subjects, the center of the primary tier; the IS/HAS/DOES anatomy; the aspect catalog; what makes each aspect IS vs HAS vs DOES.
- Instantiation, definition and instance; the subject chain; Sample as instance of Model; delegation.
- Processes, abstract and executable processes;
the classification facets (
activity_kind,segregation:); the step vocabulary; executors; state; evidence. - Mappings, reference and implementation models; the coverage calculus.
- Data and values, registries, variables, quantities, tables, time.
- Expressions, OCL as the one rule language.
- Packages, composition, modules, editions,
package-level classification (
scheme_type:). - Provenance and documents, fragments,
.prd, reconstruction. - Multilinguality, ISO 24229.
- Validation, schemas, the linker,
primmel check. - Interop, ReqIF, RDF/OWL, OpenCDD.
- Model diff and lifecycle.
- Live twins and continuous compliance, the runtime endgame: served instances, the monitor loop, the model-native passport.
- The model supply chain, manufacturer product reference models, mapped to the standard, consumed as abstract imports or live twins.
- Views and lenses, reading an implementation through a reference: the reference-shaped projection, the CoverageReport as lens, and the multi-reference composition fold.
- Twin certification, certifying the governed projection’s fidelity: the three-layer stack (device, full twin, Primmel twin), the probe channel, the verdict chain, and the twin certificate with its surveillance regime.
- References and relations, the
unified
refconstruct: one typed triple for every citation and every cross-model relationship; the predicate registry; the legacy spellings it unifies; the edges that stay dedicated.
The one-sentence summary
Section titled “The one-sentence summary”A Primmel package models a subject (what it IS, HAS and DOES), constrains it (requirements bound to its aspects), exercises it (processes, tests that constrain inputs, conditions and state while observing outcomes), records the exhibition (evidence in registries), and judges it (verdicts re-executable against the evidence), with every element provenance-anchored to the source document and every implementation mapped to its reference.