Nebbos in four slides.

The class of work that sits between intent and state. Not the model. Not the app. The layer that decides whether the call runs, what it costs, what it touches, and what it leaves behind.

Every call is measured — tokens are the unit of accounting. Every call is scoped — no reach across workloads. Every call is composable — nested calls roll up, the substrate settles. Not a wrapper. A runtime.

Four primitives. Pearl is the VM your workload runs on. Tokens are the unit of accounting — every consumption traced to its origin. Nested calls roll their traces back up to Pearl. The knowledge graph is where the substrate settles the truth.

Governance is not a feature layered on top. It is the shape of the runtime. Every call you route through Nebbos carries its own audit, its own metering, its own isolation. You do not opt in. You get it because you deployed here.