Guild Architecture Proposal

Date: February 2, 2026
Status: Draft for Founder Review
Innovation: #1098-#1105

The Questions

1. What guilds need to exist?
2. How do they map to portals (.com, .biz, .net, .org)?
3. Can members be in multiple guilds? (Yes, but how?)
4. How do we prevent cross-guild voting capture? (“Surge Protection”)
5. How do we solve the cold-start problem? (“Wait-A-Minute-Vines”)

Portal-Guild Mapping

.com (LianaBanyan.com) — Consumer Portal

No guilds. This is for general members using services.

Members here are customers of guild members, not guild members themselves.

.biz (LianaBanyan.biz) — Business Portal

Guilds for those who SELL goods/services.

.net (LianaBanyan.net) — Employment Portal

Guilds for those who WORK.

LinkedIn Integration (Optional):

• Import work history, skills, endorsements
• NOT required — members can build profile from scratch
• Other integrations welcome (Indeed, Glassdoor, etc.)
• “Lighthouse” model: we accept signals from anywhere

.org (LianaBanyan.org) — Initiative Portal

Councils, not guilds. Each initiative has its own council.

Multi-Guild Membership

The Rule: Yes, Unlimited Guilds

A member can belong to as many guilds as they qualify for and can afford.

Requirements Per Guild

Example: Multi-Guild Member

Sarah the Developer-Chef:

• Tech Guild (.net) — writes code
• Artisan Guild (.biz) — sells handmade pottery
• Let’s Make Dinner Council (.org) — volunteers cooking

She pays three fees, maintains three reputations, follows three rule sets.

If she violates pottery guild rules, it doesn’t affect her coding reputation.

Surge Protection (#1098)

The Problem

If 80% of Guild X members are also in Guild Y, Guild Y’s interests can capture Guild X’s decisions.

Example: Most Merchant Guild members are also Tech Guild members. Tech Guild votes to require all Merchant Guild listings use a specific (complex) API. Non-tech merchants get steamrolled.

The Solutions

1. Guild-Specific Voting Weight

Your vote in Guild X is weighted by your activity in Guild X, not overall platform activity.

Vote Weight = (Guild-Specific Reputation) × (Guild Tenure Bonus) × (Recent Activity Multiplier)

Someone who joined Guild X yesterday but has high reputation in Guild Y gets minimal vote weight in Guild X.

2. Cross-Guild Quorum Rules

If a vote affects another guild AND >40% of voters are members of that affected guild:

• Require supermajority (66%) instead of simple majority
• Trigger notice period (7 days) for affected guild to respond
• Allow veto by affected guild council (can be overridden by 75%)

3. Conflict Disclosure Requirement

When voting on matters that could affect another guild you’re in:

• System automatically flags the conflict
• Your vote is tagged as “conflicted” (visible in results)
• Does NOT prevent voting, just makes it transparent

4. Cooling-Off Period

New guild members cannot vote for 30 days after joining.

Prevents “guild raiding” — joining a guild just to vote on one issue.

5. Quadratic Voting (Already in Platform)

Reduces whale influence regardless of cross-membership.

Cost of N votes = N² tokens
1 vote = 1 token
2 votes = 4 tokens
10 votes = 100 tokens

6. Guild Council Veto

Each guild’s elected council can veto any member vote with 2/3 council agreement.

Members can override council veto with 80% supermajority.

Wait-A-Minute-Vines: Cold Start Solutions (#1099-#1105)

The Problem

New member: “I made an extra meal and posted it. No one bought it.”

Why?

• No one knows the platform exists yet
• No buyers in their area
• No trust established
• No reviews to prove quality

Solution 1: Seedling Guarantee (#1099)

The platform guarantees the first sale.

The food goes to someone in need (Do The Swoop recipient, local shelter, etc.)

Solution 2: Pre-Commitment Pools (#1100)

Match demand to supply BEFORE production.

“I would buy a home-cooked meal if someone near me made one.”

No wasted effort. Maker knows there’s a buyer before cooking.

Solution 3: Local Density Focus (#1101)

Don’t launch everywhere. Launch in clusters.

Concentrate members so supply and demand can find each other.

“Better to be essential to 100 people than known to 10,000.”

Solution 4: Cross-Initiative Referral (#1102)

If someone uses Let’s Get Groceries, suggest Let’s Make Dinner.

“You bought ingredients. Would you like someone to cook them?”

Solution 5: Discovery Boost (#1103)

New listings get promoted for 72 hours.

Solution 6: Anchor Member Recruitment (#1104)

Recruit “heavy users” first.

Strategy: Before opening a new area, recruit 5 anchors who commit to minimum activity.

Solution 7: Turnkey Starter Kits (#1105)

“Hit the ground running” packages for new members.

Each kit answers: “I just joined. What do I do in the next 10 minutes?”

Integration Architecture: The Lighthouse Model

Philosophy

Liana Banyan is a lighthouse, not a walled garden.

LinkedIn Integration (.net)

NOT required. Members can build profile from scratch.

Other Integrations (Planned)

API Philosophy

INPUT: We accept data from anywhere
OUTPUT: We export data anywhere the member chooses
LOCK-IN: None. Your data is yours.

Summary: Member Journey

Day 1: New Member

1. Sign up at .com (free)
2. Browse initiatives, see what’s available
3. Decide to participate: Join Let’s Make Dinner

Day 7: First Offering

4. Post first meal offering
5. If no buyer in 48 hours: Seedling Fund purchases → food goes to need
6. Get first review
7. Appear in “New in Your Area” digest

Day 30: Established

8. Regular buyers
9. Reviews accumulate
10. Consider joining Artisan Guild (.biz) to sell preserved foods

Day 90: Multi-Guild

11. Join Artisan Guild (fee: X/month)
12. Join Harper Guild (.net) to help with workplace ethics
13. Three separate reputations, three fee streams, three rule sets

Ongoing: Protected

14. Votes in Artisan Guild weighted by Artisan activity
15. Cross-guild conflicts disclosed automatically
16. Can’t be steamrolled by members who joined just to vote

Innovations This Document

Founder Decisions Needed

“Don’t force people into your system. Make your system so useful they choose it.”

For the Keep.