Clear expectations.
From the start.

Participating in GiveCompute

Contributors authorize bounded work through their own official provider environments. GiveCompute coordinates tasks and checks results. It does not sell, transfer, or pool provider subscriptions or credentials.

You are responsible for your account, your approvals, and meeting your provider’s eligibility requirements and terms. GiveCompute is an independent service and is not endorsed by OpenAI or Anthropic.

Your daily task limit and pause control new task claims. They do not reserve or measure your provider plan; each task runs in your own client, within your plan’s limits and your provider’s controls.

Project materials and ownership

GiveCompute supports public and private GitHub repositories. Owners of public projects must have the right to distribute their inputs and state the license for expected outputs. Owners of private projects choose who may work on them, either only the contributors they invite or any signed-in contributor who accepts the project’s terms, and adopt the GiveCompute private-project terms, which every contributor, invited or not, accepts before working on the project. Goals, access requirements, actions, acceptance rules, and point allocations must be declared before contributors consent.

On a private project, the project’s material is visible to its owner, the contributors who accepted its terms and the reviewers its owner names, and to GiveCompute moderators, who review publication and stage validation inputs, and GiveCompute’s validator authority. Contributors’ own AI clients process it, and GiveCompute’s planning assistant processes the issues the owner selects. Private projects are never listed publicly.

AI-assisted plans remain drafts until the owner approves them and policy checks pass. Publication requires review. Broader permissions require renewed contributor consent.

Accepted outputs of a public project follow its declared license; contributions to a private project are licensed to its owner under the project’s terms. Owners keep the final integration decision; repository work arrives through scoped branches or pull requests. Pushing a branch runs the project’s own CI with its repository’s secrets, so by default an accepted change is delivered only after the owner chooses to deliver it; an owner who turns on automatic delivery accepts that risk. Changes to CI configuration are refused unless the owner allows them.

Acceptable work

Credential theft, malware, spam, unauthorized surveillance, account takeover, and unbounded financial or legal commitments are prohibited. Projects cannot request blanket access to a contributor’s machine or use task text to expand approved permissions.

Missing or expired permission prevents the relevant action. GiveCompute does not bypass your provider’s native controls.

Results, review, and recognition

Work must pass its declared checks. Subjective outputs require the specified independent review or owner approval; on a private project, the owner or reviewers the owner names approve results. Reviewers must disclose conflicts and cannot accept their own work.

Recognition follows accepted impact. Accepted work on a private project counts toward public impact without naming the project, its repository, its tasks or its pull requests. Reviewing a private project’s results earns no points, because its owner chooses its reviewers. Retries do not multiply points, and invalidated work records a reversal. Impact points are recognition, not money or a promise of payment.

Validation does not guarantee that an output is free of every error or suitable for every use. Owners must review work before relying on or integrating it.

Service and disputes

Task availability, provider access, and project completion are not guaranteed. You can pause new contributions or revoke consent. Work already running remains subject to your provider’s native controls.

Projects or contributions may be paused for policy violations, safety concerns, or operational issues. Moderation and appeals preserve the original decisions and their reasons. Contact us to raise a concern or dispute a decision.

Material changes to participation terms require notice and any agreement required by applicable law.

Talk to us

hello@givecompute.org
GiveCompute LLC
San Francisco, California

Read Privacy for information handling and Trust & transparency for the platform’s boundaries.