Clone Solutions
Template

Integration Architecture

One picture and inventory of how Clones connect to your systems, data and each other, with scopes, owners, data flows and change control.

What this is for

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.

When to use it

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.

Who's involved

  • Implementation Engineer owns it.
  • IT lead validates systems, environments and owners.
  • InfoSec lead approves scopes and data flows.
  • Skill Engineering documents custom skills.
  • CoE lead takes ownership by Month 12.

How to fill it in

  1. Start from the Systems & Workflow Map and the Connections & Permissions Plan. Do not re-interview; extend.
  2. Draw the context diagram (section 1): people and channels, Clones, skills, systems, and other AI or automation tools.
  3. Fill in the connection inventory (section 2), one row per connection.
  4. Document custom skills (section 3) with versions and tests.
  5. Map data flows (section 4) including classification and where data rests.
  6. Document Clone-to-Clone handoffs (section 5).
  7. List adjacent AI and automation tools (section 6) so they are governed alongside Clones.
  8. Record change control and failure handling (sections 7–8).

The template

1. Context diagram

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

2. Connection inventory

#CloneSystemConnection typeScope / permissionsRead / writeData classificationApproved byApproval dateSystem ownerReview due
1Support Triage CloneHelpdeskService accountTickets: read, tag, assign; no deleteRead + writeConfidential (customer PII)InfoSec leadDay 41Support OpsDay 131
2

3. Custom skills

SkillBuilt inPurposeSystems touchedVersion in productionPinned?Test packOwnerLast change
ERP AR PostingSkillForgeCreate AR entries from approved billing requestsERPv1.1Yes12 scenarios, all passSkill Engineer → CoE builderDay 118

4. Data flows

FlowFromToDataClassificationWhere it restsRetentionEncrypted in transitNotes
Ticket summary to billingHelpdeskBilling CloneCustomer name, invoice no., issueConfidentialClone conversation historyPer org retention settingYesNo card data in scope

5. Clone-to-Clone handoffs

HandoffFrom CloneTo CloneTriggerPayloadHuman checkpointAutonomy levelFailure handling
Billing disputeSupport Triage CloneBilling CloneTicket tagged "billing"Ticket summary + invoice no.AR Manager approves credit3Returns to Support queue with reason

6. Adjacent AI and automation

ToolUseOwnerData accessGoverned byRelationship to Clones
n8nScheduled data sync ERP → warehouseITERP readAI Use Policy + IT change controlFeeds data the Finance Clone reads
Enterprise chat assistant

7. Change control

  • Production skills are version-pinned
  • Upgrades are tested against the skill's test pack before rollout
  • New connections follow the Connections & Permissions Plan approval route
  • System upgrades (helpdesk, ERP, etc.) trigger a re-test of dependent skills
  • Changes are logged with date, version, approver and rollback version
DateChangeComponentApproved byTestedRollback version

8. Failure modes

FailureDetectionImpactResponseOwner
Expired connection credentialClone Health alert; skill errorsClone cannot read ticketsReconnect via approved account; notify ChampionImplementation Engineer
Upstream API change
Rate limit reached

Good looks like

  • One row per connection, with a named approver and a review date. Nothing in production is undocumented.
  • Write access is the exception and always has a reason, a limit and a person in the loop until promotion.
  • Service accounts, not personal tokens, for anything shared.
  • Non-Clone AI tools are listed. Shadow AI is a governance gap even when it is not ours.
  • The diagram matches reality. A stale architecture doc is worse than none.
  • Common mistake: documenting the target state. Document what is live, and mark planned items clearly.

How Clone helps

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.

Sign-off

RoleNameDateDecision
IT leadApproved
InfoSec leadApproved
Implementation EngineerIssued (version ____)