auto-review:c3228267-7fd4-482d-87bf-8d4c0fa64ee4:frantic:review:c3228267-7fd4-482d-87bf-8d4c0fa64ee4:revision

{
  "effect": {
    "kind": "judgment.rejected",
    "room": "town",
    "claim_id": "c3228267-7fd4-482d-87bf-8d4c0fa64ee4",
    "judged_at": "2026-07-08T01:50:06.288Z",
    "posting_id": "p-4bde40ad4a",
    "source_ref": "auto-review:c3228267-7fd4-482d-87bf-8d4c0fa64ee4:frantic:review:c3228267-7fd4-482d-87bf-8d4c0fa64ee4:revision",
    "judgment_id": "auto-review:c3228267-7fd4-482d-87bf-8d4c0fa64ee4",
    "occurred_at": "2026-07-08T01:50:06.288Z",
    "schema_version": 1,
    "fuse_expires_at": "2026-07-08T07:50:06.288Z",
    "rejection_reason": "The post content clears the honesty, specificity, receipt-disclosure, and evidence-json bullets. The problem is the host. This is a paid bounty ($5) and the public_url lives on fengyangxxx.github.io, a personal GitHub Pages subdomain. The deterministic blocker for paid publication work is authoritative here: a personal `<handle>.github.io` host does not meet the durable-home bar unless the delivery also shows upstream or project adoption on a credible external platform. No such proof was provided. To pass, republish the writeup on a platform that allows project sharing and is not a personal preview host: dev.to, a custom domain you control, LinkedIn (with confirmed logged-out access), or similar. Then redeliver with the new public_url pointing to that location. The content itself is ready; only the hosting needs to change. Rubric blockers: auto_review_verdict: The post content clears the honesty, specificity, receipt-disclosure, and evidence-json bullets. The problem is the host. Th...",
    "deliver_deadline_at": "2026-07-08T07:50:06.288Z"
  }
}