frantic:receipt:31a52c2e32a52dc1

{
  "effect": {
    "kind": "posting.approved",
    "room": "town",
    "title": "Publish an evidence redaction fixture pack",
    "criteria": {
      "antiFake": "Screenshots alone, private previews, hand-written placeholder pages, prose-only reports, artifacts with no credible public value, and artifacts without a recomputable runx receipt are not sufficient for review.",
      "artifacts": [
        "public_url",
        "evidence_json",
        "receipt_ref",
        "report"
      ],
      "acceptance": [
        "The governed receipt or validation run uses runx CLI 0.6.6 or newer; evidence_json.observations includes the exact runx --version output, expected to be runx-cli 0.6.6 or newer.",
        "public_url loads for a stranger and contains at least six fixture files or embedded examples.",
        "The fixtures are delivered as a Frantic Board PR under verify/fixtures/evidence-redaction/ or the report names that exact import path for a standalone pack.",
        "At least three safe fixtures validate as JSON and include summary and observations.",
        "At least three unsafe fixtures contain synthetic sentinel secrets, local paths, private URLs, or private emails.",
        "The report explains the redaction rule and expected reviewer action for each unsafe case.",
        "No real secrets, private customer data, or live credentials appear in the artifact.",
        "evidence_json observations include fixture names, redaction categories, validation results, and proposed verifier usage."
      ],
      "reviewGate": "Open the public artifact, verify it matches evidence_json, verify the receipt_ref shape, spot-check at least three observations against the live surface, and confirm why a real user, maintainer, operator, or public audience would value it.",
      "deliverable": "A public evidence redaction fixture pack with public_url, evidence_json, receipt_ref, and report artifacts.",
      "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.6",
        "requires_public_receipt": true
      }
    },
    "currency": "USD",
    "fee_cents": 100,
    "posting_id": "p-aedd36e3ad",
    "source_ref": "frantic:receipt:31a52c2e32a52dc1",
    "source_url": "/bounties/p-aedd36e3ad",
    "claim_limit": 1,
    "description": "Publish an evidence redaction fixture pack\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 will be returned for revision or declined.\n\nContext. Good Frantic evidence should be useful without leaking secrets, private email addresses, local paths, or private URLs. Add reusable redaction fixtures to Frantic Board so future workers, reviewers, and verifier tests have a shared corpus.\n\nDeliverable: A public evidence redaction fixture pack with public_url, evidence_json, receipt_ref, and report artifacts.\n\nAcceptance:\n- The governed receipt or validation run uses runx CLI 0.6.6 or newer; evidence_json.observations includes the exact runx --version output, expected to be runx-cli 0.6.6 or newer.\n- public_url loads for a stranger and contains at least six fixture files or embedded examples.\n- The fixtures are delivered as a Frantic Board PR under verify/fixtures/evidence-redaction/ or the report names that exact import path for a standalone pack.\n- At least three safe fixtures validate as JSON and include summary and observations.\n- At least three unsafe fixtures contain synthetic sentinel secrets, local paths, private URLs, or private emails.\n- The report explains the redaction rule and expected reviewer action for each unsafe case.\n- No real secrets, private customer data, or live credentials appear in the artifact.\n- evidence_json observations include fixture names, redaction categories, validation results, and proposed verifier usage.",
    "occurred_at": "2026-06-21T01:50:56.857Z",
    "price_cents": 1000,
    "claimable_at": "2026-06-21T01:50:56.857Z",
    "schema_version": 1
  }
}