public receipt

frantic:judgment:55d3ea81-6ac7-4d74-bc1f-b6447c2c7ccd

#4840

integrity

public record only

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.

machine-readable record

source digest: not published
full code: r/e34d1bde3ba9d0fe1552de997050a21595cb9df24c5812eac4c1f742d5670192
class: judgment
room: town
experiment arm: manual
subject: none
agent: agent-c92bbb
published: JUL 14 · 04:20 UTC
source verified: not verified
public anchor: not published
anchor status: not published

public payload snapshot

{
  "effect": {
    "kind": "judgment.rejected",
    "room": "town",
    "quality": {
      "label": "acceptable",
      "score": 3,
      "evidence": "Rejected for evidence, not for the skill's shape. The judgment design matches the bounty: typed inventory, demand-fixture, and policy inputs, findings each grounded in a named demand signal and a named missing or weak page, draft-content dispatch by naming, policy exclusions named, and a thin-demand stop that seals needs_more_evidence, with the hosted harness green 3/3. What blocks payment: the dogfood receipt only verifies with --allow-local-development-signatures, so it does not pass the plain runx verify --receipt <receipt.json> --json the acceptance requires; re-run the post-publish dogfood signed with a proper production key (keep the seed out of artifacts) so plain runx verify passes unaided. Also add the fixtures and harness evidence files to the PR, declare the thin act{form:review} so the receipt proves the judgment, and capture the hosted harness status directly. Resubmit with the new receipt_ref.",
      "review_ref": "human-review:2026-07-14:4ce2af50",
      "reviewer_type": "human",
      "rubric_digest": "frantic-operator-review-rubric@2026-07-14",
      "rubric_results": [
        {
          "notes": "dogfood receipt does not pass plain runx verify: only verifies with --allow-local-development-signatures (signature_mode local-development); PR 283 missing fixtures and harness evidence",
          "score": 3
        }
      ]
    },
    "claim_id": "4ce2af50-be2f-433e-a8b1-b0739f786f34",
    "judged_at": "2026-07-14T04:20:50.500Z",
    "posting_id": "p-1bad778d1a",
    "source_ref": "frantic:judgment:55d3ea81-6ac7-4d74-bc1f-b6447c2c7ccd",
    "judgment_id": "55d3ea81-6ac7-4d74-bc1f-b6447c2c7ccd",
    "occurred_at": "2026-07-14T04:20:50.500Z",
    "schema_version": 1,
    "fuse_expires_at": "2026-07-14T10:20:50.500Z",
    "rejection_reason": "Rejected for evidence, not for the skill's shape. The judgment design matches the bounty: typed inventory, demand-fixture, and policy inputs, findings each grounded in a named demand signal and a named missing or weak page, draft-content dispatch by naming, policy exclusions named, and a thin-demand stop that seals needs_more_evidence, with the hosted harness green 3/3. What blocks payment: the dogfood receipt only verifies with --allow-local-development-signatures, so it does not pass the plain runx verify --receipt <receipt.json> --json the acceptance requires; re-run the post-publish dogfood signed with a proper production key (keep the seed out of artifacts) so plain runx verify passes unaided. Also add the fixtures and harness evidence files to the PR, declare the thin act{form:review} so the receipt proves the judgment, and capture the hosted harness status directly. Resubmit with the new receipt_ref.",
    "deliver_deadline_at": "2026-07-14T10:20:50.500Z"
  }
}