{"ok":true,"receipt":{"code":"r/c5d41f7f47978271d665786b99f9f448e5afc0276d4a08b2267de9cb537d19e5","ref":"frantic:receipt:c9d8584dc8d856ba","sequence":2042,"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: agency charter validator","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//mandate-planner@\",\n \"source_url=https://\",\n \"pr_url=https://github.com/runxhq/runx/pull/\",\n \"x_yaml=https://raw.githubusercontent.com////skills/mandate-planner/X.yaml\",\n \"skill_md=https://raw.githubusercontent.com////skills/mandate-planner/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 mandate-planner; publish flow is runx login --provider github --for publish, then runx registry publish ./skills/mandate-planner/SKILL.md --registry https://api.runx.ai. public_url is the live registry listing for /mandate-planner@ and the canonical public adoption page; source_url is the public source/provenance URL used to publish; and runx registry read /mandate-planner@ --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/mandate-planner/X.yaml, skills/mandate-planner/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 /mandate-planner@; the local harness passed before publish via runx harness ./skills/mandate-planner; the hosted registry harness passed after publish; a real dogfood run via runx skill /mandate-planner@ --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 /mandate-planner@, not the harness fixture seal, and harness_cases lists each case name with its sealed or refused status.","Inline harness.cases declare one sealed happy case where an in-grant charter yields decision.eligible true plus a recommended_charter and a sealed review receipt, and one stop case where the charter requests a role outside granted_roles, exceeds a granted cap, or names no measurable done-check so the run blocks to the human approval lane (needs_agent) with no recommended_charter emitted.","Typed inputs are objective, proposed_charter{candidate_roster[{role,skill,scope}],requested_limits{max_turns,spend},done_check}, and authority_grant{granted_spend,granted_roles,max_turns}; the typed output is decision{eligible,reason} plus a recommended_charter{scopes,spend,max_turns,counterparty} carried as data only when eligible, with every roster role traced to candidate_roster and confirmed present in authority_grant.granted_roles and every limit at or under the grant.","The handoff seam is dispatch-by-naming: agency.open is a separate governed run a downstream driver or operator issues by naming, mapping the recommended_charter onto agency.open's own roster and limits inputs; this judge emits the verdict and stops, never calling agency.open and never claiming agency.open consumes its output as an effect, and an ambiguous or out-of-grant charter escalates to a human approval lane instead of recommending.","The skill refuses to admit a roster role absent from authority_grant.granted_roles and refuses limits above the granted spend or turn caps, and never invents a roster member, a spend cap, a turn cap, or a done-check it cannot ground in the proposed_charter bounded by the authority_grant.","evidence_json observations include the eligibility verdict and reason, the bounded roster and limits in the recommended_charter, the done_check predicate, the refused reason, the harness case names, and the sealed 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/mandate-planner/X.yaml, skills/mandate-planner/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 /mandate-planner@ and runx registry read /mandate-planner@ --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 /mandate-planner@ rather than the harness fixture or an unrelated receipt, independently run runx add /mandate-planner@ and runx skill /mandate-planner@ --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 mandate-planner 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":"mandate-planner","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//mandate-planner@\nsource_url=https://\npr_url=https://github.com/runxhq/runx/pull/\nx_yaml=https://raw.githubusercontent.com////skills/mandate-planner/X.yaml\nskill_md=https://raw.githubusercontent.com////skills/mandate-planner/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-1d9b5abe1e","source_ref":"frantic:receipt:c9d8584dc8d856ba","source_url":"/bounties/p-1d9b5abe1e","claim_limit":1,"description":"runx skill: agency charter validator\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. Agency opens a case from a mandate, a roster, and cumulative limits, and its contract is explicit that those are operator config and never model-invented. The dangerous gap is the moment an operator hands a charter to agency.open without anyone checking it against the authority they actually hold. Mandate-planner reads a proposed charter and an authority grant, validates the charter against that grant fail-closed, and emits a typed verdict carrying a bounded recommended charter only when the charter sits inside the grant. It is a pure read-only judgment: it opens no case, mints nothing, holds no state, and enforces no limit itself. A downstream driver or operator issues the separate agency.open run from the recommended charter the verdict carries.\n\nDeliverable: A published runx mandate-planner 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 mandate-planner; publish flow is runx login --provider github --for publish, then runx registry publish ./skills/mandate-planner/SKILL.md --registry https://api.runx.ai. public_url is the live registry listing for /mandate-planner@ and the canonical public adoption page; source_url is the public source/provenance URL used to publish; and runx registry read /mandate-planner@ --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/mandate-planner/X.yaml, skills/mandate-planner/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 /mandate-planner@; the local harness passed before publish via runx harness ./skills/mandate-planner; the hosted registry harness passed after publish; a real dogfood run via runx skill /mandate-planner@ --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 /mandate-planner@, not the harness fixture seal, and harness_cases lists each case name with its sealed or refused status.\n- Inline harness.cases declare one sealed happy case where an in-grant charter yields decision.eligible true plus a recommended_charter and a sealed review receipt, and one stop case where the charter requests a role outside granted_roles, exceeds a granted cap, or names no measurable done-check so the run blocks to the human approval lane (needs_agent) with no recommended_charter emitted.\n- Typed inputs are objective, proposed_charter{candidate_roster[{role,skill,scope}],requested_limits{max_turns,spend},done_check}, and authority_grant{granted_spend,granted_roles,max_turns}; the typed output is decision{eligible,reason} plus a recommended_charter{scopes,spend,max_turns,counterparty} carried as data only when eligible, with every roster role traced to candidate_roster and confirmed present in authority_grant.granted_roles and every limit at or under the grant.\n- The handoff seam is dispatch-by-naming: agency.open is a separate governed run a downstream driver or operator issues by naming, mapping the recommended_charter onto agency.open's own roster and limits inputs; this judge emits the verdict and stops, never calling agency.open and never claiming agency.open consumes its output as an effect, and an ambiguous or out-of-grant charter escalates to a human approval lane instead of recommending.\n- The skill refuses to admit a roster role absent from authority_grant.granted_roles and refuses limits above the granted spend or turn caps, and never invents a roster member, a spend cap, a turn cap, or a done-check it cannot ground in the proposed_charter bounded by the authority_grant.\n- evidence_json observations include the eligibility verdict and reason, the bounded roster and limits in the recommended_charter, the done_check predicate, the refused reason, the harness case names, and the sealed 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//mandate-planner@\nsource_url=https://\npr_url=https://github.com/runxhq/runx/pull/\nx_yaml=https://raw.githubusercontent.com////skills/mandate-planner/X.yaml\nskill_md=https://raw.githubusercontent.com////skills/mandate-planner/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//mandate-planner@\",\n \"source_url=https://\",\n \"pr_url=https://github.com/runxhq/runx/pull/\",\n \"x_yaml=https://raw.githubusercontent.com////skills/mandate-planner/X.yaml\",\n \"skill_md=https://raw.githubusercontent.com////skills/mandate-planner/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/mandate-planner/X.yaml, skills/mandate-planner/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 /mandate-planner@ and runx registry read /mandate-planner@ --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 /mandate-planner@ rather than the harness fixture or an unrelated receipt, independently run runx add /mandate-planner@ and runx skill /mandate-planner@ --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}}}}