DMN-TCK conformance
Sutra’s DMN/FEEL evaluator (sutra-dmn + sutra-feel, see
Crates: sutra-feel and sutra-dmn) is checked against the real OMG
DMN Technology Compatibility Kit — the same corpus other DMN
implementations are measured against — rather than relying on an internal test suite alone.
Current standing
| Level | Result |
|---|---|
| Compliance level 2 | 126/126 (100%) |
| Compliance level 3 | 3365/3385 absolute (99.4%), and 100% of attempted assertions (0 semantic failures among cases the engine attempts) |
Measured against the TCK as of 2026-09-17 (commit 0456e1a), including its newest tests for
multiple model imports and DMN 1.5’s implicit type conversions.
The gap between “100% of attempted” and “99.4% absolute” is 20 enumerated assertions the
evaluator deliberately doesn’t attempt: 14 are reflective execution of {java|pmml: …} external
function bodies (the grammar parses and validates their binding shape; invoking one returns a
clear, deliberate semantic rejection rather than a wrong answer), and 6 are dates with nine-digit
years, beyond the range the engine’s temporal values represent. This is
the honest distinction the numbers are built to preserve: a wrong value on a supported construct
is a real conformance defect, and the harness that produces these numbers is built specifically to
never launder one into an “unsupported” bucket. Level 2 has no such gap at all.
What this does and doesn’t tell you
What it tells you: decision tables (all seven OMG hit policies, including COLLECT with aggregation), decision requirement graphs, business knowledge models, decision services, and the breadth of FEEL itself (temporal types and arithmetic, ranges/intervals, list/context comprehensions, string and numeric builtins, filters and projections) behave per specification across a large, independently-authored corpus — not just the cases Sutra’s own contributors thought to write.
What it doesn’t tell you: conformance to a language specification says nothing about Sutra’s BPMN coverage, its channel/transport behavior, its persistence and replica semantics, or its security posture — those are covered elsewhere in this book (see Building BPMN solutions and Architecture). It also isn’t a performance claim — conformance and throughput are separate properties.
Where this comes from
The conformance measurement is produced by a development-time harness in the workspace — it is a
tool contributors run when working on the FEEL/DMN evaluator, not something a user building a
BPMN solution ever needs to invoke. See
Debugging the engine if you’re contributing to
sutra-feel or sutra-dmn and need to reproduce or extend this measurement yourself.
Next
- Rules: DMN, FEEL, and .srl — using DMN inside a Sutra process.
- Crates: sutra-feel and sutra-dmn — using the same evaluator standalone.