Getting Started

The 90-second principal test

If you have ninety seconds, here is what you need to know.

DefendableOS is the defense layer for AI agents. When an AI agent finishes a piece of work, DefendableOS captures the work, translates the meaning, runs the Tribunal, issues a receipt, and deeds the record. The receipt and the deed are publicly hashed and anchored on Hedera. That makes the AI work auditable · repairable · and defensible — which is what every regulated · revenue-bearing · customer-facing business needs once AI agents touch real workflows.

The category we operate in is not “another AI agent” or “another LLM platform.” The category is trust infrastructure for AI work — adjacent to Datadog (observability), Vanta (compliance), KPMG (audit), Moody’s (ratings), and Cloudflare (defense). Each is a multi-billion-dollar category. DefendableOS sits at the intersection.

The principal selling this asset is Donovan Mackey — a 30-year top 1% industrial CRE broker (~$8B closed) who built the platform on the same discipline he closed buildings with: bring the math · books and records · receipts at every step · class A 5-cap. That voice runs through every surface.

What you do next depends on your seat

Board / Principal

Start with the Board Flight Sheet — same artifact a broker hands a CFO before a Class A 5-cap mandate. Then read the Buyer Profile and the Pricing Philosophy.

Operator / Builder

Start with Architecture for the full ecosystem diagram. Then read DDEED Schema, Tribunal Scoring, and the API Overview.

Buyer / Customer

Start with What DefendableOS Is, then What It Is Not, then Use Cases. The Cost to Mint page explains the per-decision economics.

Developer

Start with Schemas Overview and Examples. Then pick a rail: StreetChat for capture, StreetLedger for proof, DefendableRouter for routing.

The one-line orientation

Street talk becomes vocabulary. Vocabulary becomes receipts. Receipts become deeds. Deeds become trust.

That sentence is the entire platform. Everything in these docs is one level of detail beneath it.

Verify a deed right now

The fastest way to understand DefendableOS is to verify a real deed.

Open ledger.mrdefendable.com — the public proof layer.
Click any term in the deeded vocabulary index — pick something like Probability of Close or Books and Records.
Scroll to the proof trail — copy the canonical_json_sha256 hash.
Open /streetledger/verify — paste the hash.
Either the canon owns it, or it doesn’t. That’s the entire trust loop.

Every DefendableOS surface follows that pattern. Every receipt has a hash. Every hash is public. Every claim can be verified in seconds. That is what books-and-records discipline applied to AI work actually looks like.

Voice discipline before you read further

DefendableDocs is written in Mr. Defendable’s voice. That means:

Plain English over jargon. A CFO reads this without a glossary.
Receipts over claims. Every assertion resolves to a verifiable source.
Specific over generic. Real numbers · real hashes · real deal types.
No MBA filler. Zero “world-class”, “transformational”, “AI-powered”, “leverage synergies”.
No Web3 theatrics. Hedera-anchored books and records, not token speculation.
“To the shed” close. Every doctrine section ends decisively.

One reading order suggestion

If you read in this order you will understand DefendableOS faster than any other path:

Ecosystem Overview → Architecture → DDEED 5 Proofs → Tribunal Overview → StreetLedger Overview → StreetChat Overview → Cost to Mint Overview → Buyer Profile → Board Flight Sheet.

Thirty minutes · nine pages · operator-grade clarity.

🐝 Ring ring · welcome to DefendableOS · to the shed.