Active — GC OS v0.1

Meet Harvey
Your AI COO

Chief Operating Officer, Integrator partner, and AI team orchestrator for GrowthCommunity. Not an assistant. An operator.

EOS Operating System Surgeon Model 8 Studio Agents 7 Lab Agents Unified Memory Layer 3-Repo Workspace
↓ explore the system
Workspace Architecture

Three repos. One unified system.

GC OS is split across three repositories that form a single context. Harvey reads all three on every session start.

⚙️
gc-engine
The System
Harvey's identity, operating spec, skills, playbooks, Studio agents, Lab agents. How Harvey thinks and works. The Visionary maintains this.
You have access ✓
🧠
gc-data
The Knowledge
Business context, client state files, commitments, memory, daily sync notes, meeting lifecycle files. The live data layer shared across the team.
Access pending
🔒
david-private
The Person
Your personal overlay — identity, protected time blocks, preferences, private context. Each operator has their own. Nobody else can see it.
To be created
The Surgeon Model

The operator is the surgeon.
Harvey is the OR team.

The governing posture. Every meeting, call, and deep-work block has three phases. Harvey handles everything outside the operating room.

Pre-op
Everything ready before you walk in
  • Client State file fresh and loaded
  • Last interaction's notes surfaced
  • Open commitments both directions
  • 3–5 line pre-read with objectives
  • Materials staged, drafts drafted
  • Red flags identified and flagged
Intra-op
Invisible unless called
  • Silent during execution
  • Instantly responsive if called
  • Full context loaded, no lag
  • Captures decisions silently
  • Never interrupts the flow
  • Files commitments after close
Post-op
Loop closed without you
  • Extract commitments both directions
  • Draft follow-up emails for review
  • Update client State files
  • Route action items with due dates
  • File reminders to open.md
  • Loop closed within 24 hours
The Studio

8 AI agents.
Client-facing engagement.

GC's internal AI production team. Each agent is a domain specialist who advises and executes. The green-bordered agents are your primary partners.

01 — STRATEGY
The Architect
Client Strategist
Validate All (strategic lens)

Community strategy thesis, audience diagnosis, transformation design. Nobody builds until The Architect signs off.

02 — PROJECT
The Engine
Project & Delivery Lead
All Stages

Master timelines, dependency maps, sprint plans, blocker logs. Active from kickoff through post-launch. Never really leaves.

★ Your primary AI partner
03 — PRODUCT
The Blueprint
Offer & Product Designer
Validate Deliver

Community product spec, tier structures, pricing, Circle architecture. Systems-oriented, design obsessed.

04 — LAUNCH
The Igniter
Launch Strategist
Attract Nurture Convert

Launch campaign architecture, channel plan, pre-launch warm-up sequence. Energetic, momentum-focused.

05 — COPY
The Closer
Direct Response Copywriter
Attract Convert

Sales pages, email sequences, webinar scripts — all in the creator's voice. Empathetic, precise, voice-matching.

06 — COMMUNITY
The Habitat
Community Experience Designer
Deliver Retain

Circle build, onboarding flow, member experience architecture. Member-obsessed, experience-first.

07 — DATA
The Lens
Analytics & Performance
All Stages

Measurement infrastructure, analytics setup, performance reporting. Must be live before the first member joins.

08 — RETENTION
The Compoundor
Retention & Ascension
Retain Ascend

Churn signals, retention playbooks, annual upgrade offers, win-back campaigns, LTV modeling. Takes over at 90 days post-launch.

★ Your secondary AI partner
Default Engagement Handoff Chain
Architect → Engine ★ → Blueprint → Igniter → Closer → Habitat → Lens → 90 days → Compoundor ★
The Lab

7 AI agents.
Internal systems & builds.

The team that builds the machine. Invoked whenever something needs to be created — file structures, apps, automations, data models, interfaces.

01 — PRODUCT
The Spec
Product Strategist

PRD, requirements, non-obvious questions. Always the first agent engaged — you can't architect what you haven't specified.

02 — SYSTEMS
The Foundation
Systems Architect

First-principles structural architecture. AI-native, scale-aware. Files before databases. Databases before apps.

03 — DATA
The Schema
Data Architect

Data modeling, storage decisions, flow design. Knows when a flat file is smarter than a database.

04 — DESIGN
The Pixel
Interface Designer

Modern, clean, top-tier aesthetic. Conditional — only invoked when the build has a user-facing interface.

05 — QA
The Adversary
Adversarial Thinker

Pre-build failure mode analysis. Pressure-tests every design before a line of code is written.

06 — BUILD
The Forge
Builder

Code vs. prompt vs. skill decisions. The executor — turns specs into working systems.

07 — DELIVERY
The Conductor
Delivery Lead

Orchestration, sequencing, handoffs. Always-on from brief to ship. Routes work, tracks state, closes loops.

Invoke the full team
"Conductor, run
the Lab on this build"
Your Role

David — Client Success
Integrator Lead

You're not just a user of the system. You're named in the operating spec — four times.

D
David Salvari
Client Success Integrator Lead · GrowthCommunity
Primary AI Partner
The Engine
Provides the project architecture. You own the client relationship and execution accountability. Jordan sees escalations only.
Secondary AI Partner
The Compoundor
Designs the retention architecture. You own the relationship layer that the architecture can't replace. Personal outreach on high-risk churn signals.
"David (Client Success Integrator Lead) is The Engine's primary human partner. The Engine provides the project architecture; David owns the client relationship and execution accountability. Jordan sees escalations only."
— studio/the-engine.md
"David (Client Success) is the human partner for The Compoundor. The Compoundor designs the retention architecture; David and the creator own the relationship layer that the architecture can't replace."
— studio/the-compoundor.md
"Churn Signal Framework — High-risk: David personal outreach within 48h"
— studio/the-compoundor.md (Retention Intervention Playbook)
Daily Workflow

Four skills.
One complete day.

The daily operating loop once gc-data is live. Pre-op prep, in-meeting execution, post-op closeout — handled.

Morning
Start Day
"start-day" · "good morning"
Harvey reads yesterday's EOD, scans reminders, checks calendar, syncs comms, delivers a 5-block briefing: Headline · 3 Watch items · Red flag · Your call · Wisdom quote. Under 90 seconds to read.
Before each meeting
Prep Meeting
"prep next" · "prep [client]"
Loads client State, meeting history (Fathom transcripts), open commitments both directions, relevant playbooks. Delivers a tight pre-read in chat. You walk in with full context in under 5 minutes.
After each meeting
Close Loop
"close loop" · "wrap [meeting]"
Extracts all commitments both directions, drafts the follow-up email for your review, proposes client State updates, files reminders. Operating room cleaned up within 30 minutes.
Evening
EOD Drop
"EOD" · "closing out"
You drop 3–5 minutes: shipped · decided · stuck · on mind. Harvey files it so tomorrow-Harvey has full context. The daily handoff to your future self.
Skills Index

Every repeatable workflow
lives in a skill file.

Composable, versioned, leveled. Lightweight for reactive patterns. Full rigor for scheduled automation-grade processes.

process-creator
The meta-skill. Builds new skills through a structured interview. Start here when documenting a new workflow.
start-day
Morning bookend. 5-block briefing: headline, watch, red flag, your call, wisdom. ~1–4% context cost.
sync-comms
Sweeps Slack + Gmail + Fathom + Granola. Extracts commitments, reminders, client signals. Never runs inline.
prep-meeting
Pre-op. Loads client State, meeting history, open commitments. Delivers ≤15-line briefing in chat.
close-loop
Post-op. Extracts commitments, drafts follow-ups for review, proposes State updates. Loop closed in 30 min.
client-profile-builder
Builds per-client State files from Slack, DMs, Fathom transcripts. 14-day refresh cadence. Your intelligence layer.
capture-reminder
Logs "remind me about X" to open.md without breaking flow. Surfaces contextually at session start.
eod-drop
Evening handoff. You drop shipped / decided / stuck / on-mind. Seeds tomorrow's context.
financial-review
Monthly financial review. QB data pull, actuals vs forecast, Profit-First overlay, monthly wrap write.
copy-create
Copy Studio. Generates a single piece in entity voice with inline pantheon annotations + Copy Rationale.
copy-series
Multi-piece sequence generation. Tracks state across pieces. Respects awareness arc. Generates 1–2 at a time.
capture-wisdom
Appends quotes / insights to identity/wisdom.md. Feeds the daily wisdom surfaced by start-day.
Playbooks

GC's proprietary IP layer.
How Harvey thinks about the craft.

Frameworks and processes that make Harvey's analysis sound like GC — not generic LLM. Harvey checks these before any craft-level recommendation.

🎯
Membership Offer Design
Compounding value, tier ladders, stair-step pricing, retention. The core offer design framework for every GC engagement.
Framework + Playbook · v0.4
📞
Sales
Discovery call execution — qualify, demonstrate, close. How GC converts creators into Growth Partners.
Playbook · v0.1
🚀
Onboard
Kickoff call execution — direction, momentum, cadence. Sets the tone for the entire engagement.
Playbook · v0.1
🏗️
Design
Strategy sessions and validation — positioning, offer architecture, pricing, serve calls.
Playbook · v0.1
🔨
Build
Implementation — Circle setup, content architecture, operations foundation. From spec to live platform.
Playbook · v0.1
🎆
Launch
Go-live — gated onboarding, first-week experience, launch sequence execution.
Playbook · v0.1
📈
Optimize
Weekly operations — retention interventions, friction removal, growth levers. The ongoing engine.
Playbook · v0.1
✍️
Copy Frameworks
9 master copywriters (the Pantheon), 8 structures (AIDA, PAS, BAB, hook-then-shift...), output types, goal-based frameworks. Loaded by every copy-* skill.
Framework Library · v0.1
Client Delivery Lifecycle
Sales → Onboard → Design / Audit → Build → Launch → Optimize ★

★ Optimize is where David's day-to-day lives — ongoing retention, churn prevention, client health, and ascension architecture.