social/feedback-bridge
social/feedback-bridge— turn engagement data into roster suggestions.
Category: social
Source: workflows/social/feedback_bridge.py
Input Schema
Section titled “Input Schema”| Field | Type | Default | Description |
|---|---|---|---|
baseline_threshold | integer | 5000 | Views threshold for formula ‘win’. Default = plan 073’s failure floor (5k). |
cohort | string | "default" | Cohort to evaluate (e.g. ‘validation-cohort-1’). |
posts_log_path | string | "" | Path to the TSV posts log. Empty = ~/.fabric/posts.tsv. |
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_path | string | "" | Optional path to the cohort’s roster YAML. When set, untouched topics from the roster’s topics_pool are included in the rank with max_views=None so the operator can see what hasn’t been tried yet. |
snapshots_path | string | "" | Path to the JSONL snapshot history produced by research/viral-gate-status. Empty = ~/.fabric/post-engagement-snapshots.jsonl. |
suggestions_path | string | "" | Path to the suggestion JSONL (append-only). Empty = ~/.fabric/roster-suggestions.jsonl. |
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. |
window_days | integer | 14 | Days from posted_at within which engagement counts. Mirrors viral-gate. |
Output Schema
Section titled “Output Schema”| Field | Type | Default | Description |
|---|---|---|---|
cohort | string | required | |
formula_weights | any[] | — | |
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. |
posts_evaluated | integer | 0 | |
posts_log_path | string | required | |
posts_with_metrics | integer | 0 | |
rationale | string | "" | |
snapshots_path | string | required | |
suggested_at | string | required | |
suggestions_path | string | required | |
topic_rank | any[] | — |
Task Pipeline
Section titled “Task Pipeline”load_inputs → compute_suggestion → finalize| Task | Description |
|---|---|
load_inputs | Resolve paths, load the posts log + snapshot history. |
compute_suggestion | Build the suggestion + persist it to the JSONL log. |
finalize | Shape the aggregate output. |
Run-spec example
Section titled “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/feedback-bridge
# Optional fields — copy any line(s) under `input:` and uncomment to set:# Views threshold for formula 'win'. Default = plan 073's failure floor (5k).# [min=1]# baseline_threshold: 5000## Cohort to evaluate (e.g. 'validation-cohort-1').# cohort: default## Path to the TSV posts log. Empty = ~/.fabric/posts.tsv.# posts_log_path: ""## Optional path to the cohort's roster YAML. When set, untouched topics from the roster's topics_pool are included in the rank with max_views=None so the operator can see what hasn't been tried yet.# roster_path: ""## Path to the JSONL snapshot history produced by research/viral-gate-status. Empty = ~/.fabric/post-engagement-snapshots.jsonl.# snapshots_path: ""## Path to the suggestion JSONL (append-only). Empty = ~/.fabric/roster-suggestions.jsonl.# suggestions_path: ""## Days from posted_at within which engagement counts. Mirrors viral-gate.# [min=1, max=365]# window_days: 14#
input: {}Run it locally:
fab-workflow --from-file my-run.yamlOr submit over the wire — the same file is the request body:
curl -X POST 'https://gofabric.dev/v1/workflows/runs?name=social/feedback-bridge' \ -H 'Authorization: Bearer fab_xxx' \ -H 'content-type: application/yaml' \ --data-binary @my-run.yamlEvery 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.).