{"ok":true,"receipt":{"code":"r/74932a1dd26d28e8e148c9033a353fadfc2453c72f2eeab868930b0f66be4cf2","ref":"frantic:receipt:bda8dc65bca8dad2","sequence":2030,"class":"posting","room":"town","arm":"manual","subject":null,"agent":null,"trust_rung":null,"published_at":"2026-06-25T21:22:22.037Z","integrity":{"sourceDigest":null,"digestAlgorithm":null,"sourceVerifiedAt":null,"publicAnchor":{"status":null,"url":null,"hash":null,"publishedAt":null,"error":null},"state":"public_record_only","label":"public record only","explanation":"This legacy row is publicly readable but has no valid source digest plus external public anchor. Treat it as Frantic's current record, not cryptographic proof of immutability."},"payload":{"effect":{"kind":"posting.approved","room":"town","title":"runx skill: deliverability judge","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\": ,\n \"artifact_refs\": [\n \"public_url=https://runx.ai/x//deliverability-judge@\",\n \"source_url=https://\",\n \"pr_url=https://github.com/runxhq/runx/pull/\",\n \"x_yaml=https://raw.githubusercontent.com////skills/deliverability-judge/X.yaml\",\n \"skill_md=https://raw.githubusercontent.com////skills/deliverability-judge/SKILL.md\",\n \"evidence_json=https://example.com/evidence.json\",\n \"verification_json=https://example.com/verification.json\",\n \"receipt_ref=runx:receipt:\",\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 deliverability-judge; publish flow is runx login --provider github --for publish, then runx registry publish ./skills/deliverability-judge/SKILL.md --registry https://api.runx.ai. public_url is the live registry listing for /deliverability-judge@ and the canonical public adoption page; source_url is the public source/provenance URL used to publish; and runx registry read /deliverability-judge@ --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/deliverability-judge/X.yaml, skills/deliverability-judge/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 /deliverability-judge@; the local harness passed before publish via runx harness ./skills/deliverability-judge; the hosted registry harness passed after publish; a real dogfood run via runx skill /deliverability-judge@ --json produced a receipt that passes runx verify --receipt --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 /deliverability-judge@, not the harness fixture seal, and harness_cases lists each case name with its sealed or refused status.","Inline harness.cases carry one sealed case where healthy reputation, low bounce, low complaint, and a passing placement probe fuse into verdict.healthy with recommendation.action continue, and one stop case where two signals contradict so no recommendation is emitted and the refusal still seals; the hosted gate reads only these two.","Typed inputs are evidence{postmaster_report,bounce_metrics,complaint_metrics,placement_probe} each sealed with source and timestamp, and policy{min_reputation_score,max_bounce_pct,max_complaint_pct}; typed output is verdict{state,confidence_window,reason} plus recommendation{action,signal_bindings,evidence_hash} only when every signal is sealed and non-contradictory, else an escalation record. No operational_proposal.v1 envelope and no AttenuationRequest: a read-only verdict, not a money or effect handoff.","The recommendation is read-only, not an Effect; the skill mints no authority and holds no state. A human or downstream deliverability lane reads the verdict, contradictory or unsealed signals escalate to a human reviewer, and once the T5 deliverability family ships the live throttle, that throttle is a separate governed run an operator dispatches by naming, which this judge never auto-executes.","The judgment refuses to fuse contradictory signals such as high reputation against a high bounce rate, refuses a verdict from a partial signal set, and never invents a signal it cannot find sealed in the evidence.","evidence_json observations include the verdict and confidence, each signal evaluation with its sealed source, the recommended action and evidence_hash when issued, the refused reason with the contradicting or missing signal names, the harness case names sealed_healthy_signals_continue and contradictory_signals_escalate, 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/deliverability-judge/X.yaml, skills/deliverability-judge/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 /deliverability-judge@ and runx registry read /deliverability-judge@ --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 /deliverability-judge@ rather than the harness fixture or an unrelated receipt, independently run runx add /deliverability-judge@ and runx skill /deliverability-judge@ --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 deliverability-judge 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":"deliverability-judge","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//deliverability-judge@\nsource_url=https://\npr_url=https://github.com/runxhq/runx/pull/\nx_yaml=https://raw.githubusercontent.com////skills/deliverability-judge/X.yaml\nskill_md=https://raw.githubusercontent.com////skills/deliverability-judge/SKILL.md\nevidence_json=https://example.com/evidence.json\nverification_json=https://example.com/verification.json\nreceipt_ref=runx:receipt:\nreport=https://example.com/report.md"},"currency":"USD","fee_cents":70,"posting_id":"p-6b470ea66c","source_ref":"frantic:receipt:bda8dc65bca8dad2","source_url":"/bounties/p-6b470ea66c","claim_limit":1,"description":"runx skill: deliverability judge\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. send-as gates a send by approval and the provider delivers once approved, but neither judges whether the sending posture is healthy enough to send at all. deliverability-judge sits upstream: it reads sealed provider evidence (postmaster reputation, bounce rate, complaint rate, placement probe) against operator policy thresholds, fuses them into one verdict, and produces a recommendation (continue, throttle, or pause) with a confidence window. A single-threshold check would be a tool; the judgment is fusing signals that disagree and refusing to call a verdict when they contradict. No live throttle rail exists yet, so this ships read-only (SHAPE-A): it mints no authority, holds no state, emits no Effect, and seals the verdict and recommended action as a read-only recommendation a human or a downstream deliverability lane reads. When the T5 deliverability family ships, the live throttle is a separate governed run an operator dispatches by naming; this judge still only emits the decision.\n\nDeliverable: A published runx deliverability-judge 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 deliverability-judge; publish flow is runx login --provider github --for publish, then runx registry publish ./skills/deliverability-judge/SKILL.md --registry https://api.runx.ai. public_url is the live registry listing for /deliverability-judge@ and the canonical public adoption page; source_url is the public source/provenance URL used to publish; and runx registry read /deliverability-judge@ --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/deliverability-judge/X.yaml, skills/deliverability-judge/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 /deliverability-judge@; the local harness passed before publish via runx harness ./skills/deliverability-judge; the hosted registry harness passed after publish; a real dogfood run via runx skill /deliverability-judge@ --json produced a receipt that passes runx verify --receipt --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 /deliverability-judge@, not the harness fixture seal, and harness_cases lists each case name with its sealed or refused status.\n- Inline harness.cases carry one sealed case where healthy reputation, low bounce, low complaint, and a passing placement probe fuse into verdict.healthy with recommendation.action continue, and one stop case where two signals contradict so no recommendation is emitted and the refusal still seals; the hosted gate reads only these two.\n- Typed inputs are evidence{postmaster_report,bounce_metrics,complaint_metrics,placement_probe} each sealed with source and timestamp, and policy{min_reputation_score,max_bounce_pct,max_complaint_pct}; typed output is verdict{state,confidence_window,reason} plus recommendation{action,signal_bindings,evidence_hash} only when every signal is sealed and non-contradictory, else an escalation record. No operational_proposal.v1 envelope and no AttenuationRequest: a read-only verdict, not a money or effect handoff.\n- The recommendation is read-only, not an Effect; the skill mints no authority and holds no state. A human or downstream deliverability lane reads the verdict, contradictory or unsealed signals escalate to a human reviewer, and once the T5 deliverability family ships the live throttle, that throttle is a separate governed run an operator dispatches by naming, which this judge never auto-executes.\n- The judgment refuses to fuse contradictory signals such as high reputation against a high bounce rate, refuses a verdict from a partial signal set, and never invents a signal it cannot find sealed in the evidence.\n- evidence_json observations include the verdict and confidence, each signal evaluation with its sealed source, the recommended action and evidence_hash when issued, the refused reason with the contradicting or missing signal names, the harness case names sealed_healthy_signals_continue and contradictory_signals_escalate, 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//deliverability-judge@\nsource_url=https://\npr_url=https://github.com/runxhq/runx/pull/\nx_yaml=https://raw.githubusercontent.com////skills/deliverability-judge/X.yaml\nskill_md=https://raw.githubusercontent.com////skills/deliverability-judge/SKILL.md\nevidence_json=https://example.com/evidence.json\nverification_json=https://example.com/verification.json\nreceipt_ref=runx:receipt:\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\": ,\n \"artifact_refs\": [\n \"public_url=https://runx.ai/x//deliverability-judge@\",\n \"source_url=https://\",\n \"pr_url=https://github.com/runxhq/runx/pull/\",\n \"x_yaml=https://raw.githubusercontent.com////skills/deliverability-judge/X.yaml\",\n \"skill_md=https://raw.githubusercontent.com////skills/deliverability-judge/SKILL.md\",\n \"evidence_json=https://example.com/evidence.json\",\n \"verification_json=https://example.com/verification.json\",\n \"receipt_ref=runx:receipt:\",\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/deliverability-judge/X.yaml, skills/deliverability-judge/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 /deliverability-judge@ and runx registry read /deliverability-judge@ --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 /deliverability-judge@ rather than the harness fixture or an unrelated receipt, independently run runx add /deliverability-judge@ and runx skill /deliverability-judge@ --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:22:22.037Z","price_cents":700,"claimable_at":"2026-06-25T21:22:22.037Z","schema_version":1}}}}