Member IP Rules: What You Keep, What You Share
The short version: Use our patents freely. Keep your own unless it’s derivative of ours.
The Core Principle
“You get to use all the patent I.P. freely — within Liana Banyan; without having to share your own.”
This statement is TRUE under these conditions:
| Scenario | Your IP Status | Sharing Required? |
|---|---|---|
| Your IP is independent (not derived from LB IP) | Yours entirely | No — keep 100% |
| Your IP uses LB platform IP in your business | Yours + platform benefit | No — you’re licensed to use it |
| Your IP is derivative of internal LB IP | Must follow LB rules | Yes — if used on platform |
What “Derivative” Means
Your IP is derivative of LB IP if:
- It builds directly on a specific LB patent or innovation
- It couldn’t exist without the underlying LB framework
- It’s a modification, extension, or improvement of LB IP
Examples of DERIVATIVE (must share if used on platform):
- You improve the Patent Bucket algorithm → derivative
- You create a new Three-Gear currency variant → derivative
- You modify the Ghost-to-Physical pipeline → derivative
Examples of NOT DERIVATIVE (you keep entirely):
- You bring your own recipe to Let’s Make Dinner → yours
- You build a business using platform tools → yours
- You create original content on the platform → yours
- You have patents from before joining LB → yours
The Rules in Detail
Rule 1: Your Independent IP Stays Yours
If you bring IP to Liana Banyan that you developed independently:
- You own it 100%
- No automatic sharing with the platform
- You choose whether to register it under the Three-Tier framework
- If you don’t register it, it’s just yours — we have no claim
Rule 2: You Can Use Platform IP Freely (Within LB)
As a member, you’re licensed to use Liana Banyan’s IP portfolio:
- All 1,243 documented innovations are available for platform use
- All filed patents are licensed to members for platform operations
- No additional licensing fees for internal platform use
- Build your business using our IP infrastructure
Limitation: This license is for use within Liana Banyan. External commercial licensing of our patents requires separate arrangements.
Rule 3: Derivative IP Must Follow LB Rules (If Used on Platform)
If you create IP that is derivative of internal LB IP and you want to use it on the platform:
- You must follow LB’s economic rules (Cost+20, three-gear, etc.)
- You choose a tier (A, B, or C) just like any creator
- External licensing can happen under separate contracts with different terms
Key nuance: The rule only applies if:
- Your IP is derivative of LB IP, AND
- You use it on the Liana Banyan platform
If you develop derivative IP but use it entirely outside LB, you can structure it however you want — but you lose platform IP licensing benefits.
Rule 4: The Founder Follows the Same Rules
The Founder’s new IP is treated just like everyone else’s:
- Chooses Tier A, B, or C for each new asset
- Same control vs. payoff trade-offs
- If derivative of internal LB IP and used on platform → follows LB rules
- External licensing → separate contracts allowed
This demonstrates that the system is fair to everyone, including the Founder.
The Three-Tier Framework (If You Choose to Register)
If you voluntarily register your IP with Liana Banyan, you choose:
| Tier | Your % | LB % | Control Level | Use Case |
|---|---|---|---|---|
| A | 49% | 51% | Ethical guardrails only | Maximum utilization |
| B | 60% | 40% | Up to 5 prohibited categories | Balanced control |
| C | 75% | 25% | Case-by-case approval | Maximum control |
Key: This is opt-in. You don’t have to register your independent IP at all.
Common Scenarios
Scenario 1: Recipe Creator on Let’s Make Dinner
Your IP: Original family recipe
LB’s IP: Meal coordination logistics, matching algorithms
Status: Your recipe is yours. You’re using LB’s logistics IP (licensed to you as a member).
Sharing: None required. Your recipe stays 100% yours.
Scenario 2: Manufacturing Node Operator
Your IP: Your manufacturing techniques and processes
LB’s IP: Bounty system, quality protocols, node coordination
Status: Your techniques are yours. You’re using LB’s node infrastructure (licensed).
Sharing: None required. Your processes stay yours.
Scenario 3: Developer Improving Platform Code
Your IP: Bug fixes and improvements to LB codebase
LB’s IP: The codebase itself
Status: This is derivative of LB IP.
Sharing: Contributions to the platform follow platform rules.
Scenario 4: Inventor with Prior Patents
Your IP: Patents you held before joining LB
LB’s IP: Not involved
Status: Completely independent.
Sharing: None. Your prior patents are 100% yours forever.
The “Aircraft Carrier” Metaphor
The Founder puts it this way:
“I’m using my IP to fund the aircraft carrier so I can fly my airplane. And so can you. Because once the carrier is built, anyone else can fly theirs too.”
Translation:
- The aircraft carrier is Liana Banyan’s IP infrastructure (1,243 innovations, filed patents)
- Your airplane is your business, your recipes, your creations
- Flying your airplane means running your business on the platform
- You don’t need to give us your airplane — just use the carrier we built
Summary Table
| Your IP Type | LB’s Claim | Your Obligation |
|---|---|---|
| Independent (not derived from LB) | None | None |
| Uses LB platform IP | Licensed to you | Follow platform rules (Cost+20, etc.) |
| Derivative of LB IP + used on platform | Shared per tier | Register under A/B/C |
| Derivative of LB IP + used externally only | Separate contract | Negotiate separately |
Why This Works
- Attracts creators: You keep your independent IP
- Protects the cooperative: Derivative IP stays aligned
- Funds the infrastructure: Platform IP generates shared value
- Prevents free-riding: You can’t fork LB IP and compete against us
- Maintains fairness: Even the Founder follows the same rules
Further Reading
- Derivatives & Collaboration — Detailed rules for building on each other’s work
- Three-Tier IP Control Framework
- I Built an Aircraft Carrier to Launch My Plane
- Patent Buckets FAQ
- IP Load Balancing on the Ledger
For questions, contact: Support@LianaBanyan.org