MIT open source

Capacity contribution agreement — MIT open source

1. Parties

This agreement is between {{ownerName}} (the "Owner") and {{contributorName}} (the "Contributor"). It covers one project, {{projectTitle}}, and takes effect on {{effectiveDate}}.

2. What is being contributed

The Contributor commits {{ccuCommitted}} CCU of Claude Code capacity to {{projectTitle}}. One CCU equals one percent of a Claude Pro weekly Claude Code allowance, so {{ccuCommitted}} CCU is that fraction of a week's worth of usage. Alongside that capacity comes the Contributor's time and effort actually directing the work: writing prompts, reviewing output, fixing what the model gets wrong. The platform's ledger is what counts capacity spent, not whether any particular session produced something usable. Spending the capacity is the commitment; a good result is not guaranteed by either side.

3. Ownership of the work produced

Nobody owns this project in the copyright sense, because from the first commit everything goes into the repository at {{repoUrl}} under the MIT licence. Each party keeps copyright in the specific code, prompts, configuration and documentation they personally contribute, and licenses that contribution into the project — and to the public — under MIT terms. The Owner runs the repository and decides what gets merged, but that is stewardship of the project, not ownership of the Contributor's work. Once something is merged and published, it is out in the world under an open licence and stays there.

4. Intellectual property

Each party grants an MIT licence, covering code, prompts, configuration files, documentation and AI-generated output, to the project and to anyone who uses it. Pre-existing material either party brings in — a library, a script, a template written before this agreement — stays under whatever licence it already carries; bringing it in does not silently convert it to MIT, and each party is responsible for only contributing material they have the right to license this way. MIT is silent on patents, so this agreement isn't: each party grants the other, and everyone downstream, a non-exclusive, royalty-free licence to any patent claims they hold that their contributed code necessarily infringes. Neither party can revoke a licence once granted for code already published — that is what "open source from the first commit" means in practice.

5. Credit and attribution

Contributors are credited in the project's contributors list, and the LICENSE file carries the line "Copyright (c) [year] {{copyrightLine}}". Beyond that, MIT's own attribution requirement does the rest: anyone reusing the code has to keep the licence and copyright notice intact. Neither party owes the other any additional credit beyond what MIT already requires.

6. Confidentiality

Almost nothing here is confidential — the whole point is a public repository. Confidentiality is limited to credentials, unpublished infrastructure details (deploy targets, internal keys, private server addresses), and anything either party explicitly marks private before sharing it with the other. Once code is committed to {{repoUrl}}, it is public and this clause no longer applies to it.

7. No warranty

Everything here is provided as-is. AI-generated code and text can be wrong, insecure, or based on a misunderstanding of the task, and neither party promises otherwise. Neither party warrants that the project works, is secure, or is free of third-party rights. Neither is liable to the other for indirect or consequential losses arising from this agreement or the project it produced.

8. Not a partnership, not employment

The Owner and the Contributor are independent parties working on a shared open-source project, not partners, employers, or agents of one another. There is no joint venture. Each is responsible for their own taxes on anything they earn from work related to this project. UseMyTokens is the platform that connected the two of you and hosts the ledger; it is not a party to this agreement and has no obligation to enforce it.

9. Termination

Either party can stop contributing at any point, for any reason, by telling the other. Capacity already spent is not refunded — the platform's ledger reflects what was used. Anything already merged and published to {{repoUrl}} stays published under MIT regardless of who leaves; that is the entire mechanism this agreement relies on. Sections 4, 5, 6, 7 and 10 survive termination.

10. Governing law

This agreement is governed by the laws of {{governingLaw}}. If a disagreement comes up, both parties agree to try to work it out directly before doing anything more formal.

11. Signing

Both parties sign this agreement electronically on UseMyTokens by typing their full legal name. On signing, the platform stores a SHA-256 hash of this exact agreement text alongside each signature, so either the Owner or the Contributor can later prove exactly what they agreed to.

---

Not legal advice. UseMyTokens produced this document from a template. It is a starting point written to be read, not a substitute for a lawyer. Nobody here has reviewed it against your situation, your jurisdiction or your project. If real money, employment, an existing NDA or someone else's intellectual property is involved, get it looked at before you sign.