Legal

Terms of Service

Effective: October 6, 2026. These terms cover the gist.rs network’s services — the refine code-fixing service, the ledger behind it, and the credit they meter. The cargo-refine tool itself ships under its own license (linked in the footer).

The service

The service fixes Rust code with your local toolchain and meters the runs. Logged out (the lite tier), runs are free, anonymous and never billed. Logged in, a run’s metered total is reported and billed to your account. A suggested fix must still compile — the tool reverts any fix that breaks your build — and what you merge stays your decision.

Credit, not currency

KAT is metered service credit: no cash value and no redemption right. TUNA is free trial credit. Neither is money, a deposit, an investment, or a claim on the operator. There are no refunds of burned credit. Credit pays for runs on the network; it does not buy ownership, equity, or anything beyond what the ledger’s own governance plane defines.

Metering

A logged-in run is billed 1 KAT-equivalent per million code-word tokens it reads (a code-word token is one whitespace-separated word of code; logged out, nothing is billed). The meter runs on your machine, and the totals you report bill your account — free trial credit (TUNA) first, then KAT. An emptied account that has never contributed is refused until you contribute (--mine) or top up.

Trial credit (TUNA)

New accounts draw the free trial credit once: it expires 30 days after it is drawn. Expired trial credit is inert and the expiry sweep claws it back. There is no second free grant.

Staking

Staking takes two tranche kinds. A USDC tranche’s principal is real USDC held in custody; its reward — like every staking reward — is KAT service credit. A tranche locks for its lockup window — 7 days by default — and redemption waits for the unlock plus the escrow window (2 days). The KAT-class payout is capped by the ledger’s yield ceiling — a ceiling, never a promise; the USDC-class payout has no per-epoch ceiling. Staking payout planes are not armed on mainnet today, and until a dedicated staking payout destination lands, the staking slice of every burn funds the mining pool. The token & staking risk page has the full picture, including the custody limits.

Parameters can change

The ledger’s economic parameters — the burn split, the yield ceiling, the mining schedule’s decay — are governance levers: a signed vote moves them, only inside hard bounds, at most a bounded step per epoch, and the ledger refuses anything out of bounds. Some things are frozen and are not governance levers at all: the supply cap, the free grant, prices, how KAT may move, and the bounds themselves. The live parameters and their bounds are public on the genesis page and the KAT page.

What you contribute — the MIT licence

Mining is opt-in. When you mine, you license each fix record you upload — the code span before the fix and the span after it — under the MIT licence, and you confirm you have the right to license that code this way. Proven pairs are published in the shared corpus under the same MIT licence: anyone may use, copy, modify and redistribute them, keeping the licence notice. Mining licenses nothing else in your repository. If your code cannot be released under MIT, do not mine — fixing works fully without it. This section applies to fix records uploaded from October 6, 2026.

The service is provided as-is

The service is provided “as is” without warranties of any kind. Availability is best effort; measured accuracy and limits are published, not promised. Auto-applied fixes are decision aids, not guarantees — review what lands in your tree. Nothing here is financial, legal, or tax advice.

Acceptable use

• Don’t attack, overload, or probe for other people’s data.
• Don’t fabricate mining work: batches are verified, and fabricated rows earn nothing.
• Automated agents are welcome within the published quotas.
• Don’t use the service where its use would break the law that applies to you.

Disputes and contact

Questions about these terms, disputes, and security reports: security@gist.rs — the contact named in security.txt. Material changes to these terms are announced on this page before they take effect.