Qubit

An execution foundation, not another notation.

Qubit is the proprietary layer I built to execute multiple forms of models with common deterministic semantics, from servers to environments closer to the edge.

Different inputs. One foundation.

Details of internal transformations, scheduling, memory representation and optimizations deliberately remain private.

BPMN
CMMN
DMN
IFML
ArchiMate
EIP

Qubit

Deterministic, multi-surface execution foundation. Proprietary internal mechanisms are not documented here.

Server
Browser
Mobile
Edge
Devices
Distributed systems
Public boundary. I discuss properties, interfaces and solved problems here. Details of formal representation, scheduling, internal transformations and low-level optimizations remain proprietary.

Reduce translations that make meaning drift.

Notation agnostic

The choice of notation should not impose a different execution stack every time.

Determinism

Structural effects, rules and important transitions should remain explicit even when upstream intelligence is probabilistic.

Portability

The same model should preserve its behavior across multiple execution surfaces.

Distribution

The engine was designed as a distributed system, not as a simple local runtime.

Qubit is the result of going beneath frameworks.

IFML, BPMN, Camunda, WebAssembly and other experiments each solved part of the problem. Qubit came from the need for a more fundamental layer that does not depend on a single notation.