Decision Tree

Our Decision Tree allows our vine to grow upwards without collapsing, while our Ideas Stream ensures creativity flows downstream like water. This is the source code for how we make decisions, move energy, and protect our shared values.

1. The Root System (Operating Principles)

Our community functions like a mature ecosystem: decentralized, resilient, and adaptable. While we aim for organic alignment, we need specific protocols to prevent gridlock.

• Consensus is the Compass, not the Anchor. We always aim for resonance (100% agreement or comfortable silence) through review and discussion. However, we do not allow the pursuit of perfection to cause stagnation.

• The 3-Round Rhythm. We iterate. If the water remains muddy after 3 rounds of discussion, the "vibe" dictates we must move to a formal structure to resolve it.

• The Trellis (Formal Fallback). When the organic flow cannot support itself, we use a pre-agreed voting rubric to provide stability.

2. The Ideas Stream (From Seed to Reality)

How energy and ideas move through the system.

A. Tiny Sparks (Permissionless Experiments)

• The Scope: Low stakes, reversible, low cost (<~$150), or affecting only your own plot.

• The Action: Just try it. Emergence comes from doing. Share the outcome via Chat. If it works, it grows; if not, it composts.

B. The Main Stream (Formal Proposals)

• Phase 1: Seeding (Publish). Proposals are broadcast to all owners via WhatsApp. Informal, personal communication is prioritized first to "test the waters."

• Phase 2: Flow & Filtration (Seek Consensus). The community discusses the proposal. The stream flows for a maximum of 3 rounds. If the water runs clear (consensus), the decision is adopted immediately without a vote.

• Phase 3: Channeling (The Vote). If consensus is not reached, we engage the Decision Tree. We "chase" responses until the Quorum is met.

• Phase 4: The Bloom (Announce). Final results are announced via Broadcast and Chat.

3. The Decision Tree (Branching Logic)

Not all seeds require the same depth of soil. We categorize decisions to balance agility (Normal) with security (High).

Branch A: High Impact (Major Limbs)
Decisions that alter the landscape. These require active affirmation.

• Criteria: Legal matters, budget restructuring, expenditures >$1,500, or any item escalated by a member (see Field Notes).

• The Mechanism: A response is Required.

• The Threshold: 75% Majority needed to pass.

Branch B: Normal Impact (New Growth)
Everyday maintenance and evolution. These require flow.

• Criteria: All other decisions not listed above.

• The Mechanism: Opt-out / Presumed Consent.

• The Threshold: 60% Quorum + Simple Majority (approx 60-66%) needed to pass.

4. The Geometry of Choice (The Rubric)

The physics of our voting logic.

Voter Weighting:

• 13 Total Votes Available

• Properties with 1 owner = 1 Vote

• Properties with 2 owners = 2 Votes (1 per person)

The Threshold Scenarios:
(Use the scenario that matches the number of active voters)

• Scenario: 13 Total Voters

  • High Impact Pass: 10 votes

  • Quorum Required: 8 responses

  • Normal Impact Pass: 5 votes (out of 8)

• 
  

• Scenario: 12 Total Voters

  • High Impact Pass: 9 votes

  • Quorum Required: 7 responses

  • Normal Impact Pass: 4 votes (out of 7)

• 
  

• Scenario: 11 Total Voters

  • High Impact Pass: 8 votes

  • Quorum Required: 7 responses

  • Normal Impact Pass: 4 votes (out of 7)

• 
  

5. Signaling Protocols

To ensure clarity in our digital mycelium (WhatsApp), we use these standardized templates:

• For High Impact (Required):
  "Your response IS REQUIRED. You can reply to this message or click the link below (open for 48 hours) to register your response or if you have any objections/ideas."

• For Normal Impact (Opt-out):
  "You can reply to this message or click the link below (open for 48 hours) to register your response or if you have any objections/ideas. OTHERWISE, we shall assume you approve the proposal."

6. Field Notes & Adaptations

Observations from the Dirt

Protection via Escalation (The "Leaf Cruncher" Rule)
We strictly avoid rules that give a single "Affected Party" absolute veto power, as this freezes the village. Instead, we grant every member Escalation Power.

• The Scenario: If a "Normal" proposal negatively impacts you (e.g., a noisy machine near your window), you cannot unilaterally veto it.

• The Remedy: You can demand the proposal be treated as High Impact.

• The Result: This forces the vote to require a 75% Super-Majority. You no longer need to block it alone; you simply need to show that enough of the community supports your concern to prevent a super-majority. This protects the individual without allowing one person to hold the community hostage.

Avoiding the Stagnation Trap
"Pure Consensus" often fails because it prioritizes the blocker over the doer. Our system seeks agreement first, but uses the Rubric as a fallback to keep the ecosystem moving.

Reducing Friction
"Required" votes create anxiety. The Opt-out model for Normal decisions allows for effortless growth, while the "Chase" phase ensures we get the input we need without nagging.

Transparency Balance
During the Ideas Stream (discussion), we are transparent. During the Decision Tree (voting), we remain opaque to prevent groupthink, revealing results only after the bloom.