Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

5. Reward Rules

Rewards depend on the quality and value of the submitted session. Arca evaluates the session and any optional repo or workspace context to determine whether it contains useful, authentic, and eligible AI workflow data.

In general, submissions with stronger relevance, authenticity, and meaningful AI interaction are more likely to receive higher rewards.

Qualification Rules

A submission may qualify for reward evaluation when it meets the following conditions:

  • Supported source: The session comes from a source currently supported by Arca, such as Claude Code, Codex, Claude Cowork, VS Code extensions, or Cursor cloud agent.
  • Call-for-Data match: The submission must match a listed Call-for-Data requirement in the Dashboard, such as the requested programming language, AI model, or other stated criteria.
  • Eligible AI model: The session uses at least one model currently listed as eligible.
  • Above minimum effective tokens threshold: The session has reached the required effective token threshold. If the session was previously uploaded, only new interactions added since that upload count toward this threshold and its next quote.
  • Non-duplicate submission: The session must not duplicate a previous submission. A previously uploaded session becomes eligible again only when its new interactions meet the effective-token threshold.
  • Authentic and unaltered session: The original session data must come directly from a supported source and must not be manually edited before submission.

What Affects the Rewards

Arca evaluates each session individually. Estimated quote ranges and final reward amounts may be influenced by:

  • AI interaction quality: Whether the AI session shows meaningful problem solving, clear prompts, useful responses, tool usage, and progress toward a result.
  • Effective interaction volume: The amount of meaningful AI activity in the session, measured using effective tokens.
  • Contributor reputation score: GitHub account credibility and activity can contribute to the reward.
  • Repo relevance: For supported coding sessions, attaching the matching repo or workspace can provide additional context and may increase the quote.