What is live today vs forthcoming
Two anchors are verified live right now :
app.defendablecloud.com (the portal) and defendablecloud.com (the marketing surface) sit in front of the live API. Forthcoming / roadmap surfaces below — listed for completeness, not yet deployed: StreetChat (chat.mrdefendable.com), DefendableLedger as a standalone product, and the four ENS read-mirrors (which are read-mirrors, explicitly NOT anchors — the trust layer is the in-house per-org hash chain). The DefendableRouter is not public anywhere and is not in this map.
Surface Role URL Status Mr. Defendable FACE · principal voice mrdefendable.com Voice/brand surface DefendableLedger LEDGER · canonical books-and-records surface defendableledger.com Domain held · standalone product is roadmap StreetChat CHAT · live capture rail (subdomain) chat.mrdefendable.com Roadmap — not yet deployedStreetLedger (legacy) LEDGER subdomain · superseded by defendableledger.com ledger.mrdefendable.com Legacy / secondary
Surface Role Status Offense to the Shed CULTURE · written 5-pillar blog Domain acquired · awaiting bootstrap Pain in the Shed MEDIA · cost-of-intelligence podcast Domain acquired · awaiting bootstrap streetledger.eth (read-mirror) ENS-resolved IPFS gateway · NOT an anchor Awaiting IPFS pin + ENS contenthash
Surface Role URL DefendableDocs (canonical) DOCS · this site defendabledocs.com docs.defendableos.com DOCS (subdomain) Same source · identical content
These four ENS names underpin the published vocabulary mirrors. They are read-mirrors , not anchors — the trust layer is the in-house per-org hash chain.
ENS Role defendapedia.ethVocabulary canon · 62+ deeded terms streetvocab.ethVocabulary as deeded asset class · value of the language itself streetledger.ethBooks and records read-mirror · receipts + deeds + manifests pathing streetchat.ethLive conversation intake · per-session object-storage prefix
The surfaces are siblings, not parent/child. Each has one role.
(the principal · voice · face)
┌──────────────┬───────────────┼───────────────┬──────────────────────┐
defendableos.com defendablecloud.com defendableledger.com defendabledocs.com offensetotheshed.com / painintheshed.com
(ENGINE · rulebook) (VAULT · receipts) (BOOKS · ledger) (DOCS · this site) (CULTURE · MEDIA)
└──────┬───────┴───────────────────────┘
(in-house · client-side verifiable · NO external chain anchor)
Both domains serve identical content from one source — this Astro Starlight repo. The split exists for audience routing:
Domain Audience signal docs.defendableos.comTechnical · operator · API-first defendabledocs.comPrincipal · board · doctrine-first
Same docs · different doorway. Operators reach for the .com, builders reach for the subdomain. Cross-linking is symmetric.
Class Surface Trust mechanism Eval / Cook / Dataset / Compute / Incident receipts DefendableCloud Per-org SHA-256 hash chain — see Schemas · Receipt . Vocabulary deeds (DDEED-VOCAB · DDEED-MEDIA · DDEED-FOUNDER-ORIGIN) DefendableLedger Append-only JSONL hash chain — see DefendableLedger · Hash-Chain Format . Books-and-records publications defendableledger.com Batch publication from in-house records to the public canonical surface.
No external chain anchoring on the spine — see the Kill Hedera doctrine . The full audit trail is reproducible client-side, in-house, end to end.
🐝 Two product surfaces · books on the ledger · in-house hash chain · to the shed.