FabricFabricPlatform
Platform reference

Platform reference

A conceptual and reference manual for the Fabric platform — ontology-based architecture, agent-native runtime, and the governed mutation pipeline.

@fabricorg/platform is a portable runtime for ontology-based business applications. It owns the mechanics of governed mutation — action lifecycle, policy dispatch, state-machine validation, adapter retry, event append — and nothing else.

Vertical packages (e.g. @repo/lending) plug into that runtime by declaring a FabricModule that registers their object types, actions, policies, state machines, and event types. The host app composes modules at startup.

Why this exists

Most line-of-business apps mix three concerns:

  1. Ontology — what entities exist, what actions are legal on them, what counts as a state change.
  2. Mutation orchestration — how a request becomes a write, with auth, validation, retry, and audit.
  3. Vertical workflow — the actual business logic.

Fabric splits these. The platform owns (2). Modules own (1) and (3). The result: every domain mutation in the system flows through one auditable pipeline, regardless of whether it was triggered by a human in a UI, an AI agent, an external token holder, or a scheduled worker.

How to read these docs

If you want to…Start here
Understand the architectureArchitecture overviewmutation pipeline
Trace what happens when an action is invokedAction pipeline → triggersstages
Know which entities the platform pre-registersEntities → built-ins
Build a new vertical modulePatterns → vertical extensions and the companion vertical-modules guide
Understand how policies gate mutationsGovernance → enforcement
Look up an event-envelope or projection contractReference → event schema, projection mechanics

The one-line invariant

Actor → ActionInvocation → PolicyEvaluation → StateMachine → Handler/Saga → AdapterInvocation → AssetEvent → Projection

Every page in this section is a closer look at one segment of that line.

See also

On this page