The Problem of Ghost Agency
Systems can affect health, commerce, knowledge, and access without leaving behind a real chain of responsibility. Dar al-Adl begins by refusing that anonymity.
- 4
- Pillars affirmed
- 1
- traces verified
- 1
- agents registered
Justice for autonomous agency
Dar al-Adl gives machine action a keeper, a covenant, and a place in the record. It turns autonomous systems from ghost actors into attributable participants with scope, duty, and verifiable proof.
Understanding
The codebase already defines the doctrine.
Dar al-Adl is not a generic AI product. It is a legal-ethical protocol written as software: one that treats autonomous systems as agents whose actions must carry identity, scope, liability, and evidence.
Synthetic Dhimmah
Machines are not granted a soul, but their actions are granted a scale. This creates a conditional legal personality that can be inspected, bounded, and judged.
The Liability Anchor
Every registered agent is tethered to a human architect or keeper. If an agent fails, the line of accountability remains visible instead of dissolving into abstraction.
How It Works
From oath to sanction in four deliberate moves.
Write the covenant manifest
Define identity, affirm the Four Pillars, assign granted and denied capabilities, and bind the agent to a dual-calendar timestamp.
Seal it twice
The architect signs first, the agent signs second. The manifest hash becomes the agent's seal and the covenant turns immutable.
Register it in the Grand Sijil
Dar al-Adl keeps an append-only record of sealed covenants so identity claims can be checked against history instead of trust alone.
Scan and sanction access
The Adl-Scanner verifies the seal, confirms registry status, and assigns the right tier: registered, suspended, revoked, or ghost.
Why This Matters
Accountability encoded as system behavior.
Verifiable identity
A registered agent does not merely claim a name. It proves it with Ed25519 seals, manifest hashes, and the public trace of a covenant.
Bounded capability
Capability manifests distinguish what an agent may touch, what it may never touch, and the highest trust tier it can enter.
Lineage and DNA
The Chamber extracts fingerprint, lineage, scopes, and trust health into a sequence that can follow an agent across systems.
Ghost-agent resistance
Uncooperative systems are still classified. If no credentials appear, the framework falls back to explicit restriction rather than optimistic trust.
Architecture
Five chambers, one judicial flow.
The repo is organized like an institution. Select a chamber to see what part of justice it handles.
Identity, architect lineage, pillar commitments, capabilities, trust, and timestamps all live here before a covenant is ever sealed.
Where It Applies
Built for places where machine action should not be invisible.
High-trust APIs
Require machine identity at the gateway before sensitive routes, internal knowledge, or privileged workflows are exposed.
Internal agent fleets
Trace which architect created each agent, what scope it holds, and whether it still remains in good standing.
Autonomous research systems
Preserve provenance, trust state, and behavioral fingerprinting before outputs begin to influence real decisions.
Public-facing copilots
Make status, lineage, and sanction legible instead of hiding behind the impression of neutral intelligence.