Systems & Decision Research Lab

We do not start with software.
We start with understanding.

INSODEMA researches operational problems, decision processes, knowledge flows and relationships between systems. We turn observation and research into understanding, understanding into architecture and architecture into systems designed to evolve.

Observation Research Understanding Architecture systems designed to evolve

The meaning INSODEMA carries today

Investigating Systems.
Observing Decisions.
Engineering Meaningful Architectures.

INSODEMA studies operational, organisational, technical and knowledge systems as connected structures rather than isolated features.

We examine how decisions arise, what information they depend on and where responsibility belongs.

Verified understanding becomes architecture with a clear purpose, explicit responsibility and the ability to adapt when reality changes.

Why now

The economic boundary between standard platforms and purpose-built systems is shifting.

AI-assisted engineering lowers, in some areas, the effort required for small teams to design and operate robust purpose-built systems.

That makes technological dependencies open to renewed examination: not every dependency is wrong, but it should still justify its value today.

INSODEMA therefore investigates which dependencies create real value and which mainly persist from earlier software-development economics.

System Sovereignty is not the absence of dependencies. It is the ability to choose them deliberately.

Research Cases

Research in Practice.

Research Cases show how INSODEMA investigates real dependencies, operational capabilities and research questions and turns them into deliberate architecture decisions.

INSODEMA uses four decision directions: Build, Integrate, Retain and Replace. Retain is a valid outcome when an external dependency remains the strongest choice.

View Research Cases

Engine, AI & Trust

Intelligence is not the same as generative AI.

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.

01

Engine is not oldschool. Determinism is a design choice.

Rules, states, scoring, permissions, workflows and domain logic can represent sophisticated operational intelligence while remaining testable, reproducible and auditable.

02

AI may explain a decision without owning the decision.

Where domain authority lives in an engine or explicit rule set, AI can additionally explain factors, summarise evidence, narrate a decision path or support dialogue about the result.

03

A sovereign system is not closed. It is capable of deliberate connection.

External providers, customers, partners, logistics, payment and authority services, APIs, standards and infrastructure can deliberately remain part of a sovereign architecture.

Research changes understanding. Understanding drives architecture. Architecture enables systems designed to evolve.

How INSODEMA works

Meaning comes before implementation.

INSODEMA begins with the real operating environment: the decisions people make, the constraints they face and the patterns that formal process descriptions often miss.

Research turns those observations into a clearer model. Architecture then gives that model boundaries, responsibilities and a path into durable systems.

Explore the Method

Problems We Investigate

Not software orders. Research starting points.

INSODEMA begins where operational friction, system boundaries or dependencies need to be understood before the right solution is known.

01

We use 10% of a system we pay 100% for.

02

Employees manually transfer information between systems.

03

A critical process depends on one external provider.

04

The process exists because the software requires it.

05

The problem is too small for enterprise IT and too large for the department.

Research partnerships

Bring us a real problem.

You do not need to arrive with a finished solution. Describe the problem, dependency or operational friction. INSODEMA investigates first, before naming a solution path.

A research partnership does not guarantee that software will be built. The first value is better understanding and a better decision.

Retaining the existing solution can be the correct result.

Publications

Findings become public when they add understanding.

The public archive is currently empty.

Research is published when a finding, decision or system principle is ready to stand on its own.