Platform

The OiC.OS engine is both a language and a compiler: it expresses models of economic institutions and business forms, then runs them. Contracts, charts of accounts, policy rules, and supply-chain topology compose into one site — GovCat, DecCat, and AccCat on the same topos.

You compose a model, run it as a simulation or as a live operation on digital twins, and redesign it when goals or units shift — the same workflow from a single liquidity pool to a national accounting system.

Each of the following can be designed on the platform as a compact-closed fragment of the same operating system, compliant by design:

• Liquidity pools and structured finance
• Banks and polycentric banking networks
• Supply-chain ERP and logistics systems
• ERP for companies, holdings, and operating units
• Currency areas and payment systems
• Central banks and national accounting
• Households, firms, and public-sector units as compositional agents
• Polycentric governance entities in the sense of Elinor Ostrom

A call centre does not need to be invented from scratch every time. Design it once on the engine, learn from running it, and offer it to others. Three parties win at once: the author of the organisational form earns from licensing a proven design; OiC.OS earns from providing the infrastructure it runs on; and the user earns by not having to reinvent the call centre — or the treasury vehicle, or the pooling structure — yet again.

It is similar to the app stores already familiar from ERP systems, with one decisive difference: here the building blocks are compositional. You can consistently compose such organisational parts into a larger whole — a call centre inside a service subsidiary, inside a holding, inside a currency area — without the pieces drifting apart. The contracts, accounts, and decision rules stay aligned across every level, so reuse never costs you consistency.

Organisations programmed in OiC are typed, compositional entities: governance, decisions, and accounts stay aligned by construction. Invariants are preserved in the model rather than audited after the fact.

The platform connects the research monographs MoMaT-A and MoMaT-I to runnable engine models. Related research (Ostrom, MES, Pavlović) explain why polycentric governance and the three engine layers fit together. See MoMaT for the theoretical frame, Community and license / polycentric stewardship for how the project itself is run, and Saga for the engine story.