unifyhub

What the system can do, plane by plane.

The architecture says what must be true. This section says what the system can do, plane by plane. Each plane is a capability the whole ecosystem shares, built once and consumed through contracts rather than rebuilt inside every product.

Capability planes are not products. A product is a place where work happens and a domain stays coherent. A plane is a horizontal ability that every product draws on, which is why a community gains all of it the moment it adopts any part of the system.

The ten planes

How the system is used

  • Interface composition
    screens assembled from small governed parts, declared rather than hand-built. In build

  • Domain services
    the working capabilities of an organization, each keeping the integrity of its own subject. In build

  • Events and data
    a common event backbone and typed records, so what happened is written once and read everywhere. Running

How the system thinks and acts

  • Agentic operations
    software that acts on delegated authority, inside the same rules people work under. In build

  • Knowledge and memory
    a system that can describe itself, remember what was decided, and answer questions about its own shape. In build

  • Collection and evidence
    watching the outside world on a schedule and keeping the proof of what changed. In build

  • Models and inference
    reasoning capacity the community can own, route, train, and evaluate. In build

What it all stands on

Each plane is described here on its own terms. To see several of them working at once on one ordinary problem, read the use cases.

Why the planes matter to a community

  • Capability compounds instead of duplicating

    When collection, reasoning, events, and identity are shared planes, a new domain arrives with all of them already working. Communities stop paying for the same machinery once per tool.

  • Every plane carries the same guarantees

    Identity, policy, audit, and migration reach into every plane, so the promises made on the front page are not thinner in the parts nobody looks at.

  • Breadth stays legible

    A large system earns trust only if it can still be explained. Each plane has one job, a stated boundary, and a public contract, which is what keeps scale from becoming opacity.