Task Specific Fields
Tasks can include extended fields that depend on the task type or campaign mode. They add additional structure, and don’t overwrite or redefine core fields. Common extended fields include:
Acceptance Criteria (Requester-Facing)
A structured description of what “done” means. For direct deliverable campaigns, this can include objective requirements and rubric-based subjective requirements. For dataset campaigns, acceptance criteria often emphasize consistency, formatting, and schema adherence rather than requester preference.
Cohort Requirements
Rules defining who is eligible to complete the task, expressed as reputation requirements, Account Trust/runtime policy, allowlists, or zero-knowledge attribute proofs.
Privacy Mode
Flags controlling confidentiality constraints such as restricted prompt visibility, redaction requirements, and whether optional external analysis steps are permitted.
Quality Tier
A configuration object that defines validator quorum size, consensus threshold, audit rate, escalation triggers, and dispute availability. This allows the requester to trade off cost, latency, and verification strength.
Assistance Policy
A campaign-declared policy describing whether AI assistance is allowed, allowed only with disclosure, or disallowed for submissions. The policy determines which verification signals may be used, how audits interpret suspected automation, and what penalties can apply for violations after final resolution.
Attachments and Stimuli References
Pointers to off-chain materials (images, documents, audio, prototype links). These are referenced rather than embedded into on-chain data.
Recontact and Longitudinal Fields
Identifiers that allow repeated tasks over time under the same campaign rules, without requiring identity disclosure.
Payment and Settlement Parameters
Per-task payout, bonus rules, and milestone structure. These belong primarily at the campaign level but can be overridden for specific tasks when needed.