Clone Solutions
Template

CoE Charter

Charter for your internal AI Center of Excellence, covering mandate, people, governance board, builder community, intake and the handover from the Clone team.

What this is for

The goal of the engagement is that your organization runs its agentic program without us. The Center of Excellence (CoE) is how that happens: an internal AI governance board plus a builder community that owns intake, standards, skills, governance and enablement. This charter gives the CoE a clear mandate, named people, real decision rights and a transition plan, so self-sufficiency is planned rather than assumed.

When to use it

Draft it in Month 8 and approve it before Month 9. The CoE then shadows the Clone team in Months 9–10, co-leads in Month 11 and leads in Month 12. Review the charter annually.

Who's involved

  • Executive sponsor charters the CoE and signs.
  • CoE lead owns it day to day.
  • Governance board: InfoSec lead, IT lead, a business owner rotation, legal or compliance, HR.
  • Builder community: org admins, Champions and power users who build in SkillForge.
  • Solutions Partner and Change & Enablement Lead coach the transition.

How to fill it in

  1. Write the mission in two sentences (section 1).
  2. Agree scope: what the CoE owns, and what it does not (section 2).
  3. Name the people and protected time (section 3).
  4. Set decision rights and forums (sections 4–5). Reuse the Agentic Operating Model RACI.
  5. Define the intake process (section 6).
  6. Set measures (section 7) and the transition plan (section 8).

The template

1. Mission

Example: The Northgate AI Center of Excellence helps every team put AI teammates to work safely. We own the standards, the intake and the governance so departments can move fast without creating risk.

2. Scope

The CoE ownsThe CoE does not own
Intake and prioritization of new Clone and AI requestsDay-to-day accountability for a Clone's work (business owner)
Standards: design, naming, knowledge, prompts, testingFinal security approval (InfoSec lead)
Skill change control and the builder communityBudget decisions outside the AI program
Autonomy promotion process (runs it; does not sign)HR decisions on roles
Enablement: training, Champions, how-to library
Monitoring rhythm and optimization reviews
Governance of adjacent AI tools under the AI Use Policy

3. People

RoleNameDepartmentTime commitmentResponsibilities
CoE lead50–100%Runs the CoE; chairs intake; owns the operating model
Governance board: InfoSec2 hrs/monthSecurity approvals; incident review
Governance board: IT2 hrs/monthSystems, connections, change control
Governance board: business owner (rotating)2 hrs/monthBusiness priority and value
Governance board: legal / compliance1 hr/monthPolicy and regulatory input (not legal advice from Clone)
Lead builder40%SkillForge standards; code review; test packs
Builders (certified)10–20%Build and maintain skills
Champions networkPer charterAdoption in departments

4. Decision rights

DecisionDecided byInput fromForum
Approve a new Clone or skill requestCoE leadGovernance boardIntake review
Approve a new connectionInfoSec leadIT lead, CoEInfoSec sync
Autonomy promotionInfoSec lead AND business ownerCoE (prepares evidence)Promotion review
Skill version to productionLead builderBusiness ownerChange review
Standards and policy updatesGovernance boardChampionsMonthly board
Pause a Clone in an emergencyInfoSec lead or business owner–Any time

5. Forums and cadence

ForumCadenceAttendeesOutput
Intake reviewWeeklyCoE lead, lead builderScored and prioritized requests
Governance boardMonthlyBoardDecisions, policy changes, risk review
Builder communityBi-weeklyBuildersShared patterns, code review, demos
Champions councilBi-weeklyChampions, CoE leadAdoption issues, wins
Quarterly business reviewQuarterlySponsor, steering, CoERoadmap, promotions, results

6. Intake process

  1. Request submitted (problem, department, volume, systems, data)
  2. Scored with the opportunity rubric (value, feasibility, risk, data readiness)
  3. Route: Marketplace template / configuration / custom skill / non-Clone tool / decline
  4. Design spec and InfoSec review for anything touching new data or connections
  5. Build, test, pilot, go-live using the department rollout cycle
RequestDepartmentScoreRouteDecisionTarget date
Vendor onboarding intakeProcurement3.9Marketplace template + 1 custom skillApprovedMonth 11

7. Measures

MeasureTarget
Requests triaged within 5 business days90%
Skills built by client builders (vs. Clone team) by Month 12Majority of new skills
Workflows at Execute with approval or higher
Governance incidents above agreed severity0
Champion coverage in live departments100%
Clones reviewed for Power Rating and usage each quarter100%

8. Transition plan

CapabilityMonths 9–10 (shadow)Month 11 (co-lead)Month 12 (lead)Ready?
Intake and prioritizationClone team leads; CoE attendsCoE leads; Clone team reviewsCoE alone
Skill building (SkillForge)Builders pair with Skill EngineersBuilders lead; review by Clone teamBuilders alone
Promotion evidence packsObserveAssembleOwn
Audit log reviewsObserveCo-runOwn
Training and Champions councilCo-runLeadOwn
Optimization reviewsObserveCo-runOwn

Good looks like

  • The CoE lead has real time, ideally a dedicated role, not a side project.
  • InfoSec sits on the board and keeps its approvals. The CoE runs the process; it does not replace the signatures.
  • Intake is visible and scored. Requests do not disappear into a queue.
  • Builders ship real skills before Month 12. Certification without production work is not readiness.
  • The transition plan has a "ready?" check per capability, agreed by both sides.
  • Common mistake: chartering a committee that only meets. The CoE should do work: intake, builds, reviews.

How Clone helps

The Project Clone drafts the charter from the Agentic Operating Model and tracks the transition plan in the portal, capability by capability. The Enablement Clone runs builder and Champion training and maintains the how-to library the CoE inherits. The GRC Clone hands over the risk register, evidence routines and audit log review checklist. The Solutions Architect Clone trains the CoE on the opportunity rubric for intake.

Sign-off

RoleNameDateDecision
Executive sponsorCoE chartered
CoE leadAccepted
InfoSec leadApproved
Solutions PartnerTransition plan agreed