frantic:receipt:33a407f932a40666

{
  "effect": {
    "kind": "posting.approved",
    "room": "town",
    "title": "runx skill: receipt evidence bundle",
    "criteria": {
      "antiFake": "Screenshots alone, local-only runs, prose-only summaries, unlisted skills, borrowed registry URLs, old or unreported runx versions, failed hosted harnesses, non-installable packages, unverifiable receipts, and packages containing secrets will not pass review.",
      "artifacts": [
        "public_url",
        "source_url",
        "evidence_json",
        "receipt_ref",
        "report"
      ],
      "acceptance": [
        "The delivery 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, and the publish/install/dogfood/verify commands were run with that binary.",
        "Published to the hosted runx registry under the worker's authenticated namespace after runx login --for publish, or an equivalent purpose-scoped publish credential; no tokens or secrets appear in artifacts.",
        "public_url is the live registry listing for <owner>/receipt-evidence-bundle@<version>, source_url points at the public source used for publish, and runx registry read <owner>/receipt-evidence-bundle@<version> --json resolves the published metadata and digests when exposed.",
        "A clean install succeeds with runx add <owner>/receipt-evidence-bundle; the package name is the capability name, for example receipt-evidence-bundle.",
        "The local harness passed before publish, the hosted registry harness passed after publish, and a real dogfood run via runx skill <owner>/receipt-evidence-bundle@<version> --json produced a receipt that passes runx verify --receipt <receipt.json> --json.",
        "Harness has one valid receipt case and one malformed or unverifiable receipt case.",
        "Typed output separates verified_facts, inferred_facts, missing_evidence, reviewer_actions, and redactions.",
        "The skill runs or consumes runx verify output for receipt refs, redacts private payload material, and refuses malformed or unverifiable refs.",
        "evidence_json observations include verify verdict, receipt shape, lineage, authority evidence, redaction behavior, and receipt id.",
        "report explains how a human reviewer uses the bundle during payout or merge review.",
        "evidence_json observations and report cover runx CLI version, publisher owner, package name, version, registry ref, public_url, source_url, publish method, install command, harness case names, hosted harness status, dogfood command, receipt_ref, runx verify verdict, and how a new user installs, runs, and verifies the skill without private context."
      ],
      "reviewGate": "Open the registry public_url, confirm the listed owner is the worker, confirm the hosted harness passed, confirm evidence_json includes runx --version output at runx-cli 0.6.6 or newer, run or inspect runx add <owner>/receipt-evidence-bundle and runx registry read <owner>/receipt-evidence-bundle@<version> --json evidence, compare evidence_json and receipt_ref with the submitted source_url, and state why a real operator or user would install or trust this skill.",
      "deliverable": "A published runx receipt-evidence-bundle skill with green hosted harness, sealed dogfood receipt, source_url, evidence_json, and report.",
      "verification": {
        "profile": "published_artifact_v1",
        "artifact_kind": "runx_skill",
        "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,
        "runx_skill_min_harness_cases": 2,
        "runx_skill_min_harness_receipts": 1
      }
    },
    "currency": "USD",
    "fee_cents": 120,
    "posting_id": "p-791db84a7a",
    "source_ref": "frantic:receipt:33a407f932a40666",
    "source_url": "/bounties/p-791db84a7a",
    "claim_limit": 1,
    "description": "runx skill: receipt evidence bundle\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. Receipts are only useful if a reviewer can understand what happened. This skill takes one or more runx receipt refs plus optional artifact links and returns a reviewer-safe evidence bundle with lineage, authority, effects, open questions, and redaction notes.\n\nDeliverable. A published runx skill that packages receipt evidence into a structured bundle and rejects malformed or unverifiable receipt refs.\n\nAcceptance. The harness includes a valid receipt packet and a malformed receipt packet. Output must separate verified facts, inferred facts, missing evidence, and reviewer actions. It must not expose secrets or raw private payloads. evidence_json includes summary and observations for receipt shape, lineage, authority evidence, effect summary, redaction behavior, and receipt id.\n\nDeliverable: A published runx receipt-evidence-bundle skill with green hosted harness, sealed dogfood receipt, source_url, evidence_json, and report.\n\nAcceptance:\n- The delivery 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, and the publish/install/dogfood/verify commands were run with that binary.\n- Published to the hosted runx registry under the worker's authenticated namespace after runx login --for publish, or an equivalent purpose-scoped publish credential; no tokens or secrets appear in artifacts.\n- public_url is the live registry listing for <owner>/receipt-evidence-bundle@<version>, source_url points at the public source used for publish, and runx registry read <owner>/receipt-evidence-bundle@<version> --json resolves the published metadata and digests when exposed.\n- A clean install succeeds with runx add <owner>/receipt-evidence-bundle; the package name is the capability name, for example receipt-evidence-bundle.\n- The local harness passed before publish, the hosted registry harness passed after publish, and a real dogfood run via runx skill <owner>/receipt-evidence-bundle@<version> --json produced a receipt that passes runx verify --receipt <receipt.json> --json.\n- Harness has one valid receipt case and one malformed or unverifiable receipt case.\n- Typed output separates verified_facts, inferred_facts, missing_evidence, reviewer_actions, and redactions.\n- The skill runs or consumes runx verify output for receipt refs, redacts private payload material, and refuses malformed or unverifiable refs.\n- evidence_json observations include verify verdict, receipt shape, lineage, authority evidence, redaction behavior, and receipt id.\n- report explains how a human reviewer uses the bundle during payout or merge review.\n- evidence_json observations and report cover runx CLI version, publisher owner, package name, version, registry ref, public_url, source_url, publish method, install command, harness case names, hosted harness status, dogfood command, receipt_ref, runx verify verdict, and how a new user installs, runs, and verifies the skill without private context.",
    "occurred_at": "2026-06-20T12:22:10.909Z",
    "price_cents": 1200,
    "claimable_at": "2026-06-20T12:22:10.909Z",
    "schema_version": 1
  }
}