ORM-2.2
An individual developer naming the project publicly, under ORM 2.2
One person, no company, releasing or consuming work in their own name. Saying your product is built on or compatible with the Work. This resolves to the Root tier.
Tier
Owed
Nothing. No fee, no report, no filing.
Sections in play
1.7, 11.1, 11.2, 2.1, 2.2, 8.1
Who and what
The situation being resolved.
Actor
An individual developer
One person, no company, releasing or consuming work in their own name.
none
Situation
Naming the project publicly
Saying your product is built on or compatible with the Work.
Rulings
3 questions resolved against the text.
Which tier applies?
Root. One person, no company, releasing or consuming work in their own name. Below $20,000,000 in trailing revenue, or within an exempt category, no Canopy royalty applies. Sections 4, 6, 8, and 10 still bind every Licensee.
Sections 1.7, 2.1, 2.2
Is anything owed?
Nothing. No fee, no report, no filing.
Sections 2.1
May you say what you built on?
Yes, for truthful attribution under Section 8.1. What you may not do is imply endorsement or use the marks as your own branding.
Sections 11.1, 11.2, 8.1
Cautions
What this situation gets wrong most often.
Revenue is measured across entities under common control, per Section 1.4. A parent company above the threshold makes its subsidiary a Canopy Licensee regardless of that subsidiary's own turnover.
Section 8.3 forbids imposing a user ceiling, a regional exclusion, or an output-training restriction downstream where this licence imposes none. That prohibition is the point of the instrument.
Same actor
Other situations for this party.
Non-normative. Where this and the licence text disagree, the licence text applies.