Core concepts

Campaign

A data-production program created by a Developer. It brings together the work definition, participation requirements, Tasks, Rewards, review flow, and delivery method. Campaign, Task, Submission, and Reward states are independent.

Task

One unit of work completed by a Contributor within a Campaign. Its instructions and fields come from the human-work configuration in the Pipeline. A claimed Task can be reserved for only a limited time.

Submission

The review record created after a Contributor submits a Task. A Submission is not necessarily an accepted final result and does not by itself mean that a Reward has been earned.

Pipeline

The workflow that determines how Contributors enter a Campaign, complete Tasks, pass quality and acceptance checks, and deliver results. A common path is:

Entry Gate → Supply → Accept

Qualification and Eligibility

Checks that determine whether a Contributor can participate in a Campaign or Task. They can include profile information, region, language, education, experience, Skill, Reputation, courses, Credentials, and Agreements.

Eligibility does not guarantee Task availability.

Agreement

Terms that a Contributor must accept before joining a Campaign or performing a protected action. When a required Agreement changes, the Portal can require the current version to be accepted.

Review and acceptance

Review and quality nodes determine whether a Submission meets the Campaign requirements. Accept determines whether a result can continue to delivery and Reward processing.

Reward and Earnings

A Reward is compensation configured for eligible work. Earnings shows USDC balances, processing states, and withdrawal readiness. A Reward Activity entry is not the same as an available-to-withdraw balance.

Dataset and Data Lineage

A Dataset contains results that can be used downstream. Data Lineage shows where a contribution or result came from and which review, processing, and delivery stages it passed through.