Patch licensing policy

Licenses attach to one version

Every patch version has its own license terms, published as text and identified by the sha256 digest of that text. When you claim or buy a license, you accept that exact digest. A license covers the version it names. Later versions are only covered if the terms you accepted say so.

What a license does not grant

• Rights to the base model. Base models are licensed by their own authors, and you must follow those terms separately.
• Ownership of the patch or its copyright. A license is permission to use, under the stated scope.
• A guarantee of results. Evidence on the patch page describes a specific test, not your use case.
• Rights to the training data used to build the patch.

Free licenses

Free licenses are accepted by click-through while signed in. No wallet or transaction is needed. Free terms still set a scope, for example personal or internal development use, and can restrict redistribution.

Paid licenses and onchain receipts

Paid licenses are bought through the Retoque license market contract on Robinhood Chain, at a fixed price in an allowlisted payment token. The contract checks that the price and terms digest have not changed since you reviewed them, and records the gross amount, creator payout and platform fee.

A chain receipt proves that a payment was made for a version under a terms digest. It is not a copyright transfer, and on its own it is not a complete license agreement. The terms text it points to is. A license entitlement is bound to the account whose linked wallet made the purchase and is not transferable unless the terms say otherwise.

Purchases on a test network are non-commercial tests and create no paid license.

Downloads cannot be recalled

Before a download, we check your entitlement and issue a single-use, short-lived link. After that, the files are on your systems and nothing technical stops them from being copied. We don't claim otherwise, and a hash on a blockchain does not prevent copying. Your obligations under the terms continue after download.

Withdrawals, refunds and revocation

• A version can be withdrawn if it is found to be faulty, unsafe or disputed. Withdrawal is announced on the patch page, its evidence stays public, and existing licensees keep access where lawful and technically possible.
• For a security problem, we may suspend downloads of a version, including for existing licensees, and will publish a notice saying why.
• Refund terms are part of each version's license terms. Where a refund is given, future access may end, but copies already downloaded can't be recalled.

Creator obligations

Creators who publish a patch confirm that they have the right to distribute it, that their training data was used lawfully, that the patch complies with the base model's license, and that third-party material is credited. Paid publication is limited to verified publishers while the review process is new. Fees and payout timing will be shown before a paid version is published. No fee rate is committed policy yet.

Disputes

If you believe a patch infringes your rights or was built on data used without permission, contact us with the patch name, version and the basis of your claim. We may suspend the listing while we review it. A published contact address for disputes will be added before paid licenses go live.