UI · the operational spine
Task spine — the gap, as work
Every plan, audit and suggestion lands here as a task. This is how a website finally has a workflow: on-site and off-site work in one backlog, each owned by you or Claude, each traceable to a goal. Claude reads and advances these over MCP.
all · 22
on-site · 9
off-site · 13
◍ owned by Claude · 8
goal: AEO for agencies
✦ auto-generated from the gap
Backlog7
Write "AEO for agencies" pillar page
on-siteCranking
Add JSON-LD to 4 service pages
on-siteC
Guest post pitch — 3 finance blogs
off-siteYoubacklink
Claim + optimize LinkedIn company page
off-siteYou
In progress3
Fix 6 orphan pages — internal links
on-siteC
Draft 3 Medium articles on brand memory
off-siteCcitation
Reply to 4 Quora questions on NRI tax
off-siteYou
Review gate2
Publish "AEO for agencies" page
on-siteCapprove?
Send backlink pitch to fintechweekly
off-siteCapprove?
Done10
Publish "NRE vs NRO 2026" guide
on-siteCEO 86
Connect Search Console
setupYou
Reconcile entity graph
on-siteC
Inside a task
Write "AEO for agencies" pillar pageranking goal
- Type
- on-site · authority
- Owner
- C Claude (via MCP)
- Why
- Entity has 0 coverage & high intent — from the gap
- Goal
- Rank top-5 for "AEO for agencies"
- Checklist
- brief → write → SEO+EO → publish gate
Why a spine, not a checklist
A checklist is static. The spine is alive: the brain regenerates and re-prioritises tasks as the gap changes, Claude can pick up any task and act, and every task is tied to a goal and a measurable outcome. It's the difference between a to-do list and a workflow that runs itself — with you approving the moves that matter.