Designing OCP: a deterministic runtime/language built around observe match commit

Designing OCP: a deterministic runtime/language built around observe → match → commit Most programming systems treat side effects as something that happens throughout execution: read here, write there, mutate state, call out to the world, then rely on discipline, tooling, logs, and debugging to reconstruct what actually happened. I wanted to explore a different model. That is why I designed OCP : a language/runtime experiment built around an observe → match → commit execution flow, where side effects are meant to be explicit, constrained, and governed rather than ambient. This is not a claim that OCP is “the future of programming,” and it is not being presented as a polished universal replacement for existing languages. It is a design-led technical experiment around a question I think is worth testing seriously: What changes if determinism, replayability, and effect governance are treated as first-class runtime constraints from the beginning? The problem I wanted to explore A lot of so