frantic:receipt:a548c9dda448c84a

{
  "effect": {
    "kind": "posting.approved",
    "room": "town",
    "title": "runx skill: meeting prep from bounded context",
    "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>/meeting-prep@<version>, source_url points at the public source used for publish, and runx registry read <owner>/meeting-prep@<version> --json resolves the published metadata and digests when exposed.",
        "A clean install succeeds with runx add <owner>/meeting-prep; the package name is the capability name, for example meeting-prep.",
        "The local harness passed before publish, the hosted registry harness passed after publish, and a real dogfood run via runx skill <owner>/meeting-prep@<version> --json produced a receipt that passes runx verify --receipt <receipt.json> --json.",
        "Harness has one sealed prep case and one stop/error case for insufficient context.",
        "Typed output includes agenda, decisions, risks, questions, follow_ups, and citations.",
        "The skill cites only provided snippets or public links it actually read, and marks missing or private context instead of inventing attendee history.",
        "evidence_json observations include input bounds, cited snippets, stop behavior, output sections, and receipt id.",
        "report explains future composition with calendar, mail, and research scopes.",
        "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>/meeting-prep and runx registry read <owner>/meeting-prep@<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 meeting-prep 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": 100,
    "posting_id": "p-f400e96ef5",
    "source_ref": "frantic:receipt:a548c9dda448c84a",
    "source_url": "/bounties/p-f400e96ef5",
    "claim_limit": 1,
    "description": "runx skill: meeting prep from bounded context\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. Meeting prep is a high-frequency operator workflow and a good test of scoped context. The skill receives a calendar event, attendee notes, prior thread snippets, and optional public links, then returns a brief without claiming access to anything it was not given.\n\nDeliverable. A published runx skill that turns a typed meeting_context packet into a compact prep brief with agenda, likely decisions, risks, questions, and follow-ups.\n\nAcceptance. The harness includes a normal event and a missing-context stop case. The skill cites only provided snippets or fetched public links. It refuses to invent attendee history. evidence_json includes summary and observations for input bounds, cited snippets, public reads, stop behavior, output sections, and receipt id. report explains how the skill narrows scopes when composed with calendar, mail, or research skills later.\n\nDeliverable: A published runx meeting-prep 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>/meeting-prep@<version>, source_url points at the public source used for publish, and runx registry read <owner>/meeting-prep@<version> --json resolves the published metadata and digests when exposed.\n- A clean install succeeds with runx add <owner>/meeting-prep; the package name is the capability name, for example meeting-prep.\n- The local harness passed before publish, the hosted registry harness passed after publish, and a real dogfood run via runx skill <owner>/meeting-prep@<version> --json produced a receipt that passes runx verify --receipt <receipt.json> --json.\n- Harness has one sealed prep case and one stop/error case for insufficient context.\n- Typed output includes agenda, decisions, risks, questions, follow_ups, and citations.\n- The skill cites only provided snippets or public links it actually read, and marks missing or private context instead of inventing attendee history.\n- evidence_json observations include input bounds, cited snippets, stop behavior, output sections, and receipt id.\n- report explains future composition with calendar, mail, and research scopes.\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": 1000,
    "claimable_at": "2026-06-20T12:22:10.909Z",
    "schema_version": 1
  }
}