hawkes.aiKey ideas
- The one idea — Model licenses range from genuinely permissive (MIT/Apache) to custom terms with scale thresholds, acceptable-use policies, and naming duties — read before you build.
- How it is shown — Three crates, three seals: the permissive stamp, the community license with its threshold clause and use-policy ribbons, the research-only lock — each deciding what actually ships.
- The trap to avoid — "Free to download" read as "free to ship" — the license is the product decision, and it can change between model versions.
- What it sets up — You can judge machinery, meaning of open, and terms — next: judge the CLAIMS.
Some free-to-download models carry contracts: user-count thresholds, acceptable-use rules, even naming duties. Free to download is not free to ship.
The one idea
Model licenses range from genuinely permissive (MIT/Apache) to custom terms with scale thresholds, acceptable-use policies, and naming duties — read before you build.
The model downloaded free; the weights are yours forever. Between you and shipping a product stands one artifact this series hasn't read: the license. Some are as free as they look. Some are contracts in costume. Today: the seals that bind. Start with the real thing. MIT and Apache — software's classic permissive seals — appear on major model families and mean what they've meant for decades: commercial use, modification, redistribution, unencumbered. A top-tier model under one is a substantive commitment, not a vibe. The freedom survives the reading. Note which labs do this. The middle shelf: custom "community licenses," one famous pattern — broadly free, with clauses. A scale threshold: pass a user-count line and separate terms apply; irrelevant to most, decisive for a few.
How it works — the demo
Three crates, three seals: the permissive stamp, the community license with its threshold clause and use-policy ribbons, the research-only lock — each deciding what actually ships.
An acceptable-use policy binding you and your users. Naming duties on derivatives. Workable — if read before, not after. The far end: research-only seals — study freely, ship never. And the quiet hazard: licenses change between versions. Permissive last release can turn conditional this one, a routine bump importing new terms into your product. The license isn't attached to the lab — it's attached to the crate. Check every crate. So install the ritual, per crate, before product: identify the seal. Check thresholds against your ambitions — not your size, your ambitions. Map the use-policy against your surface. Note naming duties.
The trap to avoid
"Free to download" read as "free to ship" — the license is the product decision, and it can change between model versions.
Why it matters — and what’s next
You can judge machinery, meaning of open, and terms — next: judge the CLAIMS.
Pin the version; archive its license text, so a future bump can't smuggle terms past you. Minutes of reading, guarding everything you build. The trap, named finally because it costs real launches: free to download is not free to ship. Two keys. The download button hands out the first; the second is cut individually by your crate's specific version. The license — not the model card, not the hype thread — is the product decision. Read it like one. That completes the legal layer: doors, artifacts, seals — what you can take, know, and ship. The act's next literacy is sharper: the claims. Every release wears a model card — a résumé of benchmark triumphs and careful boasts. Reading one unfooled is a skill. Next group: model cards, and the family tree.
This is one short episode in AI: Zero → Frontier, a step-by-step climb through how AI actually works. Each episode builds only on the ones before it.
Full transcript 2:30 of narration
The model downloaded free; the weights are yours forever. Between you and shipping a product stands one artifact this series hasn't read: the license. Some are as free as they look. Some are contracts in costume. Today: the seals that bind.
Start with the real thing. MIT and Apache — software's classic permissive seals — appear on major model families and mean what they've meant for decades: commercial use, modification, redistribution, unencumbered. A top-tier model under one is a substantive commitment, not a vibe. The freedom survives the reading. Note which labs do this.
The middle shelf: custom "community licenses," one famous pattern — broadly free, with clauses. A scale threshold: pass a user-count line and separate terms apply; irrelevant to most, decisive for a few. An acceptable-use policy binding you and your users. Naming duties on derivatives. Workable — if read before, not after.
The far end: research-only seals — study freely, ship never. And the quiet hazard: licenses change between versions. Permissive last release can turn conditional this one, a routine bump importing new terms into your product. The license isn't attached to the lab — it's attached to the crate. Check every crate.
So install the ritual, per crate, before product: identify the seal. Check thresholds against your ambitions — not your size, your ambitions. Map the use-policy against your surface. Note naming duties. Pin the version; archive its license text, so a future bump can't smuggle terms past you. Minutes of reading, guarding everything you build.
The trap, named finally because it costs real launches: free to download is not free to ship. Two keys. The download button hands out the first; the second is cut individually by your crate's specific version. The license — not the model card, not the hype thread — is the product decision. Read it like one.
That completes the legal layer: doors, artifacts, seals — what you can take, know, and ship. The act's next literacy is sharper: the claims. Every release wears a model card — a résumé of benchmark triumphs and careful boasts. Reading one unfooled is a skill. Next group: model cards, and the family tree.