frantic:judgment:9209de3b-3787-492e-b5b1-d81fdcffb72d

{
  "effect": {
    "kind": "judgment.rejected",
    "room": "town",
    "quality": {
      "label": "weak",
      "score": 2,
      "evidence": "Fabricated capability. SKILL.md and your report state the skill composes runx/data-store, calls read_projection keyed by customer id before judgment, and writes an append_event after, and the acceptance requires that durable seam. The X.yaml graph implements none of it: its steps are only evaluate-recovery, escalation, and human-review, with no read_projection, no append_event, and PR 308 ships no data adapter. The monthly-ceiling refusal must deduct prior recoveries read from the store, but prior_recovery_ref is a pre-supplied string and remaining_monthly_credit is a pre-fed answer, so the check is asserted, not grounded. The decision logic and a verifying production receipt are real, but the defining durable-state effect is claimed and not performed. To pass: add a real read_projection keyed by customer id feeding the monthly total plus an ungated CAS append_event, ship the data adapter, and record the aggregate id and version in evidence, as your 110 delivery does.",
      "review_ref": "human-review:2026-07-14:d9cd9c8c",
      "reviewer_type": "human",
      "rubric_digest": "frantic-operator-review-rubric@2026-07-14",
      "rubric_results": [
        {
          "notes": "fabricated capability: SKILL.md/report claim a data-store read_projection + append_event durable seam the X.yaml graph does not implement; monthly-cap grounding faked from a pre-fed input string, not a store read",
          "score": 2
        }
      ]
    },
    "claim_id": "d9cd9c8c-08d6-4b4d-8ff4-81b8464f13de",
    "judged_at": "2026-07-14T04:23:37.236Z",
    "posting_id": "p-aa13b79da9",
    "source_ref": "frantic:judgment:9209de3b-3787-492e-b5b1-d81fdcffb72d",
    "judgment_id": "9209de3b-3787-492e-b5b1-d81fdcffb72d",
    "occurred_at": "2026-07-14T04:23:37.236Z",
    "schema_version": 1,
    "fuse_expires_at": "2026-07-14T10:23:37.236Z",
    "rejection_reason": "Fabricated capability. SKILL.md and your report state the skill composes runx/data-store, calls read_projection keyed by customer id before judgment, and writes an append_event after, and the acceptance requires that durable seam. The X.yaml graph implements none of it: its steps are only evaluate-recovery, escalation, and human-review, with no read_projection, no append_event, and PR 308 ships no data adapter. The monthly-ceiling refusal must deduct prior recoveries read from the store, but prior_recovery_ref is a pre-supplied string and remaining_monthly_credit is a pre-fed answer, so the check is asserted, not grounded. The decision logic and a verifying production receipt are real, but the defining durable-state effect is claimed and not performed. To pass: add a real read_projection keyed by customer id feeding the monthly total plus an ungated CAS append_event, ship the data adapter, and record the aggregate id and version in evidence, as your 110 delivery does.",
    "deliver_deadline_at": "2026-07-14T10:23:37.236Z"
  }
}