Derivatives & Collaboration

Module of the Three-Tier IP Control Framework Use this alongside the IP Load Balancing and Three-Tier IP Control documentation.


The Core Principle

Liana Banyan is designed for people to build on each other’s work. That’s the whole point — a cooperative where collaboration multiplies value instead of creating legal minefields.

To keep that safe and fair, we distinguish clearly between four types of IP:

TypeWho Owns ItPlatform Rights
Background IPYouOnly what you grant
LB IPLiana BanyanEveryone can use on-platform
LB-Derivative IPYou (under your Tier)LB gets perpetual license
Jointly-Created IPCrew agreementDefined by collaborators

Background IP

What you bring with you.

You keep ownership of your own pre-existing IP and anything you develop independently of the platform.

Key Points

  • You own it. Nothing in LB terms should be read as a blanket assignment of your entire IP portfolio.
  • Grant only what’s needed. If you choose to use your Background IP on the platform, you grant LB only the rights needed to operate (display, integrate into products, route payments).
  • Take it with you. If you leave, your Background IP leaves with you.

Example

You’re a furniture designer who joins LB. Your existing furniture designs are Background IP. If you sell them through Let’s Go Shopping, you grant LB a license to display and process transactions — but you still own the designs and can sell them elsewhere.


LB IP

The platform’s foundation.

LB IP includes the patent portfolio (1,243 innovations, 210 formal claims across 7 applications) and core frameworks the platform is built on.

Key Points

  • Cooperative ownership. LB IP is owned by or assigned to Liana Banyan Corporation.
  • Universal access. Everyone can use LB IP inside the platform under LB’s economic rules (Cost+20%, 60/20/20 split, IP Load Balancing).
  • No external ownership. No individual member owns LB IP — it’s shared infrastructure.

What’s Included

  • Three-Gear Currency system (Credits, Marks, Joules)
  • Tereno Hydraulic Platform mechanics
  • Seedling Guarantee crowdfunding structure
  • The 300 Framework governance model
  • DNA Lock inheritance system
  • All 8 Crown Jewels and supporting innovations

Example

You want to build a new game that uses the Tereno water-channel mechanics. You can — that’s LB IP available to all members. Your game becomes LB-Derivative IP (see below).


LB-Derivative IP

What you create on top of LB IP.

If you create work that directly builds on or incorporates LB IP and you use it on the platform, that work is LB-Derivative IP.

Key Points

  • You can still own it. Subject to your chosen Tier (A/B/C), you own your derivative work.
  • LB gets a perpetual license. LB must have a perpetual license to use LB-Derivative IP inside the ecosystem.
  • Same economics apply. It participates in the same cooperative economics (tiers, IP Load Balancing) as other platform IP.

Creator’s Prerogative: The Three Tiers

Choose your control vs. value balance. More control = smaller pie. Less control = bigger pie.

TierYour EquityPlatform EquityControl LevelBenefit
A49%51%Platform-firstHighest utilization, biggest absolute returns
B60%40%BalancedBest of both worlds
C75%25%Creator-firstMaximum control, smaller pie

Key Insight: Tier A earns MORE absolute dollars despite lower percentage because platform utilization multiplies reach.

Example

You create a new training curriculum that depends on LB’s patented game frameworks. If you use it on-platform, it’s LB-Derivative IP. You own it under your chosen Tier, but LB has a perpetual license to use it within the ecosystem.

What Makes Something LB-Derivative?

Ask these questions:

  1. Does it require LB IP to function? (e.g., needs the Three-Gear Currency)
  2. Does it incorporate LB IP directly? (e.g., uses Tereno mechanics)
  3. Would it not exist without LB IP? (e.g., built specifically for the platform)

If yes to any, it’s likely LB-Derivative IP.


Jointly-Created IP

What you and others create together that is NOT based on LB IP.

When crews collaborate on something that doesn’t depend on LB IP, that’s Jointly-Created IP.

Key Points

  • Crew defines ownership. Ownership and revenue splits are defined by crew agreements, not platform defaults.
  • Flexible structures. You can choose joint ownership, one owner with licenses to others, or a different structure entirely.
  • LB facilitates, doesn’t own. LB provides the collaboration tools but doesn’t claim ownership of Jointly-Created IP.

LB’s Default Recommendation

If you don’t have a specific agreement, we recommend:

  1. Name a steward — One person handles admin (filings, payments, decisions).
  2. Clear economic shares — Everyone involved gets a defined percentage.
  3. Exit terms — Define what happens if someone leaves the project.

Example

Your crew builds a new board game from scratch — original mechanics, original theme, no LB IP involved. That’s Jointly-Created IP. You and your crew decide how to split ownership and revenue. LB just provides the marketplace and manufacturing pipeline.


Derivative Risk Guardrails

To avoid disputes, follow these practices:

1. Choose Your Tier

Every creator chooses a Tier (A/B/C) for IP they register on LB. This determines the equity split for any LB-Derivative IP you create.

2. Document Collaboration Agreements

Every collaboration agreement should:

  • Identify asset types — Which assets are Background IP vs LB-Derivative vs Jointly-Created?
  • Authorization terms — Who can authorize derivatives and under what conditions?
  • Scope limits — Confirm that LB gets rights only for LB-Derivative IP used on-platform, not for unrelated work.

3. Use the IP Registry

Register your IP in the platform’s Innovation Registry. This:

  • Timestamps your creation (blockchain-anchored)
  • Documents the IP type and your chosen Tier
  • Creates a clear record for any future disputes

Quick Reference: “Can I Build On This?”

You Want To Build On…AnswerYour IP Type
Your own pre-existing workYes, alwaysBackground IP
LB’s patented frameworksYes, on-platformLB-Derivative IP
Another member’s Background IPOnly with their permissionDepends on agreement
Another member’s LB-DerivativeYes, on-platform (same rules apply)LB-Derivative IP
Jointly-Created IP from your crewPer your crew agreementPer agreement
Jointly-Created IP from another crewOnly with their permissionDepends on agreement

The Bottom Line

“Build on each other’s work” is a feature, not a loophole.

The IP framework exists to make collaboration safe:

  • Background IP — Yours, always.
  • LB IP — Everyone’s to use, no one’s to own.
  • LB-Derivative IP — Yours under your Tier, with LB license.
  • Jointly-Created IP — Whatever you and your crew decide.

When in doubt:

  1. Document the IP type before you start.
  2. Choose your Tier.
  3. Get collaboration agreements in writing.
  4. Register in the Innovation Registry.


“Help each other help ourselves”

FOR THE KEEP!