OpenRoots

ORM-2.2

A side business forking and modifying it, under ORM 2.2

A sole trader or small partnership earning under six figures from the work. Changing the Work and distributing your version. This resolves to the Root tier.

Tier

Root

Owed

Nothing. No fee, no report, no filing.

Sections in play

1.7, 2.1, 2.2, 8.1, 8.2

Who and what

The situation being resolved.

Actor

A side business

A sole trader or small partnership earning under six figures from the work.

under 100k USD

Situation

Forking and modifying it

Changing the Work and distributing your version.

Rulings

3 questions resolved against the text.

clear

Which tier applies?

Root. A sole trader or small partnership earning under six figures from the work. 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

clear

Is anything owed?

Nothing. No fee, no report, no filing.

Sections 2.1

clear

What travels with a fork?

Identify the base model under Section 8.1 and publish the nature of the modification and data categories used under Section 8.2.

Sections 8.1, 8.2

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.

Evaluating it internallyOperating it internallyShipping it in productionEmbedding it in a product you sellOffering it as a hosted serviceRedistributing it without chargeReselling itRepackaging itPorting itListing it in a marketplaceUsing it in a larger productDeploying to customer-controlled infrastructureDeploying it for a paying clientTraining a model on itIncluding it in a datasetUsing it for retrieval augmentationCrossing the revenue thresholdBeing acquiredChecking licence continuityCombining it with other licencesNaming the project publiclyContributing backBeing auditedDiscovering you are in breachThe Licensor disappearsProducing an SBOM

Non-normative. Where this and the licence text disagree, the licence text applies.