{
  "for_llm": "This page documents THREE helper sub-scenarios inside School of Bots' Funnel Intake System \u2014 two build the funnel's task checklist, one builds the brief Google Doc. They have no trigger of their own; the two main automations (units 3 and 4) call them. To assess it: read the visible tabs, then use this manifest. You can answer what is safe to change (change_policy), what breaks if a 'red' item changes, how it connects to sibling pages (edges), and its known issues. Sibling pages live at ../documentation/<slug>.",
  "system": "Funnel Intake System",
  "unit": {
    "index": 5,
    "of": 6,
    "node": "Sub-scenarios + Delivery \u2014 task builders & brief doc"
  },
  "platform": "make.com",
  "scenarios": [
    {
      "id": 4655587,
      "team": 37047,
      "zone": "us1",
      "name": "Page 1 - Funnel Briefs Tasks",
      "role": "Creates 7 build tasks (1,2,3,6,8,10,11) in Funnel Calendar",
      "trigger": "called via Run-a-scenario"
    },
    {
      "id": 4655591,
      "team": 37047,
      "zone": "us1",
      "name": "Page 2 - Funnel Briefs Tasks",
      "role": "Creates 6 build tasks (4,5,7,9,12,13) plus a Launch Date record",
      "trigger": "called via Run-a-scenario"
    },
    {
      "id": 662018,
      "team": 37047,
      "zone": "us1",
      "name": "[Delivery] Create Funnel Brief",
      "role": "Router picks a Google-Doc brief template by funnel shape, creates the doc, writes its URL back to the funnel",
      "trigger": "http webhook"
    }
  ],
  "trigger": {
    "type": "called",
    "by": "main automations units 3 and 4",
    "self_scheduled": false
  },
  "reads": [
    {
      "airtable": "Funnels: Internal",
      "table": "tblQEsC2ZneADsMyU",
      "why": "get the funnel record by id"
    },
    {
      "airtable": "Accounts (Agency)",
      "table": "tblzYMsrs3gSpmflP",
      "why": "Delivery pulls the linked account"
    }
  ],
  "writes": [
    {
      "airtable": "Funnel Calendar: All",
      "table": "tblo2VTsX2AwYaeHV",
      "why": "create the 13 build tasks + a launch-date record"
    },
    {
      "airtable": "Funnels: Internal",
      "table": "tblQEsC2ZneADsMyU",
      "why": "write the Brief GDoc URL back onto the funnel"
    }
  ],
  "notifies": [],
  "edges": {
    "upstream": [
      {
        "node": "New Funnel Brief >> Push to AirTable",
        "scenario": 4620714,
        "unit": 3,
        "via": "CallSubscenario / http_webhook"
      },
      {
        "node": "Express Funnel >> Push to AirTable",
        "scenario": 4742834,
        "unit": 4,
        "via": "CallSubscenario / http_webhook"
      }
    ],
    "downstream": [
      {
        "node": "Growth Strategist \u2014 funnel copy",
        "unit": null,
        "via": "Brief GDoc URL on funnel record"
      }
    ]
  },
  "capabilities": [
    "Page 1 sub creates 7 build tasks (Adjust Team Task List, Confirm Tracking Setup, Write Funnel Copy, Install & Adjust ManyChat Template, Build Integrations, Create Looker Dashboard Page, Send Client Launch Instructions)",
    "Page 2 sub creates 6 build tasks (QA All Copy, Client Copy & Strategy Review, Build DM Funnel in ManyChat, QA & Launch ManyChat + Integrations, Document Funnel via Screenshots, Handoff to Ongoing Monitoring) plus a Launch Date calendar record",
    "Task due dates anchor to the submission date, except client launch instructions which anchor to the launch date",
    "Delivery routes on funnel shape, creates the matching Google-Doc brief from template, and writes the doc URL back to the funnel"
  ],
  "boundaries": [
    "Runs only when a main calls it \u2014 no trigger or schedule of its own",
    "Only knows the funnel it is handed (a single record ID); does not search or match anything itself",
    "Task subs are the legacy build system, retained for handover; retired by unlinking the call in the mains, not by editing here",
    "Delivery only builds briefs for funnel shapes that have a router branch and a doc template"
  ],
  "change_policy": {
    "green": [
      "task names and task descriptions",
      "brief-doc template wording (edit the Google Docs themselves)"
    ],
    "amber": [
      "which task lands on the Page 1 vs Page 2 sub",
      "which Google-Doc template maps to which funnel type"
    ],
    "red": [
      "the get-funnel-record bindings at the top of each sub",
      "the input contract the mains send in (renaming breaks units 3 & 4)",
      "Delivery's funnel-type router"
    ]
  },
  "known_issues": [
    "Task subs are the old build system, kept live only for a clean handover \u2014 expected to be unlinked later",
    "As of 13 Jul the live Replit form maps to ~4 template families (free resource, live event, new follower, paid product) though the router still holds many more branches",
    "Older module labels say 'Campaigns Internal' \u2014 now renamed 'Funnels Internal'; same table"
  ],
  "recovery": {
    "blueprint_backups": [
      "backups/bp_4655587.json",
      "backups/bp_4655591.json",
      "backups/bp_662018.json"
    ]
  }
}