Watch This Capital

Affiliate portfolio control plane

One frontend for portfolio visibility, site layout, and the next phase of agent-driven site creation.

Active sites3
Portfolio repowtc-affiliate-portfolio
VPS clone path/home/parryh/wtc-affiliate-portfolio

Portfolio sites

Each site stays independently deployable while living in one repo.

AI voice tools affiliate editorial

AIVoiceReview

active
Domain
aivoicereview.com
App path
sites/aivoicereview/web
Scheduler
aivoicereview-scheduler
Vercel
aivoicereview

pending-definition

Partners

active
Domain
partners.vercel.app
App path
sites/partners/web
Scheduler
partners-scheduler
Vercel
partners

UK tax and accounting affiliate editorial

SoleTraderGuide

active
Domain
soletraderguide.co.uk
App path
sites/soletraderguide/web
Scheduler
stg-scheduler
Vercel
soletraderguidev2

Repo layout

  • `apps/control-panel` hosts the shared frontend.
  • `sites/<slug>/web` contains the deployable app.
  • `sites/<slug>/scheduler` contains VPS automation.

Scheduler model

  • Schedulers clone this portfolio repo on demand.
  • Each scheduler enters the site web folder before running Claude.
  • Each site retains its own service name, port, and API path.

New site workflow

  1. Create a site request and scaffold the new site folder.
  2. Define the agent workflow and skills for content, deployment, and scheduler setup.
  3. Create or link the Vercel project for the new site.
  4. Wire the VPS scheduler service, cron, and status endpoints.

The scaffold exists now. The agent workflow and repo skills still need to be defined before full automation is enabled.

API stubs

Provisioning is intentionally explicit until the workflow is defined.

GET /api/sitesRead portfolio site manifests
POST /api/provision-siteReturns 501 until the agent workflow is finalized
Inspect live manifest output