Inter-Group Cooperation: Fractal Governance

Scenario: "Outdoor Enthusiasts of Maine" (OEM, 50 members) + "Swim Buddies" (4 members).

The Pattern: "The Joint Venture"

Instead of merging memberships, the two groups form a Third Entity (e.g., "Summer Event Committee").

• Members of Joint Group:
  1. Wallet_OEM (Representing 50 people).
  2. Wallet_SwimBuddies (Representing 4 people).
• Governance Model:
  • Equal Partnership: 1 Vote per Group (1-1 tie possible).
  • Proportional: Votes weighted by membership or contribution (e.g., OEM=50, SB=4).

The Flow: Recursive Voting

This architecture allows groups to act as "Super-Individuals".

1. The Trigger

A proposal is made in the Joint Group:

Prop #1: Allocate $500 for the Combined BBQ. Voting Window: 7 Days.

2. The Fan-Out (Downstream)

The system detects that the "Members" are actually Groups (Smart Accounts).

• Automation: The irl.coop orchestration engine triggers Internal Proposals in both parent groups.
  • OEM Dashboard: New Proposal: "Vote on Joint BBQ" (Links to Prop #1).
  • Swim Buddies Dashboard: New Proposal: "Vote on Joint BBQ" (Links to Prop #1).

3. The Internal Deliberation

• Swim Buddies: Joe, Sam, Tony vote "YES". Bob votes "NO".
  • Internal Result: PASSED (75%).
• OEM: The hikers debate.
  • Internal Result: PASSED (60%).

4. The Roll-Up (Upstream)

Once the internal deadlines hit (or consensus is reached):

• Swim Buddies Lit PKP: Signs a transaction on the Joint Group contract: VOTE: YES.
• OEM Lit PKP: Signs a transaction on the Joint Group contract: VOTE: YES.

5. Execution

The Joint Group Proposal passes (2/2 YES).

• Joint Treasury releases $500.

Technical Requirements

1. Recursive Awareness: The Governance Engine (Secret Network) needs to know that Member_A is actually a Contract_A.
2. Time Buffers:
   • Joint Proposal Duration must be > Internal Proposal Duration.
   • Example: Joint = 7 days. Internal = 3 days.
   • Allows 4 days for the "System Hand" to relay the vote.
3. Vote Translation (Configurable Logic) Each group defines its own "Instruction Logic" in its Secret Contract settings:
   • Thresholds: "We only vote 'YES' on external partnerships if 75% of us agree."
   • Quorum: "We only vote if 50% of us participate."
   • Logic:

     if (internal_yes_percent >= config.upstream_threshold) {
         return "YES";
     } else {
         return "ABSTAIN"; // or NO
     }
     

   • Result: The Joint Group doesn't dictate how Swim Buddies decides; it just accepts the final signal.

Why This Wins

• Autonomy: Swim Buddies keeps their own vibe, treasury, and rules. They don't get "swallowed" by the big hiking group.
• Safety: If the Joint Event is a disaster, Swim Buddies only loses their contribution, not their entire treasury.
• Scalability: This pattern repeats. The "Joint Group" could join a "National Park Federation".