Approach
Measured, not asserted.
These four principles decide what we build. More usefully, they decide what we refuse to ship — which is the part that actually protects the operator.
Evidence over intuition
Every claim in a VIML system resolves to a row someone can inspect. Provenance is a feature, not documentation.
- Each figure carries a link to the records that produced it.
- Transform chains are stored, not reconstructed after the fact.
- A claim with no inspectable derivation is treated as a bug.
The refusal
We will not ship a number whose derivation we cannot display on request — however confident the model is.
A broad cloud of assertions contracting to the subset that survives checking. The left extreme is everything a system could claim; the right is only what the evidence actually supports.
Constraints before creativity
We fix the schema, the baseline, and the definition of done first. Unconstrained systems drift toward whatever is easiest to compute.
The refusal
We will not begin modelling against a substrate whose shape is still under negotiation.
Verify against the artifact
Nothing is complete because the code looks right. It is complete when the rendered result has been inspected and measured.
The refusal
We will not report a result we have not observed directly.
Honest negatives
When the data cannot support a conclusion, the system says so. A blank state beats a confident fabrication.
The refusal
We will not fill an empty state with an estimate in order to make a surface look complete.
Contact
If you already have the data, we can show you what it says.
We take on a small number of operators at a time. Engagements start with a read-only audit of what your existing systems already know.