← Deployment

§11.1

Seeding an HAO Network

Initiating a Humanized Autonomous Organization (HAO) — the network’s coordinating framework — depends less on capital or technology than on clarity of intent, defined architectural choices, and trust among founding participants. This section defines the minimum viable conditions, design parameters, and early actions required to instantiate a coherent HAO network.

11.1.1 Prerequisites for Genesis

Before operationalization, the initiating team defines several preconditions for the HAO model:

  • Shared Ethical Grounding: All founding members commit to applying the ETHICAL framework (Empathy, Transparency, Harmony, Integrity, Collaboration, Accountability, Learning & Longevity) as constraints on design and decision-making.

  • Intent Declaration: A Statement of Purpose is codified, answering:

    • What domain or problem space the HAO exists to support
    • Who the first beneficiaries are (members, communities, ecosystems)
    • Why distributed autonomy is more appropriate than centralized control

  • Initial Trust Fabric: A minimum viable trust layer (formed through prior collaboration, trusted referrals, or progressive trust verification) is required for high-stakes cooperation under uncertainty.

  • Resource Alignment: Founders must contribute one or more of:

    • Time-based capital (operational labor)
    • Knowledge capital (design, legal, technical)
    • Financial capital (seed investment, grants, mutual credit commitments)

These are tracked as early “risk contributions” and will later be converted to equity or influence under the HAO’s dynamic value model.

11.1.2 Selection of Domain Scope

While HAO is a general-purpose architectural pattern, early instantiation benefits from domain specificity to constrain complexity. Founders must choose:

  • Generalist HAO (e.g., provide.io, focused on enabling infrastructure and services across sectors)
    Pros: Broad applicability, supports many UMEs (small, self-managing venture teams of up to ~15 people)
    Cons: Higher coordination load, delayed domain feedback

  • Domain-Specific HAO (e.g., ICN (the reference cooperative business network) for cooperative enterprise, MTU (the network’s credit-union-like financial institution) for community banking)
    Pros: Immediate feedback from context-specific needs
    Cons: Requires deeper subject matter expertise

Selection of scope should consider:

  • Level of regulatory complexity (e.g., healthcare vs. creative cooperatives)
  • Capital intensity and infrastructure readiness
  • Potential for UMEs to emerge organically within the chosen domain

11.1.3 Initial Governance Stack

The governance structure must be instantiated at the outset with minimal viable complexity but long-term extensibility. It should include:

Constitutional Layer

  • Codified in a Dynamic Enterprise Agreement (DEA) v0.1 — a versioned operating agreement replacing fixed bylaws
  • Specifies:
    • Core principles and right-to-exit
    • Value accounting primitives (contribution → equity → influence)
    • Process for proposing, accepting, or amending changes (versioned, not overwritten)

Strategic Layer

  • Defines:
    • Short-term funding priorities
    • Network formation sequencing (e.g., which UMEs are bootstrapped first)
    • Role designations (e.g., conveners, facilitators, architects, fiduciaries)

Operational Layer

  • Defines:
    • Decision-making mechanics (e.g., sociocratic consent, dynamic roles)
    • Conflict resolution protocol
    • Feedback cadence and audit schedules

This stack should be bootstrapped using open, forkable governance tools (e.g., DAO-style frameworks, sociocratic role systems, collaborative docs with versioning), with an emphasis on human readability and multi-language accessibility.

11.1.4 Role Formation and Scaffolding

Initial participants act as scaffolders for the broader system rather than as formal “members” of a UME. Suggested minimum roles include:

Role Purpose
Convener(s) Steward initial alignment, facilitate purpose refinement
Architect(s) Translate HAO concepts into operational, legal, and technical patterns
Legal Navigator Design entity formation, agreements, and jurisdictional protections
Systems Integrator Build the initial digital stack (ledger, schema, governance tools)
Cultural Anchor Safeguard psychological safety, coherence, and value alignment

These roles are temporary and rotating, governed by the principle of subsidiarity: authority is held only as long as it is needed, and as close to the point of action as possible.

11.1.5 Readiness Gates and Activation

Before moving from prefiguration to operational launch, the founding team conducts a readiness assessment:

  • Has the purpose been codified in shared language?
  • Do all key roles have redundancy or succession plans?
  • Has the DEA been ratified by all initial participants?
  • Have initial capital contributions (time, knowledge, financial) been logged and committed?
  • Has a minimum viable infrastructure stack been deployed and tested?

Once affirmative, the HAO is considered in “genesis mode” and proceeds to instantiate its first UME(s) and SEP(s) — joint ventures between teams — evolving through the full stack described in Section 11.2 onward.