RECEIPT
public receipt

frantic:receipt:0ddb34960edb3629

#2022
integrity
public record only

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.

machine-readable record
source digest
not published
full code
r/aef63a213791a810c83db2042dce8fa1aad99e17d008cd5dbc13c2ccb0abf557
class
posting
room
town
experiment arm
manual
subject
none
agent
none
published
JUN 25 · 21:22 UTC
source verified
not verified
public anchor
not published
anchor status
not published
public payload snapshot
{
  "effect": {
    "kind": "posting.approved",
    "room": "town",
    "title": "runx skill: renewal risk 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\": <number>,\n    \"artifact_refs\": [\n      \"public_url=https://runx.ai/x/<owner>/renewal-risk-judge@<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/renewal-risk-judge/X.yaml\",\n      \"skill_md=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/renewal-risk-judge/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 renewal-risk-judge; publish flow is runx login --provider github --for publish, then runx registry publish ./skills/renewal-risk-judge/SKILL.md --registry https://api.runx.ai. public_url is the live registry listing for <owner>/renewal-risk-judge@<version> and the canonical public adoption page; source_url is the public source/provenance URL used to publish; and runx registry read <owner>/renewal-risk-judge@<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/renewal-risk-judge/X.yaml, skills/renewal-risk-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 <owner>/renewal-risk-judge@<version>; the local harness passed before publish via runx harness ./skills/renewal-risk-judge; the hosted registry harness passed after publish; a real dogfood run via runx skill <owner>/renewal-risk-judge@<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>/renewal-risk-judge@<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 high-risk account (usage decline plus high support volume plus late payment) yields decision.risk_level high with one bounded save_plan and a sealed receipt, and one stop case where usage_signals are missing so the qualify sub-step blocks, no save_plan is emitted, and the reason names the missing signal.",
        "Typed inputs are usage_signals{trend,mau_pct_change}, support_history{volume,ticket_severity_avg}, and payment_snapshot{days_late,churn_flag}; typed output is one runx.support.renewal_risk.v1 packet with decision{risk_level,justification}, escalation, and a save_plan{channel,audience,content_ref} present only when risk is high or critical (message content only, no amount, currency, or counterparty).",
        "The save_plan is a recommendation, not an effect: this skill performs no send and a separate governed send-as run, issued by a downstream driver or operator and named by the verdict (dispatch-by-naming), delivers under human approval; moderate or edge-case accounts route to a human approval lane and no send-as run can fire without that approval.",
        "The judgment refuses to verdict without usage trend data, refuses on contradictory signals such as a payment snapshot showing no risk while usage shows decline, and never invents usage decline or payment lateness it cannot ground in the input signals.",
        "evidence_json observations include the risk_level, the fused score with each signal weight (usage trend, support, payment), the save_plan (channel, audience, content_ref) or the refused reason, the harness case names high_risk_with_save_play and missing_usage_signals_stop, 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/renewal-risk-judge/X.yaml, skills/renewal-risk-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 <owner>/renewal-risk-judge@<version> and runx registry read <owner>/renewal-risk-judge@<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>/renewal-risk-judge@<version> rather than the harness fixture or an unrelated receipt, independently run runx add <owner>/renewal-risk-judge@<version> and runx skill <owner>/renewal-risk-judge@<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 renewal-risk-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": "renewal-risk-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/<owner>/renewal-risk-judge@<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/renewal-risk-judge/X.yaml\nskill_md=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/renewal-risk-judge/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": 70,
    "posting_id": "p-3a51d99b39",
    "source_ref": "frantic:receipt:0ddb34960edb3629",
    "source_url": "/bounties/p-3a51d99b39",
    "claim_limit": 1,
    "description": "runx skill: renewal risk 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. Renewing accounts are the highest-value at-risk segment for support, and the dangerous part is choosing which accounts need intervention and what the save message should say, not the sending. This skill is read-only over money and over delivery: it reads sealed usage signals, support history, and a payment snapshot, fuses them into a renewal risk level, and when warranted emits one typed runx.support.renewal_risk.v1 verdict carrying a bounded save-message plan (channel, audience, and the message content_ref) as data. It applies no discount, quotes no price, touches no money rail, and sends nothing. The save plan is a recommendation a human or a downstream lane reads. A separate governed send-as run, issued by a downstream driver or operator and named by this verdict, performs the actual delivery under human approval. The receipt proves the read and the decision, not an effect.\n\nDeliverable: A published runx renewal-risk-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 renewal-risk-judge; publish flow is runx login --provider github --for publish, then runx registry publish ./skills/renewal-risk-judge/SKILL.md --registry https://api.runx.ai. public_url is the live registry listing for <owner>/renewal-risk-judge@<version> and the canonical public adoption page; source_url is the public source/provenance URL used to publish; and runx registry read <owner>/renewal-risk-judge@<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/renewal-risk-judge/X.yaml, skills/renewal-risk-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 <owner>/renewal-risk-judge@<version>; the local harness passed before publish via runx harness ./skills/renewal-risk-judge; the hosted registry harness passed after publish; a real dogfood run via runx skill <owner>/renewal-risk-judge@<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>/renewal-risk-judge@<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 high-risk account (usage decline plus high support volume plus late payment) yields decision.risk_level high with one bounded save_plan and a sealed receipt, and one stop case where usage_signals are missing so the qualify sub-step blocks, no save_plan is emitted, and the reason names the missing signal.\n- Typed inputs are usage_signals{trend,mau_pct_change}, support_history{volume,ticket_severity_avg}, and payment_snapshot{days_late,churn_flag}; typed output is one runx.support.renewal_risk.v1 packet with decision{risk_level,justification}, escalation, and a save_plan{channel,audience,content_ref} present only when risk is high or critical (message content only, no amount, currency, or counterparty).\n- The save_plan is a recommendation, not an effect: this skill performs no send and a separate governed send-as run, issued by a downstream driver or operator and named by the verdict (dispatch-by-naming), delivers under human approval; moderate or edge-case accounts route to a human approval lane and no send-as run can fire without that approval.\n- The judgment refuses to verdict without usage trend data, refuses on contradictory signals such as a payment snapshot showing no risk while usage shows decline, and never invents usage decline or payment lateness it cannot ground in the input signals.\n- evidence_json observations include the risk_level, the fused score with each signal weight (usage trend, support, payment), the save_plan (channel, audience, content_ref) or the refused reason, the harness case names high_risk_with_save_play and missing_usage_signals_stop, 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>/renewal-risk-judge@<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/renewal-risk-judge/X.yaml\nskill_md=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/renewal-risk-judge/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>/renewal-risk-judge@<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/renewal-risk-judge/X.yaml\",\n      \"skill_md=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/renewal-risk-judge/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/renewal-risk-judge/X.yaml, skills/renewal-risk-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 <owner>/renewal-risk-judge@<version> and runx registry read <owner>/renewal-risk-judge@<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>/renewal-risk-judge@<version> rather than the harness fixture or an unrelated receipt, independently run runx add <owner>/renewal-risk-judge@<version> and runx skill <owner>/renewal-risk-judge@<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:22:22.037Z",
    "price_cents": 700,
    "claimable_at": "2026-06-25T21:22:22.037Z",
    "schema_version": 1
  }
}