Executable standards
Process requirements and data requirements expressed in a language a computer can read and run — not just a document humans have to interpret.
Executable standards modelling
Primmel turns ISO, BSI, and OIML standards into typed, machine-readablerunnable models. Process flows, data requirements, and evidence — in one plain-text .prl file.
root HelloWorld
metadata {
title "Hello World"
namespace "HelloWorld"
}
role Greeter { name "Greeter" }
start_event Start { }
end_event Done { }
process Greet {
name "Greet the world"
actor Greeter
}
canvas Root {
elements {
Start { x 0 y 0 }
Greet { x 0 y 100 }
Done { x 0 y 200 }
}
process_flow {
E1 { from Start to Greet }
E2 { from Greet to Done }
}
}Today
With Primmel
.prl models a computer can parse and runArchitecture
From the moment a reference model is published to the moment an auditor hands down a verdict — each pillar has a distinct actor and a distinct artifact.
Why Primmel
Process requirements and data requirements expressed in a language a computer can read and run — not just a document humans have to interpret.
One canonical model per standard. Auditors, implementers, and certifiers all read from the same artifact.
Map your own processes and controls onto any Primmel-modelled standard. Reuse, extend, and specialise without forking the source.
Built-in primitives for classes, processes, gateways, provisions, and measurements.
Every requirement carries evidential hooks. Auditors locate compliance evidence by following the model.
A public language, available for any standards organisation to adopt.
Read the introduction, then build your first .prl model.