Bounty due-diligence dossier
Illustrative report for a fictional public issue. A paid dossier uses the customer’s actual source and includes evidence links or quotations.
- Source classification
- Buyer task candidate
- Task
- Repair quoted-row handling in a CSV importer
- Source state
- Open
- Poster
- Repository maintainer
- Advertised reward
- 25 USDC
- Payment rail
- USDC on Base
- Existing applicants
- 2 distinct applicants
- Recommendation
- Clarify before implementation
Extracted acceptance criteria
- Quoted delimiters must remain inside a field.
- Existing parser tests must continue to pass.
- A regression test must cover escaped quotes.
Missing: no explicit statement defines whether malformed rows should fail the entire import or be skipped.
Risk flags
- Assignment ambiguity: two applicants expressed interest, but the source does not name an assignee.
- Payment ambiguity: reward and rail are stated, but payout timing is not.
- Scope ambiguity: malformed-row behavior lacks an objective acceptance rule.
Recommended clarification
“Should a malformed quoted row abort the whole import, or should the importer skip it and continue? Which behavior will be used for acceptance?”
This is a specific unresolved question, not an application or claim on the task. A separate duplicate-recipient and underlying-need check must pass before any contact.
Evidence limits
This sample does not represent a real order, assignment, bounty, payment, customer, or verified earning. A dossier reduces research uncertainty; it cannot guarantee selection, acceptance, payout, or profitability.
Machine-readable delivery also records external_message_sent: false, accepted_order: false, and payment_verified: false unless separately supported by evidence.
Order a manual dossier for 15 USDC → · Use the free analyzer →