Engagement
A modeling project starts with need, not with software customising. In a consulting engagement we establish perimeter, goals, books, contracts, and agents — then we build the customised system with the OiC.OS workbench: the same tool surface documented under Help.
Think of that workbench as a compiler and language for management and economic systems. Specification becomes an executable twin; governance, decisions, and data analysis stay on one spine. Offer overview: Modeling Service.
From need to twin
- Diagnose — which decisions must improve? which governance rules bind? which ledgers and compliance regimes (e.g. IFRS / GAAP) apply?
- Model — assemble Acc · Dec · Gov in the workbench (2D / 3D, simulation, audit, film workflows).
- Learn with users — simulation players of your system: teams play the twin, teach operational knowledge, redesign from within.
- Handover — one customer environment: your world, your data, your books — see below.
Classical “change management” as chaos coordination is what we avoid: the twin keeps memory across restructurings. Thesis: institutional learning.
Simulation players — educate, learn, change from within
Consultants and client teams are not readers of a report. They are suppliers of organisational form: models, forecasts, and mandates with the engine behind them. Playing the twin is how the organisation learns — and how the model stays true to operations.
One customer, one environment
The unit we hand over is an environment of your own: your world, your data, your books, your users — for a firm of two hundred or a single practice. Separate environments keep confidentiality and keep the derivation from the model clean.
Two surfaces over the same books
The workbench is where the world is modelled and simulated: language, spreadsheet round trip, 2D / 3D views, simulation trace. The everyday business surface is where everyone else works — books as spreadsheets, decisions as dashboards — same state, familiar form. Mapping without teaching category theory to a bookkeeper.
Access and catalogue
| Access | Role |
|---|---|
| Public | Landing, vision, research, product pages |
| Sandbox | Example worlds, read-only playback (in preparation) |
| Customer | Own environment, models, data |
| Team | Full workbench and administration |
Catalogue of forms and partner supply: Org Shop. Status by environment: Product start. Contact: contact@oicos.systems.
Where this stands
Running today: workbench and simulation for the team (Tailnet). In preparation: sandbox, everyday surface, per-customer sign-in, provisioning from world to structures. Connecting live books of a real organisation comes after the modelled twin — deliberately.