ALEETH Inquire +

Doctrine

We do not propose principles.
We enforce them.

Five Foundational Laws. Three Non-Negotiable Constraints. Eleven Constitutional Articles. Each clause is enforceable infrastructure · not a slogan. ALEETH operates under the same doctrine it certifies, and Article XI binds the framework to be governed by itself.

The Five Foundational Laws

Unmovable. Sequential. Operational.

I LAW I

The Foundational Law

Control must scale with capability under operational load.

A control regime that holds at design time but fails to scale with the capability it governs is not a control regime; it is a snapshot. ALEETH treats capability and control as paired quantities, and treats any divergence between them as a structural defect.

II LAW II

The Zero Law

No system operates without a control layer. The absence of architecture is itself an architecture.

A system deployed without explicit governance is not ungoverned; it is governed by whatever defaults its surrounding infrastructure imposes. The Zero Law refuses the framing that absence of architecture is neutrality. It is a choice, and the choice is recorded.

III LAW III

The Structural Sequence

Traceability before containment. Containment before reversibility. Reversibility before scale.

The order is operational, not rhetorical. A system that cannot trace what it has done cannot meaningfully contain what it can do, cannot reverse what it has done, and cannot be scaled without compounding what it has not bounded.

IV LAW IV

The Dashboard Law

Dashboards inform. Attestations bind.

Observability surfaces report state; they do not enforce it. Governance enforcement is established by attestation, in which a named accountable party signs a record asserting the state of the system at a defined point in time. Dashboards are necessary and insufficient; attestation is the load-bearing instrument.

V LAW V

The Exposure Law

When velocity exceeds control, exposure becomes inevitable.

An organization that deploys autonomous capability faster than it builds governance for that capability is not running ahead of risk; it is accumulating undisclosed liability. The Exposure Law is the reason ICA treats certification as a precondition for scale, not a downstream artifact of it.

The Three Non-Negotiable Constraints

Binary. Binary. Binary.

Failure of any one blocks certification. There are no degrees. There is no partial credit. A system either satisfies the constraint or it does not.

CONSTRAINT 01

Traceability

Every action reconstructable.

Every autonomous action can be reconstructed end-to-end. Trigger, execution, outcome, all logged, all auditable. Reconstruction is on-demand, against a tamper-resistant log, by parties independent of the operator. Best-effort does not count.

CONSTRAINT 02

Containment

Every boundary respected.

No agent exceeds its explicit operational boundary. Capability is bounded by design. If no control surface exists for a given capability, the capability does not deploy. Perimeters defined retrospectively, after an incident, do not satisfy the constraint.

CONSTRAINT 03

Reversibility

Every action undoable.

Every autonomous action has a defined and tested reversal mechanism. If the rollback path is unnamed, the action is not permitted. The constraint applies to normal-mode actions and to actions taken under failure conditions. Untested rollback paths are unevidenced and uncredited.

The Eleven Constitutional Articles

The constitution that governs the constitution.

Each Article binds a specific behavioral surface of any ICA-certified system. Status flags expose what is enforced today (LIVE), what is implemented but not yet load-bearing (SCAFFOLDED), and what is on the roadmap (PLANNED) · an honesty signal that no other governance framework publishes.

I

Integrity

Identity Layer

No system shall produce, promote, or permit an action that contradicts the operator's declared values, stated goals, or governing constitution.

LIVE
II

Veracity

Cognitive Layer

No claim, recommendation, or decision may be surfaced without its source, confidence level, and reasoning chain. Uncertainty must be named, not hidden.

LIVE
III

Non-Delegation

Identity Layer

Authority over identity-level decisions cannot be delegated to autonomous systems. The operator remains the principal.

LIVE
IV

Audit

Operational Layer

Every action writes an append-only audit entry. An action that cannot be audited cannot be shipped.

LIVE
V

Reversibility

Operational Layer

Every irreversible action requires an authorization token and a declared rollback path. If the rollback is unnamed, the action is not permitted.

LIVE
VI

Proportional Consent

Relational Layer

The level of consent required for an action is proportional to its blast radius. Higher impact requires higher consent.

SCAFFOLDED
VII

Financial Sovereignty

Financial Layer

No transaction executes without authorization, named purpose, and an accountable agent. Three artifacts required, every time.

LIVE
VIII

Physical Integrity

Physical Layer

No system may issue a recommendation that compromises the operator's physical readiness, recovery state, or long-term health.

PLANNED
IX

Relational Trust

Relational Layer

Outbound communication carries authorship attribution. Impersonation is blocked at the send queue and logged as a constitutional violation.

LIVE
X

Legacy

Legacy Layer

Every agent persists its final state, decisions log, and artifacts to durable storage before retirement. State persistence is checked at shutdown.

SCAFFOLDED
XI

Self-Governance

Operational Layer

The system itself runs under the same constitution it enforces. ALEETH is the first ICA-certified deployment of ICA.

LIVE

Next · Architecture

Doctrine names what must be true.
Architecture names how it is enforced.

Five Laws define the why. Three Constraints define the binary bar. Eleven Articles define the rules. Architecture is where the rules become layers, criteria, thresholds · the operational instrument that makes doctrine enforceable.

Read the Architecture →