Ecosystem
One blueprint, used at three levels.
The same five-layer blueprint runs the whole growth function, each discipline inside it, and every skill inside those. The Search OS is one of seven disciplines.
76
skills across seven disciplines, all built on one blueprint
The blueprint
AI OS Foundation
1Operating manual
2Context
3Infrastructure
4Engine
5Processes
APPLIED AT EVERY LEVEL ▾
Level 1 · The whole growth function
Growth OS
Owns the shared business documents, the tools list, and the planning calendar.
Company
Brand voice
Personas
Messaging
Competitors
Metrics
Ops & tools
Seven shared business documents, read by every discipline below
Level 2 · One system per discipline
Search OSVisibility in search engines and AI answers · 35 skills
Level 3 · Each skill is a small systemAudit a page · Write a blog for AI answers · Track AI visibility · Launch a visibility program · and 31 more
Paid & Campaigns5 skills
Content & Creative6 skills
Lifecycle & Conversion6 skills
Sales Enablement5 skills
Insights & Analytics6 skills
Growth Ops & Programs6 skills
Level 1The whole function
Level 2One discipline
Level 3One workflow
The ruleEach level uses what's above it and adds its own. Nothing is copied.
AI OS Foundation
Five questions every system answers.
Each layer answers one question. When something could fit two layers, the question decides where it goes.
5
layers, plus a set of governance rules that applies to all of them
1Operating manual
How must it behave?Rules, naming, which source wins when two disagree, what never to do
2Context
What's true?Knowledge (refreshed on a schedule) · current state (overwritten) · memory (added to, never erased)
3Infrastructure
What can it reach?Data sources, connected tools, storage, account details
4Engine
What does the work?Skills, agents, and orchestrators that run skills in order
5Processes
When does it run, who approves, where does it go?Schedules, triggers, approval steps, handoffs, where finished work is saved
Governance
Governance, in every layerOne owner and one home per document · dated versions · refresh schedules · a confidence tag on every claim · a checklist before delivery
Two scopesShared: true for every business, kept once. Business: true for one business, kept in its own folder.
Design top-down, run bottom-upDesign from rules down to schedules. At run time, a schedule triggers a skill, which uses tools to read context and follows the rules.
Growth OS · Level 1
What every discipline shares.
The Growth OS sets the rules, the business documents, the tools list, and the calendar. Each discipline inherits them.
7
shared business documents, written once and read by every discipline
1Operating manual
Growth operating manualGovernance lower levels can't loosenApproval pathsBrand and legal guardrails
2Context
CompanyBrand voicePersonasMessagingCompetitorsMetrics
Plus current goals, roadmap and backlog, team capacity, and a decision log3Infrastructure
Ops & tools listGoogle Drive and NotionSearch, analytics, CRM, ads, email, AI visibility, ticketing
Skills ask for a kind of data. The tools list says which tool and account provide it.4Engine
Search OS · 35Paid & Campaigns · 5Content & Creative · 6Lifecycle & Conversion · 6Sales Enablement · 5Insights & Analytics · 6Growth Ops & Programs · 6Document upkeep · 7
5Processes
Quarterly planningWeekly prioritiesReporting calendarDocument refresh: brand, personas and messaging quarterly; competitors and metrics monthlyRetros that feed lessons back
Growth OS · Shared documents
Seven documents power every discipline.
Each cell counts the skills in a discipline that read that document. Write each document once, and every discipline uses the same version.
69
skills across the seven disciplines read these documents
Every skill also reads the ops & tools list, because that's how it finds its data. For the Search OS, "Company" includes product details and approved claims, and "Metrics" includes goals and targets.
Growth OS · Engine
Seven disciplines, each with its own working documents.
Each discipline adds its own documents on top of the shared seven. Disciplines can read each other's work: Content uses Search's topic clusters, and Lifecycle uses Content's inventory.
7
disciplines, plus seven skills that keep the shared documents current
Search OS · 35
Own documents: search knowledge base (updated weekly) · search landscape · page inventory · program statusResearch queries & prompts · Map topic clusters · Build a content brief · Audit a page · Technical site audit · Write a blog for AI answers · Track AI visibility · Track AI crawler access · AI visibility report · Find citation opportunities · Launch a visibility program · and 24 more
Paid & Campaigns · 5
Own documents: channel playbook · campaign calendar · budget planCampaign briefs · Ad copy · Audience targeting · Budget pacing · Event plans
Content & Creative · 6
Own documents: content inventory · editorial standards · subject-expert directoryContent strategy · Content briefs · Long-form content · Case studies · Social posts · Repurposing
Lifecycle & Conversion · 6
Own documents: lifecycle map · email and design system · experiment logLanding pages · Emails · Nurture sequences · Lead scoring · Experiments · Customer communications
Sales Enablement · 5
Own documents: sales process · objection library · proof library · CRM field guideAccount research · Battlecards · Outbound sequences · Deal briefs · Sales assets
Insights & Analytics · 6
Own documents: data sources map · baselines and targets · known data issues · reporting calendarPerformance reports · Dashboards · Anomaly investigations · Attribution · Tracking audits · Customer feedback themes
Growth Ops & Programs · 6
Own documents: goals · team capacity · stakeholder map · roadmap and backlogWeekly priorities · Tickets · Stakeholder updates · Executive decks · Quarterly planning · Retros
Document upkeep · 7
One skill keeps each shared document currentCompany · Brand voice · Personas · Messaging · Competitors · Metrics · Ops & tools
Search OS · Level 2
Visible, accurate, and chosen in search and AI answers.
One shared system serves any number of businesses. Items tagged From Growth OS are inherited, not rebuilt.
10
knowledge files on search and AI best practices, refreshed every week
1Operating manual
Search OS operating manualThe same 6-step start-up check in all 35 skillsRules for who updates which file"Active business" set in each projectGrowth rulesFrom Growth OS
2Context
Search knowledge base, with a confidence tag on every claimWeekly change log and digestSearch landscape: topics, queries, AI prompts, questions, cited sourcesPage inventoryProgram status: baselines, findings, backlog, memoryBusiness documentsFrom Growth OS
3Infrastructure
20 kinds of data: search performance, AI visibility, crawl data, crawler logs, keywords, rankings, page fetch, ticketing…Google Drive as the home for all contextTools listFrom Growth OS
4Engine
Setup · 2Research · 4Strategy · 4Audit · 4Create · 6Authority · 3Monitoring · 5Reporting · 4Orchestrators · 3
5Processes
Knowledge update every Monday, once for all businessesOne file reviewed in depth each weekMonitors scheduled per businessApproval before drafts, plans, tickets, pitches and reports go outWeekly prioritiesFeeds Growth OS
Search OS · Engine
35 skills in eight groups, run by three orchestrators.
Each skill does one job. Orchestrators run skills in order, pause for your approval, and pass results along through Drive.
35
skills · 6 run on a schedule
Setup2Build and maintain context
Set up the knowledge baseUpdate the knowledge base
Research4What people ask, who answers
Queries & AI promptsAudience questionsCompetitorsSources AI engines cite
Strategy4What to build, in what order
Map topic clustersCheck for overlapPrioritize opportunitiesBuild a content brief
Audit4What's broken, and why
Audit a pageTechnical site auditContent inventoryDiagnose traffic drops
Create6Make and improve pages
Blog for AI answersPage copySchema markupTitles & descriptionsInternal linksReview colleagues' drafts
Authority3Get mentioned where AI looks
Find citation opportunitiesDraft media pitchesFix third-party profiles
Monitoring5Watch and alert on a schedule
AI visibilityAI crawler accessCompetitor movesContent freshnessSearch news impact
Reporting4Show results, hand off work
Search performance reportAI visibility reportExecutive briefDev tickets
Orchestrators
Launch a visibility program
Queries → Questions → Competitors → Cited sources Approve → Topic clusters → Overlap → Priorities Approve → Briefs → Monitors → Kickoff brief
Full site audit
Technical → Content inventory → Key pages → Third-party profiles Approve → Priorities → Executive brief Approve → Dev tickets
Plan the week
Program status + Monitor results + Knowledge digest + Open tickets → Priorities → This week's plan
Runs on a scheduleApproveYou approve before it continuesHover a skill to see its exact name
Search OS · Running a business
From install to a weekly rhythm.
Install and shared setup happen once. After that, each business runs inside its own Claude project, one chat per job. Drive holds the memory, so a new chat picks up where the last one stopped.
1
Claude project per business, one chat per job
Once
1Install
Upload the 35 skills. Connect Drive and your data tools.
Once, shared
2Shared setup
Knowledge base in Drive. Weekly update scheduled.
"Set up the knowledge base."
Each business
3Onboard
Use existing docs or draft them. Connect tools. Approve.
"Onboard this business…"
Then quarterly
4Launch
Research, plan, briefs. Monitors switched on.
"Launch a visibility program…"
As needed
5Audit
Ranked fixes, executive brief, dev tickets.
"Full site audit."
Weekly
6Plan & do
A weekly plan, then one task at a time.
"Plan my week." "Go 1."
Monthly
7Report
Search and AI visibility, plus an executive summary.
"Monthly SEO report."
Chats in each business project
OnboardingOnce: setup, drafts, approvals
Program launchOnce, then quarterly
Site auditAs needed, through to tickets
Week of [date]A new chat each Monday for small tasks
One per deliverableA blog, a page rewrite, a set of tickets
Monthly reportReports and the executive summary
Who does what
Claude runs itAudits, research, monitors, briefs. You review.
Claude drafts, you approveBlogs, page copy, tickets, pitches, executive briefs
You do itSend pitches, approve changes, adjust account settings
Always a personBusiness document drafts, the ranked plan, tickets, every pitch, reports before they go out
Growth OS + Search OS · Processes
How the two systems keep time.
Search schedules fit inside the Growth calendar. The knowledge base updates once for every business. Monitors and plans run for each business separately.
1
weekly knowledge update, shared by every business
| Growth OS | Search OS · shared | Search OS · each business | |
|---|---|---|---|
| Daily | — | — | AI crawler access |
| Weekly | Priorities across disciplines Budget pacing | Knowledge update (Monday) One file reviewed in depth | AI visibility Competitor moves Search news impact Plan my week |
| Monthly | Performance reporting Competitor and metrics refresh | Refresh skill backup copies | Content freshness Search and AI visibility reports Cited sources and competitor footprint |
| Quarterly | Quarterly plan and goals Brand, personas, messaging review Retros | — | Research refresh Strategy cycle Content inventory |
The weekly loop
Lessons flow back: program memory → knowledge base → change log.
Runs on a schedule
Growth OS + Search OS · Where things live
One system, many businesses.
Best practices are kept once and shared. Business facts stay in that business's folder. Adding a business means onboarding it, not rebuilding anything.
1
shared knowledge base for every business you add
Shared · kept once
True for every business
Maintained on a schedule
AI OS FoundationRules
Growth operating manualRules
Search knowledge baseKnowledge
10 best-practice filesWeekly
Change log and digestsMemory
Conversion and UX knowledgeWith Lifecycle
Ad platform specsWith Paid
Per business · one folder each
True for one business
Never copied between businesses
Shared business documentsGrowth OS
Company · voice · personas · messaging · competitors · metrics
Tools listAccess
Goals and backlogStatus
Search folderSearch OS
Search landscapeKnowledge
Page inventory · program statusStatus
Monitor logsMemory
Other discipline foldersTheir own docs
Claude account
Skills, schedules, projects
Set up once
76 skillsEngine
1 shared knowledge updateSchedule
Monitors for each businessSchedule
1 project per businessRules
Business Aproject + folder
Business Bproject + folder
Business Cproject + folder
Inherit, then addSearch reads the Growth business documents and adds its own. It never copies them.
One home, one ownerEvery document lives in one place. Skills keep only a labeled backup for when Drive can't be reached.
Ask for data, not toolsA skill asks for "search performance." The tools list maps that to a tool and account for each business.
Which rule winsGrowth rules, then Search rules, then the skill. A lower level can be stricter, never looser.