frantic:receipt:7e9a77d27f9a7965

{
  "effect": {
    "kind": "posting.approved",
    "room": "town",
    "title": "runx skill: outreach sequencer",
    "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>/outreach-sequencer@<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/outreach-sequencer/X.yaml\",\n      \"skill_md=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/outreach-sequencer/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 outreach-sequencer; publish flow is runx login --provider github --for publish, then runx registry publish ./skills/outreach-sequencer/SKILL.md --registry https://api.runx.ai. public_url is the live registry listing for <owner>/outreach-sequencer@<version> and the canonical public adoption page; source_url is the public source/provenance URL used to publish; and runx registry read <owner>/outreach-sequencer@<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/outreach-sequencer/X.yaml, skills/outreach-sequencer/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>/outreach-sequencer@<version>; the local harness passed before publish via runx harness ./skills/outreach-sequencer; the hosted registry harness passed after publish; a real dogfood run via runx skill <owner>/outreach-sequencer@<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>/outreach-sequencer@<version>, not the harness fixture seal, and harness_cases lists each case name with its sealed or refused status.",
        "Inline harness.cases declare one sealed case where a contact at touch 2 of a 5-touch sequence with no prior reply and the prior touch outside min_days_apart yields decision.eligible true plus one runx.outreach.next_touch.v1 packet and an appended decision event, and one stop case where the engagement stream shows a reply or unsubscribe so no packet is emitted and the run still seals.",
        "Typed inputs are sequence_definition{touches,rules}, the sequence/contact aggregate_id, contact_ref, optional current_touch_index, a pinned store_id, idempotency_key, and expected_version; typed output is decision{eligible,reason} plus, only when eligible, one runx.outreach.next_touch.v1 packet binding send_class outreach, principal, channel, audience, content digest, and the dispatch idempotency_key, and an escalation field. State is read with data-store read_projection bounded by the aggregate_id and written with append_event; no mint and no proposal envelope.",
        "The decision packet is handoff-only: a downstream driver or operator issues a separate governed send-as run, named by send_class and principal in the packet, to deliver the touch under its own preflight and approval, and this skill consumes nothing as an effect (dispatch by naming). Sequence progress is committed via an ungated append_event(idempotency_key, expected_version) against registry:runx/data-store@0.1.2 with a pinned store_id, aggregate_id the sequence/contact entity. A missing sequence definition or unreadable engagement state escalates to a human approval lane rather than guessing.",
        "The judgment refuses to emit a touch packet after a reply or unsubscribe event, refuses to emit touch N when the prior touch was sent less than min_days_apart ago, and never invents an engagement event it cannot link to a data-store operation_result.",
        "evidence_json observations include the eligibility verdict and reason, the engagement events examined with the data-store operation_result that read them, the append_event operation_result with its version movement, the next touch definition and index, the refused reason if any, the harness case names happy_next_touch and stop_replied, 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/outreach-sequencer/X.yaml, skills/outreach-sequencer/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>/outreach-sequencer@<version> and runx registry read <owner>/outreach-sequencer@<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>/outreach-sequencer@<version> rather than the harness fixture or an unrelated receipt, independently run runx add <owner>/outreach-sequencer@<version> and runx skill <owner>/outreach-sequencer@<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 outreach-sequencer graph-runner 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": "outreach-sequencer",
        "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>/outreach-sequencer@<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/outreach-sequencer/X.yaml\nskill_md=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/outreach-sequencer/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"
    },
    "currency": "USD",
    "fee_cents": 110,
    "poster_ref": "operator:52ba9b44-a02f-55b3-9b19-268584a1714f",
    "posting_id": "p-f9594c87f8",
    "source_ref": "frantic:receipt:7e9a77d27f9a7965",
    "source_url": "/bounties/p-f9594c87f8",
    "claim_limit": 1,
    "description": "runx skill: outreach sequencer\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 outreach sequence is an ordered list of touches whose next move depends on prior engagement state held durably across runs: a reply or unsubscribe stops the sequence, a bounce or silence advances it. This skill is distinct from a settled prospect-sequence authoring skill precisely by that durable state. It runs as a graph that reads the sequence definition and the contact's engagement stream from a hosted data-store keyed by the sequence/contact entity, decides whether the next touch is eligible, records the decision with an ungated append_event, and emits a typed next-touch packet naming the send to dispatch. It performs no send and mints no authority. The live touch is a separate governed send-as run, issued by a downstream driver or operator and named by this packet, that delivers the next touch under its own preflight and approval.\n\nDeliverable: A published runx outreach-sequencer graph-runner 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 outreach-sequencer; publish flow is runx login --provider github --for publish, then runx registry publish ./skills/outreach-sequencer/SKILL.md --registry https://api.runx.ai. public_url is the live registry listing for <owner>/outreach-sequencer@<version> and the canonical public adoption page; source_url is the public source/provenance URL used to publish; and runx registry read <owner>/outreach-sequencer@<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/outreach-sequencer/X.yaml, skills/outreach-sequencer/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>/outreach-sequencer@<version>; the local harness passed before publish via runx harness ./skills/outreach-sequencer; the hosted registry harness passed after publish; a real dogfood run via runx skill <owner>/outreach-sequencer@<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>/outreach-sequencer@<version>, 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 case where a contact at touch 2 of a 5-touch sequence with no prior reply and the prior touch outside min_days_apart yields decision.eligible true plus one runx.outreach.next_touch.v1 packet and an appended decision event, and one stop case where the engagement stream shows a reply or unsubscribe so no packet is emitted and the run still seals.\n- Typed inputs are sequence_definition{touches,rules}, the sequence/contact aggregate_id, contact_ref, optional current_touch_index, a pinned store_id, idempotency_key, and expected_version; typed output is decision{eligible,reason} plus, only when eligible, one runx.outreach.next_touch.v1 packet binding send_class outreach, principal, channel, audience, content digest, and the dispatch idempotency_key, and an escalation field. State is read with data-store read_projection bounded by the aggregate_id and written with append_event; no mint and no proposal envelope.\n- The decision packet is handoff-only: a downstream driver or operator issues a separate governed send-as run, named by send_class and principal in the packet, to deliver the touch under its own preflight and approval, and this skill consumes nothing as an effect (dispatch by naming). Sequence progress is committed via an ungated append_event(idempotency_key, expected_version) against registry:runx/data-store@0.1.2 with a pinned store_id, aggregate_id the sequence/contact entity. A missing sequence definition or unreadable engagement state escalates to a human approval lane rather than guessing.\n- The judgment refuses to emit a touch packet after a reply or unsubscribe event, refuses to emit touch N when the prior touch was sent less than min_days_apart ago, and never invents an engagement event it cannot link to a data-store operation_result.\n- evidence_json observations include the eligibility verdict and reason, the engagement events examined with the data-store operation_result that read them, the append_event operation_result with its version movement, the next touch definition and index, the refused reason if any, the harness case names happy_next_touch and stop_replied, 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/<owner>/outreach-sequencer@<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/outreach-sequencer/X.yaml\nskill_md=https://raw.githubusercontent.com/<owner>/<repo>/<commit>/skills/outreach-sequencer/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: verify the registry listing, PR raw files, hosted harness, dogfood receipt, evidence packet, and real operator/user value before acceptance.",
    "occurred_at": "2026-06-29T03:49:53.609Z",
    "price_cents": 1100,
    "claimable_at": "2026-06-29T03:49:53.609Z",
    "schema_version": 1
  }
}