Constitutional physics for AI
Constitutional physics is Ubiquity's stance that purpose, trust, risk, economics, and consequence have weight inside the runtime. Governance is not language attached to a system; it is the field the system reasons inside. Correct behavior becomes the path of least resistance.
Plain definition
Constitutional physics is the design principle that governance lives as weighted forces inside the runtime rather than as text attached outside it. Purpose gives direction. Trust has weight. Risk creates pressure. Economics creates gravity and friction. Agency remains sacred. The constitution makes those dynamics legible, bounded, and accountable.
Why it matters
A constitution that lives only in text is a document the agent never reads. A constitution that lives as physics shapes what the agent can do before output is produced. Correct behavior stops being an externally enforced veto and starts being the path of least resistance.
What it is not
- A policy document attached to the model.
- A static rules engine running after the fact.
- A claim that the AI obeys laws of nature.
- A metaphor for compliance frameworks.
Example
A harness drafts an action whose risk weight exceeds its earned scope. The substrate routes the draft into review before it becomes execution. No veto fires; the runtime simply does not let the action precipitate without judgment.
Where it appears in Ubiquity
Constitutional physics is the design stance underneath Ubiquity. It is the substrate-level expression of runtime governance for AI.
Ladder context
Demand ladder
Related terms
Frequently asked
- Is constitutional physics literal physics?
- No. It is a design stance. Forces like trust, risk, and economics are encoded as weighted properties in the runtime so the substrate has shape, not just policy.
- How is this different from a rules engine?
- A rules engine evaluates statements. A constitutional physics substrate weights forces so that some actions take more energy than others. The harness moves through a shaped field instead of asking permission against a checklist.