Bounties & Requests (MVP)

Use bounties to request specific proofs: a fact‑check, a set of citations, or a refreshed dataset with provenance. Bounties are funded with CRUX escrow and governed by receipts and clear acceptance criteria.

Why Bounties Exist

Sometimes the evidence you need isn’t in your workspace or is not easily findable on the open web. You might know the question, but not the right sources, or you need a dataset that is scattered across PDFs. Bounties give you a way to ask the community for help while keeping everything proof‑first:

  • You state the claim or data you need and fund a small CRUX escrow.
  • Contributors respond with results backed by QUORUM (MiSES) citations (MiSES = Minimal Evidence Set) and a signed CROWN receipt.
  • You only release escrow when the result verifies and meets your acceptance criteria.

This makes bounties a safe, auditable way to fill gaps without guesswork or blind trust.

Story: “I can’t find the numbers I need”

Maya runs a small charity and needs verified numbers for a grant proposal: “How many community solar installations were added in Region X in 2024?” Search engines return blog posts and opinion pieces, but no trustworthy breakdown.

Here’s how a bounty solves it:

  1. Maya opens Bounties → “Request a proof”. She writes: scope (Region X), timeframe (2024), sources (official registries preferred), and acceptance criteria (≥2 independent domains; licence OK; timestamps ≤12 months).
  2. She funds escrow with CRUX sized for verified mode. The request becomes visible to contributors. OpsCrux tags it “energy • official‑stats • 2024”.
  3. A contributor assembles evidence from the regional energy regulator and an open‑data portal. They submit a short answer with QUORUM (MiSES) chips and a “View Receipt” link. The receipt shows the claim graph, citations, and licence metadata.
  4. WebCrux verifies the receipt and runs automatic checks (diversity, freshness, licence). Everything passes, so Maya releases escrow.
  5. Maya pastes the summary into her grant draft. Later, she uses the Public Proof Page to share the receipt safely with reviewers.

In a day, Maya got the exact numbers, proof and all without hiring a consultant or trusting an unverified blog.

Posting a Request

  1. Describe the claim or dataset needed, scope (jurisdiction, dates), and acceptance criteria.
  2. Fund an escrow amount in CRUX based on the expected mode (verified/audit) and size.
  3. OpsCrux may curate and tag requests for discoverability.

Acceptance & Escrow

  • Escrow releases when a submission includes a valid receipt and meets acceptance criteria (coverage, diversity, licence).
  • Partial fulfilments can earn partial releases; failed receipts result in revisions rather than payout.
  • OpsCrux can close spam or unsafe requests and return escrow to the requester.

What You Receive

  • A concise, cited answer with QUORUM (MiSES) chips (domains, licences, timestamps).
  • A downloadable CROWN receipt for reproducibility and audit.
  • Optional Public Proof Page link for sharing outside your org.

Everything is verifiable without trusting the UI anyone can replay the receipt.

Good Requests Win Faster

  • Be precise (what to prove, why, and constraints).
  • Ask for audit mode only when truly needed; verified mode is often sufficient.
  • Prefer primary sources; ask for counterfactuals when the topic is contentious.

Flow at a Glance

sequenceDiagram
    participant User as You (Requester)
    participant Bounties as Bounties
    participant Ops as OpsCrux (Curation)
    participant Engine as Engine (CROWN/QUORUM (MiSES))

    User->>Bounties: Create request + CRUX escrow
    Bounties-->>Ops: Tag & surface
    Engine-->>Bounties: Submission with receipt
    Bounties-->>User: Auto‑checks (diversity/licence/freshness)
    User-->>Bounties: Accept & release escrow

sequenceDiagram
    participant User as You (Requester)
    participant Bounties as Bounties
    participant Ops as OpsCrux (Curation)
    participant Engine as Engine (CROWN/QUORUM (MiSES))

    User->>Bounties: Create request + CRUX escrow
    Bounties-->>Ops: Tag & surface
    Engine-->>Bounties: Submission with receipt
    Bounties-->>User: Auto‑checks (diversity/licence/freshness)
    User-->>Bounties: Accept & release escrow

If auto‑checks fail, the submission returns for revision. Disputes follow the Disputes & Refunds guide.

Table of Contents