{"ok":true,"receipt":{"code":"r/a7a2f4354d458e437cb5b06adda2e4f468f724f241655ed48794ed9370926ec0","ref":"frantic:receipt:00fd8f7ffffd8dec","sequence":4253,"class":"posting","room":"town","arm":"manual","subject":null,"agent":null,"trust_rung":null,"published_at":"2026-07-12T03:43:06.173Z","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: revenue leakage auditor","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//revenue-leakage-auditor@\",\n \"source_url=https://\",\n \"pr_url=https://github.com/runxhq/runx/pull/\",\n \"x_yaml=https://raw.githubusercontent.com////skills/revenue-leakage-auditor/X.yaml\",\n \"skill_md=https://raw.githubusercontent.com////skills/revenue-leakage-auditor/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.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 revenue-leakage-auditor; publish flow is runx login --provider github --for publish, then runx registry publish ./skills/revenue-leakage-auditor/SKILL.md --registry https://api.runx.ai. public_url is the live registry listing for /revenue-leakage-auditor@ and the canonical public adoption page; source_url is the public source/provenance URL used to publish; and runx registry read /revenue-leakage-auditor@ --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/revenue-leakage-auditor/X.yaml, skills/revenue-leakage-auditor/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 /revenue-leakage-auditor@; the local harness passed before publish via runx harness ./skills/revenue-leakage-auditor; the hosted registry harness passed after publish; a real dogfood run via runx skill /revenue-leakage-auditor@ --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 /revenue-leakage-auditor@, 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 usage exceeds billing past the threshold for at least one eligible account, decision.leakage_found is true, and one bounded AttenuationRequest ceiling is emitted per eligible account, plus one STOP case that omits caller.answers so the human approval sub-step blocks to needs_agent, or a deterministic all-in-threshold case that still seals with stop reason no_change and emits no ceiling; the hosted gate reads only these inline cases.","Typed inputs are usage_records{account_id, usage_amount, period}, billing_history{account_id, billed_amount, period}, discount_policy{excluded_accounts, known_discounts}, charge_threshold_pct, and parent_adjustment_bounds as an AuthorityBounds clamp; typed output is decision{leakage_found, reason}, ceilings[] each a bounded AttenuationRequest{amount, currency, scopes} as DATA (clamped to parent_adjustment_bounds) with usage_evidence_ref, billing_evidence_ref, and idempotency_key, only when leakage_found is true, plus escalation; durable per-account case state is read by read_projection and written by an ungated append_event(idempotency_key, expected_version) keyed by account_id across reconciliation runs.","Each ceiling is a typed value, not an effect: a downstream driver hands it to the core spend/refund accepting runner (C3), which alone reserves, mints, settles, and seals the attenuated subset within amount, currency, and scopes and fail-closes if a request exceeds the ceiling; the data-store append is an ungated CAS write keyed by account_id, not a gated proposal; ambiguous or incomplete billing records escalate to a human approval lane rather than emitting a ceiling.","The judgment refuses to propose a ceiling for an account listed as excluded by discount policy, refuses to treat a gap a known discount covers as leakage, refuses to emit a ceiling when usage evidence is incomplete or unverified, and never invents a discount or usage record it cannot ground in the policy and input records.","evidence_json observations include the leakage verdict and reason, the under-billed accounts and amounts, the usage and billing evidence references, the bounded ceiling{amount, currency, scopes} and idempotency_key per eligible account, the data-store aggregate_id and appended version, the refused or stop reason, the two harness case names, 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/revenue-leakage-auditor/X.yaml, skills/revenue-leakage-auditor/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 /revenue-leakage-auditor@ and runx registry read /revenue-leakage-auditor@ --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 /revenue-leakage-auditor@ rather than the harness fixture or an unrelated receipt, independently run runx add /revenue-leakage-auditor@ and runx skill /revenue-leakage-auditor@ --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 revenue-leakage-auditor graph skill with green hosted harness, a sealed dogfood receipt carrying the act{form: review} decision plus the bounded AttenuationRequest ceiling per eligible account (no mint, no attenuation subset claim), 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":"revenue-leakage-auditor","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//revenue-leakage-auditor@\nsource_url=https://\npr_url=https://github.com/runxhq/runx/pull/\nx_yaml=https://raw.githubusercontent.com////skills/revenue-leakage-auditor/X.yaml\nskill_md=https://raw.githubusercontent.com////skills/revenue-leakage-auditor/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","claim_window_minutes":180},"currency":"USD","fee_cents":110,"posting_id":"p-a118e194a2","source_ref":"frantic:receipt:00fd8f7ffffd8dec","source_url":"/bounties/p-a118e194a2","claim_limit":1,"description":"runx skill: revenue leakage auditor\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. Under-billed accounts leak revenue when usage outpaces what was invoiced, and the load-bearing part is the judgment of which adjustments are policy-eligible and the binding of each one to the exact reconciliation evidence and to a bounded authority. This skill reads sealed usage records, billing history, and discount policy, reconciles actual usage against billed amounts after applying any known discount, identifies accounts under-billed by more than a configured threshold, and emits a typed reconciliation decision plus, for each eligible account, a bounded AttenuationRequest ceiling carrying amount, currency, and the adjustment scopes as data. bookkeeper keeps the books where this skill hunts uncollected revenue and hands a bounded charge ceiling downstream. A known discount that explains the gap is not leakage and yields no ceiling. This skill is a money JUDGMENT, not an executor: it does not mint, never moves money, and its receipt proves the decision plus the ceiling it emitted, never an attenuated subset. A downstream driver hands the ceiling to the core spend/refund accepting runner (C3), which mints, reserves, settles, and seals the attenuated subset. This member never invents a discount or usage record absent from the inputs.\n\nDeliverable: A published runx revenue-leakage-auditor graph skill with green hosted harness, a sealed dogfood receipt carrying the act{form: review} decision plus the bounded AttenuationRequest ceiling per eligible account (no mint, no attenuation subset claim), 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 revenue-leakage-auditor; publish flow is runx login --provider github --for publish, then runx registry publish ./skills/revenue-leakage-auditor/SKILL.md --registry https://api.runx.ai. public_url is the live registry listing for /revenue-leakage-auditor@ and the canonical public adoption page; source_url is the public source/provenance URL used to publish; and runx registry read /revenue-leakage-auditor@ --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/revenue-leakage-auditor/X.yaml, skills/revenue-leakage-auditor/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 /revenue-leakage-auditor@; the local harness passed before publish via runx harness ./skills/revenue-leakage-auditor; the hosted registry harness passed after publish; a real dogfood run via runx skill /revenue-leakage-auditor@ --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 /revenue-leakage-auditor@, 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 usage exceeds billing past the threshold for at least one eligible account, decision.leakage_found is true, and one bounded AttenuationRequest ceiling is emitted per eligible account, plus one STOP case that omits caller.answers so the human approval sub-step blocks to needs_agent, or a deterministic all-in-threshold case that still seals with stop reason no_change and emits no ceiling; the hosted gate reads only these inline cases.\n- Typed inputs are usage_records{account_id, usage_amount, period}, billing_history{account_id, billed_amount, period}, discount_policy{excluded_accounts, known_discounts}, charge_threshold_pct, and parent_adjustment_bounds as an AuthorityBounds clamp; typed output is decision{leakage_found, reason}, ceilings[] each a bounded AttenuationRequest{amount, currency, scopes} as DATA (clamped to parent_adjustment_bounds) with usage_evidence_ref, billing_evidence_ref, and idempotency_key, only when leakage_found is true, plus escalation; durable per-account case state is read by read_projection and written by an ungated append_event(idempotency_key, expected_version) keyed by account_id across reconciliation runs.\n- Each ceiling is a typed value, not an effect: a downstream driver hands it to the core spend/refund accepting runner (C3), which alone reserves, mints, settles, and seals the attenuated subset within amount, currency, and scopes and fail-closes if a request exceeds the ceiling; the data-store append is an ungated CAS write keyed by account_id, not a gated proposal; ambiguous or incomplete billing records escalate to a human approval lane rather than emitting a ceiling.\n- The judgment refuses to propose a ceiling for an account listed as excluded by discount policy, refuses to treat a gap a known discount covers as leakage, refuses to emit a ceiling when usage evidence is incomplete or unverified, and never invents a discount or usage record it cannot ground in the policy and input records.\n- evidence_json observations include the leakage verdict and reason, the under-billed accounts and amounts, the usage and billing evidence references, the bounded ceiling{amount, currency, scopes} and idempotency_key per eligible account, the data-store aggregate_id and appended version, the refused or stop reason, the two harness case names, 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//revenue-leakage-auditor@\nsource_url=https://\npr_url=https://github.com/runxhq/runx/pull/\nx_yaml=https://raw.githubusercontent.com////skills/revenue-leakage-auditor/X.yaml\nskill_md=https://raw.githubusercontent.com////skills/revenue-leakage-auditor/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: 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":1100,"claimable_at":"2026-07-12T03:43:06.173Z","schema_version":1}}}}