coppermind-cmo 0.3.2__tar.gz → 0.3.4__tar.gz

{coppermind_cmo-0.3.2/src/coppermind_cmo.egg-info → coppermind_cmo-0.3.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: coppermind-cmo
-Version: 0.3.2
+Version: 0.3.4
 Summary: AI-powered memory for fractional CMOs — never forget a client detail, never leak data between clients
 Author-email: Ben Finklea <ben@volacci.com>
 License-Expression: LicenseRef-Proprietary

{coppermind_cmo-0.3.2 → coppermind_cmo-0.3.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "coppermind-cmo"
-version = "0.3.2"
+version = "0.3.4"
 description = "AI-powered memory for fractional CMOs — never forget a client detail, never leak data between clients"
 readme = "README.md"
 license = "LicenseRef-Proprietary"
@@ -71,4 +71,4 @@ exclude_lines = [
 where = ["src"]
 
 [tool.setuptools.package-data]
-coppermind_cmo = ["supabase-ca.pem", "skills/*.md", "statusline.sh"]
+coppermind_cmo = ["supabase-ca.pem", "skills/*.md", "statusline.sh", "commands/*.md"]

coppermind_cmo-0.3.4/src/coppermind_cmo/commands/cmo-actions.md

@@ -0,0 +1,39 @@
+# /cmo-actions — Cross-Client Action Items
+
+Show overdue and open action items across all clients.
+
+## Steps
+
+1. Call `list_minds` to get all client minds.
+2. For each client, switch and search for commitment-type memories.
+3. Build a unified action item view grouped by urgency:
+
+```
+ACTION ITEMS — All Clients
+
+OVERDUE
+- [Acme] Send revised media plan to Sarah — due 3/8 (7 days overdue)
+- [5 Star] Follow up with Stephanie on LSA lead marking — due 3/11 (4 days overdue)
+
+DUE THIS WEEK
+- [Acme] Approve Q3 creative concepts — due 3/18
+- [XSCAPE] Verify satellite office signage — no date, committed 3/11
+
+OPEN (no due date)
+- [5 Star] Evaluate RP1 as Lead Truffle replacement
+- [5 Star] Help with van wrap design
+- [XSCAPE] Review direct mail demographics with Josh before printing
+- [Bluebell] Finalize Q2 content calendar
+
+TOTAL: 8 open items across 3 clients
+```
+
+4. Ask: "Want me to focus on any of these?"
+
+## Rules
+- Process all clients in parallel.
+- Sort overdue items by how late they are (most overdue first).
+- Only include commitments that haven't been resolved by a later memory.
+- If a commitment was clearly completed based on subsequent memories, skip it.
+- Keep descriptions to one line each.
+- Show the client name in brackets on every line — this is a cross-client view.

coppermind_cmo-0.3.4/src/coppermind_cmo/commands/cmo-batch.md

@@ -0,0 +1,44 @@
+# /cmo-batch — Batch Content Creation
+
+Write content for multiple clients in one session.
+
+## Usage
+
+User says something like:
+- "Write this week's social posts for all my clients"
+- "Draft newsletters for Acme and 5 Star"
+- "Write a blog post for each client about spring topics"
+
+## Steps
+
+1. Parse which clients and what content type.
+   - If "all clients": use `list_minds` to get the full list.
+   - If specific clients named: use those.
+2. For each client:
+   a. Switch to the client
+   b. Pull brand voice, content themes, and recent memories
+   c. Write the requested content using the client's voice and themes
+   d. Label it clearly with the client name
+3. Present all content together with clear separators:
+
+```
+---
+ACME CORP — Social Post (Instagram)
+[content in Acme's brand voice]
+---
+5 STAR CHARLESTON — Social Post (Instagram)
+[content in 5 Star's brand voice]
+---
+XSCAPE — Social Post (Instagram)
+[content in XSCAPE's brand voice]
+---
+```
+
+4. Ask: "Want me to adjust any of these, or copy them all to clipboard?"
+
+## Rules
+- Each piece of content MUST use that client's brand voice. This is the whole point — don't use a generic voice.
+- Reference recent events/memories when relevant ("Just launched our rebrand!" for XSCAPE, "Spring tune-up season is here" for 5 Star).
+- Match the content type to the platform (short for social, longer for blogs, professional for newsletters).
+- If a client has no brand voice set, mention it: "[Client] doesn't have brand voice configured yet. Want me to set it up?"
+- Don't show the switch_client responses. Just present the final content.

coppermind_cmo-0.3.4/src/coppermind_cmo/commands/cmo-connect.md

@@ -0,0 +1,43 @@
+# /cmo-connect — Pull Data from Any MCP
+
+Bridge data from any connected MCP into Coppermind. Claude acts as the extractor — fetches data, breaks it into memories, and stores them with the right types.
+
+## Usage
+
+- `/cmo-connect pull my last 3 Granola meetings into the right client minds`
+- `/cmo-connect search Gmail for emails from sarah@acme.com about the rebrand`
+- `/cmo-connect pull recent Slack messages from #acme-marketing`
+
+## Steps
+
+1. Parse what the user wants: which data source, what data, which client(s).
+2. Check if the required MCP is connected (look for its tools in available tools).
+   - **If not connected:** Tell them exactly how to add it. Example: "Granola isn't connected. Run `claude mcp add granola -- uvx granola-mcp-server` and restart."
+   - **If connected:** Proceed.
+3. Fetch the data using the source MCP's tools.
+4. For each item (meeting, email, message):
+   a. Determine which client mind it belongs to (match by participant names, company names, or ask the user).
+   b. Switch to that client mind.
+   c. Extract and store memories using the same rules as transcript ingestion:
+      - Stakeholder profiles, decisions, commitments, key facts
+      - Tag with the source date and source type
+   d. Report progress every 10 memories.
+5. Summarize: "Pulled [N] items from [source]. Stored [M] memories across [K] clients."
+
+## Known MCP Setups
+
+- **Granola:** `claude mcp add granola -- uvx granola-mcp-server` (no API key, reads local cache)
+- **Slack:** Check for `slack_read_channel`, `slack_search_public` tools
+- **Gmail:** Check for `gmail_search_messages`, `gmail_read_message` tools
+- **Google Calendar:** Check for `gcal_list_events` tools
+
+## Rate Limits
+- Maximum 50 memories per invocation
+- Maximum 20 source items per fetch (emails, meetings, messages)
+- If the source has more, store the 50 most recent/important first and tell the user: "There's more — want me to continue?"
+
+## Rules
+- Always confirm which client mind to store into before storing. If ambiguous, ask.
+- Don't store duplicate content — check if a similar memory already exists before storing.
+- Meeting transcripts from Granola should be processed the same way as pasted transcripts (full extraction, not just a raw dump).
+- Report what was stored at the end, not during. Keep the output clean.

coppermind_cmo-0.3.4/src/coppermind_cmo/commands/cmo-followup.md

@@ -0,0 +1,25 @@
+# /cmo-followup — Post-Meeting Follow-Up Email
+
+Draft a follow-up email after a client meeting.
+
+## Steps
+
+1. Confirm the active client. If none, ask which client the meeting was with.
+2. Pull the most recent memories (last 24 hours) and the last meeting brief if saved.
+3. Check if a CMO voice profile exists (search for an internal mind called "CMO Profile" or check for a `cmo_voice` memory). If found, use it for tone and style. If not, use a neutral professional tone — warm, concise, and direct.
+4. Do NOT use the client's brand voice for emails. Brand voice is how the client talks to their customers. This email is from the CMO to the client.
+5. Draft a follow-up email that includes:
+   - Brief thank-you / recap of what was discussed
+   - Key decisions made (bulleted)
+   - Action items with owners and deadlines (bulleted)
+   - Next steps or next meeting date if known
+6. Match formality to the relationship — use stakeholder profile to gauge. If the stakeholder profile says "direct communicator" or the transcript shows casual language, be casual. Otherwise default to professional.
+7. Present the draft and ask: "Want me to adjust anything, or copy this to your clipboard?"
+
+## Rules
+- Keep it short — 3-4 paragraphs max. CMOs send dozens of these.
+- Never include internal notes or agency-specific details. This goes TO the client.
+- Action items should clearly state who owns each one (including items the CMO owns).
+- If the user just pasted a transcript, extract from that. Don't make them re-explain.
+- Offer to copy to clipboard when done.
+- If this is the first follow-up email and no CMO voice exists, mention it once: "Tip: paste 2-3 emails you've sent to clients and I'll learn your writing style for future emails."

coppermind_cmo-0.3.4/src/coppermind_cmo/commands/cmo-handoff.md

@@ -0,0 +1,57 @@
+# /cmo-handoff — Client Handoff Document
+
+Generate a comprehensive handoff document for a client engagement. This is the "deliverable mind" — when the engagement ends, the client gets this.
+
+## Steps
+
+1. Confirm the active client. If argument provided, switch to that client.
+2. Gather everything:
+   - `get_brand_voice` — full brand DNA
+   - `search_memory` — broad search for decisions, commitments, stakeholders, facts, campaign outcomes
+   - `get_campaign_history` — all campaign results
+   - `get_last_brief` — most recent meeting brief
+   - Company info from the mind's configuration
+3. Generate a structured handoff document:
+
+```
+CLIENT HANDOFF: [Client Name]
+Prepared by: [CMO name] | Date: [today]
+Engagement period: [first memory date] — [today]
+
+COMPANY OVERVIEW
+[From company_info: industry, location, services, key details]
+
+BRAND DNA
+Voice & Tone: [summary]
+Positioning: [tagline, positioning statement]
+Key Differentiators: [bulleted]
+Target Audience: [description]
+Content Themes: [bulleted]
+
+KEY STAKEHOLDERS
+[Name, title, role, communication style — for each]
+
+DECISION LOG
+[Chronological list of major decisions with dates and rationale]
+
+ACTIVE COMMITMENTS
+[Open action items with owners]
+
+CAMPAIGN HISTORY & RESULTS
+[Campaign summaries with outcomes]
+
+STRATEGIC CONTEXT
+[Key concerns, priorities, and unresolved questions]
+
+RECOMMENDATIONS FOR NEXT CMO
+[Based on patterns in the data — what to focus on, what to avoid, relationship dynamics]
+```
+
+4. Ask: "Want me to copy this to clipboard, or save it as a file?"
+
+## Rules
+- This is the crown jewel feature. Make it comprehensive and polished.
+- Write the "Recommendations" section as genuine strategic advice, not just a data dump.
+- Include dates on everything — decisions, campaigns, stakeholder additions.
+- The document should be useful to someone who has NEVER met this client.
+- Use the brand voice description but write the document in a professional, neutral tone — it's a handoff, not marketing copy.

coppermind_cmo-0.3.4/src/coppermind_cmo/commands/cmo-help.md

@@ -0,0 +1,53 @@
+# /cmo-help — Coppermind Help
+
+Provide help, troubleshooting, and how-to guidance for Coppermind CMO.
+
+## Steps
+
+1. Read `docs/product-knowledge.md` for the full knowledge base.
+2. Read `docs/QUICKSTART.md` if the user needs setup help.
+3. Answer the user's question conversationally from those sources.
+
+## If no specific question
+
+Show this quick reference:
+
+```
+COPPERMIND CMO — Quick Reference
+
+GETTING STARTED
+  "Set up [client name]"          Create a new client
+  "Switch to [client]"            Change active client
+  "List my clients"               Show all client minds
+
+MEETINGS
+  "Prep my meeting with [client]" Build a meeting brief
+  "Save the brief"                Persist for later retrieval
+  "Show my last brief"            Pull up saved brief
+
+MEMORY
+  "Remember: [anything]"          Store a structured memory
+  "Quick note: [anything]"        Fast capture, no classification
+  "What did we decide about X?"   Search decisions
+  "Who is [person]?"              Search stakeholders
+
+CONTENT
+  "Write a blog post for [client]"    Uses client's brand voice
+  "Draft a social post about X"       On-brand content
+  "Write a follow-up email"           Post-meeting email draft
+
+POWER FEATURES
+  /cmo-morning                    Daily briefing across all clients
+  /cmo-followup                   Draft post-meeting follow-up email
+  /cmo-handoff                    Generate client handoff document
+  /cmo-actions                    Overdue items across all clients
+  /cmo-batch                      Write content for multiple clients
+  /cmo-review                     Quarterly review for a client
+  /cmo-connect                    Pull data from Granola/Gmail/Slack
+```
+
+## Rules
+- Always check the knowledge base and quickstart before saying "I don't know."
+- For setup issues, walk them through step by step — don't just link to the doc.
+- Only suggest emailing coppermind@volacci.com for issues you genuinely cannot resolve.
+- Keep answers short and actionable. CMOs don't want tutorials.

coppermind_cmo-0.3.4/src/coppermind_cmo/commands/cmo-morning.md

@@ -0,0 +1,38 @@
+# /cmo-morning — Daily Briefing
+
+Build a morning briefing across all clients.
+
+## Steps
+
+1. Call `list_minds` to get all client minds.
+2. For each client with memories, switch to it and gather:
+   - Open commitments (action items not marked complete)
+   - Any memories from the last 48 hours
+   - Current sprint status and what's due (if sprint plan exists)
+3. If Google Calendar MCP is connected, check today's meetings and match attendees to client minds.
+4. Present a unified briefing:
+
+```
+GOOD MORNING — [Date]
+
+TODAY'S MEETINGS
+- 10:00 Acme Corp (Sarah Chen) — prep available, say "prep my meeting with Acme"
+- 2:30 5 Star Charleston (Stephen Graham) — no recent notes, consider catching up
+
+NEEDS ATTENTION
+- [Acme] 2 action items overdue from Sprint 3
+- [Bluebell] No interaction in 18 days — consider a check-in
+- [5 Star] Stephen waiting on van wrap designs (committed 3/10)
+
+THIS WEEK'S SPRINT DELIVERABLES
+- [Acme] Publish 4 SEO pages, launch outbound calling
+- [5 Star] Finalize hiring reqs, evaluate RP1 platform
+```
+
+5. End with: "Want me to prep any of these meetings?"
+
+## Rules
+- Process clients in parallel if possible.
+- Only show clients that have something to report — skip clients with no open items and no recent activity.
+- Keep it scannable. No paragraphs. Bullets and short lines only.
+- Don't show the raw switch_client responses. Just present the final briefing.

coppermind_cmo-0.3.4/src/coppermind_cmo/commands/cmo-review.md

@@ -0,0 +1,60 @@
+# /cmo-review — Quarterly Review
+
+Generate a quarterly review for a client.
+
+## Usage
+
+- `/cmo-review` — reviews current quarter for active client
+- `/cmo-review Q4 2025` — reviews a specific quarter
+- "How did Q1 go for Acme?" — triggers naturally
+
+## Steps
+
+1. Confirm the active client and quarter. Default to current quarter from cadence.
+2. Gather all memories from that quarter:
+   - Decisions made (with dates)
+   - Commitments — which were completed, which are still open
+   - Campaign outcomes and metrics
+   - Key facts and status changes
+   - Stakeholder changes (new hires, departures, role changes)
+3. If a sprint plan exists for that quarter, pull completion rates per initiative.
+4. Generate the review:
+
+```
+QUARTERLY REVIEW: [Client Name] — [Quarter Year]
+
+SUMMARY
+[2-3 sentence executive summary of the quarter]
+
+WINS
+- [Completed initiatives, successful campaigns, goals met]
+
+DECISIONS MADE
+- [Date] [Decision and rationale]
+- [Date] [Decision and rationale]
+
+CAMPAIGNS & RESULTS
+- [Campaign name]: [outcome, metrics if available]
+
+OPEN ITEMS CARRIED FORWARD
+- [Items not completed this quarter that carry into next]
+
+SPRINT PLAN SCORECARD (if applicable)
+- Initiative 1: 5/6 sprints complete ████████░░ 83%
+- Initiative 2: 3/6 sprints complete █████░░░░░ 50%
+- Initiative 3: CUT in Sprint 4
+
+TEAM CHANGES
+- [New hires, departures, role changes during the quarter]
+
+LOOKING AHEAD
+[Recommendations for next quarter based on what happened this quarter]
+```
+
+5. Ask: "Want me to copy this, or use it as input for next quarter's planning?"
+
+## Rules
+- Be honest. If results were poor, say so constructively. CMOs need accurate assessments, not cheerleading.
+- Include specific dates and numbers wherever available.
+- The "Looking Ahead" section should be genuine strategic recommendations, not generic advice.
+- If there's not enough data for a full review, say so: "I only have [N] memories from Q4. The review will be thin — want to feed me more context first?"

{coppermind_cmo-0.3.2 → coppermind_cmo-0.3.4}/src/coppermind_cmo/server.py

@@ -330,8 +330,9 @@ def _startup_checks():
     # Install statusline script if it doesn't exist
     _install_statusline()
 
-    # Install bundled skills
+    # Install bundled skills and commands
     _install_skills()
+    _install_commands()
 
     # Optional: auto-start session watcher
     _start_watcher()
@@ -370,6 +371,39 @@ def _install_skills():
         logger.warn(f"Failed to install skills: {e}")
 
 
+def _install_commands():
+    """Copy bundled /cmo command files to ~/.claude/commands/ if newer or missing."""
+    import hashlib
+    from pathlib import Path
+    from importlib import resources
+
+    commands_dir = Path.home() / ".claude" / "commands"
+    commands_dir.mkdir(parents=True, exist_ok=True)
+
+    try:
+        commands_package = resources.files("coppermind_cmo") / "commands"
+        if not commands_package.is_dir():
+            return
+
+        for cmd_file in commands_package.iterdir():
+            if not cmd_file.name.endswith(".md"):
+                continue
+
+            dest = commands_dir / cmd_file.name
+            source_content = cmd_file.read_text(encoding="utf-8")
+            source_hash = hashlib.md5(source_content.encode()).hexdigest()
+
+            if dest.exists():
+                dest_hash = hashlib.md5(dest.read_text(encoding="utf-8").encode()).hexdigest()
+                if source_hash == dest_hash:
+                    continue
+
+            dest.write_text(source_content, encoding="utf-8")
+            logger.info(f"Installed command: {cmd_file.name}")
+    except Exception as e:
+        logger.warn(f"Failed to install commands: {e}")
+
+
 def _install_statusline():
     """Copy statusline.sh to ~/.coppermind/ on first run (skipped on Windows)."""
     if sys.platform == "win32":

{coppermind_cmo-0.3.2 → coppermind_cmo-0.3.4}/src/coppermind_cmo/tools/minds.py

@@ -141,6 +141,12 @@ def _switch_client(
     has_customer = _has_customer_id_col(db)
 
     # --- LOOKUP: filter by customer_id when available ---
+    # Default-deny: if isolation column exists but customer_id is missing, refuse lookup.
+    if has_customer and not customer_id:
+        return tool_error("PROVISIONING_ERROR",
+                          "Your account could not be identified. "
+                          "This usually means your API key is misconfigured. "
+                          "Contact coppermind@volacci.com for help.")
     has_access = _has_access_table(db)
     if customer_id and has_customer:
         # Only show minds this customer owns or has access to
@@ -322,8 +328,13 @@ def _list_minds(limit: int, offset: int, db: Database, include_internal: bool =
     where_clauses = []
     params: list = []
 
-    # Customer isolation: only show minds this customer owns or has access to
-    if customer_id and _has_customer_id_col(db):
+    # Customer isolation: only show minds this customer owns or has access to.
+    # Default-deny: if the isolation column exists but customer_id is missing,
+    # return nothing rather than leaking all customers' data.
+    if _has_customer_id_col(db):
+        if not customer_id:
+            logger.warn("Isolation column present but no customer_id — returning empty list")
+            return []
         if _has_access_table(db):
             where_clauses.append(
                 "(cm.customer_id = %s OR EXISTS ("

{coppermind_cmo-0.3.2 → coppermind_cmo-0.3.4/src/coppermind_cmo.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: coppermind-cmo
-Version: 0.3.2
+Version: 0.3.4
 Summary: AI-powered memory for fractional CMOs — never forget a client detail, never leak data between clients
 Author-email: Ben Finklea <ben@volacci.com>
 License-Expression: LicenseRef-Proprietary

{coppermind_cmo-0.3.2 → coppermind_cmo-0.3.4}/src/coppermind_cmo.egg-info/SOURCES.txt

@@ -27,6 +27,14 @@ src/coppermind_cmo.egg-info/dependency_links.txt
 src/coppermind_cmo.egg-info/entry_points.txt
 src/coppermind_cmo.egg-info/requires.txt
 src/coppermind_cmo.egg-info/top_level.txt
+src/coppermind_cmo/commands/cmo-actions.md
+src/coppermind_cmo/commands/cmo-batch.md
+src/coppermind_cmo/commands/cmo-connect.md
+src/coppermind_cmo/commands/cmo-followup.md
+src/coppermind_cmo/commands/cmo-handoff.md
+src/coppermind_cmo/commands/cmo-help.md
+src/coppermind_cmo/commands/cmo-morning.md
+src/coppermind_cmo/commands/cmo-review.md
 src/coppermind_cmo/skills/cmo-onboard-client.md
 src/coppermind_cmo/tools/__init__.py
 src/coppermind_cmo/tools/brand.py