Once the system moved beyond principles, the focus shifted to structure.
The question was no longer what should be considered, but how different considerations should relate to each other inside a decision.
The diagram captures that first structural decision.
Separate signals from execution
The method is built around a clear separation.
External signals explain why an idea exists — whether there is enough relevance and stability for it to be worth considering at all.
Internal factors determine whether the idea can survive execution — under real workflow, supply, and human constraints.
These inputs are evaluated independently, before they are ever allowed to interact.
This prevents trend appeal from masking operational fragility, and operational simplicity from justifying ideas with no external relevance.
Feasibility is gated, not blended
At the centre of the system is a gating step.
Rather than blending all inputs into a single score, the method is designed to stop ideas early when risk accumulates in unacceptable ways.
Some conditions cannot be compensated for.
If they are triggered, the concept does not proceed — regardless of its appeal.
This is an intentional design choice.
From ideas to executable structures
Concepts that pass gating are not treated as finished ideas.
They are reduced into constrained ingredient and process structures that remain executable under the identified limits.
This step exists to prevent theoretically appealing concepts from entering development when they cannot be delivered consistently in real service.
Failure is evaluated before it happens
Before a final decision is made, the method explicitly considers the cost of failure.
Not just in financial terms, but in operational disruption and recovery effort.
This shifts attention away from upside narratives and towards downside exposure — while reversibility still exists.
A bounded decision by design
The method produces a bounded outcome: proceed, proceed with conditions, or do not proceed.
It does not extend beyond this point.
Creative development, optimisation, and execution remain human responsibilities.
The system’s role is to ensure that development begins only when it can be justified under real operating conditions.