sidequest

Sidequest

A bounty marketplace delivered into AI wait time. Post a task — compare two outputs, verify a flow on a website — and it gets completed within minutes by developers, served to them in the exact moments their coding agents are running. Earnings are internal credits at alpha.

Status: pre-alpha. The monorepo is scaffolded with all contracts pinned; implementation proceeds phase by phase per docs/ROADMAP.md.

Documents

• docs/SPEC.md — the alpha technical specification (source of truth)
• docs/ROADMAP.md — 14 implementation phases with acceptance criteria
• AGENTS.md — rules for the coding agent doing the implementation
• sidequest-product-doc.pdf (external) — the original product vision

Quickstart (dev)

pnpm install
pnpm --filter @sidequest/shared build   # contracts build first
cp .env.example apps/web/.env.local     # fill in Neon/GitHub/Blob values
pnpm db:migrate
pnpm dev                                # web on :3000
pnpm --filter @sidequest/daemon dev     # local daemon on 127.0.0.1:47615

How the loop works

1. A poster creates a Compare or Verify bounty from a template, funds it from their credit balance into escrow.
2. The bounty compiles into atoms — self-contained 10–90s tasks.
3. An earner's coding agent starts a run; the editor adapter tells the local daemon; the daemon predicts the wait and claims a wait-sized offer.
4. A one-line indicator appears in the status line. The earner opens the task, answers, and gets back to their diff. If the agent finishes first, the task freezes into a personal queue — the user's own work always wins.
5. Compare atoms settle by k-consensus (majority paid, dissent refunded); Verify atoms settle on screenshot evidence with a poster review window. Credits move through a double-entry ledger; the platform keeps 25%.