social/account-growth

social/account-growth — daily per-account follower / view snapshots.

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

Input Schema

Field	Type	Default	Description
cohort	string	"default"	Cohort label (e.g. ‘validation-cohort-1’) for grouping snapshots.
cohort_start_date	string	""	ISO date for cohort Day 0 (e.g. ‘2026-04-29’). Empty = use the earliest fetched_at in the existing log for this cohort, or today if none. Used to compute day_index per row.
days_target	integer	30	Days from cohort start by which the target should be hit.
handles	any[]	—	List of (platform, handle) to snapshot in parallel.
log_path	string	""	Path to the growth-log JSONL. Empty = ~/.fabric/account-growth.jsonl.
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.
target_followers	integer	1000	Follower target for the growth-curve pace projection.
target_views	integer	1000000	Total-views target for the growth-curve pace projection.
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
cohort	string	required
curves	any[]	—
day_index	integer	0	Days since cohort_start_date for this snapshot run.
fetched_at	string	required
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.
log_path	string	required
snapshots	any[]	—
snapshots_written	integer	0

Task Pipeline

snapshot_handles → compute_curves → finalize

Task	Description
snapshot_handles	Fan out across handles in parallel, persist, and build output rows.
compute_curves	Build per-(handle, platform, metric) growth-curve rollups.
finalize	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/account-growth

# Optional fields — copy any line(s) under `input:` and uncomment to set:
# Cohort label (e.g. 'validation-cohort-1') for grouping snapshots.
#   cohort: default
#
# ISO date for cohort Day 0 (e.g. '2026-04-29'). Empty = use the earliest fetched_at in the existing log for this cohort, or today if none. Used to compute day_index per row.
#   cohort_start_date: ""
#
# Days from cohort start by which the target should be hit.
# [min=1, max=365]
#   days_target: 30
#
# List of (platform, handle) to snapshot in parallel.
#   handles: []
#
# Path to the growth-log JSONL. Empty = ~/.fabric/account-growth.jsonl.
#   log_path: ""
#
# Follower target for the growth-curve pace projection.
# [min=1]
#   target_followers: 1000
#
# Total-views target for the growth-curve pace projection.
# [min=1]
#   target_views: 1000000
#

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/account-growth' \
  -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.).