Org Shop
OiC.OS is not an accounting system with a theory behind it. It is a shop for organisational forms — an app shop, except that what you install is not a program but a way of organising: a pool that shares liquidity along a supply chain, a contract form that shares profit and loss instead of charging interest, an internal clearing scheme for an association.
What is actually traded
An organisational form is, before anything else, a set of rights, roles and rules — the governance layer, GovCat. Who may issue, who may draw, who decides, who is liable. Everything else follows from it: the decisions that agents can take, and the bookings those decisions produce. That is why governance is the layer that is bought and sold, and why a form remains recognisable when it is moved into a different world at a different scale.
The people who buy our engine typically sell forms of their own. An economist or a consultant builds a variant of a pooling scheme for a particular industry, or a contract form for a particular jurisdiction, and delivers it to their clients. Our customers are therefore not only buyers but suppliers in a second market, and the platform has to support that from the start.
Why a shop needs proof, not review
An app store works because apps run against a stable, typed platform, and because the store checks that installing one will not break the device. That check is a review process and, in the end, a matter of trust.
Here the check is stronger, and it is provable. A form may be installed into a world only if two conditions hold: its ports are type compatible with the ports it docks onto, and the balance identity of the composed world is preserved — every claim still has its counter-claim, the books of the assembled whole still close. Both are properties of the composition, checked before installation, not opinions about the seller.
No app store can promise that about its apps. This is the reason a shop for organisational forms is possible at all: composability is not hoped for, it is verified. What the Magic Sauce describes as glueing locally simple pieces into something globally complex is here not only the mathematics — it is the merchandise.
Everything is a catalogue entry
The recurring question "what exactly is the product" dissolves once the catalogue is the answer: example worlds, the terminal, libraries, organisational forms, templates. The list is deliberately heterogeneous.
What makes it a catalogue rather than a junk drawer is not the kind of good but the shape of every entry: a typed interface, a version, a licence. With that discipline, a buyer can be told which entries fit into their world and which do not — the same port compatibility that governs assembly also governs what is worth buying. Without it, a catalogue of mixed goods becomes unusable within a year.
The storefront itself — catalogue, variants, digital delivery, payment, invoicing — is standard commerce software and the easy part. The work is in the packaging format, not in the shop window.
Where this stands
The forms exist and run as models; the packaging format, the port types as a public interface, and version compatibility between forms are the next construction step. The shop, the customer accounts and the billing behind it are described under Engagement. Nothing here is offered for sale yet.