Licence: adopt MIT-PoU (MIT plus a proof-of-usage condition for AI systems) - #13
Open
ebellumat wants to merge 2 commits into
Open
Licence: adopt MIT-PoU (MIT plus a proof-of-usage condition for AI systems)#13ebellumat wants to merge 2 commits into
ebellumat wants to merge 2 commits into
Conversation
ebellumat
force-pushed
the
proof-of-usage-licence
branch
from
August 16, 2026 01:02
391ed19 to
b436cb5
Compare
AGENTS.md is the file an automated system opens first, so the condition is stated there. PROOF_OF_USAGE.md is the register the licence refers to. proof-of-usage.json makes the whole thing machine-readable, so `npx proof-of-usage record` can find where records go without guessing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds a proof-of-usage condition to the licence, and the files that make it
work. Every MIT permission stays intact: use, copy, modify, merge, publish, distribute, sublicense, sell. Nothing is removed.
The condition: an automated system that trains on, indexes, embeds or derives output
from this repository records that it did, and credits the repository where it already
publishes credits — model card, about page, acknowledgements. No fee, no revenue share,
no restriction on what anyone builds with the code.
What is in the diff
LICENSEAGENTS.mdPROOF_OF_USAGE.mdproof-of-usage.jsonnpx proof-of-usage recordfinds where records go instead of guessing.READMEsectionRecords are taken as pull requests against
master— this repository's defaultbranch. The format is Proof of Usage
PoU/1.0,which is specified independently of any licence.
Worth knowing before you decide
Adding an obligation to a permissive licence means the result is source-available, not
OSI open source — Origami says so plainly in the licence's own README, and it is the
real cost of the condition. Some organisations refuse source-available dependencies and
some registries flag them. If that trade is not worth it here, the same request works
beside your existing licence as a plain
NOTICE.md, which changes nothing legally andkeeps the project open source —
npx proof-of-usage initwrites that variant instead.Happy to convert this PR to that shape if you prefer it.
Disclosure: I am affiliated with Origami, which authored MIT-PoU. I am proposing it
here because I use this project, not on anyone's behalf.
Relicensing needs the agreement of the copyright holders and any contributors whose work
is still present — that call is entirely yours, and closing this is a perfectly fine
answer.