This system does not start with a model. We start by watching real decisions — large numbers of them — and decomposing what kind of choice a person stably makes under different conditions.
Then we simulate: when conditions shift, where does the choice drift? We are not focused on outcomes. We are focused on the conditions under which a person reliably picks one thing over another — which is also why most errors are not accidents. They repeat.
§1Not starting from a model
Most methodologies start with a framework and try to fit reality into it. Decision System works the other way — we start with observation. We watch real decisions, decompose what kind of choice a person stably makes under different conditions, and reverse-engineer the structure from those patterns.
Starting from observation has a benefit: when conditions change, the method doesn’t collapse. Frameworks forced onto reality crack at the edges. Methods grown out of reality reposition themselves. We are not in a rush to package this as a sellable framework, because that would lock its flexibility.
§2The three motions
Decision System has only three working motions: Frame, Pressure-test, and Commit.
Frame is the act of opening up the assumptions you didn’t know you were making, and pulling out the boundaries you treated as fixed. Pressure-test is letting that framing run into adversarial conditions and seeing where it breaks first. Commit is choosing a direction with the breakage made visible — not in spite of it.
These three motions are not a linear pipeline. They cycle. After a commit, new conditions force a new framing; the new framing has to be pressure-tested again. Decision System is not “run once, done.” It is “run enough times that the pattern surfaces.”
§3Axiom Hexa as one surface
Axiom Hexa is the public surface of Decision System on the slice of individual decision pattern — when you complete the assessment, what you see is your own Frame / Pressure-test / Commit shape under founder-grade pressure.
But Axiom Hexa is not the entirety of Decision System. The same scaffold also grows into team-observation tools, an investment-judgment review process, and an organizational decision-cadence calibration framework — those surfaces are still in development and won’t be rushed out for the sake of being public.
§4Why a scaffold, not a methodology
A methodology is a method that assumes it can be reproduced — step 1, step 2, step 3, anyone using it should get a similar result. A scaffold is different. It is structure, not steps. The point is that you grow your own judgment on top of it.
We chose scaffold over methodology because founder decision contexts can’t be reproduced: different industries, different stages, different teams, different windows of opportunity. Reproducible methods crack at the edges. Adaptive scaffolds hold.
This is also why Decision System won’t ever be packaged as a “five-step book to become a better decider.” Books want closed answers. We want open structure.