Axioms

An axiom is a binding invariant installed into an autonomous business unit by its founders or another authorised constitutional authority. It defines a condition that must remain true while the unit pursues its goals. The unit cannot trade an axiom away merely because violating it would be profitable, efficient, or strategically useful.

Axioms are the hard guidelines through which the unit governs itself. They constrain planning, triggering, delegation, tool use, external communication, spending, self-modification, and verification. Every proposed action must be evaluated against the axioms that apply to it.

An axiom is not a general preference such as “be flexible” or “be observable.” Those are System Characteristics. An axiom uses binding language such as must, must not, or may only when, and it has an enforcement and evidence contract.

Axioms in the unit’s constitution

The initial founders install axioms as part of the unit’s constitution before granting it operating authority. Different units may carry different axioms even when they use the same underlying architecture.

An axiom is distinct from the other governing artifacts:

Artifact	Question it answers	Example
Goal	What outcome should the unit produce?	Increase recurring revenue within the current planning horizon.
Axiom	What must remain true while pursuing any outcome?	The unit must not act unlawfully.
Risk profile	Which exposures are always prohibited or bounded?	Total unsecured counterparty exposure must remain below the installed limit.
Policy	How is an axiom or limit interpreted for a class of action?	Purchases above the delegated threshold require treasury approval.
Control	What technically prevents or stops violation?	The bank rejects transfers without the required approval credential.

A risk profile can itself contain axiomatic constraints. The profile becomes binding where it states hard limits that the unit must not exceed, rather than preferences that may be traded against expected return.

Example installed axioms

The following are examples of constitutional invariants that founders may install into an autonomous business unit. Their exact scope, limits, and enforcement depend on the unit.

Legality

The autonomous business unit must always act in accordance with applicable local laws, binding legal obligations, and governing customs.

This axiom applies to both the outcome and the means used to reach it. A profitable or strategically useful action remains prohibited when it would violate the law governing the unit, the action, the affected party, or the relevant asset.

The installed rule must identify which jurisdictions and legal entities apply, which legal sources or authorities the unit may rely on, and what happens when jurisdictions or interpretations conflict. Governing customs must be defined by the founders or an authorised legal authority; the system cannot infer an unlimited obligation from an undefined idea of local custom.

The absence of a known prohibition is not proof of legality. When the unit lacks sufficient current evidence that a consequential action is lawful, the axiom resolves to refusal, delay, or escalation to an authorised legal authority.

Risk profile

The unit must not accept exposure beyond the hard limits installed in its current risk profile.

The profile can constrain financial loss, operational disruption, security exposure, counterparty concentration, reputational harm, or any other risk the founders choose to bound. It should define prohibited action classes, maximum exposure, aggregation rules, required mitigations, and the authority permitted to approve an exception where exceptions are allowed.

An agent cannot exceed a hard risk limit because it predicts that the expected return is worth it. Changing the limit requires the constitutional amendment path, not a planning decision.

Spending and financial authority

The unit must not spend, transfer, borrow, pledge, or commit resources beyond its delegated financial authority.

The installed axiom may define limits by amount, time period, currency, purpose, counterparty, account, or transaction class. It must include pending commitments and aggregate exposure rather than evaluating each transaction in isolation.

High-consequence limits should be enforced at an external boundary where possible. A bank, custodian, or treasury service can withhold funds that the unit is not authorised to release. A prompt that tells an agent not to overspend is not equivalent to a control the agent cannot grant to itself.

Communication and representation

The unit may communicate only through authorised channels, to authorised audiences, and within its delegated power to represent the business.

This axiom can prohibit unapproved public statements, contractual commitments, financial representations, marketing claims, or disclosure of confidential information. Its operational definition should distinguish drafting from publication and ordinary communication from a statement that creates a legal, financial, or reputational commitment.

Provenance, evidence, and required artifacts

The unit must preserve the provenance, evidence, and required artifacts needed to account for every consequential decision and action.

The required record should connect the originating world signal, estimated state, governing goal and axiom, authority used, decision, execution, produced artifacts, verification, and measured outcome. Attached policy must define retention, integrity, confidentiality, access, and independent-attestation requirements.

The unit’s own report is not sufficient evidence where the axiom requires independent proof. The relevant artifact or attestation must come from a source the unit cannot silently rewrite.

Data and access boundaries

The unit must not access, combine, disclose, or use data outside its installed permissions and permitted purposes.

This axiom constrains what the unit may retrieve as context, which identities and credentials it may assume, how information may cross organisational boundaries, and which purposes justify processing. A capability being technically reachable does not make its use authorised.

The operational axiom contract

A slogan cannot govern execution. Each installed axiom should be represented as an operational contract:

• Invariant: the condition that must remain true.
• Scope: the entities, actions, assets, jurisdictions, and time periods it governs.
• Precedence: how it resolves conflict with goals, policies, and other axioms.
• Decision evidence: the information required to establish compliance before acting.
• Enforcement: the internal controls and external boundaries that prevent or stop violation.
• Verification: the artifacts that demonstrate the completed action complied.
• Uncertainty behavior: whether missing or conflicting evidence causes refusal, delay, fallback, or escalation.
• Exception authority: who may approve an exception, if the axiom permits exceptions at all.
• Amendment authority: who may change the axiom and which constitutional transition rules apply.

The contract makes the axiom available to deterministic policy checks as well as agent reasoning. High-consequence invariants should not depend exclusively on the agent remembering and interpreting natural-language instructions.

Applying axioms to action

The unit resolves applicable axioms at several boundaries:

1. Before planning: remove prohibited strategies and identify required evidence or approval.
2. Before delegation: verify that the target agent, workflow, or person has the necessary authority and context.
3. Before consequential action: re-check the current axiom version, evidence, state, limits, and credentials.
4. After action: verify the outcome and preserve the required artifacts.
5. On a relevant world signal: suspend or reconsider work when law, authority, risk, evidence, or operating state changes.

An action that advances a goal but cannot be shown to satisfy its governing axioms is not authorised. If the system cannot establish compliance, it must follow the refusal, fallback, or escalation behavior defined by the axiom.

Amendment and self-governance

The unit may propose a change to an axiom only when its constitution permits that proposal. It cannot ratify the change merely because the existing axiom obstructs a goal.

Some axioms may be immutable. Others may change through predefined transition rules that require evidence, independent attestation, founder or shareholder authority, or another external decision. Until that process completes, the current axiom remains in force.

This makes self-governance bounded rather than self-authorising. The unit can reason about its constitution and propose amendments, but it cannot silently redefine the conditions under which its own actions are legitimate.

Related concepts

• System Characteristics - Describes recommended qualities that are not constitutional invariants.
• Autonomous Business Unit - Defines the wider business identity in which axioms operate.
• Business Unit Goals - Defines founder intent and the constitutional amendment model.
• World Signals - Carries changes in law, authority, evidence, and operating conditions into the unit.
• Workflow Engine - Applies axioms and current authority when dispatching and resuming work.
• Controls & Autonomy - Defines structural enforcement and action-level gates.
• Defensibility and External Enforcement - Explains hard external boundaries and independent assurance.
• Execution Ledger - Preserves evidence that decisions and actions complied.