founding claim
Human primacy, not code supremacy
A DAO enforces structure with a smart contract. An HAO uses technology to support human judgment — and treats governance, learning and trust as first-class design elements alongside the code.
Humanized Autonomous Organization
The HAO is a full-stack socio-technical framework: polycentric governance, trickle-up capital, and a socio-emotional layer treated as real infrastructure rather than culture-deck decoration. This site is the framework, the working sessions that stress-tested it, and an honest account of where it breaks.
Eight claims the framework stands or falls on. Each one links back to the sessions and source sections that argue it — including the ones that argue against.
founding claim
A DAO enforces structure with a smart contract. An HAO uses technology to support human judgment — and treats governance, learning and trust as first-class design elements alongside the code.
economic engine
Capital and decision rights stay at the productive edge of the network and flow upward, rather than being allocated downward from a centre that never touched the work.
coordination substrate
Trust as a weighted, dynamic, multi-dimensional map — with access, roles and credit capacity that grow as reputational signals accrue, rather than being granted or bought.
decision architecture
Multiple concurrent decision centres, no single layer holding unilateral control, decisions pushed to the lowest competent level, and consent rather than majority vote.
design tradeoff
Overlapping roles, duplicated capability and deliberate slack — treated as fault tolerance rather than waste.
infrastructure claim
Emotional safety, ritual design and conflict resolution treated as engineered infrastructure with the same rigour as the ledger — and the specific ways that goes wrong.
evidence
Two cooperative federations operating at scale for decades — one proving nested governance and ecosystem self-sufficiency, the other proving the relational layer. Including what each had to give up.
the case against
The framework's own documentation identifies the failure modes most likely to kill it. Collected here without softening, because a model that cannot state its own break points has not been designed yet.
Deep dives, debates, explainers and critiques generated from the source material, transcribed and speaker-separated. This is the framework being argued with, not just described.
The full framework — from structural overview to federation — readable chapter by chapter or as one continuous document.
13 chapters · 58 sections
Decks, infographics, maps, and written reports generated alongside the sessions.
deck
report
mindmap
deck
infographic
report
infographic