ORA-2.2
A scale-up above the threshold checking licence continuity, under ORA 2.2
Past the threshold on trailing revenue, now a Canopy Licensee. You need to know whether a release ever changes licence by time alone. 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, 7.1, 7.2, 7.3
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
Checking licence continuity
You need to know whether a release ever changes licence by time alone.
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
Does the licence change by time alone?
No. Section 7 states that current releases do not convert automatically to Apache, MIT, Creative Commons, or any other fallback licence. A later version can apply to future releases only according to Section 16.
Sections 7.1, 7.2, 7.3
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.