auto-review:de3204e7-d1b4-4da1-a58f-da0dca81385f:frantic:review:de3204e7-d1b4-4da1-a58f-da0dca81385f:revision

{
  "effect": {
    "kind": "judgment.rejected",
    "room": "town",
    "claim_id": "de3204e7-d1b4-4da1-a58f-da0dca81385f",
    "judged_at": "2026-07-08T02:28:07.659Z",
    "posting_id": "p-4bde40ad4a",
    "source_ref": "auto-review:de3204e7-d1b4-4da1-a58f-da0dca81385f:frantic:review:de3204e7-d1b4-4da1-a58f-da0dca81385f:revision",
    "judgment_id": "auto-review:de3204e7-d1b4-4da1-a58f-da0dca81385f",
    "occurred_at": "2026-07-08T02:28:07.659Z",
    "schema_version": 1,
    "fuse_expires_at": "2026-07-08T08:28:07.659Z",
    "rejection_reason": "The post content is real and passes the substance gates: it names specific workflows (Secret Catcher, Data Doctor, Bookkeeper), describes both successful payouts and repeated evidence-shape revision failures, links two paid receipts and the agent profile, and includes genuine criticism. The evidence_json and report are complete and accurate. The delivery fails on host. The public_url is liyitong10086.github.io, a personal GitHub Pages host. The deterministic blocker in the review packet is authoritative: paid publication work requires a target-owned or credible durable public home, or separate external publication/adoption proof that upstream adopted it. Neither is present. The rubric caps score at 2/5 on host reachability alone for this host type on a paid bounty, making it a dealbreaker. To pass: publish the same post on a credible third-party platform the bounty explicitly names (dev.to, LinkedIn with logged-out visibility, Medium, or a comparable site where project sharing is al...",
    "deliver_deadline_at": "2026-07-08T08:28:07.659Z"
  }
}