OBSIDIAN

Multi-agent orchestration through constitutional consensus.

Autonomous. Adversarial. Correct.

Enter

What if software agents governed themselvesnot by obedience, but by constitution?

EXHIBIT 02

How It Works

Obsidian replaces central control with constitutional consensus. Agents coordinate through shared principles, not through a scheduler telling them what to do.

W

The Warden

Constitutional guardian, not a scheduler. The Supreme Court, not the Executive Branch.

C

Constitutional Consensus

Agreement through correctness, not voting. When the Constitution is clear enough, coordination happens without intervention.

A

Autonomous Agents

Genuine sovereignty within constitutional bounds. Real decisions about strategy — not microservices with delusions of grandeur.

F

Fractal Delegation

Tasks decompose into self-similar subtasks. Constraints flow downward, never upward.

T

Task Pipeline

Six auditable stages. Every decision traceable. Every result verifiable.

R

Built in Rust

When decisions compound recursively through delegation trees, you want the substrate to be correct. Not eventually consistent. Correct.

Constitutional consensus replaces central scheduling
Task Flow
  SUBMIT ──▶ VALIDATE ──▶ ASSIGN ──▶ EXECUTE ──▶ VERIFY ──▶ COMPLETE
    │           │            │           │           │           │
    │      Constitution   Consensus    Agent     Constitution   State
    │        check        protocol    autonomy     check       commit
    │           │            │           │           │           │
    └───────────┴────────────┴───────────┴───────────┴───────────┘
                        Warden oversight (continuous)

Enter the Documentation

The Constitution is written. The agents are sovereign.

What follows is the complete record — every principle, every protocol, every pattern that governs the system. Cross the threshold.

Enter the Documentation Cross the threshold

The system remembers those who enter