Equal partners

Capacity contribution agreement — equal partners

1. Parties

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

2. What is being contributed

The Contributor commits {{ccuCommitted}} CCU of Claude Code capacity to the project. One CCU equals one percent of a Claude Pro weekly Claude Code allowance, and the platform's ledger — not the Owner's or Contributor's own account of things — is what determines how much has actually been spent. Alongside that capacity comes the time and effort it takes to use it: reviewing output, steering the model, fixing what it gets wrong, and shipping the result.

3. Ownership of the work produced

Anyone who contributes at least {{coOwnerThresholdCcu}} CCU to this project becomes an equal co-owner of its copyright, holding an equal undivided share alongside every other contributor who has also crossed that line. This is not proportional to how much any one person spent above the threshold — it is one contributor, one equal share. As new contributors qualify, shares re-divide equally among everyone who holds one, including the Owner. The Owner's own share shrinks each time someone new qualifies, exactly like everyone else's.

{{ccuCommitted}} is the Contributor's commitment against the {{coOwnerThresholdCcu}} CCU threshold. The share does not vest on the promise. It vests only once the threshold is actually reached and that capacity has actually been spent, as recorded on the ledger.

Major decisions — relicensing the project, selling it, taking on investment, changing this agreement, or admitting a new co-owner below the {{coOwnerThresholdCcu}} threshold — are decided by {{decisionRule}}. Day-to-day maintenance and merging ordinary contributions need no vote. Net revenue from the project splits equally among co-owners, and net costs split the same way, except that no co-owner has to fund anything they did not agree to in advance. If {{decisionRule}} produces no answer within 30 days, any co-owner may fork the project under their standing licence from clause 4 and continue without the others. A co-owner who leaves keeps their vested share and their standing licence, and simply stops accruing anything new.

4. Intellectual property

Ownership under clause 3 is joint ownership of the copyright in the work. Every co-owner holds a standing, non-exclusive, irrevocable licence to use, modify, and reuse the work — including in their own future projects, commercial or not — without asking permission or accounting to the other co-owners for it.

Each side keeps whatever they already owned coming in: pre-existing code, tools, templates, or material either party brings to the project stays theirs. By contributing it here, the owning party grants the other co-owners the licence they need to use that material as part of this project, but ownership of the underlying pre-existing material does not transfer. This covers code, prompts, configuration, documentation, and anything the Claude Code sessions generate along the way.

5. Credit and attribution

Every co-owner gets credited as a contributor to {{projectTitle}} wherever the project lists its contributors — READMEs, release notes, project pages. No one is entitled to be listed as sole author or sole owner once co-ownership has vested.

6. Confidentiality

Anything shared to do this work — private repository access, credentials, unreleased plans, unpublished business details — stays confidential and is used only for the project. That obligation does not cover information that is already public, or that a party already knew independently before this agreement. Either party may say, publicly, that they worked on {{projectTitle}} and describe their role in general terms; that is not a confidentiality breach.

7. No warranty

The work is provided as-is. AI-generated code and content can be wrong, insecure, or infringe something neither party checked for. Neither the Owner nor the Contributor promises that the project works, is secure, or is free of third-party rights issues. Neither is liable to the other for indirect or consequential losses arising from the work or from this agreement.

8. Not a partnership, not employment

Co-owners of a work are not partners in a legal partnership. This agreement does not create one, and does not create employment, agency, or a joint venture. Each side is responsible for their own taxes on anything they earn from the project. UseMyTokens is the platform that facilitated this agreement — it is not a party to it and has no obligation to enforce it.

9. Termination

Either party can walk away from future involvement at any time by telling the other in writing. Capacity already spent is not refundable in CCU or in cash. Clauses 3 through 8 survive termination, since they govern ownership of work already done, not future participation.

10. Governing law

This agreement is governed by the laws of {{governingLaw}}. Before either side takes a dispute anywhere else, they agree to try to work it out between themselves first.

11. Signing

Both parties sign this agreement electronically on UseMyTokens by typing their full name. The platform stores a SHA-256 hash of this exact text alongside each signature, so either party can later prove exactly what they signed.

---

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.