← Structure

§2.3

Strategic Enterprise Partnerships (SEPs)

United Micro Enterprises (UMEs) — small, self-managing venture teams of up to ~15 people — act as autonomous units of value creation. Strategic Enterprise Partnerships (SEPs) — joint ventures between teams — are how UMEs collaborate, formally, temporarily, or semi-permanently, to pursue goals beyond an individual UME’s scope. A SEP is not a merger, acquisition, or hierarchical relationship; it is a collaboration framework defined by agreements, shared ownership, and bounded scope.

SEPs allow the network coordinated by the HAO (the network’s coordinating framework) to scale horizontally without centralization and without sacrificing local autonomy.

Purpose and Function

SEPs exist to:

  • Enable coordinated action across multiple UMEs without dissolving their autonomy
  • Pursue shared missions or access new markets that are impractical for individual UMEs to reach alone
  • Pool resources, capabilities, or infrastructure in ways that benefit all parties
  • Prototype or pilot initiatives that may eventually become new UMEs or system-wide features
  • Provide bounded accountability, legal clarity, and economic coordination for joint ventures

In short, SEPs let UMEs work together without forming a new bureaucracy or permanently binding themselves to one another.

Key Characteristics

A Strategic Enterprise Partnership is defined by several core design traits:

  • Collaborative, not Competitive: Formed around mutual benefit and aligned mission.
  • Scoped and Time-bound: Defined by a charter, with milestones and review points.
  • Legally Structured: Can be instantiated as a joint LLC, contract-based collaboration, or trust-bound cooperative venture.
  • Governance-Aware: Uses a hybrid of the partners’ local governance systems, with agreed fallback protocols for conflict or impasse.
  • Dynamic Equity Participation: Revenue or asset rights are distributed based on contributions and commitments, not fixed shares.

Each SEP is unique, but all share a common structural grammar that keeps them legible to the network.

Formation Process

The SEP lifecycle is governed by a Shared Project Formation Protocol, which includes:

  1. Intent Declaration: Public or private articulation of the mission, timeline, partners, and expected outcomes.
  2. Partner Vetting and Alignment: Capability assessment, value alignment review, and legal-technical readiness.
  3. SEP Charter Drafting: Agreement on scope, decision protocols, value flows, and conflict resolution.
  4. Resource Commitment: Each UME (and potentially the HAO) declares what it is contributing: time, capital, access, tech, reputation.
  5. Legal Instantiation (if needed): Setup of joint legal entity or binding contract structure.
  6. Launch: Initiation of operations, tracked against shared KPIs and milestones.

SEPs can be created quickly (some form and deploy within days using standardized templates), while others evolve over months for more complex initiatives.

Governance Structure

SEP governance is designed to be:

  • Lightweight: Focused on coordination rather than control.
  • Proportional: Voting power or influence can be based on stake, effort, or domain expertise.
  • Fail-safe integrated: Includes predefined fallback paths if trust breaks or partners exit.
  • Versioned: SEP charters are treated as living documents and updated through formal processes.

A SEP uses facilitated coordination, with rotating roles such as:

  • SEP Steward: Maintains alignment and rhythm
  • Operations Lead: Handles execution-level oversight
  • Finance Contact: Manages pooled budgets and revenue sharing
  • Governance Contact: Responsible for protocol adherence and internal checks

Roles are filled by partner UMEs, often rotated or reassigned periodically.

Economic Agreements

SEP value flows are encoded in a Dynamic Revenue Participation Model, which defines:

  • Revenue Distribution Rules: How proceeds are split across participating UMEs (and potentially the HAO)
  • Expense Responsibility: Who bears what operational or capital costs
  • Equity and IP Rights: Whether the output is shared, licensed, or owned by a specific UME
  • Reinvestment Pooling: Option to allocate a % of returns to further SEP expansion or spinouts

SEP agreements are structured to change as partners’ contributions or circumstances shift.

Examples

Example 1: Multi-UME Product Launch
Three UMEs—one specializing in design, one in software development, and one in education—form a SEP to create an ethical edtech platform. They sign a SEP charter, launch a joint pilot, and agree to distribute revenue proportionally based on effort and resource inputs.

Example 2: Regional Market Interface
A cluster of UMEs in a geographic region form a SEP to interface with a local logistics provider. They create a pooled legal entity, negotiate as a collective, and rotate service contracts across members.

Example 3: Public Infrastructure Build
The HAO initiates a SEP with five mature UMEs to co-develop a new governance tool. Contributions include funding, development time, and operational testing environments. All resulting infrastructure is licensed back to the network.

Exit and Transition

SEPs are designed to end, evolve, or spin out. At any point:

  • Partners can exit under defined protocols
  • The SEP can end upon completion of its mission
  • A SEP can spin out into a new UME, SEP, or shared infrastructure layer
  • If conflict emerges, fallthrough governance and mediation procedures are followed, with HAO mediation only as a last resort

SEP dissolution does not indicate failure; it indicates that the SEP’s bounded intent has reached a natural conclusion or transformed into something else.

Relationship to UMEs and HAO

SEPs sit at the meso-layer between UME autonomy and HAO coherence:

  • They are formed by UMEs
  • Often use HAO infrastructure
  • Can be funded, seeded, or incubated by the HAO
  • And may eventually inform broader network evolution

They are a mechanism for scaling the network without centralizing it.