ORA-2.2
A scale-up above the threshold forking and modifying it, under ORA 2.2
Past the threshold on trailing revenue, now a Canopy Licensee. Changing the Work and distributing your version. This resolves to the Canopy tier.
Tier
Owed
A quarterly Canopy Report. Section 5.1 imposes a royalty only when the Canopy Licensee makes Production Use.
Sections in play
1.8, 3.1, 5.1, 5.2, 8.1, 8.2
Who and what
The situation being resolved.
Actor
A scale-up above the threshold
Past the threshold on trailing revenue, now a Canopy Licensee.
20M to 100M USD
Situation
Forking and modifying it
Changing the Work and distributing your version.
Rulings
3 questions resolved against the text.
Which tier applies?
Canopy. Past the threshold on trailing revenue, now a Canopy Licensee. Section 5.2 reporting applies; the Section 5.1 royalty attaches when the Licensee makes Production Use and only to attributable revenue.
Sections 1.8, 3.1, 5.1
Is anything owed?
A quarterly Canopy Report. Section 5.1 imposes a royalty only when the Canopy Licensee makes Production Use.
Sections 5.1, 5.2
What travels with a fork?
Preserve manifest attribution under Section 8.1 and state the model, runtime, or protocol version against which the Modification was validated under Section 8.2.
Sections 8.1, 8.2
Cautions
What this situation gets wrong most often.
Attribution lives in the package manifest under ORA 8.1, not only in documentation, because an agent package is installed by a machine that never reads a directory listing.
Same actor
Other situations for this party.
Non-normative. Where this and the licence text disagree, the licence text applies.