Canonical · Not-a
Not a model wrapper
A model wrapper exposes a model behind an API and calls it product. Ubiquity does not wrap a model. It governs the harness around any model — the runtime layer where memory, trust, authority, and human judgment decide what is permitted to become action.
Why the distinction matters
Wrappers compete on UX over the same underlying capability. Substrate competes on what is permitted to happen, regardless of the underlying capability. The two are not in the same category.
Demand ladder
L1 Pain→L2 Contrast→L3 Category→L4 Primitive→L5 Branded
Adjacent transitions
This is
- A governance substrate that runs beneath the harness.
- Model-agnostic — the same primitives govern any underlying model.
- Concerned with what may become action, not which model produced the token.
This is not
- A thin API in front of a model.
- A model router or model marketplace.
- A SaaS reseller of foundation-model inference.
Frequently asked
- Does Ubiquity require a specific model?
- No. The substrate governs the harness, not the model. Swap the model and the governance primitives still hold.
- If you are not a wrapper, what are you?
- Coherence infrastructure for AI-mediated organizations. Runtime governance for AI harnesses.