← Structure

§2.1

Structural Overview of the HAO Framework

The Humanized Autonomous Organization (HAO) — the network’s coordinating framework — is a pattern language for organizing human and technological systems around shared values, distributed autonomy, and mechanisms for reinvesting economic surplus across the network.

This section describes the primary structural components of the HAO, which together form a modular, composable system. These structures are not rigid: they provide the scaffolding for culture, trust, governance, and value flow.

The five foundational elements explored here are:

  • The HAO layer: A coordination and systems integration layer that maintains integrity across a distributed network without centralizing power.
  • United Micro Enterprises (UMEs) — small, self-managing venture teams of up to ~15 people: the autonomous, semi-permeable value-generating nodes of the system.
  • Strategic Enterprise Partnerships (SEPs) — joint ventures between teams: temporary or long-term collaborations between UMEs to pursue aligned missions.
  • Micro Enterprise Ecosystem (MEE) — the network’s protected internal economy: a protected yet porous economic and cultural environment that allows UMEs to operate while maintaining alignment with core principles.
  • Public Market Interfaces (PMIs) — buffer companies between the network and outside investors: specialized structures that allow selective engagement with external capital or market forces without compromising internal governance.

Each component is meaningful on its own and interdependent with the others, forming a system intended to grow, self-correct, and evolve while maintaining coherence.

We begin with the HAO itself.

2.1 The Humanized Autonomous Organization (HAO)

Every HAO-based system includes the HAO layer: a coordinating, enabling, and value-protecting structure that facilitates communication, coherence, and shared learning across nodes, rather than functioning as a command center, corporate headquarters, or founder-led hub.

Purpose of the HAO

The HAO exists to:

  • Maintain alignment between distributed units and shared principles
  • Provide enabling infrastructure: governance, technical, legal, financial
  • Ensure interoperability between local autonomy and global coherence
  • Facilitate cross-network coordination, learning, and resilience
  • Protect the system’s integrity against value extraction outside agreed terms or misaligned incentives

Its role is to make agency and coherence compatible at scale without becoming bureaucratic or controlling.

Characteristics

The HAO is defined by a few key structural features:

  • Non-centralized but coordinating: It does not “own” the network, but provides shared infrastructure and arbitration mechanisms.
  • Constitutional Layer: It maintains the Dynamic Enterprise Agreement (DEA) — a versioned operating agreement replacing fixed bylaws — that underpins the system’s governance.
  • Polycentric Facilitation: It enables multiple centers of decision-making across contexts and domains, using protocols like the Adaptive Governance Framework (AGF) — the network’s layered governance system.
  • Implementation-Agnostic: The HAO model can be implemented by different entities (e.g., provide.io) depending on context, domain, and regional needs.
  • Temporal Role: In some networks, the HAO may phase out over time, with responsibility distributed fully to autonomous entities.

HAO Functions

Core HAO responsibilities include:

  • Governance Enablement: Managing the lifecycle and integrity of the DEA and AGF across the network.
  • Tech Infrastructure Deployment: Provisioning and maintaining distributed ledger systems, reputation layers, and cultural monitoring tools.
  • Capital Coordination: Managing trickle-up investment flows, revenue reconciliation, and reinvestment protocols.
  • Conflict Mediation: Offering neutral third-party resolution mechanisms and shared socioemotional language systems.
  • Standards and Integration: Ensuring compatibility across protocols, data formats, and organizational lifecycles.

HAO is Not:

  • A CEO or “founder” structure
  • A traditional holding company or central bank
  • A blockchain DAO governed solely by token-based consensus
  • A static or permanent authority
  • An outside funder extracting profit from edge contributors

It functions as a systems integrator that evolves over time, structured as a coordinating pattern rather than a corporate entity.

Multiple Instantiations

There is no single “correct” HAO. In one network, it might be implemented by a systems integration entity like provide.io. In another, it could emerge as a shared cooperative council. What matters is adherence to structural roles and principles, not branding.

As long as it fulfills the responsibilities of coordination, coherence, and integrity, without concentrating power or value, the HAO pattern is considered valid.