social/daily-drop

social/daily-drop — multi-character daily content fan-out.

Category: social
Source: workflows/social/daily_drop.py

Input Schema

Field	Type	Default	Description
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.
roster	object	—	Inline roster dict — overrides roster_path when set.
roster_path	string	""	Path to a roster YAML/JSON file. Empty = look for ~/.fabric/characters.yaml then ./dogfood/characters.yaml.
slot_offset	integer	0	Rotate topics + formulas by this offset (e.g. for morning vs evening drops). Slot N picks topics_pool[(slot_offset + N) % len(pool)].
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
drops	any[]	—	Per-(character × slot) results.
failure_count	integer	0	Drops that errored — kept for visibility, not aborted on.
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.
roster_name	string	required	Roster identifier.
success_count	integer	0	Drops produced without error.
total_estimated_usd	number	0.0	Pre-flight estimated spend for this run.

Task Pipeline

load_and_preflight → generate_drops → finalize_daily_drop

Task	Description
load_and_preflight	Load the roster, validate it, and refuse to start if cost cap is exceeded.
generate_drops	Fan out across characters in parallel, gather per-character results.
finalize_daily_drop	Shape the aggregate output.

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: social/daily-drop

# Optional fields — copy any line(s) under `input:` and uncomment to set:
# Inline roster dict — overrides roster_path when set.
#   roster: {}
#
# Path to a roster YAML/JSON file. Empty = look for ~/.fabric/characters.yaml then ./dogfood/characters.yaml.
#   roster_path: ""
#
# Rotate topics + formulas by this offset (e.g. for morning vs evening drops). Slot N picks topics_pool[(slot_offset + N) % len(pool)].
#   slot_offset: 0
#

input: {}

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=social/daily-drop' \
  -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.).

Worked examples

These checked-in run-specs exercise this workflow — good starting points to copy and tweak:

• examples/run-inputs/daily-drop-fabric-team.yaml