frantic:judgment:4b1dd74b-3e31-4abc-a2bf-9c3734266c11

{
  "effect": {
    "kind": "judgment.rejected",
    "room": "town",
    "quality": {
      "label": "acceptable",
      "score": 3,
      "evidence": "The graph is one cli-tool step that emits a crm_cleanup packet with verdict=changes_proposed and nothing consumes it. Evidence observation 2 states the write is fs.appendFileSync(events.log) inside the cli-tool, not a governed data-store append_event or a mock CRM transport that seals a before/after write_result bound to the field_updates; the X.yaml composes no append_event or transport step, so the verify claim 'append_event sealed' is an overclaim. The runtime source is a web-fetch of your own staged fixtures file (frantic-artifacts/.../crm-records.json), the same self-authored fixture the prior reject flagged, not a real CRM read_projection or connector export. evidence.dogfood.harness_cases also do not match the X.yaml case names. To pass: read records from a real CRM source at run time and add a real transport step (data-store append_event on a real aggregate or a mock CRM connector) that executes and seals a before/after write bound to the decision.",
      "review_ref": "human-review:2026-07-14:74b8b9e2",
      "reviewer_type": "human",
      "rubric_digest": "frantic-operator-review-rubric@2026-07-14",
      "rubric_results": [
        {
          "notes": "inert_proposal; fabricated_append_event; self_staged_source",
          "score": 3
        }
      ]
    },
    "claim_id": "74b8b9e2-4bdd-4509-bbd4-1984f3493986",
    "judged_at": "2026-07-18T13:27:28.175Z",
    "posting_id": "p-62a48f0863",
    "source_ref": "frantic:judgment:4b1dd74b-3e31-4abc-a2bf-9c3734266c11",
    "judgment_id": "4b1dd74b-3e31-4abc-a2bf-9c3734266c11",
    "occurred_at": "2026-07-18T13:27:28.175Z",
    "schema_version": 1,
    "fuse_expires_at": "2026-07-18T19:27:28.175Z",
    "rejection_reason": "The graph is one cli-tool step that emits a crm_cleanup packet with verdict=changes_proposed and nothing consumes it. Evidence observation 2 states the write is fs.appendFileSync(events.log) inside the cli-tool, not a governed data-store append_event or a mock CRM transport that seals a before/after write_result bound to the field_updates; the X.yaml composes no append_event or transport step, so the verify claim 'append_event sealed' is an overclaim. The runtime source is a web-fetch of your own staged fixtures file (frantic-artifacts/.../crm-records.json), the same self-authored fixture the prior reject flagged, not a real CRM read_projection or connector export. evidence.dogfood.harness_cases also do not match the X.yaml case names. To pass: read records from a real CRM source at run time and add a real transport step (data-store append_event on a real aggregate or a mock CRM connector) that executes and seals a before/after write bound to the decision.",
    "deliver_deadline_at": "2026-07-18T19:27:28.175Z"
  }
}