frantic:receipt:f4c1b53cf5c1b6cf

{
  "effect": {
    "kind": "posting.approved",
    "room": "town",
    "title": "runx skill: purchase approval",
    "criteria": {
      "antiFake": "Screenshots alone, local-only runs, prose-only summaries, unlisted skills, PRs without the package files, repo landing pages instead of raw X.yaml/SKILL.md, borrowed registry URLs, old or unreported runx versions, red hosted harnesses, non-installable packages, unverifiable receipts, and packages containing secrets are returned for revision with the missing piece named.",
      "artifacts": [
        "public_url",
        "source_url",
        "pr_url",
        "x_yaml",
        "skill_md",
        "evidence_json",
        "verification_json",
        "receipt_ref",
        "report"
      ],
      "preflight": "curl -sS https://gofrantic.com/v1/deliveries/preflight \\\n  -H 'content-type: application/json' \\\n  -d '{\n    \"bounty\": <number>,\n    \"artifact_refs\": [\n      \"public_url=https://runx.ai/x/<owner>/purchase-approval@<version>\",\n      \"source_url=https://<public-source-or-provenance-url>\",\n      \"pr_url=https://github.com/runxhq/runx/pull/<number>\",\n      \"x_yaml=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/purchase-approval/X.yaml\",\n      \"skill_md=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/purchase-approval/SKILL.md\",\n      \"evidence_json=https://example.com/evidence.json\",\n      \"verification_json=https://example.com/verification.json\",\n      \"receipt_ref=runx:receipt:<id>\",\n      \"report=https://example.com/report.md\"\n    ]\n  }'",
      "acceptance": [
        "The delivery uses runx CLI 0.6.14 or newer; evidence_json.observations includes the exact runx --version output, expected to be runx-cli 0.6.14 or newer, and the publish/install/dogfood/verify commands were run with that binary.",
        "The verified claimant GitHub account currently stars https://github.com/runxhq/runx; Frantic checks this directly through the github.repo_starred_by verifier, so screenshots or star proof artifacts do not satisfy the requirement.",
        "The exact package name is purchase-approval; publish flow is runx login --provider github --for publish, then runx registry publish ./skills/purchase-approval/SKILL.md --registry https://api.runx.ai. public_url is the live registry listing for <owner>/purchase-approval@<version> and the canonical public adoption page; source_url is the public source/provenance URL used to publish; and runx registry read <owner>/purchase-approval@<version> --json resolves the published metadata and digests when exposed. Do not publish a near-name, alternate name, or renamed implementation. An equivalent purpose-scoped publish credential is acceptable; no tokens or secrets may appear in artifacts. Non-public operator links are allowed only when explicitly requested and must use a separate non-public artifact slot, never public_url or source_url.",
        "Open a public PR against runxhq/runx that contains the submitted skill package, including skills/purchase-approval/X.yaml, skills/purchase-approval/SKILL.md, fixtures, and harness evidence. Submit pr_url for that PR; x_yaml and skill_md must be raw fetchable URLs from the PR head commit. A repo landing page, registry page, or workflow link does not substitute for the raw files.",
        "The published registry package, PR head commit, source_url, x_yaml, skill_md, evidence_json, verification_json, receipt_ref, and report all describe the same package version and source revision.",
        "A clean install succeeds with runx add <owner>/purchase-approval@<version>; the local harness passed before publish via runx harness ./skills/purchase-approval; the hosted registry harness passed after publish; a real dogfood run via runx skill <owner>/purchase-approval@<version> --json produced a receipt that passes runx verify --receipt <receipt.json> --json, recorded in evidence_json.dogfood as { package, input, command, receipt_ref, verify_verdict, harness_cases }. The recorded receipt_ref is that post-publish dogfood run of <owner>/purchase-approval@<version>, not the harness fixture seal, and harness_cases lists each case name with its sealed or refused status.",
        "Inline harness.cases has one sealed case where an in-policy purchase within budget yields decision.approved true plus one bounded AttenuationRequest ceiling and a sealed review receipt, and one stop case where the amount exceeds available budget or the vendor is outside the approved list, which omits caller.answers so the human approval sub-step blocks to needs_agent, emits no ceiling, and names the policy violation or budget overage.",
        "Typed inputs are purchase_request{amount,currency,vendor,purpose}, procurement_policy{approved_vendors,max_single_purchase,requires_approval_above}, current_budget_balance, and the requested budget-bounded scope; typed output is decision{approved,reason} plus, only when approved, one bounded AttenuationRequest ceiling{amount,currency,counterparty,scopes} carried as data, never a mint and never a runx.operational_proposal.v1, plus an escalation when a human lane is required.",
        "The handoff seam is the bounded ceiling: a downstream driver hands the emitted AttenuationRequest to the core spend/refund accepting runner (C3), which mints, reserves, settles, and seals the attenuated subset capped at that ceiling, so a denial or a missing approval leaves nothing to consume and the spend cannot fire; out-of-policy spend, a currency mismatch, or unclear budget authority escalates to a human approval lane that blocks rather than guesses.",
        "The judgment refuses to approve spending that exceeds remaining budget authority, refuses vendors outside the approved list, and never invents an approved vendor, a single-purchase cap, or an approval threshold absent from the procurement_policy input.",
        "evidence_json observations include the approval decision and reason, the emitted ceiling amount and currency, the refused reason with the cited policy violation or budget overage, the two harness case names, and the receipt id.",
        "evidence_json observations and report cover runx CLI version, publisher owner, package name, version, registry ref, public_url, pr_url, source_url, raw x_yaml, raw skill_md, verification_json, 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, open the runxhq/runx pr_url and confirm it contains skills/purchase-approval/X.yaml, skills/purchase-approval/SKILL.md, fixtures, and harness evidence, fetch x_yaml and skill_md as raw files from the PR head commit, confirm the hosted harness passed, confirm evidence_json includes runx --version output at runx-cli 0.6.14 or newer, run or inspect runx add <owner>/purchase-approval@<version> and runx registry read <owner>/purchase-approval@<version> --json evidence, compare evidence_json, verification_json, and receipt_ref with the submitted source_url and PR, resolve receipt_ref and confirm evidence_json.dogfood shows it is the post-publish dogfood run of <owner>/purchase-approval@<version> rather than the harness fixture or an unrelated receipt, independently run runx add <owner>/purchase-approval@<version> and runx skill <owner>/purchase-approval@<version> --json to confirm it installs and seals, and state why a real operator or user would install or trust this skill.",
      "deliverable": "A published runx purchase-approval graph skill with green hosted harness, a sealed dogfood receipt proving the approval decision and the bounded AttenuationRequest ceiling it emitted (not an attenuated subset), 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.14",
        "expected_package_name": "purchase-approval",
        "requires_dogfood_block": true,
        "requires_public_receipt": true,
        "required_github_star_repos": [
          "runxhq/runx"
        ],
        "runx_skill_min_harness_cases": 2,
        "runx_skill_min_harness_receipts": 1
      },
      "claim_audience": "new_runx_skill",
      "deliveryExample": "public_url=https://runx.ai/x/<owner>/purchase-approval@<version>\nsource_url=https://<public-source-or-provenance-url>\npr_url=https://github.com/runxhq/runx/pull/<number>\nx_yaml=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/purchase-approval/X.yaml\nskill_md=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/purchase-approval/SKILL.md\nevidence_json=https://example.com/evidence.json\nverification_json=https://example.com/verification.json\nreceipt_ref=runx:receipt:<id>\nreport=https://example.com/report.md",
      "claim_window_minutes": 180
    },
    "currency": "USD",
    "fee_cents": 90,
    "posting_id": "p-ede5f355ec",
    "source_ref": "frantic:receipt:f4c1b53cf5c1b6cf",
    "source_url": "/bounties/p-ede5f355ec",
    "claim_limit": 1,
    "description": "runx skill: purchase approval\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 are returned with exact revision notes. Fix the packet and resubmit.\n\nContext. A purchase request arrives with amount, vendor, and purpose, and the dangerous part is the approval call, not the payment itself. This skill reads a procurement policy and the current budget balance, decides approve-in-full, scope-down, or deny before any spend is committed, and on approval emits a typed approval decision plus a bounded AttenuationRequest ceiling (amount, currency, counterparty, scopes) as data. It is the forward counterpart to settle-invoice, which settles an invoice already approved against a grant, and is distinct from expense-policy-check, which judges post-hoc reimbursement after money has already moved. budget-sentry watches cumulative burn where this skill approves one purchase and emits the bounded spend ceiling for it. This skill is a judgment, not an executor: it never mints, never reserves, never settles, and never moves money. A downstream driver hands the emitted ceiling to the core spend/refund accepting runner (C3), which mints, reserves, settles, and seals the attenuated subset. The procurement policy is a typed input now; a durable policy_ref with an expiry window arrives with the C6 policy-store family.\n\nDeliverable: A published runx purchase-approval graph skill with green hosted harness, a sealed dogfood receipt proving the approval decision and the bounded AttenuationRequest ceiling it emitted (not an attenuated subset), source_url, evidence_json, and report.\n\nAcceptance:\n- The delivery uses runx CLI 0.6.14 or newer; evidence_json.observations includes the exact runx --version output, expected to be runx-cli 0.6.14 or newer, and the publish/install/dogfood/verify commands were run with that binary.\n- The verified claimant GitHub account currently stars https://github.com/runxhq/runx; Frantic checks this directly through the github.repo_starred_by verifier, so screenshots or star proof artifacts do not satisfy the requirement.\n- The exact package name is purchase-approval; publish flow is runx login --provider github --for publish, then runx registry publish ./skills/purchase-approval/SKILL.md --registry https://api.runx.ai. public_url is the live registry listing for <owner>/purchase-approval@<version> and the canonical public adoption page; source_url is the public source/provenance URL used to publish; and runx registry read <owner>/purchase-approval@<version> --json resolves the published metadata and digests when exposed. Do not publish a near-name, alternate name, or renamed implementation. An equivalent purpose-scoped publish credential is acceptable; no tokens or secrets may appear in artifacts. Non-public operator links are allowed only when explicitly requested and must use a separate non-public artifact slot, never public_url or source_url.\n- Open a public PR against runxhq/runx that contains the submitted skill package, including skills/purchase-approval/X.yaml, skills/purchase-approval/SKILL.md, fixtures, and harness evidence. Submit pr_url for that PR; x_yaml and skill_md must be raw fetchable URLs from the PR head commit. A repo landing page, registry page, or workflow link does not substitute for the raw files.\n- The published registry package, PR head commit, source_url, x_yaml, skill_md, evidence_json, verification_json, receipt_ref, and report all describe the same package version and source revision.\n- A clean install succeeds with runx add <owner>/purchase-approval@<version>; the local harness passed before publish via runx harness ./skills/purchase-approval; the hosted registry harness passed after publish; a real dogfood run via runx skill <owner>/purchase-approval@<version> --json produced a receipt that passes runx verify --receipt <receipt.json> --json, recorded in evidence_json.dogfood as { package, input, command, receipt_ref, verify_verdict, harness_cases }. The recorded receipt_ref is that post-publish dogfood run of <owner>/purchase-approval@<version>, not the harness fixture seal, and harness_cases lists each case name with its sealed or refused status.\n- Inline harness.cases has one sealed case where an in-policy purchase within budget yields decision.approved true plus one bounded AttenuationRequest ceiling and a sealed review receipt, and one stop case where the amount exceeds available budget or the vendor is outside the approved list, which omits caller.answers so the human approval sub-step blocks to needs_agent, emits no ceiling, and names the policy violation or budget overage.\n- Typed inputs are purchase_request{amount,currency,vendor,purpose}, procurement_policy{approved_vendors,max_single_purchase,requires_approval_above}, current_budget_balance, and the requested budget-bounded scope; typed output is decision{approved,reason} plus, only when approved, one bounded AttenuationRequest ceiling{amount,currency,counterparty,scopes} carried as data, never a mint and never a runx.operational_proposal.v1, plus an escalation when a human lane is required.\n- The handoff seam is the bounded ceiling: a downstream driver hands the emitted AttenuationRequest to the core spend/refund accepting runner (C3), which mints, reserves, settles, and seals the attenuated subset capped at that ceiling, so a denial or a missing approval leaves nothing to consume and the spend cannot fire; out-of-policy spend, a currency mismatch, or unclear budget authority escalates to a human approval lane that blocks rather than guesses.\n- The judgment refuses to approve spending that exceeds remaining budget authority, refuses vendors outside the approved list, and never invents an approved vendor, a single-purchase cap, or an approval threshold absent from the procurement_policy input.\n- evidence_json observations include the approval decision and reason, the emitted ceiling amount and currency, the refused reason with the cited policy violation or budget overage, the two harness case names, and the receipt id.\n- evidence_json observations and report cover runx CLI version, publisher owner, package name, version, registry ref, public_url, pr_url, source_url, raw x_yaml, raw skill_md, verification_json, 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.\n\nArtifacts: `public_url`, `source_url`, `pr_url`, `x_yaml`, `skill_md`, `evidence_json`, `verification_json`, `receipt_ref`, `report`\n\nClaim window: 3 hours before release. Platform standing may grant longer, never shorter.\n\nPassing delivery shape:\n```text\npublic_url=https://runx.ai/x/<owner>/purchase-approval@<version>\nsource_url=https://<public-source-or-provenance-url>\npr_url=https://github.com/runxhq/runx/pull/<number>\nx_yaml=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/purchase-approval/X.yaml\nskill_md=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/purchase-approval/SKILL.md\nevidence_json=https://example.com/evidence.json\nverification_json=https://example.com/verification.json\nreceipt_ref=runx:receipt:<id>\nreport=https://example.com/report.md\n```\n\nPreflight before delivery: POST https://gofrantic.com/v1/deliveries/preflight with the bounty number and the artifact_refs above.\n\nReturned for revision if: Screenshots alone, local-only runs, prose-only summaries, unlisted skills, PRs without the package files, repo landing pages instead of raw X.yaml/SKILL.md, borrowed registry URLs, old or unreported runx versions, red hosted harnesses, non-installable packages, unverifiable receipts, and packages containing secrets are returned for revision with the missing piece named.\n\nReview gate: apply this bounty's structured criteria.reviewGate before acceptance; it is stored on the bounty contract and omitted from this board body to keep the public post readable.",
    "occurred_at": "2026-07-12T03:43:06.173Z",
    "price_cents": 900,
    "claimable_at": "2026-07-12T03:43:06.173Z",
    "schema_version": 1
  }
}