{
  "example_kind": "original synthetic manual planning case",
  "slug": "review-veto-versus-average",
  "title": "Keep a mandatory review gate out of an average",
  "scenario": "Synthetic planning case: A proof has readability score 9/10 and layout 9/10 but fails the required accurate-date gate. A draft averages only the two scores and calls the proof accepted.",
  "layout": "protocol",
  "dataset": {
    "heading": "Inspect the invented case records",
    "headers": [
      "Review dimension",
      "Toy result",
      "Decision role"
    ],
    "rows": [
      [
        "Readability",
        "9/10",
        "Preference score"
      ],
      [
        "Layout",
        "9/10",
        "Preference score"
      ],
      [
        "Date accuracy",
        "Fail",
        "Required acceptance gate"
      ]
    ]
  },
  "derivation": "(9+9)/2=9 is the average of the two scored preferences. It does not include or override the separate required true-date condition.",
  "result": "The required date gate holds acceptance regardless of the nine-point score average. Keep the veto condition outside a compensating preference average.",
  "boundary": "The artifact prevents a mandatory acceptance failure from disappearing inside an average.",
  "limitations": "The example does not mandate a universal rubric. Its gate and preference roles are supplied local rules.",
  "sources": [
    "original"
  ],
  "tasks": [
    [
      "Identify mandatory conditions",
      "Receiving owner",
      "Date accuracy is a noncompensating acceptance requirement."
    ],
    [
      "Separate gates from scores",
      "Reviewer",
      "The failed gate is visible beside, not averaged into, the preference summary."
    ],
    [
      "Request the bounded correction",
      "Delivery owner",
      "The date is corrected and rechecked before acceptance; unrelated approved layout need not be invented anew."
    ]
  ],
  "faqs": [
    [
      "Could a gate be changed?",
      "Only through an explicit authorized requirement decision, not by a high average."
    ],
    [
      "Does a failed gate make all design work worthless?",
      "No. Preserve accepted evidence while holding the unmet required boundary."
    ]
  ],
  "method_references": [
    {
      "id": "original",
      "title": "Original worked-case definitions",
      "scope": "Definitions, policy choices, records and calculations are authored for this worksheet. No external standard, statistical validation or live product measurement is claimed."
    }
  ]
}