Decision Systems
How systems can support better operational choices while keeping responsibility and judgment visible.
Research
Research is the public memory of INSODEMA.
Publications, notes and decision models preserve the reasoning behind INSODEMA's systems. They make findings inspectable and allow new understanding to build on documented work.
Research becomes valuable when it changes understanding or improves a decision.
Research direction
From thesis to investigation of real problems.
The question is therefore not merely whether software can be built. It is whether a dependency remains economically, operationally and architecturally justified within the system as a whole.
01
Research Cases
Internal cases show both deliberately replaced and deliberately retained dependencies without marketing inflation.
View Research Cases → 02System Sovereignty
System Sovereignty is not the absence of dependencies. It is the ability to choose them deliberately.
System Sovereignty → 03Problems We Investigate
Problem-first examples show the kinds of friction and dependency that can become research starting points.
Explore problem areas → 04Engine, AI & Trust
INSODEMA deliberately separates operational decision logic, AI assistance and governance. A system can be highly intelligent, adaptable and interoperable without a language model owning its domain decisions.
Engine, AI & Trust → 05Research Partnerships
Organisations can start with a real problem, dependency or operational friction without already knowing the solution.
Open Research Partnerships →Research thesis
Systems, Dependencies & Sovereignty
Many technological dependencies were not inevitable. They became economically rational because individual systems were too expensive to build. AI-assisted engineering may be changing that assumption.
Research question: Which dependencies still create real value — and which only remain because the economics of building alternatives were different?
This is a research direction, not a claim that every dependency should be removed. Standard software, cloud services and external platforms can remain the best operational choice when their value, responsibility boundaries and replacement cost justify them.
The relevant boundary is changing because AI-assisted engineering can reduce the cost and organisational effort required to create focused systems. INSODEMA investigates where that shift changes a decision and where it does not.
The question is therefore not merely whether software can be built. It is whether a dependency remains economically, operationally and architecturally justified within the system as a whole.
System Sovereignty
The ability to choose dependencies deliberately.
System Sovereignty is not the absence of dependencies. It is the ability to choose them deliberately.
That requires understanding which systems an organisation depends on, why those dependencies exist, what value they provide, which data and operational responsibilities they control and how difficult they would be to replace.
INSODEMA uses four decision directions: Build, Integrate, Retain and Replace. Retain is a valid outcome when an external dependency remains the strongest choice.
System Sovereignty therefore does not mean building everything internally, rejecting cloud services or treating large technology providers as a problem by default. It means making dependencies visible enough to choose them rather than inherit them unquestioned.
A sovereign system is not closed. It is capable of deliberate connection.
Engine, AI & Trust
Intelligence is not the same as generative AI.
Rules, states, scoring, permissions, workflows and domain logic can represent sophisticated operational intelligence while remaining testable, reproducible and auditable.
AI may explain a decision without owning the decision.
AI assistance is governed by the data and security context. Depending on the agreed boundary, external models, private models or no AI processing may be used.
This is not a blanket AI Act compliance statement. Legal assessment remains product-, feature-, role- and use-case-specific.
Research Areas
Fields that shape the development of INSODEMA systems.
Operational Research
How work actually happens across constraints, timing, exceptions and field-level context.
System Architecture
How understanding becomes modular structures, clear boundaries and reliable data flows.
Research-driven Engineering
How findings and documented decisions are translated into systems with controlled paths for adaptation.
Knowledge architecture
Different findings require different forms.
Publications
Formal research assets with traceable versions and a clear publication status.
ExploreResearch Notes
Focused observations, hypotheses and emerging findings.
ExploreMethod Repository
Public principles for research, architecture and documented engineering decisions.
ExploreDecision Models
Structured explanations of choices, constraints and alternatives.
ExploreSystems
Operational systems developed from INSODEMA research and architecture.
ExplorePublishing principle
Publish when the finding is ready to carry meaning.
A publication should clarify understanding, document a decision or explain a system principle. Frequency is less important than relevance, traceability and intellectual honesty.
Versioning preserves how a finding developed without presenting unfinished work as settled knowledge.
Available publications
Published research and system knowledge.
No public publications yet.
The archive will open with the first finding ready for formal publication.