Skip to content

Chapter 7 — 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.

Chapter at a glance

flowchart TD
    A[Tested workflow<br/>on Account A] --> B[Duplicate tab<br/>per target account]
    B --> C[Renumber node IDs<br/>globally]
    C --> D[Swap avatar ref<br/>+ persona details]
    D --> E[Verify STANDARD<br/>byte-identical]
    E --> F[Test gen<br/>per tab]
    F --> G[Sync tracker]

The 7-step protocol for shipping a workflow across accounts.

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 6 — 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)

Try this

Take the Lvl 3 variant you tested in Chapter 6 (or any single-account workflow at V1+) and fan it out to one additional account.

Steps:

  1. Identify your test account and the target account. Confirm the target avatar reference is uploaded to R2 (Chapter 8 — avatar refs)
  2. Walk the 7-step fan-out protocol: duplicate the tab, renumber node IDs globally, rename node titles, swap the avatar ref Media node, apply per-avatar customizations
  3. Build the STANDARD vs CUSTOMIZED checklist for this workflow if it doesn't exist yet. Confirm STANDARD items are byte-identical between the two tabs after fan-out
  4. Run a single test generation per tab to sanity-check the avatar swap before committing to a full production run
  5. After both accounts ship, sync the master tracker (Syncing the tracker)

If you hit:

  • The new account's tab still has the test account's node titles → step 3 of the protocol got skipped. Re-do it
  • Reference images aren't reaching G-Labs for the new tab → stale per-node link refs after renumbering. Re-read Recovery from failed fan-out and run the link-refs resync helper
  • A STANDARD prompt is rendering differently between the two tabs → byte-level diff. Don't silently diverge — promote the change to STANDARD across all tabs or document the override in CUSTOMIZED
  • Tracker is out of date after fan-out → run tracker-sync explicitly

When you're ready

→ Next: Chapter 8 — 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 9 where you'll add new ones.