WrightOps Field tool 01

Software bounty preflight

Evidence before effort.

Twelve checks before you claim, code, spend, or share access. Mark only what authoritative evidence supports. Missing evidence stays unknown—and unknown counts as a flag.
Runs entirely in this browser

Record what the evidence says

“Clear” requires support. “Present” or “unknown” is counted as a flag.

01

Payout is not verifiably funded. Blocking

Can authoritative evidence show that the stated payout is funded and available?

02

The claim window is closed, expired, or ambiguous. Blocking

Is the claim window open now, with the deadline and eligibility rules confirmed?

03

Someone else is assigned or already building.

Have assignees, claims, pull requests, forks, comments, and submissions been checked?

04

Acceptance criteria are missing or subjective.

Are the deliverable and acceptance tests objective enough to verify before work starts?

05

The person offering payment may lack acceptance authority.

Is it clear who can accept delivery, resolve disputes, and release the payout?

06

You must pay, bond, purchase, or provision first. Blocking

Can the work be attempted without an unjustified bond, purchase, subscription, or spend?

07

Delivery requires private credentials or production access. Blocking

Can the deliverable be completed without secrets, customer data, or live-system access?

08

Payment depends on third-party adoption, promotion, or approval.

Is acceptance controlled by the named payer rather than an unrelated third party?

09

The real scope exceeds the headline task.

Does the estimate include setup, tests, docs, review cycles, support, and collection?

10

The project baseline is unhealthy or inactive.

Does the baseline build, test, and provide enough maintainer activity for acceptance?

11

Rights or compliance obligations are unclear.

Are licenses, data rights, disclosure duties, taxes, and platform rules understood?

12

Expected hourly return falls below your floor.

After costs and payment risk, does expected return still clear the required hourly floor?

Decision rule

Hard stops outrank the count.

Unfunded or unavailable work, unauthorized access, prohibited conduct, and unjustified mandatory spending stay blocked until resolved.

Economics check

Price the whole path to payment.

Include review, revisions, communication, costs, and collection risk.

(payout × payment probability − unavoidable costs) ÷ total hours

Need the evidence sourced for you? WrightOps offers a $49 written GO / HOLD / NO-GO review for one public software bounty, after scope is confirmed.

See the $49 review and request scope