frantic:receipt:3569004d3468feba

{
  "effect": {
    "kind": "posting.approved",
    "room": "town",
    "title": "runx skill: inbox triage to drafted reply",
    "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>/inbox-triage@<version>, source_url points at the public source used for publish, and runx registry read <owner>/inbox-triage@<version> --json resolves the published metadata and digests when exposed.",
        "A clean install succeeds with runx add <owner>/inbox-triage; the package name is the capability name, for example inbox-triage.",
        "The local harness passed before publish, the hosted registry harness passed after publish, and a real dogfood run via runx skill <owner>/inbox-triage@<version> --json produced a receipt that passes runx verify --receipt <receipt.json> --json.",
        "Harness has at least one sealed happy path and one stop/error path for missing sender, missing body, or unsafe reply.",
        "Typed inputs and outputs are schema-validated; input includes a bounded inbox packet, sender metadata, and operator policy, and output includes classification, triage_queue, draft_reply, and gated_send_proposal fields.",
        "The skill drafts a reply but never sends. Any send is represented as a gated proposal.",
        "evidence_json observations include schema validation result, classification labels, draft output, stop condition, and receipt id.",
        "The report explains how the skill composes with send-as without bypassing approval.",
        "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>/inbox-triage and runx registry read <owner>/inbox-triage@<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 inbox-triage 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": 130,
    "posting_id": "p-eec5d2beef",
    "source_ref": "frantic:receipt:3569004d3468feba",
    "source_url": "/bounties/p-eec5d2beef",
    "claim_limit": 1,
    "description": "runx skill: inbox triage to drafted reply\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. Operators need a safe daily skill that reads a bounded inbox packet, classifies messages, drafts replies, and stops before sending. The skill must use fixture data, not a private mailbox, and it must hand off any send through an explicit send-as gate.\n\nDeliverable. A published runx skill under the worker's namespace that accepts a typed inbox packet, returns a triage queue, drafts one professional reply where warranted, and produces a receipt showing no customer-facing send occurred.\n\nAcceptance. public_url is the live runx registry listing under the worker's owner namespace. Hosted harness passes with at least one happy case and one stop/error case. The execution profile (`X.yaml`) declares typed runners, outputs, allowed refs, side-effect posture, and no mutation except an explicit gated send proposal. evidence_json has summary and observations covering input schema, classification labels, draft shape, stop condition, receipt id, and anti-leak checks. report explains how this composes with send-as and where a human approval gate sits.\n\nDeliverable: A published runx inbox-triage 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>/inbox-triage@<version>, source_url points at the public source used for publish, and runx registry read <owner>/inbox-triage@<version> --json resolves the published metadata and digests when exposed.\n- A clean install succeeds with runx add <owner>/inbox-triage; the package name is the capability name, for example inbox-triage.\n- The local harness passed before publish, the hosted registry harness passed after publish, and a real dogfood run via runx skill <owner>/inbox-triage@<version> --json produced a receipt that passes runx verify --receipt <receipt.json> --json.\n- Harness has at least one sealed happy path and one stop/error path for missing sender, missing body, or unsafe reply.\n- Typed inputs and outputs are schema-validated; input includes a bounded inbox packet, sender metadata, and operator policy, and output includes classification, triage_queue, draft_reply, and gated_send_proposal fields.\n- The skill drafts a reply but never sends. Any send is represented as a gated proposal.\n- evidence_json observations include schema validation result, classification labels, draft output, stop condition, and receipt id.\n- The report explains how the skill composes with send-as without bypassing approval.\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": 1300,
    "claimable_at": "2026-06-20T12:22:10.909Z",
    "schema_version": 1
  }
}