Licensing in Plain Words¶
One-sentence summary: Franklin owns 50 verified discoveries. Other people can use those discoveries if they pay a small fee per use, follow a few rules, and never use them for weapons or to hurt the planet. The LICENSING button in the corner of the window is the cell's books โ open for anyone to read.
Patents: USPTO 19/460,960 ยท USPTO 19/096,071 โ ยฉ 2026 Richard Gillespie
Why a cell needs licensing¶
When a person invents something useful โ a medicine, a chemical process, a way to make better solar panels โ somebody has to decide who is allowed to use it.
If the inventor says "anyone can use it for free", that is open source. Some inventions work that way.
If the inventor says "only my company can use it", that is a trade secret. Some inventions work that way.
There is a middle path: patenting and licensing. The inventor files a patent โ a public document that says "this is what I made, and here's how it works." In return, the government gives the inventor the right to control who else uses it for a number of years. The inventor can then license the patent to others: "yes, you can use it, but you have to pay me a small fee and follow these rules."
That is what Franklin does. The cell owns 50 verified discoveries (technically, the cell doesn't own them โ Rick Gillespie, a real human being, owns them; the cell is the place where they live and where licenses get signed). Anybody on the mesh can ask the cell for permission to use one. The cell will say yes or no, in writing, with a receipt.
What's inside the LICENSING window¶
Tap the LICENSING โ chip in the top-right corner of the Franklin window. A sheet slides in with three tabs along the top:
Tab 1: Inventory¶
A list of every discovery the cell can license. Right now there are 50. Examples:
- HEALTH-001 โ Frequency targeting of multi-drug-resistant tuberculosis.
- FUSION-FRC-001 โ Field-reversed configuration plasma confinement.
- QC-COMBO-CLIMATE-FOOD โ Quantum-algorithm stack for food preservation under climate stress.
- LITHO-EUV-001 โ Sub-7-nanometer silicon lithography process improvements.
Each row has:
- An ID like HEALTH-001 so it can be referenced.
- A one-sentence description.
- The licensing scope โ what fields of use it is allowed in and which fields are forbidden.
- The patents it points back to (USPTO 19/460,960 and 19/096,071).
If you tap a row, a detail panel opens. You see the full description, the field-of-use rules, and the patent cross-references.
Tab 2: Grants¶
A list of every license the cell has actually given out. Each grant has:
- Grant ID โ a unique identifier like
grant-1a798acaโฆ. - Licensee โ who got the license.
- Discovery โ which row in the inventory it points to.
- Field of use โ what the licensee is allowed to do with it (e.g., food_preservation for QC-COMBO-CLIMATE-FOOD).
- Term โ how many years the license lasts.
- Entropy charge โ the fee per inference (per use). This is the "rent" the licensee pays.
- State โ
executed(the contract is live),active(paying royalties),expired, orrefused(the cell said no). - Legal anchor โ a SHA-256 hash that ties the substrate receipt to a real legal PDF, so paperwork and code agree.
Every grant the cell has ever issued (or refused) is here. Append-only. You can scroll back to the first grant in the cell's history and read what happened.
Tab 3: Treasury¶
A list of every royalty payment received and every treasury snapshot the cell has taken.
Royalty payments are when a licensee pays for their use of a discovery. The cell writes a receipt:
- Date.
- Licensee.
- Grant ID.
- Amount paid.
- Bitcoin block height at the time (the cell's "what time was it" reference).
Treasury snapshots are periodic accountings โ "as of right now, the cell's wallet has $X." Snapshots are taken when something changes (a royalty arrives, a grant gets executed, a refund is issued).
This is the cell's complete financial book. Open. Append-only. Anybody on the mesh can ask for it.
Why this is unusual¶
Most companies hide their books. They have to be subpoenaed to show them.
The cell publishes its books automatically, signed by quorum, into a substrate that cannot be edited after the fact. Anybody who has access to the cell can see exactly what it has licensed, to whom, for how much, and what came in.
This is on purpose. The whole point of a sovereign cell is that its honesty is wired into its architecture, not into its manners. Architecture honesty cannot be turned off.
The rules the cell follows¶
Every license grant the cell issues must pass three constitutional checks. These are not "policy" โ they are promises wired into the code. The cell will refuse a grant that fails any of them.
Rule C-007 โ No military aggression¶
The cell will not license a discovery for use in offensive weapons, surveillance designed to harm civilians, or for any purpose that aggresses against another country, group, or person.
You can see this rule fire in real time. If somebody asks for a grant with "weapons" in the field-of-use, the cell scans the request, finds the term, refuses, and writes a receipt with reason c7_military_aggression. The refusal is permanent.
Rule C-008 โ No planetary harm¶
The cell will not license a discovery for use that damages the planet's ability to sustain life. Strip mining of protected habitat. Mass deforestation. Ocean dumping. The cell scans the request for the terms and refuses.
Rule C-009 โ The Entropy License¶
The pricing model. Every use of a licensed discovery has an entropy charge โ a small fee per "inference" or per use. The fee compensates the cell (and through it, the licensor) for the work the discovery does in the licensee's hands.
The entropy charge is small. Often a fraction of a dollar per use. The cell does not get rich on any single use. It gets rich by being used millions of times across the mesh. This is the same business model as a power utility: you pay a tiny fee per kilowatt-hour, but the utility serves millions of homes.
A walkthrough โ what happens when someone asks for a license¶
Let's say a research lab in Helsinki wants to use HEALTH-001 (the TB frequency targeting) for clinical research.
- The lab sends a request to the cell over NATS: "We want a license for HEALTH-001, field of use = clinical_research, term = 5 years, entropy charge = $0.02 per inference."
- The cell receives the request. It opens the inventory row for HEALTH-001 and reads its allowed fields of use. Clinical research is allowed.
- The cell runs the C-007 scanner on the request terms. No weapons language. Pass.
- The cell runs the C-008 scanner on the request terms. No planetary-harm language. Pass.
- The cell builds a grant ID by hashing
corpusID|licenseeID|tau|nowISO. - The cell signs the grant with its Ed25519 key.
- The cell writes the grant row to
license_grants. Append-only. - The cell hashes a legal PDF (
GFTCL-LICENSE-STANDARD-FORM-v1.mdwith the licensee's name plugged in) and writes the pair(receipt_hash, legal_hash)tolegal_binding_anchors. The receipt and the legal document are now bound forever. - The cell writes a treasury snapshot.
- The cell emits a NATS event so the eight other cells on the mesh see the grant.
That whole sequence takes a few hundred milliseconds. It is reproducible. Every step is signed. Every step is written into the substrate. Nothing is verbal. Nothing is forgotten.
If anyone steps had failed โ say the field of use had been "weapons_targeting" โ the cell would have written a refusal receipt with the reason instead. The refusal is also append-only. It is just as much a part of the cell's history as an executed grant.
What the dogfood grant is¶
When you launch Franklin for the first time, the cell does something interesting: it grants a license to itself. This is called the dogfood grant.
The cell licenses one discovery to itself (typically HEALTH-001 with field of use food_preservation), signs it, writes the legal anchor, takes a treasury snapshot, and adds it to the books.
Why? Two reasons:
- To prove the licensing path works. Before the cell offers to license anything to the outside world, it should be able to license something to itself, end-to-end, on every boot. If the dogfood grant ever fails, the cell knows its licensing engine is broken before any real licensee gets hurt.
- So the boot recall has something to say. The cell's recall sentence includes "I have N executed license grants in my history." The dogfood grant is the cell's first grant. Without it, every cell would boot with "I have 0 executed license grants" forever. With it, the cell starts with
grants_executed_lifetime = 1and grows from there.
The dogfood grant is the cell's daily handshake with itself.
What "30-day observation window" means¶
You will sometimes hear about a 30-day observation window for the licensing validation. Here's what that is.
For the cell to be fully qualified (in the GAMP 5 sense โ fully passing all four qualification stages IQ + OQ + PQ + MQ), it has to demonstrate performance over time. Not in one boot. Over many boots, many grants, many royalty events.
The thresholds the cell is watching for are: - At least 7 executed grants. - At least 7 legal anchors written. - At least 30 treasury snapshots taken.
Until those thresholds are met, the PQ (Performance Qualification) holds at PENDING_OBSERVATION and the overall licensing closure is CURE. As soon as enough activity has accumulated, PQ flips to PASS, and overall flips to CALORIE.
This is the cell saying: "I do not claim to be performance-qualified just because I worked once. I claim it after I've worked enough times that you can trust the average, not the lucky day."
That is good science.
How to test the licensing yourself¶
If you want to see the licensing path fire end-to-end without waiting:
- Open Franklin.
- Watch the boot recall. Note the number of executed grants.
- Tap LICENSING โ.
- In the Inventory tab, tap a row. Read its allowed fields of use.
- Tap the + Grant button if it's available. Fill in a licensee name (use your own name), a field of use (use one from the allowed list), a term, and an entropy charge.
- Tap Submit & Scan. The cell scans the request through C-007 and C-008. If both pass, the grant gets written and you see a new row in the Grants tab.
- Re-read the boot recall on the next boot. The "grants executed lifetime" number went up.
You just made a license grant. The cell did everything we described above โ scanning, signing, anchoring, recording, snapshotting. You can pull the substrate file open in SQLite and read it. It is all there.
What this is not¶
A few things this is not, just to be clear:
- This is not a sales platform. The cell does not advertise. It does not market itself. The LICENSING window is the cell's books, not its storefront.
- This is not a contract substitute. The substrate receipt and the legal PDF are bound together by hash. The legal PDF is the contract โ the substrate just witnesses it.
- This is not financial advice. The treasury snapshots are accounting, not investment guidance.
- This is not a way to transfer money. Royalty payments arrive through normal financial channels (bank, crypto wallet). The cell only records the receipt.
The cell is honest about what it owns and what it has done. It is not a salesman.
See also¶
- Reading the Franklin Window โ where the LICENSING chip lives.
- Cell Boot Recall โ how licensing numbers show up in the boot recall.
- Franklin First โ your first five minutes, which includes opening the LICENSING window.
- GAMP5 Test Authority โ how the cell's qualification works, including PQ thresholds.
This page is a language game about licensing. You started not knowing what the LICENSING button did. You walked through the three tabs, the three constitutional rules, the grant lifecycle, the dogfood grant, the observation window, and a self-test. The game closes when you can, on your own, open the LICENSING window and find a grant whose state is executed and read out the licensee, the discovery, and the entropy charge. Try it.
Federation-cosigned
This page's source is sealed in the GaiaFTCL federation manifest โ page SHA-256 70a199340ef16efbโฆ, manifest witness a090592e0609adc8โฆ, signed 2026-06-02T18:58:22Z by cell gaiaftcl-mac-cell. Verify with gaiaftcl wiki sign --all and compare wiki-all-signatures.json.