Platform
The product platform behind the [Modeling Service](/docs/products/modeling): a language and runtime for organisational forms and **customer digital twins**. You compose Acc · Dec · Gov, simulate, and run — beside ERP, CRM, SRM, APS, WMS, TMS — with verifiable books, smart-contract governance, and modern agents. Companion: [Technology](/docs/vision/technology) · [Engagement](/docs/products/delivery) · [Workbench](/docs/products/help).
Language, compiler, workbench
OiC.OS is a **compiler and programming surface for business, economics, and management systems**: contracts, charts of accounts, policy rules, and network topology compose into one site — GovCat, DecCat, and AccCat on the same topos. Invariants (QEB / Pacioli, sheaf glue, adjunctions) belong to the runtime, not a later audit project. The workbench is where we build the customer’s world in engagement.
Compose a model, run it as simulation or live twin, redesign when goals shift — the same workflow from (Central) Banking to verticals. See Verification & Bench for scale.
Kernels and forms on one spine
Catalogue order is architectural: (Central) Banking is the MoMaT foundation made runnable (Einbank → Dreibank) including **international balances**; Islamic Banking builds *on* that substrate; LiquiPool is *contained in* it. Crypto / token / blockchain settlement is a service on the same verified books — not a parallel stack.
Each of the following can be designed on the platform as a compact-closed fragment of the same operating system, compliant by design:
- (Central) Banking kernels and polycentric banking networks
- Liquidity pools (LiquiPool) and structured finance inside that architecture
- Islamic Banking and other governance variants on the MoMaT Acc substrate
- Digital money: crypto currencies, stablecoins, tokenised deposits, blockchain rails
- International balances, currency areas, and payment systems (MoMaT-I)
- Supply-chain finance and logistics orchestration (WMS / TMS streams under Acc)
- ERP / APS / CRM / SRM as enterprise surfaces on one Acc · Dec · Gov spine
- Central banks, national accounting, holdings, and Ostrom-style polycentric entities
A marketplace of organisational forms
A call centre — or a treasury vehicle, or a pooling structure — need not be invented from scratch every time. Design it once on the engine, learn from running it, and offer it via the Org Shop. Three parties win: the author of the form, OiC.OS as infrastructure, and the user who reuses a proven twin.
Unlike a flat ERP app store, building blocks are **compositional**: a form installs only if ports fit and the balance identity of the composed world survives. Contracts, accounts, and decision rules stay aligned across levels — reuse never costs consistency.
From MoMaT to deployment
**MoMaT** (Monetary Macro Accounting Theory) on this website is the foundation of OiC.OS: MoMaT, MoMaT-A (axiomatic money and macro accounting), MoMaT-I (currency areas and international clearing). Organisations programmed in OiC are typed, compositional entities: governance, decisions, and accounts stay aligned by construction.
Related research (Ostrom, MES, Pavlović) explains why polycentric governance and the three engine layers fit together. See Saga for the engine story and whoami for the people behind the work.