Skip to content

Chapter 6 — Fan-out & Multi-account

A workflow is built and tested on one account first. Once it works there, you ship it to the remaining target accounts. This is fan-out, and there's a fixed 7-step protocol that protects shared content from drift.

What you'll learn

  • What fan-out is and why we don't skip the single-account test phase
  • The difference between STANDARD content (same across all accounts) and CUSTOMIZED content (per-account)
  • Why globally-unique node IDs matter when duplicating tabs
  • The 7-step fan-out protocol in detail
  • How to recover when a fan-out goes wrong (drift, broken links, etc.)
  • How to sync the master tracker after a fan-out using the tracker-sync skill

Before this chapter

Read Chapter 5 — Lvl 3-4 Variants. You should have at least one workflow that's gone through testing and is ready to ship to more accounts.

Sections

  1. Fan-out protocol (the 7 steps) — the canonical procedure
  2. STANDARD vs CUSTOMIZED — the rule — the most important fan-out concept
  3. Recovery from a failed fan-out — restoring, diagnosing, retrying
  4. Syncing the tracker — keeping the master tracker current (also see skills/tracker-sync)

When you're ready

→ Next: Chapter 7 — Products & Accounts. Concepts for the brand / product / account structure — what files exist, how avatars are set up, how sales channels work, what compliance rules apply. Sets up Chapter 8 where you'll add new ones.