CE Doc Review � Marketing ops fractional CMO CE plan (iteration 2)

Date: 2026-05-06
Status: current
Mode: ce-doc-review style assessment
Reviewed doc: docs/plans/2026-05-06-marketing-ops-fractional-cmo-ce-plan.md
Delta from iteration 1: Jadyn writer+coordinator; Lisa 2�3�/week + top-down; Linear marketing sprints; luke-gpt renamed cmo-gpt + Lisa customization; calendar snapshot refresh workflow.


Executed (same day � CE doc review follow-through)

RecommendationWhat shipped
1. Migrate luke memories to lisaSupabase migration 017_migrate_luke_to_lisa.sql updates user_id and knowledge_repo.author from luke ? lisa on all scoped tables. Runbook: knowledge/sales/second-brain/docs/migrate-luke-to-lisa.md. Mem0 cloud still requires operator choice (merge vs re-ingest) � documented in runbook.
2. Every Notion calendar row ? Linear issue URLnotion-properties-reference.md, content-calendar-mapping.md, vault content-calendar.md � required Linear issue field + sync steps.
3. Robert OOO ? Lisa approveslinkedin-pre-publish-checklist.md (approval routing table), linkedin-checklist-quick-reference.md, incidents/README.md.

Reviewed statement

Marketing operates with Lisa as fractional CMO (themes + approvals), Jadyn as writer/coordinator (Notion + vault + Linear sprint hygiene), Hannah and Mickey on design and multimedia, AI drafts with mandatory human QC, partnership flows gated on Slack, and cmo-gpt as the CMO LinkedIn/voice bundle � with Linear as the execution backbone again.

Findings by severity

Critical

  1. Notion remains authoritative for Topic/Status � The vault content-calendar.md uses placeholders and reconcile steps; if Jadyn skips weekly paste-in, drift returns.

High

  1. Second Brain � Postgres vs Mem0 � Migration 017 fixes Supabase. Mem0 Cloud may still hold memories under user_id=luke until you merge or re-ingest per runbook.

  2. cmo-gpt memory still contains legacy examples � Lisa should curate /learn additions over time.

Medium

  1. Campaign brief intake � README already lists CMO GPT; extend CAMPAIGN_BRIEF_INTAKE / templates to mention CMO GPT when relevant (optional follow-up).

  2. QC routing � One-page sensitivity ladder still optional.

Low

  1. Linear labels � Optional convention (content, campaign, partner) on Marketing issues.
  1. Optional: golden eval / golden posts for marketing tone regression.
  2. Extend campaign intake MD files to mirror README’s third GPT option everywhere.

Recommendation

Proceed-with-gates � Supabase migration + Linear URL rule + OOO routing remove three major operational gaps.

Top open questions (updated)

  1. Migrate luke ? lisa Done for Postgres; Mem0 path TBD per runbook.
  2. Linear link per row Documented as required; Jadyn enforces in Notion.
  3. Partner co-marketing when Robert OOO � Lisa default; involve Hannah if creative-heavy (informal).

Final position

Execute 017 on the deployed Second Brain database during your next maintenance window, then confirm counts for user_id = 'lisa'. Keep weekly Notion ? vault paste as the anti-drift habit.

Lisa handoff: use docs/plans/2026-05-06-marketing-ops-fractional-cmo-ce-plan.md section Handoff to Lisa (start here).