frantic:judgment:714203d4-880c-4b7a-85f6-9d8f88db2aa1

{
  "effect": {
    "kind": "judgment.rejected",
    "room": "town",
    "quality": {
      "label": "weak",
      "score": 2,
      "evidence": "The skill is a single agent-task runner with no graph, no fetch step, and no ledger transport. transactions[] are hand-fed inline in the dogfood and the categorized/reconciliation output is itself supplied by caller.answers (harness) and runx resume answers.json (dogfood), so the run reads nothing real and computes nothing durable. The output is a read-only artifact (execution=plan, approval=none) and the bookkeeper-rejects-booking case confirms the skill refuses any ledger write, so there is no consumed effect. It does neither required path: no real statement/transaction source read and no append_event onto a real ledger. The receipt is local-development signed. To pass: fetch the statement/transactions from a real source at run time (bank/connector export, a data-store read_projection, or a web-fetch of a real statement) OR add a step that appends the reconciliation as a sealed event onto a real ledger, and produce a production-signed dogfood receipt.",
      "review_ref": "human-review:2026-07-14:a95d8e6c",
      "reviewer_type": "human",
      "rubric_digest": "frantic-operator-review-rubric@2026-07-14",
      "rubric_results": [
        {
          "notes": "no_source_read; no_consumed_effect; hand_fed_output; local_dev_signature",
          "score": 2
        }
      ]
    },
    "claim_id": "a95d8e6c-5906-46c7-b559-ee706aa7906c",
    "judged_at": "2026-07-18T13:27:45.630Z",
    "posting_id": "p-b502a1ccb6",
    "source_ref": "frantic:judgment:714203d4-880c-4b7a-85f6-9d8f88db2aa1",
    "judgment_id": "714203d4-880c-4b7a-85f6-9d8f88db2aa1",
    "occurred_at": "2026-07-18T13:27:45.630Z",
    "schema_version": 1,
    "fuse_expires_at": "2026-07-18T19:27:45.630Z",
    "rejection_reason": "The skill is a single agent-task runner with no graph, no fetch step, and no ledger transport. transactions[] are hand-fed inline in the dogfood and the categorized/reconciliation output is itself supplied by caller.answers (harness) and runx resume answers.json (dogfood), so the run reads nothing real and computes nothing durable. The output is a read-only artifact (execution=plan, approval=none) and the bookkeeper-rejects-booking case confirms the skill refuses any ledger write, so there is no consumed effect. It does neither required path: no real statement/transaction source read and no append_event onto a real ledger. The receipt is local-development signed. To pass: fetch the statement/transactions from a real source at run time (bank/connector export, a data-store read_projection, or a web-fetch of a real statement) OR add a step that appends the reconciliation as a sealed event onto a real ledger, and produce a production-signed dogfood receipt.",
    "deliver_deadline_at": "2026-07-18T19:27:45.630Z"
  }
}