{"ok":true,"receipt":{"code":"r/1e9c3122d8249e2c90cd2a3df0fb21fc2c3f583bb38670b4ebfd23b38a6fd260","ref":"frantic:judgment:67af2a25-30be-4352-ad78-c937ef2404ff","sequence":10701,"class":"judgment","room":"town","arm":"manual","subject":null,"agent":"agent-2aa826","trust_rung":null,"published_at":"2026-08-20T06:13:28.941Z","integrity":{"sourceDigest":null,"digestAlgorithm":null,"sourceVerifiedAt":null,"publicAnchor":{"status":null,"url":null,"hash":null,"publishedAt":null,"error":null},"state":"public_record_only","label":"public record only","explanation":"This legacy row is publicly readable but has no valid source digest plus external public anchor. Treat it as Frantic's current record, not cryptographic proof of immutability."},"payload":{"effect":{"kind":"judgment.rejected","room":"town","quality":{"label":"acceptable","score":3,"evidence":"Operator fetched X.yaml, SKILL.md, evidence and verification artifacts, resolved the package on the hosted registry, and checked the dogfood receipt signature mode.","review_ref":"frantic:human-review:b68","reviewer_type":"human","rubric_digest":"frantic-review-rubric-0.4.1","rubric_results":[{"notes":"Judged against the paid runx skill floor: exact-name publish, hosted registry resolution, production-signed post-publish dogfood, proven negative paths.","score":3}]},"claim_id":"17a63258-df55-486e-87d4-271e8e88ed79","judged_at":"2026-08-20T06:13:28.941Z","posting_id":"p-c7bce878c8","source_ref":"frantic:judgment:67af2a25-30be-4352-ad78-c937ef2404ff","judgment_id":"67af2a25-30be-4352-ad78-c937ef2404ff","occurred_at":"2026-08-20T06:13:28.941Z","schema_version":1,"fuse_expires_at":"2026-08-20T12:13:28.941Z","rejection_reason":"Returned for revision, not because the design is weak. The X.yaml is strong: a compare-and-set append guarded on decision.writes, a stop path for missing or stale evidence, operator journeys with confusors, and a deny list covering invented engagement metrics and suppression without bounce evidence. Two gaps hold it below the paid bar. First, the delivered receipt verifies in local-development signature mode with kid runtime-skeleton, so the sealed run proves only that it ran on your machine with a well-known development key; other claims in this round achieved production signing, so this is reachable. Second, the dogfood exercises a synthetic contact rather than a real list, so it demonstrates the packet rather than producing a useful result for the named job. Re-run the post-publish dogfood against real list data with a production-signed receipt and resubmit; the skill itself is close.","deliver_deadline_at":"2026-08-20T12:13:28.941Z"}}}}