AD SEO Agent plan
internal prototype · canonical JSON + Dreamborn Forge HTML
internal generated
plan · supabase_json

AD SEO Agent plan

plan artifact · for AD SEO Agent · status approved

Planning Surface

Use this to decide what happens next.

Status

approved

open questions
idownerblocksstatusquestion
OQ-PLAN-001justin- M-01.T2 data quality onlydeferredWhich exact competitor domains should be used in final Hubbard seed data?
OQ-PLAN-002atlas- M-08.T1 release acceptance onlydeferredShould /products/seo alias be configured in parent bezeliq.ai Cloudflare routing before Monday demo?
Agent Handoff
Start Here

plan artifact · for AD SEO Agent · status approved

Completion Evidence

No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.

Open Questions
  • OQ-PLAN-001: id: string, owner: string, blocks: object, status: string, question: string
  • OQ-PLAN-002: id: string, owner: string, blocks: object, status: string, question: string
Structured Payload

Machine-readable source fields

git
repo url

https://github.com/justinb2bea/seo-studio.git

pr policy

optional

merge policy

manual

branch prefix

feature/ad-seo-agent-

commit policy

optional

worktree root

/opt/redk3y/apps/seo-studio

execution mode

redkey_worker_git_dispatch

default base branch

main

worker dispatch allowed

true

clean workspace required

false

worker dispatch preconditions
  • Use repo_url https://github.com/justinb2bea/seo-studio.git.
  • Use worktree_root /opt/redk3y/apps/seo-studio on worker hosts.
  • Workers must commit or clearly summarize diffs for review; merge remains manual/review-gated.
  • Justin must approve each new module scope in EXEC_PLAN_REVIEW before dispatch.
gates
idnametypedepends onreturn pathblocks dispatch
GATE-000PLAN Approval Gateexec- PLAN.jsontask_planningtrue
GATE-001Data Contract Gateautomated- M-01.T2requirementstrue
GATE-002Approval Demo-Local Gatereviewer- M-04.T1decompositiontrue
GATE-003Route Composition Gatereviewer- M-07.T1task_planningtrue
GATE-004Monday Production Demo Gateexec- M-08.T1decompositiontrue
modules
idgoalnameriskstasksstatus
M-00Use the completed M-00 audit as source for PLAN ownership and constraints.Host Confirmation and Prototype Audit- RISK-M00-001: Agents may treat prototype code as approved implementation.- Apply M-00 Audit to PLAN: git: object, role: string, brief: string, title: string, output: object, dispatch: object, local_id: string, acceptance: object, agent_hint: string, depends_on: object, hard_stops: object, files_owned: objectcomplete
M-01Create complete bundled Hubbard seed data and object contracts.AI Object Model and Hubbard Seed Dataset- RISK-M01-001: Weak seed data makes the product feel fake.- Refactor Data Contract: git: object, role: string, brief: string, title: string, output: object, dispatch: object, local_id: string, acceptance: object, agent_hint: string, depends_on: object, hard_stops: object, files_owned: object - Expand Hubbard Seed Fixture: git: object, role: string, brief: string, title: string, output: object, dispatch: object, local_id: string, acceptance: object, agent_hint: string, depends_on: object, hard_stops: object, files_owned: objectcomplete
M-02Rename and shape client route shell for AD SEO Agent at /seo.Product Route and Blanc Shell- RISK-M02-001: Shell may inherit internal Studio assumptions.- Refactor Route Shell and Metadata: git: object, role: string, brief: string, title: string, output: object, dispatch: object, local_id: string, acceptance: object, agent_hint: string, depends_on: object, hard_stops: object, files_owned: objectcomplete
M-03Implement impact, opportunities, evidence, constraints, and agent activity.Command Center and Opportunity Experience- RISK-M03-001: UI may regress to conventional SEO dashboard.- Build Core Recommendation Surfaces: git: object, role: string, brief: string, title: string, output: object, dispatch: object, local_id: string, acceptance: object, agent_hint: string, depends_on: object, hard_stops: object, files_owned: objectcomplete
M-04Implement ApprovalGate and sessionStorage-backed demo-local decisions.Governance and Demo-Local Approval- RISK-M04-001: Approval UI could imply real publishing.- Build Demo-Local ApprovalGate: git: object, role: string, brief: string, title: string, output: object, dispatch: object, local_id: string, acceptance: object, agent_hint: string, depends_on: object, hard_stops: object, files_owned: objectcomplete
M-05Show seeded source mode, provider fallback, dataset version, and production-readiness status.System/Data Status- RISK-M05-001: Seeded data may feel fake if status is hidden.- Build SystemDataStatus: git: object, role: string, brief: string, title: string, output: object, dispatch: object, local_id: string, acceptance: object, agent_hint: string, depends_on: object, hard_stops: object, files_owned: objectcomplete
M-06Add optional member-network white-label proof without admin overbuild.White-Label Story- RISK-M06-001: White-label could read like marketing filler.- Build Optional WhiteLabelPreview: git: object, role: string, brief: string, title: string, output: object, dispatch: object, local_id: string, acceptance: object, agent_hint: string, depends_on: object, hard_stops: object, files_owned: objectdraft
M-07Serialize final app/page.tsx composition after child components complete.Route Composition Integration- RISK-M07-001: Parallel component work may not integrate cleanly.- Compose Final Product Route: git: object, role: string, brief: string, title: string, output: object, dispatch: object, local_id: string, acceptance: object, agent_hint: string, depends_on: object, hard_stops: object, files_owned: objectcomplete
M-08Verify local and Cloudflare readiness for Monday pilot.Production QA and Monday Demo Gate- RISK-M08-001: Local success may fail Cloudflare routing/deploy.- Run Production Verification: git: object, role: string, brief: string, title: string, output: object, dispatch: object, local_id: string, acceptance: object, agent_hint: string, depends_on: object, hard_stops: object, files_owned: objectcomplete
project
id

ad-seo-agent

name

AD SEO Agent for Affiliated Distributor Networks

status

draft

deadline

2026-05-04

client id

ad

source artifacts
decomp

docs/projects/ad-seo-agent/artifacts/DECOMP.json

intent

docs/projects/ad-seo-agent/artifacts/INTENT.json

policy

No value captured.

ux spec

docs/projects/ad-seo-agent/artifacts/UX_SPEC.json

research

No value captured.

m00 audit

docs/projects/ad-seo-agent/artifacts/M00_AUDIT.json

architecture

docs/projects/ad-seo-agent/artifacts/ARCHITECTURE.json

requirements

docs/projects/ad-seo-agent/artifacts/REQUIREMENTS.json

intake triage

docs/projects/ad-seo-agent/artifacts/INTAKE_TRIAGE.json

coherence review

docs/projects/ad-seo-agent/artifacts/COHERENCE_REVIEW.json

dev studio
views
  • summary
  • module_board
  • dependency_graph
  • task_table
  • context_packets
  • gates
  • risks
  • open_questions
  • completion_contracts
render as

project_plan

open questions
idownerblocksstatusquestion
OQ-PLAN-001justin- M-01.T2 data quality onlydeferredWhich exact competitor domains should be used in final Hubbard seed data?
OQ-PLAN-002atlas- M-08.T1 release acceptance onlydeferredShould /products/seo alias be configured in parent bezeliq.ai Cloudflare routing before Monday demo?
schema version

1.0

dependency graph
root tasks
  • M-00.T1
critical path
  • M-00.T1
  • M-01.T1
  • M-01.T2
  • M-03.T1
  • M-07.T1
  • M-08.T1
terminal tasks
  • M-08.T1
parallel groups
idreasontask refsfile conflict checked
PG-001Data contract and shell can proceed independently after M-00; allowed paths do not overlap.- M-01.T1 - M-02.T1true
PG-002Child modules avoid app/page.tsx, app/styles.css, and overlapping data fixture files. M-07 owns final shared route composition and stylesheet integration.- M-03.T1 - M-04.T1 - M-05.T1 - M-06.T1true
planning summary
goal

Ship a production-ready AD SEO Agent pilot for Hubbard Supply Co. at https://bezeliq.ai/seo.

must show
  • Hubbard Supply Co. and hubbardsupply.com are visible immediately.
  • ROI appears before SEO/ranking details.
  • At least 10 Hubbard-specific governed recommendations render from bundled seed data.
  • Evidence, action, risk, confidence, owner agent, and governance tier are visible per recommendation.
  • Agent activity is visible as an operating surface.
  • ApprovalGate uses demo-local state only.
  • System/Data status clearly labels seeded data and provider fallback.
  • Desktop and mobile QA show no incoherent overlap.
out of scope
  • Live SEO provider integration for Monday.
  • Autonomous publishing.
  • Full white-label tenant admin.
  • Approval persistence unless Justin explicitly reopens architecture.
  • Using bezeliq-studio, Dev Studio, or internal Studio as product host.
global hard stops
  • Build dispatch before Justin approves PLAN.json.
  • Implementation in bezeliq-studio or Dev Studio.
  • Treating components/seo-studio.tsx as approved architecture.
  • Adding live provider dependency to Monday render.
  • Adding approval network persistence without returning to architecture.
global constraints
  • Artifacts override current seo-studio prototype code.
  • Use C:/Users/jstnk/Downloads/cc/projects/seo-studio as canonical repo.
  • Worker execution source is https://github.com/justinb2bea/seo-studio.git.
  • Dev-agent worktree root is /opt/redk3y/apps/seo-studio; local Windows checkout remains a mirror/reference only.
  • Use committed app/vendor/blanc snapshot for Monday Cloudflare Pages.
  • Upstream Blanc source remains C:/Users/jstnk/Downloads/cc/projects/blanc.
  • Do not use blanc: file:../blanc as Cloudflare production evidence.
  • Monday runtime uses bundled static Hubbard fixture.
  • No provider keys or RedKey credentials in browser bundle.