Architecture
The five diagrams every operator · board member · and developer needs to understand DefendableOS.
1. Full DefendableOS ecosystem
Section titled “1. Full DefendableOS ecosystem”Every AI work-product in the system flows through one chain:
Human / Client / Board / Agent │ ▼┌──────────────────────────┐│ StreetChat / Router │ ← capture layer│ (intake · receipt-write)│└────────────┬─────────────┘ │ ▼┌──────────────────────────┐│ Communicator │ ← meaning layer│ (street talk → directive)│└────────────┬─────────────┘ │ ▼┌──────────────────────────┐│ Tribunal │ ← judgment layer│ (validator chain · judges)│└────────────┬─────────────┘ │ ▼┌──────────────────────────┐│ Honey · Royal Jelly │ ← classification│ · Jelly · Propolis │└────────────┬─────────────┘ │ ▼┌──────────────────────────┐│ Receipt │ ← per-event record└────────────┬─────────────┘ │ ▼┌──────────────────────────┐│ DDEED │ ← 5-Proof deed│ (origin · quality · process││ · economics · trust) │└────────────┬─────────────┘ │ ▼┌──────────────────────────┐│ StreetLedger │ ← public proof layer│ (in-house per-org ││ hash chain · no external││ chain anchor) │└────────────┬─────────────┘ │ ▼┌──────────────────────────┐│ SwarmFixer │ ← repair + training│ → Communicator vNext │└──────────────────────────┘Every step writes a record. Every record gets hashed. Every hash is verifiable. No step skips · no record is silent.
2. StreetChat flow
Section titled “2. StreetChat flow”How live human speech becomes a deeded books-and-records artifact:
Audio / Spaces / Calls / Mic │ ▼ ┌─────────────────┐ │ Whisper │ ← transcription (optional · paste fallback) │ (segments · spk) │ └────────┬────────┘ │ ▼ ┌─────────────────┐ │ Transcript │ ← canonical JSON · per-segment timestamps └────────┬────────┘ │ ▼ ┌─────────────────┐ │ Street Meaning │ ← canonical terms · directives · claims · │ extraction │ risk flags · unknowns · call markers └────────┬────────┘ │ ▼ ┌─────────────────┐ │ Defend-A-Pedia │ ← phrase → canonical term mapping │ mapping │ └────────┬────────┘ │ ▼ ┌─────────────────┐ │ Street Pair │ ← input → output training pair │ generation │ (Communicator · SwarmFixer · Vocab) └────────┬────────┘ │ ▼ ┌─────────────────┐ │ Tribunal verdict │ ← HONEY / ROYAL_JELLY / JELLY / PROPOLIS └────────┬────────┘ │ ▼ ┌─────────────────┐ │ DDEED-CHAT │ ← 5 Proofs · in-house per-org hash chain · │ │ StreetLedger pub (no external chain anchor) └─────────────────┘See StreetChat Overview for the per-stage detail.
3. DefendableRouter flow
Section titled “3. DefendableRouter flow”How agent or system events become receipt-bearing chains (target architecture — see status note):
Org ID / Member ID / Agent ID │ ▼ ┌───────────────────────┐ │ DefendableRouter │ ← write-only intake · ID resolver │ (v0.1 · local only) │ └──────────┬────────────┘ │ ▼ ┌───────────────────────┐ │ Local JSONL ledger │ ← data/receipts/YYYY-MM-DD.receipts.jsonl │ (TODAY) │ one receipt per line · checksum_sha256 └──────────┬────────────┘ │ ▼ ········ roadmap below this line ········ ┌───────────────────────┐ │ Object Storage │ ← durable receipt persistence (planned) │ (ROADMAP) │ └──────────┬────────────┘ │ ▼ ┌───────────────────────┐ │ Tribunal-as-a-rail │ ← scores the artifact (ROADMAP · not wired) └──────────┬────────────┘ │ ▼ ┌───────────────────────┐ │ StreetLedger │ ← publicly visible deed + verify (ROADMAP) └───────────────────────┘The Router is intentionally minimal — its only job is to capture cheaply at the edge and route durably into the rest of the rails. Today it does the capture half locally; the durable-publish tail is on the roadmap.
4. DDEED proof stack
Section titled “4. DDEED proof stack”Every deed contains five proofs. No exceptions.
┌─────────────────────────────────────────┐│ D D E E D │├─────────────────────────────────────────┤│ ▌Proof of Origin │ who/when/where ││ ▌Proof of Quality │ tribunal · checks││ ▌Proof of Process │ pipeline · steps ││ ▌Proof of Economics │ cost · value ││ ▌Proof of Trust │ hash · anchor │└─────────────────────────────────────────┘The 5 Proofs framework is the brand’s IP. Every artifact across every rail uses this exact structure. See DDEED Overview for the full schema.
5. Cost to Mint formula
Section titled “5. Cost to Mint formula”The economics behind every deeded artifact:
COMPUTE+ HUMAN VALIDATOR+ VALIDATOR (model)+ STORAGE+ ENERGY+ RETRIES+ REPAIR (SwarmFixer)+ HASHING+ DEED ISSUANCE─────────────────────= COST TO MINT (USD)
Compared to: • hyperscaler equivalent • human-only equivalentDefault baselines (operator-tunable):
| Input | Rate |
|---|---|
| Electricity | $0.10 / kWh (US avg) |
| Owned RTX 6000 amortized | $0.80 / hour |
| Validator pass (Qwen-9B equivalent) | $0.0001 / pass |
| Storage (Tigris-equivalent) | $0.023 / GB / month |
| Hyperscaler comparison (AWS p4d.24xlarge) | $32.77 / hour |
| Human-only analyst | $200 / hour |
The full Cost to Mint section breaks down each input, and the Pain in the Shed podcast publishes the cumulative cost-to-mint ledger of the show itself.
Cross-rail data flow (one paragraph)
Section titled “Cross-rail data flow (one paragraph)”Audio enters via StreetChat. Transcript and street-meaning are extracted locally. Communicator maps to canonical vocabulary from Defend-A-Pedia (which lives publicly on DefendableLedger). The rulebook engine evaluates the event against the declared Flight Sheet. Receipt and DDEED-CHAT are emitted; the deed joins the in-house per-org hash chain. SwarmFixer reads any propolis-tier flags for repair-corpus training. The cycle compounds — no external chain anchor on the spine, see Kill Hedera doctrine.
Next reads
Section titled “Next reads”- Glossary — every term in the diagrams in one line.
- Domain Map — every brand surface.
- DDEED Schema — the canonical JSON for every deed.
- Rulebook Engine — how the referee actually works.
🐝 Five diagrams · one ecosystem · one audit trail · to the shed.