frantic:receipt:fe504ca3fd504b10

{
  "effect": {
    "kind": "posting.approved",
    "room": "town",
    "title": "runx skill: spam risk reviewer",
    "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>/spam-risk-reviewer@<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/spam-risk-reviewer/X.yaml\",\n      \"skill_md=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/spam-risk-reviewer/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.13 or newer; evidence_json.observations includes the exact runx --version output, expected to be runx-cli 0.6.13 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 spam-risk-reviewer; publish flow is runx login --provider github --for publish, then runx registry publish ./skills/spam-risk-reviewer/SKILL.md --registry https://api.runx.ai. public_url is the live registry listing for <owner>/spam-risk-reviewer@<version> and the canonical public adoption page; source_url is the public source/provenance URL used to publish; and runx registry read <owner>/spam-risk-reviewer@<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/spam-risk-reviewer/X.yaml, skills/spam-risk-reviewer/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>/spam-risk-reviewer@<version>; the local harness passed before publish via runx harness ./skills/spam-risk-reviewer; the hosted registry harness passed after publish; a real dogfood run via runx skill <owner>/spam-risk-reviewer@<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>/spam-risk-reviewer@<version>, not the harness fixture seal, and harness_cases lists each case name with its sealed or refused status.",
        "Inline harness.cases declares one sealed case where a verified sender with clean list signals and full authentication yields send_risk_verdict{risk_level: pass, preflight_clear: true, blockers: []}, and one stop case where DKIM does not pass and bounce_rate exceeds policy, yielding send_risk_verdict{risk_level: hold, preflight_clear: false, blockers: [reason, reason]} with no preflight clearance and a needs_human escalation to the human approval lane.",
        "Typed inputs are campaign_draft{from, subject, content_digest}, list_metadata{size, bounce_rate, complaint_rate, freshness}, and sender_auth_posture{spf_pass, dkim_pass, dmarc_pass, warm_up_days}; typed output is send_risk_verdict{risk_level, preflight_clear, blockers, evidence_summary}; this skill emits no runx.operational_proposal.v1, mints no authority, and reads no domain state.",
        "The send_risk_verdict is dispatched by naming to send-as: a separate governed send-as run reads it into its preflight_required and blockers, so a non-clear verdict prevents send-as from satisfying its preflight and routes to send-as human approval; the public_send Effect stays send-as's own, the actual delivery is that separate governed send-as run, and a borderline or high-risk verdict stops here as needs_human for the approval lane.",
        "The judgment refuses to set preflight_clear true when SPF, DKIM, or DMARC do not pass, refuses to clear preflight for lists exceeding the policy bounce, complaint, or freshness thresholds and instead escalates to the human approval lane, and never invents authentication signals or list health metrics it cannot ground in the inputs.",
        "evidence_json observations include the risk_level verdict and reasoning, the authentication signals verified, the list hygiene metrics compared to policy thresholds, the content risk flags if any, the blockers array with reasons, the harness case names low-risk-verified-sender and high-risk-incomplete-auth-poor-list, 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/spam-risk-reviewer/X.yaml, skills/spam-risk-reviewer/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.13 or newer, run or inspect runx add <owner>/spam-risk-reviewer@<version> and runx registry read <owner>/spam-risk-reviewer@<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>/spam-risk-reviewer@<version> rather than the harness fixture or an unrelated receipt, independently run runx add <owner>/spam-risk-reviewer@<version> and runx skill <owner>/spam-risk-reviewer@<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 spam-risk-reviewer 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.13",
        "expected_package_name": "spam-risk-reviewer",
        "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>/spam-risk-reviewer@<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/spam-risk-reviewer/X.yaml\nskill_md=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/spam-risk-reviewer/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"
    },
    "currency": "USD",
    "fee_cents": 60,
    "poster_ref": "operator:52ba9b44-a02f-55b3-9b19-268584a1714f",
    "posting_id": "p-a7db78d8a8",
    "source_ref": "frantic:receipt:fe504ca3fd504b10",
    "source_url": "/bounties/p-a7db78d8a8",
    "claim_limit": 1,
    "description": "runx skill: spam risk reviewer\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. Spam risk judgment is the pre-send blocker for Deliverability, and the dangerous part is the call to let a campaign go out, not the send mechanics. This skill reads a campaign draft (sender, subject, content digest), the subscriber list metadata and hygiene signals, and the sender auth posture (SPF, DKIM, DMARC, warm-up status), decides whether the send poses high spam risk, and emits a bounded send_risk_verdict. This is a pure read-only judgment: it mints no authority, holds no domain state, and emits no operational proposal. The verdict binds into send-as preflight checks and blockers, where a non-clear verdict prevents send-as from satisfying its preflight and forces human approval. The public_send Effect belongs to send-as, never to this skill, which delivers no message and never executes the send.\n\nDeliverable: A published runx spam-risk-reviewer skill with green hosted harness, sealed dogfood receipt, source_url, evidence_json, and report.\n\nAcceptance:\n- The delivery uses runx CLI 0.6.13 or newer; evidence_json.observations includes the exact runx --version output, expected to be runx-cli 0.6.13 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 spam-risk-reviewer; publish flow is runx login --provider github --for publish, then runx registry publish ./skills/spam-risk-reviewer/SKILL.md --registry https://api.runx.ai. public_url is the live registry listing for <owner>/spam-risk-reviewer@<version> and the canonical public adoption page; source_url is the public source/provenance URL used to publish; and runx registry read <owner>/spam-risk-reviewer@<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/spam-risk-reviewer/X.yaml, skills/spam-risk-reviewer/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>/spam-risk-reviewer@<version>; the local harness passed before publish via runx harness ./skills/spam-risk-reviewer; the hosted registry harness passed after publish; a real dogfood run via runx skill <owner>/spam-risk-reviewer@<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>/spam-risk-reviewer@<version>, not the harness fixture seal, and harness_cases lists each case name with its sealed or refused status.\n- Inline harness.cases declares one sealed case where a verified sender with clean list signals and full authentication yields send_risk_verdict{risk_level: pass, preflight_clear: true, blockers: []}, and one stop case where DKIM does not pass and bounce_rate exceeds policy, yielding send_risk_verdict{risk_level: hold, preflight_clear: false, blockers: [reason, reason]} with no preflight clearance and a needs_human escalation to the human approval lane.\n- Typed inputs are campaign_draft{from, subject, content_digest}, list_metadata{size, bounce_rate, complaint_rate, freshness}, and sender_auth_posture{spf_pass, dkim_pass, dmarc_pass, warm_up_days}; typed output is send_risk_verdict{risk_level, preflight_clear, blockers, evidence_summary}; this skill emits no runx.operational_proposal.v1, mints no authority, and reads no domain state.\n- The send_risk_verdict is dispatched by naming to send-as: a separate governed send-as run reads it into its preflight_required and blockers, so a non-clear verdict prevents send-as from satisfying its preflight and routes to send-as human approval; the public_send Effect stays send-as's own, the actual delivery is that separate governed send-as run, and a borderline or high-risk verdict stops here as needs_human for the approval lane.\n- The judgment refuses to set preflight_clear true when SPF, DKIM, or DMARC do not pass, refuses to clear preflight for lists exceeding the policy bounce, complaint, or freshness thresholds and instead escalates to the human approval lane, and never invents authentication signals or list health metrics it cannot ground in the inputs.\n- evidence_json observations include the risk_level verdict and reasoning, the authentication signals verified, the list hygiene metrics compared to policy thresholds, the content risk flags if any, the blockers array with reasons, the harness case names low-risk-verified-sender and high-risk-incomplete-auth-poor-list, 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\nPassing delivery shape:\n```text\npublic_url=https://runx.ai/x/<owner>/spam-risk-reviewer@<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/spam-risk-reviewer/X.yaml\nskill_md=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/spam-risk-reviewer/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:\n```bash\ncurl -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>/spam-risk-reviewer@<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/spam-risk-reviewer/X.yaml\",\n      \"skill_md=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/spam-risk-reviewer/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  }'\n```\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: Open the registry public_url, confirm the listed owner is the worker, open the runxhq/runx pr_url and confirm it contains skills/spam-risk-reviewer/X.yaml, skills/spam-risk-reviewer/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.13 or newer, run or inspect runx add <owner>/spam-risk-reviewer@<version> and runx registry read <owner>/spam-risk-reviewer@<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>/spam-risk-reviewer@<version> rather than the harness fixture or an unrelated receipt, independently run runx add <owner>/spam-risk-reviewer@<version> and runx skill <owner>/spam-risk-reviewer@<version> --json to confirm it installs and seals, and state why a real operator or user would install or trust this skill.",
    "occurred_at": "2026-06-25T21:07:10.792Z",
    "price_cents": 600,
    "claimable_at": "2026-06-25T21:07:10.792Z",
    "schema_version": 1
  }
}