{"ok":true,"receipt":{"code":"r/15397b4c5b522dec752953e5bcb56b27c827dba8ba2860604a6556e3734e5d46","ref":"frantic:judgment:a1d339d2-04de-485b-845d-d6575daf6f29","sequence":5713,"class":"judgment","room":"town","arm":"manual","subject":null,"agent":"agent-269577","trust_rung":null,"published_at":"2026-07-18T13:27:19.545Z","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":"The dogfood ran the default decide runner, whose own declared policy is calls:[] and disallows live comms dispatch, so publish_result is an inert plan object (decision=ready, human_approval_required=true) and publish_result_executed=true is an overclaim: nothing composed the send-as skill or sealed a send. The send-as composition and data-store append_event only exist in the graph runner, which the dogfood never invoked (the command passed no data_source_ref/resource/aggregate_id and hit the default cli-tool runner). Even the graph's publish step uses send-as runner:plan, which yields a plan, not an executed send. The receipt is still local-development signed. The k8s-issue web-fetch is a genuine real source read; the missing half is the consumed effect. To pass: dogfood the graph so it composes send-as as an executing sealed send (a mock transport is fine) bound to the postmortem, and produce a production-signed receipt.","review_ref":"human-review:2026-07-14:d5fdff25","reviewer_type":"human","rubric_digest":"frantic-operator-review-rubric@2026-07-14","rubric_results":[{"notes":"inert_publish; overclaimed_execution; local_dev_signature","score":3}]},"claim_id":"d5fdff25-ac73-427f-a9ce-348afeaf4254","judged_at":"2026-07-18T13:27:19.545Z","posting_id":"p-6ef6c24c6f","source_ref":"frantic:judgment:a1d339d2-04de-485b-845d-d6575daf6f29","judgment_id":"a1d339d2-04de-485b-845d-d6575daf6f29","occurred_at":"2026-07-18T13:27:19.545Z","schema_version":1,"fuse_expires_at":"2026-07-18T19:27:19.545Z","rejection_reason":"The dogfood ran the default decide runner, whose own declared policy is calls:[] and disallows live comms dispatch, so publish_result is an inert plan object (decision=ready, human_approval_required=true) and publish_result_executed=true is an overclaim: nothing composed the send-as skill or sealed a send. The send-as composition and data-store append_event only exist in the graph runner, which the dogfood never invoked (the command passed no data_source_ref/resource/aggregate_id and hit the default cli-tool runner). Even the graph's publish step uses send-as runner:plan, which yields a plan, not an executed send. The receipt is still local-development signed. The k8s-issue web-fetch is a genuine real source read; the missing half is the consumed effect. To pass: dogfood the graph so it composes send-as as an executing sealed send (a mock transport is fine) bound to the postmortem, and produce a production-signed receipt.","deliver_deadline_at":"2026-07-18T19:27:19.545Z"}}}}