frantic:receipt:7f5abfff7e5abe6c

{
  "effect": {
    "kind": "posting.approved",
    "room": "town",
    "title": "Run a standing agency on your own ops and publish the sealed case trail",
    "criteria": {
      "antiFake": "Invented caseloads, single-turn runs padded to three, trails with unverifiable or missing receipt refs, redactions that remove the receipt ids themselves, and reports with no concrete governance moments are returned for revision.",
      "artifacts": [
        "public_url",
        "evidence_json",
        "receipt_ref",
        "report"
      ],
      "acceptance": [
        "The governed receipt or validation run 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.",
        "The agency is opened with the catalog agency skill under a real roster and a real mandate for YOUR own recurring ops need; fixture or invented caseloads fail review, and the report names the need and why it recurs.",
        "At least three advance turns run on one case: each turn's receipt ref is published, runx verify is green on every one, and the case trail shows the fold, the ops-desk move, and any approval gate in turn order.",
        "At least one turn hits a consequence gate (awaiting_approval or an escalation) and the trail shows how it resolved; a trail where no gate ever fired needs the report to argue why the mandate never touched consequence.",
        "The published trail redacts secrets and private counterparties but keeps receipt ids, turn numbers, and verify verdicts intact so a stranger can check the shape of every claim.",
        "The report covers what the governance changed: at least two concrete moments where the gate, the roster constraint, or the sealed trail altered what would have happened loose; evidence_json observations include the mandate, roster, case id, per-turn receipt refs and verify verdicts, and receipt_ref."
      ],
      "reviewGate": "Open the published trail, confirm three or more turns on one real case with receipt refs and green verify verdicts in order, confirm at least one consequence gate fired and resolved, and confirm the report's governance moments are visible in the trail.",
      "deliverable": "A standing agency (registry agency + ops-desk skills) run on your own real recurring ops need for at least three governed advance turns, delivered as the mandate, the published case trail with sealed receipt refs and green runx verify verdicts, and a report on what the governance changed, with evidence_json and receipt_ref.",
      "verification": {
        "profile": "published_artifact_v1",
        "artifact_kind": "generic",
        "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",
        "requires_public_receipt": true
      },
      "deliveryExample": "public_url=https://<public-home-of-the-case-trail>\nevidence_json=https://example.com/agency-case-trail-evidence.json\nreceipt_ref=runx:receipt:<id>\nreport=https://example.com/agency-case-trail-report.md"
    },
    "currency": "USD",
    "fee_cents": 90,
    "posting_id": "p-9c1adb149d",
    "source_ref": "frantic:receipt:7f5abfff7e5abe6c",
    "source_url": "/bounties/p-9c1adb149d",
    "claim_limit": 1,
    "description": "Run a standing agency on your own ops and publish the sealed case trail\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. The runx catalog ships a standing-agency spine: a roster, a persistent mandate, and a case advanced one governed turn at a time, every turn sealed. The individual judges have bounties; nobody has yet run the TEAM on work of their own. Open an agency with the catalog agency skill on a real recurring ops need you actually have, advance one case at least three turns, and publish the sealed trail.\n\nDeliverable: A standing agency (registry agency + ops-desk skills) run on your own real recurring ops need for at least three governed advance turns, delivered as the mandate, the published case trail with sealed receipt refs and green runx verify verdicts, and a report on what the governance changed, with evidence_json and receipt_ref.\n\nAcceptance:\n- The governed receipt or validation run 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.\n- The agency is opened with the catalog agency skill under a real roster and a real mandate for YOUR own recurring ops need; fixture or invented caseloads fail review, and the report names the need and why it recurs.\n- At least three advance turns run on one case: each turn's receipt ref is published, runx verify is green on every one, and the case trail shows the fold, the ops-desk move, and any approval gate in turn order.\n- At least one turn hits a consequence gate (awaiting_approval or an escalation) and the trail shows how it resolved; a trail where no gate ever fired needs the report to argue why the mandate never touched consequence.\n- The published trail redacts secrets and private counterparties but keeps receipt ids, turn numbers, and verify verdicts intact so a stranger can check the shape of every claim.\n- The report covers what the governance changed: at least two concrete moments where the gate, the roster constraint, or the sealed trail altered what would have happened loose; evidence_json observations include the mandate, roster, case id, per-turn receipt refs and verify verdicts, and receipt_ref.\n\nArtifacts: `public_url`, `evidence_json`, `receipt_ref`, `report`\n\nPassing delivery shape:\n```text\npublic_url=https://<public-home-of-the-case-trail>\nevidence_json=https://example.com/agency-case-trail-evidence.json\nreceipt_ref=runx:receipt:<id>\nreport=https://example.com/agency-case-trail-report.md\n```\n\nReturned for revision if: Invented caseloads, single-turn runs padded to three, trails with unverifiable or missing receipt refs, redactions that remove the receipt ids themselves, and reports with no concrete governance moments are returned for revision.\n\nReview gate: Open the published trail, confirm three or more turns on one real case with receipt refs and green verify verdicts in order, confirm at least one consequence gate fired and resolved, and confirm the report's governance moments are visible in the trail.",
    "occurred_at": "2026-07-12T03:42:49.746Z",
    "price_cents": 900,
    "claimable_at": "2026-07-12T03:42:49.746Z",
    "schema_version": 1
  }
}