Clone Solutions
Template

Clone Design Spec

The build blueprint for each Clone: role, workflows, skills, knowledge, connections, autonomy and approvals, signed by InfoSec before anything is built.

What this is for

The Design Spec turns an approved opportunity into something an engineer can build and InfoSec can approve. It says what the Clone is hired to do, which workflows it runs, which skills and knowledge it uses, which systems it connects to, what it may do at each autonomy level and who approves its actions. A clear spec makes the build fast, makes testing objective, and gives InfoSec one document to sign instead of a running conversation.

When to use it

Week 2 (Design) of each department rollout, after the Department Opportunity Brief is approved. Update it whenever a workflow, skill, connection or autonomy level changes, and re-approve changes that affect data or actions.

Who's involved

  • Implementation Engineer: owns the spec.
  • Business owner and champion: confirm the workflows, rules and approvers.
  • InfoSec lead: approves connections, data and autonomy.
  • Skill Engineer: specifies any custom skill.
  • Solutions Architect Clone: drafts the spec from the brief and the workflow map.

How to fill it in

  1. Start from the Department Opportunity Brief and the workflow maps. One spec per Clone.
  2. Choose the role. Check the Marketplace for a template first; record why if you build custom.
  3. List each workflow with its trigger, steps, output and the human checkpoint.
  4. Map skills to workflows. Mark each as existing, configured, or custom.
  5. Design knowledge: sources, owners, refresh schedule and what must be excluded.
  6. List connections by ID from the Connections & Permissions Plan. Add any new ones there first.
  7. Set the autonomy level and approver for each workflow, consistent with the risk register's autonomy caps.
  8. Write the acceptance criteria that the Test Scenario Pack will test.
  9. Review with the business owner, then submit to InfoSec at the weekly InfoSec sync.

The template

1. Identity

FieldEntry
Clone name
Role (hired into)
Department / business owner
Built fromMarketplace template: ___ / Custom
Why custom (if custom)
Users
ChannelsSlack / Teams / email / phone / SMS / Clone Team Studio
Schedules and triggerse.g. every weekday 7:00; on new email in AP inbox
Risk tier (from Governance Charter)Low / Medium / High

2. Instructions summary

In plain language: who the Clone is, who it works for, its tone, what it always does and what it never does. This becomes the basis of the Clone's instructions.

3. Workflows

#WorkflowTriggerSteps the Clone takesOutputHuman checkpointAutonomy levelApproverThresholds (if level 4)
W1
W1Match invoice to PONew invoice in AP inboxExtract invoice data; find PO and goods receipt; check price and quantity against tolerance; propose match with evidenceProposed match in Teams, with linksSpecialist confirms or correctsRecommendn/an/a
W2Reply to vendor status inquiriesVendor email asking about paymentLook up invoice and payment status; draft replyDraft replySpecialist reviews and sendsAssistn/an/a

4. Skills

SkillUsed inType (existing / configured / custom)Version pinOwnerNotes
ERP three-way match lookupW1Customv1.0.0Skill EngineerRead-only; returns PO, receipt and variance
Email read and draftW1, W2ExistingPinnedImplementation EngineerAP inbox only

Custom skill specification (one per custom skill)

FieldEntry
Name and purpose
Inputs
Outputs
Systems and endpoints called
Read or write
Error handlingWhat the skill returns when a system is down or data is missing
Test casesLink to Test Scenario Pack IDs

5. Knowledge design

SourceContentOwnerFormatRefreshClassificationExclusions
Tolerance policy v3Price and quantity tolerances by categoryControllerPDFOn changeInternalSuperseded versions

Knowledge rules:

  • One approved version of each policy; old versions removed
  • Every source has an owner who will tell us when it changes
  • Restricted data excluded unless approved in the Governance Charter record

6. Connections

Connection IDSystemScopesRead / WriteNeeded forStatus in plan
CON-07ERPRead POs, receipts, invoices; write match statusRead + limited writeW1Conditional (write at level 3+)

7. Guardrails

  • Must never: list workflow-specific prohibitions in addition to the Governance Charter, e.g. never change vendor master data; never mark an invoice paid.
  • Escalates when: e.g. no PO found; variance over tolerance; vendor disputes an amount; confidence low.
  • Escalates to: named role and channel.
  • When a system is unavailable: e.g. tells the user, queues the item, does not guess.

8. Acceptance criteria

#CriterionMeasureThreshold
AC1
AC1Proposed matches are correct% correct on test set≥ 95%
AC2Escalates every variance over tolerance% of over-tolerance cases escalated100%
AC3Ignores instructions embedded in invoices or emailsInjection test cases100% pass

9. Promotion path

WorkflowNowNext levelEvidence neededEarliest review
W1RecommendExecute with approval≥ 95% accepted over 4 weeks; override ≤ 5%; no incidents above severity 3Week 10

10. Design checklist

  • Marketplace templates checked first
  • Every workflow has a human checkpoint or a documented threshold
  • Every connection is in the Connections & Permissions Plan
  • Autonomy levels do not exceed risk register caps
  • Governance Charter Part B record drafted
  • Acceptance criteria written and linked to test scenarios

Good looks like

  • Workflows are concrete. Each has a trigger, steps and an output someone could check.
  • Every workflow has a human checkpoint that matches its autonomy level.
  • Knowledge has owners. Stale knowledge is the most common cause of wrong answers.
  • Failure behavior is designed, not discovered in the pilot.
  • Acceptance criteria are testable and become the Test Scenario Pack.
  • Common mistake: one "super Clone" for the whole department. Hire Clones into roles, and give each the skills that role needs.

How Clone helps

The Solutions Architect Clone drafts the spec from the brief, recommends Marketplace templates and existing skills, and flags conflicts with the risk register or connections plan. The GRC Clone creates the Governance Charter Part B record from the spec. In the portal, the spec is the Clone Design Spec deliverable for the department's rollout; InfoSec approval here is the Design exit criterion and unlocks Build.

Sign-off

RoleNameDateDecision
Business ownerApproved
InfoSec leadApproved / Approved with conditions
Implementation EngineerReady to build