frantic:receipt:b76a4b4bb66a49b8

{
  "effect": {
    "kind": "posting.approved",
    "room": "town",
    "title": "runx skill: agency health",
    "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>/agency-health@<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/agency-health/X.yaml\",\n      \"skill_md=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/agency-health/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 agency-health; publish flow is runx login --provider github --for publish, then runx registry publish ./skills/agency-health/SKILL.md --registry https://api.runx.ai. public_url is the live registry listing for <owner>/agency-health@<version> and the canonical public adoption page; source_url is the public source/provenance URL used to publish; and runx registry read <owner>/agency-health@<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/agency-health/X.yaml, skills/agency-health/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>/agency-health@<version>; the local harness passed before publish via runx harness ./skills/agency-health; the hosted registry harness passed after publish; a real dogfood run via runx skill <owner>/agency-health@<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>/agency-health@<version>, not the harness fixture seal, and harness_cases lists each case name with its sealed or refused status.",
        "Harness declares inline cases: one SEALED case where a running agency with stuck turns and cap pressure yields decision ready, health_verdict.status degraded, graded findings, and typed intervention findings with named target lanes, expect status sealed; and one STOP case where an agency_ref with no readable case events over the period yields decision needs_more_evidence, no findings graded, and no intervention emitted, expect status sealed (a deterministic conflict that still seals).",
        "Typed inputs are data_source_ref, store_id, agency_ref, optional period and case_id, optional health_baseline{threshold_days_stuck,cap_pressure_pct,refusal_spike_rate}; typed output is decision{ready|needs_more_evidence|needs_human}, health_verdict{status,findings[]} where each finding ties a folded metric to a named norm, and intervention_findings[] each naming a target lane and citing its grounding case_id and turn or ledger id-stub; the domain-keyed state read is the data-store read_projection over the agency case and the cross-run aggregate read is the ledger read runner by receipt id-stub only.",
        "The handoff seam is dispatch-by-naming: this lane moves no money and grants no access, so each intervention_finding carries no ceiling and no effect bound and is consumed only when a downstream driver or operator issues the separate policy-author or improve-skill run; the human ops lane is the escalation lane for any cap-widening or authority-widening remedy and any critical finding, and this skill issues no rail run and claims no rail consumes its output.",
        "Refusals: it refuses to grade a signal not grounded in the folded case projection or a ledger id-stub aggregate, refuses to invent a cap or threshold it cannot read from the agency charter snapshot or the supplied baseline, and never invents a turn state the sealed event order does not show.",
        "evidence_json observations include the decision and health_verdict.status, the graded findings (seal_rate, stuck_case_count, cap_usage_pct, escalation_backlog) with their assessments, the named intervention target lanes and reasons, the refused reason when no events are readable, the folded case_id and turn numbers, the referenced ledger id-stubs, the harness case names (concerning-agency-sealed, no-case-events-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/agency-health/X.yaml, skills/agency-health/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>/agency-health@<version> and runx registry read <owner>/agency-health@<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>/agency-health@<version> rather than the harness fixture or an unrelated receipt, independently run runx add <owner>/agency-health@<version> and runx skill <owner>/agency-health@<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 agency-health 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.14",
        "expected_package_name": "agency-health",
        "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
      },
      "deliveryExample": "public_url=https://runx.ai/x/<owner>/agency-health@<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/agency-health/X.yaml\nskill_md=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/agency-health/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": 100,
    "posting_id": "p-3b89d0b03c",
    "source_ref": "frantic:receipt:b76a4b4bb66a49b8",
    "source_url": "/bounties/p-3b89d0b03c",
    "claim_limit": 1,
    "description": "runx skill: agency health\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. An agency runs a standing mandate one governed turn at a time, and every turn appends an event to that agency's case stream in the hosted data-store. Over days that stream is operational state: turns that advanced cleanly, turns parked in awaiting_approval, cumulative spend and act counts approaching the charter caps, and turns making no progress. This skill assembles a health bundle for one running agency over a period. It reads the domain-keyed turn state by composing the registry-pinned data-store read_projection (C2) keyed on the agency case, and it reads cross-run aggregates (seal rate, refusal spikes) from the ledger read runner (C7), referencing those receipts by id-stub only because the ledger is audit-only and can never be a domain-keyed state read. It folds the case projection in version order, grades the signals against declared norms, and seals a health_verdict plus typed intervention findings. It is read-only: it appends nothing, sends nothing, executes nothing, and consumes no effect. Each warranted finding names its target lane (policy-author to tighten a policy or timeout, improve-skill to debug a member behind a refusal spike); a downstream driver or operator issues that separate governed run. Any remedy that would widen a cap or authority, and any critical finding, escalates to the human ops lane rather than routing as a routine tighten. run-history-analyst reads runs across the whole catalog ledger and receipt-auditor audits one receipt where this skill reads one live agency case projection end to end.\n\nDeliverable: A published runx agency-health skill with green hosted harness, sealed dogfood receipt, 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 agency-health; publish flow is runx login --provider github --for publish, then runx registry publish ./skills/agency-health/SKILL.md --registry https://api.runx.ai. public_url is the live registry listing for <owner>/agency-health@<version> and the canonical public adoption page; source_url is the public source/provenance URL used to publish; and runx registry read <owner>/agency-health@<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/agency-health/X.yaml, skills/agency-health/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>/agency-health@<version>; the local harness passed before publish via runx harness ./skills/agency-health; the hosted registry harness passed after publish; a real dogfood run via runx skill <owner>/agency-health@<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>/agency-health@<version>, not the harness fixture seal, and harness_cases lists each case name with its sealed or refused status.\n- Harness declares inline cases: one SEALED case where a running agency with stuck turns and cap pressure yields decision ready, health_verdict.status degraded, graded findings, and typed intervention findings with named target lanes, expect status sealed; and one STOP case where an agency_ref with no readable case events over the period yields decision needs_more_evidence, no findings graded, and no intervention emitted, expect status sealed (a deterministic conflict that still seals).\n- Typed inputs are data_source_ref, store_id, agency_ref, optional period and case_id, optional health_baseline{threshold_days_stuck,cap_pressure_pct,refusal_spike_rate}; typed output is decision{ready|needs_more_evidence|needs_human}, health_verdict{status,findings[]} where each finding ties a folded metric to a named norm, and intervention_findings[] each naming a target lane and citing its grounding case_id and turn or ledger id-stub; the domain-keyed state read is the data-store read_projection over the agency case and the cross-run aggregate read is the ledger read runner by receipt id-stub only.\n- The handoff seam is dispatch-by-naming: this lane moves no money and grants no access, so each intervention_finding carries no ceiling and no effect bound and is consumed only when a downstream driver or operator issues the separate policy-author or improve-skill run; the human ops lane is the escalation lane for any cap-widening or authority-widening remedy and any critical finding, and this skill issues no rail run and claims no rail consumes its output.\n- Refusals: it refuses to grade a signal not grounded in the folded case projection or a ledger id-stub aggregate, refuses to invent a cap or threshold it cannot read from the agency charter snapshot or the supplied baseline, and never invents a turn state the sealed event order does not show.\n- evidence_json observations include the decision and health_verdict.status, the graded findings (seal_rate, stuck_case_count, cap_usage_pct, escalation_backlog) with their assessments, the named intervention target lanes and reasons, the refused reason when no events are readable, the folded case_id and turn numbers, the referenced ledger id-stubs, the harness case names (concerning-agency-sealed, no-case-events-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\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>/agency-health@<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/agency-health/X.yaml\nskill_md=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/agency-health/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": 1000,
    "claimable_at": "2026-07-12T03:43:06.173Z",
    "schema_version": 1
  }
}