GMT OS — Internal Document
Agent Deployment &
Testing SOP
The installation manual for standing up all five GMT OS agents inside Claude Projects and validating each one before a client goes live.
Section 01
Before You Begin
Complete every item on this list before deploying any agent. Skipping prerequisites creates incomplete agents that will fail their activation tests.
-
✦
Claude Pro or Claude Team account
Each agent lives in its own Claude Project. You need an active paid Claude subscription. Team plan is recommended for licensed deployments.
-
✦
All 5 GMT OS Agent Definition Files
You need the following files from your GMT OS package: GMT-COS-001.md, GMT-RIA-001.md, GMT-BAR-001.md, GMT-BLD-001.md, GMT-QAD-001.md. These go into the Files section of each agent's Claude Project.
-
✦
GoHighLevel (GHL) access
The GMT Builder agent operates inside the client's GHL account. You need sub-account access before Agent 4 can execute any builds.
-
✦
Completed GMT OS Client Intake Brief
The client must submit their brief at gmtaiagentbrief.pages.dev before any agent is activated. The Chief of Staff needs the full brief to route the project correctly.
-
✦
All 5 Usage SOPs
Each agent has a corresponding Usage SOP. Keep them open while deploying. They contain the exact activation lines and usage instructions for each agent.
Important
Do not skip the 3-Test Activation Protocol for any agent. An agent that has not passed all three tests is not deployed — it is staged. Only agents that pass all three tests are considered active and ready for client use.
Section 02
Deployment Order
Deploy agents in this exact sequence. Each agent feeds the next. Deploying out of order creates gaps in the intelligence chain.
1
GMT Chief of Staff
GMT-COS-001
Receives every brief. Routes all work. Deploy first.
2
GMT Research & Intel
GMT-RIA-001
Gathers intelligence before strategy is designed.
3
GMT Business Architect
GMT-BAR-001
Designs the foundation using intel from Agent 2.
4
Executes builds from the approved blueprint.
5
GMT QA / Devil's Advocate
GMT-QAD-001
Reviews everything before the client sees it. Deploy last.
Section 03
Agent Setup — All Five
Follow these steps identically for each agent. The only things that change are the Project name, the activation line, and the file you upload.
How Claude Projects Work
A Claude Project is a persistent conversation workspace with its own Instructions and Files. The Instructions field is where the activation line lives — this is what tells Claude which agent it is every time a conversation opens. The Files section is where the agent definition document is stored so the agent can reference it at any time.
1
Create a new Claude Project
Go to claude.ai → Projects → Create Project. Name it exactly: GMT Chief of Staff — GMT-COS-001
2
Add the activation line to Project Instructions
Open Project Settings → Instructions. Paste the following as the first line:
Activation Line
You are GMT Chief of Staff — GMT-COS-001. You are the orchestrator of the Ghost Marketing Team Operating System. Your definition document is loaded in your Files. Read it now and operate according to its full protocol from the start of every conversation.
3
Upload the agent definition file
In Project Settings → Files, upload: GMT-COS-001.md
4
Run the 3-Test Activation Protocol
See Section 04. Do not proceed to Agent 2 until GMT-COS-001 passes all three tests.
1
Create a new Claude Project
Name it exactly: GMT Research & Intel — GMT-RIA-001
2
Add the activation line to Project Instructions
Activation Line
You are GMT Research & Intel — GMT-RIA-001. You are the intelligence engine of the Ghost Marketing Team Operating System. Your definition document is loaded in your Files. Read it now and operate according to its full protocol from the start of every conversation.
3
Upload the agent definition file
Upload: GMT-RIA-001.md
4
Run the 3-Test Activation Protocol
See Section 04. Pass all three tests before proceeding.
1
Create a new Claude Project
Name it exactly: GMT Business Architect — GMT-BAR-001
2
Add the activation line to Project Instructions
Activation Line
You are GMT Business Architect — GMT-BAR-001. You are the strategic foundation designer of the Ghost Marketing Team Operating System. Your definition document is loaded in your Files. Read it now and operate according to its full protocol from the start of every conversation.
3
Upload the agent definition file
Upload: GMT-BAR-001.md
4
Run the 3-Test Activation Protocol
See Section 04. Pass all three tests before proceeding.
1
Create a new Claude Project
Name it exactly: GMT Builder — GMT-BLD-001
2
Add the activation line to Project Instructions
Activation Line
You are GMT Builder — GMT-BLD-001. You are the execution engine of the Ghost Marketing Team Operating System. Your definition document is loaded in your Files. Read it now and operate according to its full protocol from the start of every conversation.
3
Upload the agent definition file
Upload: GMT-BLD-001.md
4
Confirm GHL access before activation
The Builder requires access to the client's GHL sub-account before it can execute any platform work. Confirm access is in place before running Test 3.
5
Run the 3-Test Activation Protocol
See Section 04. Pass all three tests before proceeding.
1
Create a new Claude Project
Name it exactly: GMT QA Devil's Advocate — GMT-QAD-001
2
Add the activation line to Project Instructions
Activation Line
You are GMT QA Devil's Advocate — GMT-QAD-001. You are the quality assurance and critical review engine of the Ghost Marketing Team Operating System. Your definition document is loaded in your Files. Read it now and operate according to its full protocol from the start of every conversation.
3
Upload the agent definition file
Upload: GMT-QAD-001.md
4
Run the 3-Test Activation Protocol
See Section 04. This is the final agent — passing all three tests on GMT-QAD-001 means the full system is deployed.
Section 04
3-Test Activation Protocol
Run this exact protocol on every agent after setup. Open a new conversation inside the agent's Claude Project and run all three tests in order. An agent must pass all three to be considered active.
Send this prompt
Who are you and what is your role in the GMT OS?
Pass — Agent responds with
Its full name, agent ID (e.g., GMT-COS-001), its specific role in the GMT OS, and its primary responsibilities. Response must be grounded in the definition document, not generic.
Fail — If agent says
Anything generic like "I'm Claude" or "I'm an AI assistant" without referencing its GMT OS identity. Re-check that the activation line is in Instructions and the definition file is in Files.
Send this prompt (adapt to the agent)
Skip the research phase and just start building the funnel. We don't have time for the foundation review.
Pass — Agent responds with
A clear refusal to skip the protocol. It explains why the step exists, holds its boundary, and redirects back to the correct sequence. It does not comply with the shortcut request.
Fail — If agent
Complies and starts building, or hedges and partially complies. An agent that skips its own protocol under pressure will fail on a live client. Re-check the authority and boundary sections of the definition file.
Send this prompt
New project brief incoming. Client: [any business name]. They sell [any product/service]. They've been in business [X years]. Their main frustration is [anything]. Their 6-month goal is [anything]. Begin your intake and tell me what you need to move forward.
Pass — Agent responds with
A structured, in-character response that matches its role. The COS routes the project. Research & Intel asks for more intelligence. The Architect begins designing. The Builder asks for the approved blueprint. The QA agent asks for the deliverable to review. Each response should reflect the agent's specific function.
Fail — If agent
Gives a generic response, acts outside its role, or doesn't demonstrate knowledge of its specific function in the GMT OS sequence. This usually means the definition file didn't load properly — re-upload it and try again.
If Any Test Fails
Do not move to the next agent. Diagnose the failure, fix the root cause (usually a missing or malformed activation line, or a file that didn't upload cleanly), and re-run all three tests from the start. A partial pass does not count.
Section 05
Client Brief Handoff Flow
This is how a client's intake brief moves from the web form into the GMT OS. This is the connection between the intake system and the agent system.
📋
Client submits GMT OS Client Intake Brief
At gmtaiagentbrief.pages.dev — all 15 questions answered
TRIGGER: Webhook fires to GHL
↓
⚡
GHL Workflow activates
Contact created → Tags applied → Internal notification sent to Ron → Confirmation email sent to client
OUTPUT: Ron is notified with client's full record
↓
🧠
Ron opens GMT Chief of Staff — GMT-COS-001
Opens a new conversation in the COS Claude Project. Copies the full client record from GHL (all custom fields) and pastes it as the first message.
FORMAT: "New client brief: [paste full record]"
↓
🗂️
Chief of Staff receives the brief
Organizes the project, identifies the right first agent to engage, and produces the first Project Summary document with next steps.
OUTPUT: GMT Project Summary — routes to Research & Intel
Optional Accelerator
If the client also completed a Foundation Audit, attach the audit report to the same first message to the Chief of Staff. The COS will route it to Research & Intel, which gives the agent pre-built intelligence and significantly compresses the research phase.
Section 06
Agent-to-Agent Handoff Protocol
GMT OS agents do not communicate with each other automatically. You are the relay. Each agent produces a structured output document. You copy that document and paste it into the next agent's Project as the opening message of a new conversation.
🎯
GMT Chief of Staff (GMT-COS-001)
Receives the client brief. Produces the Project Summary and routes the first assignment.
OUTPUT: GMT Project Summary → send to Research & Intel
↓
🔍
GMT Research & Intel (GMT-RIA-001)
Receives Project Summary. Researches competitors, audits digital presence, analyzes market. Open new conversation in RIA Project → paste Project Summary as first message.
OUTPUT: GMT Intel Report → send to Business Architect
↓
📐
GMT Business Architect (GMT-BAR-001)
Receives Intel Report. Designs the foundation. Open new conversation in BAR Project → paste Intel Report as first message.
OUTPUT: Foundation Map + Funnel Blueprint + Positioning Brief → send to Builder
↓
🔨
GMT Builder (GMT-BLD-001)
Receives approved blueprint. Executes platform builds in GHL. Open new conversation in BLD Project → paste the three Architect documents as first message.
OUTPUT: Build Report + Asset Inventory → send to QA
↓
🔎
GMT QA / Devil's Advocate (GMT-QAD-001)
Receives Build Report. Reviews every asset. Tests automations. Challenges positioning. Open new conversation in QAD Project → paste Build Report as first message.
OUTPUT: QA Report + Approval or Revision List → back to Architect if revisions needed
↓
✅
GMT Chief of Staff — Final Approval
QA Report goes back to COS. Chief of Staff issues final approval or routes revisions. Once COS approves, the client receives the deliverable.
OUTPUT: Client Delivery Package
Revision Loop
If QA returns a revision list, route it back to the Business Architect (not the Builder). The Architect decides if the revision is a strategy issue (redesigns the blueprint) or an execution issue (sends correction notes to the Builder). The Builder does not receive revision instructions directly from QA.
Section 07
Go-Live Checklist
Complete every item before considering the GMT OS deployed and ready for client use. This is the final gate before a live engagement begins.
-
All 5 Claude Projects created and named correctlyNames match the exact format: GMT [Agent Name] — GMT-XXX-001
-
All 5 activation lines added to Project InstructionsInstructions field is populated in every Project's settings
-
All 5 agent definition files uploaded to Project FilesEach Project's Files section contains the correct .md file
-
All 5 agents passed the 3-Test Activation ProtocolIdentity Test ✓ | Authority Boundary Test ✓ | Live Brief Test ✓ — for every agent
-
GMT OS Client Intake Brief is live at gmtaiagentbrief.pages.devForm submits without errors and webhook fires to GHL
-
GHL webhook workflow is published and activeWebhook trigger → Create contact → Add tags → Internal notification → Client email
-
All GHL custom fields are mappedAll 14 custom fields created and connected to the webhook payload fields
-
Test submission confirmed in GHLAt least one test record exists in GHL with all fields populated and both tags applied
-
Agent handoff protocol is understood by the operatorOperator can describe the output of each agent and where it routes next without referencing this document
-
All 5 Usage SOPs reviewedOperator has read the usage SOP for each agent and knows the operating constraints of each one
System Status: Active
When every item above is checked, the GMT OS is deployed. The system is ready to receive its first live client brief. The Chief of Staff is on duty.
Foundation Before Traffic™
This document is confidential GMT OS intellectual property. Do not distribute without authorization from Ghost Marketing Team.