Campaign → Landing Page Strategy

Loading…

Campaigns by Intent Lane

Campaigns grouped by search intent. Each lane header shows total campaigns, markets covered, dominant page type strategy, and active A/B tests.

Quiz Workstream

Deep dive on quiz rebuild. 4-phase roadmap · 12-variant matrix (3 variants × 4 markets) · current build progress.

Collection / Shopify Port Workstream

Shopify port plan for GABA, Dopamine and future lanes. Build options ranked by speed. Priority build queue v2.

Decisions Log

Full audit trail of all layered decisions — original recommendation greyed, updated recommendation highlighted. Chronological, newest first.

⚠ Awaiting sign-off · Created 2026-05-09

Campaign Planner v2 — Phase B Preconditions

Phase A audited the current Campaign Planner + Creative Production Tracker spine and found it's GAQL-primary (built off live Google Ads inventory) when it should be architecture+briefs-primary (built off your Phase 0/1 strategic outputs). Two independent Opus passes + cross-reviews from Codex 5.5 and Gemini all agree on the spine flip. Before any code is written or any sheet is touched, I need 5 decisions from you.

The 5 decisions

DECISION 1

Override file approval — most important

8 of 19 briefs match cleanly to architecture rows by automated heuristic. 11 of 19 need manual mappings. With the 3 flat briefs added (P3 finding), the override file totals 17–18 entries. I'll generate config/brief-slug-overrides.json with proposed mappings + per-row confidence + rationale, render it as a second sign-off item on this dashboard, and only write to the new sheet once you've signed off.

Decision: OK to proceed with the human-review-before-write pattern? (default: yes)

DECISION 2

Source-of-truth for arch files

Two collisions exist:

  • Within Agentic-OS: config/campaign-architecture.json has 19 PMax campaigns; tools/pmax_data.json has 24. 5-row delta.
  • Across repos: Older copies still exist at F:/Claude Root/v4.0/... and F:/Claude Root/tools/.... They've drifted from Agentic-OS copies (May 3 vs May 6, DG file is from 2026-04-12 — almost a month stale).

Decision 2A: Make config/campaign-architecture.json the canonical Phase 2 declaration; tools/pmax_data.json the Phase 5 state. Reconcile the 5-row delta.

Decision 2B: Retire the Claude Root drift copies — replace with stub redirects, then grep consumers and delete. (You've already said yes — confirming for the record.)

DECISION 3

Three brief-side architecture gaps

Architecture rows that have no matching strategic brief:

  • DE Gut-Hirn (campaign exists, no Phase 0 strategy doc)
  • FR Students (DG ad-group, no brief)
  • US Workers (DG ad-group, no brief)

Decision: Are these intentional (no brief needed) or backlog work (briefs to be written)? Either way they get strategic_debt: true; the question is whether they get a "Brief Needed" flag in the planner. (default: backlog with flag)

DECISION 4

The active SERP UK ADHD campaign

cid=11666978147 SERP UK ADHD is currently ENABLED but has no v4.0 architecture entry. It's the live campaign tied to the ADHD article LP.

  • Path A: Add it to arch.search_campaigns[] with brief_slug=uk-adhd-... as part of Phase B init — clean, slightly retroactive.
  • Path B: Let it show up as ORPHAN red-flag in the v2 planner so you can triage on first review — slower, but visible.

(default: A — quick fix, keeps the planner clean from day one)

DECISION 5

Sheet design — minimum viable tabs

Both Opus passes proposed 11 tabs. Two reviewers flagged this as overwhelming. Trimmed to 5 minimum-viable:

  • Master (every v4.0 campaign + ORPHAN red-flags)
  • Search Detail (per ad-group)
  • PMax Detail (per asset-group)
  • DG Detail (per ad-group)
  • Orphans (live drift triage)

Phase C (post-Phase B) adds Briefs / Legacy / Brand-Defence / Drift / Removed / Strategic-Debt tabs if you want them. (default: ship 5 tabs first)

What happens after sign-off

  1. I clear the 9 codebase preconditions (P1–P9 — paths, schema, snapshot tooling, JSON sanitization, etc.). 4 already done — P3, P4, P5, P8 came back from background agents.
  2. I generate the override file (decision 1) and bring it back as a second sign-off item on this tab.
  3. Once override file approved, I build tools/assemble_v4_spine.py.
  4. v2 planner + v2 tracker sheets get built to fresh sheet IDs (parallel deployment, not in-place).
  5. You review v2 sheets before cutover. v1 stays read-only for audit.

What I won't do without sign-off

How to sign off

Reply in the chat with approved (or approved with changes — change X to Y). The session running this work will pick it up and proceed. The override-file table will then appear as a second item on this tab for per-mapping review.

Source artifacts:
  • Six-pass synthesis: projects/briefs/campaign-planner-v2/.planning/phase-a/PHASE-A-SYNTHESIS.md
  • Phase A passes: .planning/phase-a/pass-1-opus-A/ + .planning/phase-a/pass-2-opus-B/
  • Roadmap: .planning/ROADMAP.md · State: .planning/STATE.md
  • First snapshot: data/phase_a_snapshots/2026-05-09-1256.json

Deployed Pages Registry

Every Shopify page/article/collection deployed across UK/US/DE/FR. Live status from Shopify Admin API; QC results from automated sweep. Updated —. Schema v—.

Shelf Pricing — 4-Market Review

Verified 2026-05-02. Review base price, subscribe price, variant IDs and discount codes before rollout. Use the dropdowns and notes to flag any corrections, then export as JSON for implementation.

Feedback status:
0 Correct
0 Needs Update
0 Check This
16 Not reviewed