Decision Science / DeciMatrix / Active Experiment
Bringing JEV into DeciMatrix: A Hybrid Approach to Decision Simulation
Using a typed, probabilistic model as the decision-evaluation core—and Monte Carlo simulation to explore what could happen next.
DeciMatrix is built around a practical question: when I have to make a decision, how can I evaluate its likely outcomes rather than rely only on intuition? I'm exploring a hybrid design that places JEV at the centre of the evaluation process and uses Monte Carlo simulation as the mechanism for examining a range of possible futures.
01 / THE MODEL
Why JEV caught my attention
JEV, developed by TypeSafe AI, is described as a discriminative AI model rather than a text-generation model. Instead of returning prose, it returns typed values alongside probability estimates and confidence scores. Its outputs are designed to be consumed directly by software.
Another notable characteristic is its ability to perform zero-shot learning for categories supplied at inference time, using the contextual information provided. That makes the model interesting to explore in a decision product where the categories and evaluation criteria may vary from one decision to another.
In this article, I'm treating those capabilities as the model's described interface—not as proof that its outputs are automatically calibrated, causal, or suitable for every decision domain. Those properties would need to be tested in the context of the application.
02 / THE DESIGN HYPOTHESIS
JEV as the evaluation core
My current design hypothesis is to give JEV the role of evaluating a decision against a context supplied by the user and the decision framework. The application could define relevant categories—such as feasibility, expected benefit, downside exposure, or alignment with a user's priorities—and request structured assessments.
The typed outputs, probability estimates, and confidence scores could then become structured inputs to the next stage of the pipeline. This would make the model's assessment inspectable by application logic instead of relying on a generated paragraph as the only result.
The exact schema, category definitions, and mapping from model outputs into simulation variables are still design work. I want those mappings to be explicit, versioned, and testable rather than hidden inside an opaque score.
03 / THE SIMULATION
Monte Carlo as the deduction layer
A single model assessment is only one view of a decision under a particular set of assumptions. Real decisions involve uncertainty: estimates can vary, constraints can change, and the future rarely follows one fixed path.
Monte Carlo simulation offers a way to explore that uncertainty by repeatedly sampling from defined input distributions and calculating the resulting outcomes. In the proposed DeciMatrix flow, JEV's structured assessments would inform selected variables or assumptions; the simulation would then evaluate many possible combinations to produce an outcome distribution rather than one deterministic prediction.
The important distinction is that a model confidence score is not automatically a probability distribution for Monte Carlo sampling. I will need to define and validate the transformation from model outputs to simulation assumptions, and make the assumptions visible to the user.
04 / THE PROPOSED PIPELINE
From decision context to a range of futures
- Capture the decision. Collect the proposed action, context, constraints, goals, and the user's priorities.
- Define evaluation categories. Select the dimensions that matter for this decision and provide their definitions to the model.
- Request structured assessments. Use JEV's typed outputs and associated estimates as the model-evaluation layer.
- Construct simulation assumptions. Translate supported outputs into explicit variables, ranges, dependencies, and distributions—with validation and documented assumptions.
- Run Monte Carlo trials. Sample the uncertain variables repeatedly and calculate outcomes for each trial.
- Explain the results. Present outcome ranges, downside scenarios, sensitivity to assumptions, and the limits of the analysis.
05 / WHAT I WANT TO LEARN
The real question is whether the combination helps
The goal is not to make a simulation look precise. It is to make uncertainty easier to reason about. I want to investigate whether a structured discriminative model can make decision evaluation more adaptable, and whether simulation can turn those assessments into a more useful view of possible outcomes.
That means testing the quality and stability of model assessments, checking how sensitive results are to assumptions, comparing simulated results with baseline approaches, and communicating uncertainty without presenting the output as a guarantee.
At this stage, this is an implementation direction I'm exploring for DeciMatrix—not a claim that the integration is complete or that it can predict the future. The interesting engineering work is in making the boundary between model judgement, simulation assumptions, and calculated outcomes rigorous and transparent.
Project in focus
DeciMatrix
This experiment is part of my ongoing work on DeciMatrix, a decision-support project exploring structured evaluation, risk, and outcome simulation.
Explore the project ↗