ORM-2.2
A reseller or systems integrator discovering you are in breach, under ORM 2.2
Packages and resells software built by others. You realise an obligation was missed, and it may have been missed for some time. 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, 10.1, 10.2, 10.3, 3.1, 5.1, 5.2
Who and what
The situation being resolved.
Actor
A reseller or systems integrator
Packages and resells software built by others.
varies
Situation
Discovering you are in breach
You realise an obligation was missed, and it may have been missed for some time.
Rulings
3 questions resolved against the text.
Which tier applies?
Canopy. Packages and resells software built by others. 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 happens on breach?
Thirty days to cure from written notice, under Section 10.1. Reinstatement is available on curing and paying what would have been owed, with interest, unless you have already had rights terminated for the same Work within twenty-four months. Downstream recipients who remain compliant are unaffected by Section 10.3.
Sections 10.1, 10.2, 10.3
Cautions
What this situation gets wrong most often.
Section 1.7 excludes an entity acting as a reseller or intermediary for a Legal Entity above the threshold from the Root tier, even where its own revenue is small.
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.