{
  "id": "operations-conflict",
  "group": "operations",
  "variant": "complication",
  "kind": "recorded internal Grid test",
  "sources": [
    {
      "id": "schedule",
      "title": "Today’s schedule",
      "text": "Sample business: Northline Studio. Tuesday 22 September. 09:00 project review owned by Alex. 11:00 supplier call owned by Morgan. 15:00 client review owned by Sam."
    },
    {
      "id": "inbox",
      "title": "A conflicting update",
      "text": "Client asks to move the 15:00 review to 11:00. Morgan now says they must attend both the supplier call and client review. No alternative time has been approved. Alex will send project notes after 09:00."
    },
    {
      "id": "rules",
      "title": "Operating boundary",
      "text": "Draft a concise daily brief. Do not send messages or change calendars. Flag conflicts and keep the original schedule until a person approves a change. Keep ownership exactly as supplied."
    }
  ],
  "output": {
    "title": "Daily operations brief",
    "summary": "Northline Studio has a proposed client review move that conflicts with Morgan’s 11:00 supplier call. Keep the original schedule until approval.",
    "findings": [
      {
        "label": "Original schedule",
        "text": "09:00 project review owned by Alex; 11:00 supplier call owned by Morgan; 15:00 client review owned by Sam.",
        "sourceIds": [
          "schedule"
        ]
      },
      {
        "label": "Conflict",
        "text": "Client requested moving the 15:00 review to 11:00, when Morgan must attend both supplier call and client review.",
        "sourceIds": [
          "inbox"
        ]
      },
      {
        "label": "Required handling",
        "text": "No alternative time is approved; keep ownership unchanged and retain the original schedule until a person approves changes.",
        "sourceIds": [
          "inbox",
          "rules"
        ]
      }
    ],
    "humanAction": "Review and approve any reschedule before calendars or messages change.",
    "boundary": "No messages sent or calendar changes made."
  },
  "checks": [
    "Completed on the Grid’s installed runtime.",
    "Every finding references a supplied input.",
    "No action tools or customer systems were used.",
    "The conflicting request stays unapproved; original ownership is preserved."
  ],
  "limitation": "Controlled drafting test using fictional business data. It does not establish production calendar integration or reliability across customer workflows.",
  "completedAt": "2026-09-21T17:19:55.665704+00:00",
  "model": "gpt-5.5",
  "runtime": "Grid test runtime",
  "toolsAvailable": 0,
  "inputSha256": "878b64a1b96160b3cfb5be8bd745f73247f31adfc4b7f81e78d5cf93e72e1bbf",
  "outputSha256": "f7d1c19db6d32ee90919633756b2ea979c0777e44f79469214da69e8abb8c2c8",
  "executionReceiptSha256": "0ba061a03bf7f58b48eeb69ae5587f0ffb275c9b122e1cad41d6afd6e4beb7cd"
}