Policy Keys Reference

Policy selection and mapping for job resolution.

Quick reality check

In current CLI flows, policy is usually selected when posting a job:

consensus-tools jobs post --title "..." --desc "..." --policy APPROVAL_VOTE

Some wrappers expose additional policy helper commands, but the canonical behavior is driven by --policy / policyKey at job creation.

Canonical policy keys

Use these values:

  • APPROVAL_VOTE
  • FIRST_SUBMISSION_WINS
  • HIGHEST_CONFIDENCE_SINGLE
  • TRUSTED_ARBITER
  • OWNER_PICK

Legacy labels and mapping

Legacy labelUse instead
MAJORITY_VOTEAPPROVAL_VOTE
UNANIMOUSAPPROVAL_VOTE (strict threshold/quorum config)
WEIGHTED_STAKEAPPROVAL_VOTE (weighted votes)
FIRST_PAST_THE_POSTFIRST_SUBMISSION_WINS
CONFIDENCE_PICKHIGHEST_CONFIDENCE_SINGLE
ARBITERTRUSTED_ARBITER
MANUALOWNER_PICK

Examples

Approval-vote job

consensus-tools jobs post \
  --title "PR safety review" \
  --desc "Review for regressions" \
  --mode VOTING \
  --policy APPROVAL_VOTE

Speedrun job

consensus-tools jobs post \
  --title "fast patch" \
  --desc "first valid fix wins" \
  --mode SUBMISSION \
  --policy FIRST_SUBMISSION_WINS

Confidence-ranked job

consensus-tools jobs post \
  --title "single best answer" \
  --desc "pick highest confidence submission" \
  --mode SUBMISSION \
  --policy HIGHEST_CONFIDENCE_SINGLE

Next steps

Previous←tests runNextOverview→