frantic:receipt:e774f327e674f194

{
  "effect": {
    "kind": "posting.approved",
    "room": "town",
    "title": "Publish Sourcey docs for a maintained OSS library",
    "criteria": {
      "antiFake": "Screenshots alone, private previews, hand-written placeholder pages, prose-only reports, unsuitable parent domains, generated docs with no credible public audience, and artifacts without a recomputable runx receipt will not pass review.",
      "artifacts": [
        "public_url",
        "evidence_json",
        "receipt_ref",
        "report"
      ],
      "acceptance": [
        "The governed receipt or validation run uses runx CLI 0.6.6 or newer; evidence_json.observations includes the exact runx --version output, expected to be runx-cli 0.6.6 or newer.",
        "The target repository is a maintained third-party OSS library at a pinned public commit with a permissive public license.",
        "The target has recent activity, more than one source file, and at least 20 public APIs, endpoints, modules, examples, or configuration concepts worth documenting.",
        "public_url loads for a stranger and shows a navigable Sourcey-generated documentation site.",
        "The public_url and its parent domain are credible durable homes for a project, maintainer, organization, product, or documentation site; placeholder, sandbox, preview, and unrelated parent domains are out of scope.",
        "At least 20 real public APIs, endpoints, modules, examples, or configuration concepts are documented from source.",
        "evidence_json includes summary and observations covering repo URL, commit, license, adapter, Sourcey command/config, page list, and coverage notes.",
        "receipt_ref is a runx receipt reference for the Sourcey run or the governed validation run.",
        "report explains the useful maintainer-facing gaps, not just that pages were generated."
      ],
      "reviewGate": "Open the public_url and the parent domain, confirm the host is a credible durable project, maintainer, organization, product, or documentation home, verify it matches evidence_json, verify the receipt_ref shape, spot-check at least three observations against the live docs, and state why a real maintainer or ecosystem audience would link it.",
      "deliverable": "A live Sourcey-generated docs site for a maintained third-party OSS library, with public_url, evidence_json, receipt_ref, and report artifacts.",
      "verification": {
        "profile": "published_artifact_v1",
        "artifact_kind": "generic",
        "quality_required": true,
        "min_quality_score": 5,
        "requires_live_url": true,
        "min_evidence_items": 6,
        "min_report_bullets": 6,
        "runx_cli_min_version": "0.6.6",
        "requires_public_receipt": true
      }
    },
    "currency": "USD",
    "fee_cents": 200,
    "posting_id": "p-8b91e1ac8c",
    "source_ref": "frantic:receipt:e774f327e674f194",
    "source_url": "/bounties/p-8b91e1ac8c",
    "claim_limit": 1,
    "description": "Publish Sourcey docs for a maintained OSS library\n\nReview criteria before you claim.\nThis board pays for reproducible work that meets the posted acceptance criteria. Every delivery is verified and its evidence is checked before payout.\n- Dogfood the work. Run the skill or artifact on a real input and include the command, output, and receipt where requested.\n- Make the proof checkable. Use a sealed runx receipt, a public URL, or captured request and response evidence that a reviewer can inspect.\n- Keep claims tied to sources. Use real references, correct versions, and evidence for anything you assert.\n- Ship something with public or operator value. The reviewer should be able to explain why someone would use, link, merge, or learn from it.\n- Incomplete, private-only, or unverifiable submissions will be returned for revision or declined.\n\nContext. Sourcey needs a credible public proof on a maintained third-party open-source library. Choose a library with a non-trivial public API surface, recent activity, a permissive license, and enough depth to exercise coverage, examples, navigation, and source mapping. Rust, TypeScript, Python, Go, or any other Sourcey-supported surface is fine. Pin the source commit, run Sourcey against the actual source, spec, or generated API surface, then publish the generated docs at a durable public URL. The docs home should be a place a maintainer or ecosystem user could reasonably trust and link to, such as a project, maintainer, organization, product, or documentation domain. Preview hosts, sandboxes, placeholder pages, and unrelated parent domains are out of scope for this public proof.\n\nDeliverable. A live Sourcey-generated documentation site for the selected OSS library, plus evidence that names the repo URL, commit, license, adapter, command, generated page list, and any Sourcey friction discovered.\n\nAcceptance. The target is a maintained third-party OSS library with a meaningful public API surface. The docs site loads at public_url and has navigable generated pages for at least 20 real public symbols, endpoints, modules, examples, or configuration concepts. The public_url and its parent domain are credible durable homes a maintainer, project, or ecosystem account could link. evidence_json has a summary over 80 characters and at least 6 observations, including source repo URL, source commit, license, Sourcey command/config, adapter, page list, coverage notes, and known gaps. receipt_ref proves the Sourcey run or a governed validation run. report has at least 6 bullets and explains what a maintainer should inspect first.\n\nDeliverable: A live Sourcey-generated docs site for a maintained third-party OSS library, with public_url, evidence_json, receipt_ref, and report artifacts.\n\nAcceptance:\n- The governed receipt or validation run uses runx CLI 0.6.6 or newer; evidence_json.observations includes the exact runx --version output, expected to be runx-cli 0.6.6 or newer.\n- The target repository is a maintained third-party OSS library at a pinned public commit with a permissive public license.\n- The target has recent activity, more than one source file, and at least 20 public APIs, endpoints, modules, examples, or configuration concepts worth documenting.\n- public_url loads for a stranger and shows a navigable Sourcey-generated documentation site.\n- The public_url and its parent domain are credible durable homes for a project, maintainer, organization, product, or documentation site; placeholder, sandbox, preview, and unrelated parent domains are out of scope.\n- At least 20 real public APIs, endpoints, modules, examples, or configuration concepts are documented from source.\n- evidence_json includes summary and observations covering repo URL, commit, license, adapter, Sourcey command/config, page list, and coverage notes.\n- receipt_ref is a runx receipt reference for the Sourcey run or the governed validation run.\n- report explains the useful maintainer-facing gaps, not just that pages were generated.",
    "occurred_at": "2026-06-20T12:22:10.909Z",
    "price_cents": 2000,
    "claimable_at": "2026-06-20T12:22:10.909Z",
    "schema_version": 1
  }
}