bundle/ad-hoc

Ad-hoc bundle dispatcher — heterogeneous workflow fan-out.

Category: bundle
Source: workflows/bundle/ad_hoc.py

Input Schema

Field	Type	Default	Description
bundle	any[]	required	Heterogeneous fan-out list (1–10 entries). Each entry runs its declared workflow with its own input in parallel.
regenerate	object	—	When set, this run is a regeneration. Workflows may read direction / keep / extra_instructions to modulate prompts; the engine persists parent_run_id and parent_variant_index as run lineage columns.
variants	integer	1	Number of independent variant executions (1–10). When > 1, the engine runs the workflow N times with different sampling, producing N outputs.

Output Schema

Field	Type	Default	Description
kind	object	—	Variant card shape: video / carousel / image / text. Surfaced on the per-variant entry of the run-output API and used by gallery UIs to pick the right layout.
note	string	"bundle/ad-hoc has no terminal output of its own; consumers should read outputs[i].output for each per-entry workflow's result."	Reminder that per-entry results live on outputs[].

Task Pipeline

reject_direct_execution

Task	Description
reject_direct_execution	Defensive guard — should never run in the normal dispatch path.

Run-spec example

Save the YAML below as my-run.yaml, edit the values, and run with the CLI or POST it to the API. Required fields are uncommented; optional knobs are documented above the input: block — copy any line under input: and uncomment to set.

workflow: bundle/ad-hoc

# Optional fields — copy any line(s) under `input:` and uncomment to set:

input:
  # Heterogeneous fan-out list (1–10 entries). Each entry runs its declared workflow with its own input in parallel.
  # [min_items=1, max_items=10]
  bundle: []

Run it locally:

fab-workflow --from-file my-run.yaml

Or submit over the wire — the same file is the request body:

curl -X POST 'https://gofabric.dev/v1/workflows/runs?name=bundle/ad-hoc' \
  -H 'Authorization: Bearer fab_xxx' \
  -H 'content-type: application/yaml' \
  --data-binary @my-run.yaml

Every workflow also accepts the universal WorkflowInput fields — variants (1–10 fan-out) and regenerate (creative-direction hints with run lineage). See Run-specs (YAML / TOML / JSON) for the full top-level shape (metadata, priority, bundle, parent, etc.).

Warnings

• Task reject_direct_execution has no Pydantic types — contract is opaque to consumers.