By Month 4, Clones are working across CRM, ERP, HR systems, ticketing and the data warehouse, and starting to hand work to each other. Without one shared picture, nobody can answer simple questions: what can this Clone touch, which skill writes to the ERP, what breaks if we upgrade the helpdesk? This document is that picture. It covers every connection, custom skill, data flow and handoff, plus the non-Clone AI and automation tools on the roadmap, so the platform stays governed instead of becoming a tangle.
Draft it when Department rollout 3 begins or the first cross-department workflow is designed, whichever is first. Update it before any new connection, custom skill or handoff goes live. Review it quarterly with IT and InfoSec. It becomes part of the handoff documentation at Month 12.
Show, left to right: channels (Slack, Teams, email, phone, SMS, Clone Team Studio) → Clones (grouped by department) → skills (Marketplace and custom) → systems (by owner) → data stores. Mark Commander-orchestrated workflows and every point where a person approves.
code
[Slack / Teams / Email / Phone]
│
┌──────┴────────┐
│ Support Clone │──skill: Helpdesk (v2.3, pinned)──▶ [Helpdesk]
│ │──handoff──▶ [Billing Clone] ──skill: ERP AR (custom v1.1)──▶ [ERP]
└───────────────┘ │
approval: AR Manager
The Solutions Architect Clone drafts the inventory from the Systems & Workflow Map and the approved connections, generates the context diagram, and flags drift when a connection or skill version changes without an update. The GRC Clone checks every row against the Connections & Permissions Plan. The portal keeps the document versioned and links each row to its approval record.