Planning lane
activeTurns a loose brief into a page map, target keywords, and content constraints before any file writes happen.
Managed Astro generation
Build the first Astro draft from one brief, then inspect the file tree before it ships.
Draftlane is the operator surface for the platform you described: Anthropic-managed agents plan the site, write the Astro app, run QA, and prepare the Cloudflare deployment handoff. This slice now includes the protected workspace, billing layer, and deploy-ready hosting path.
Current scope
Platform shell
Landing, pricing, dashboard, shared layout, security headers, billing actions, and the first interactive studio preview.
Hosting target
Cloudflare
The app now targets Cloudflare Workers for SSR hosting so the authenticated workspace and billing flow can stay intact at the edge.
Agent workspacemanaged run
Nothing is running yet.
Start a prompt to watch the planner, builder, and QA passes fill the project graph.
How the platform runs
Three lanes, one review surface.
The planner, builder, and QA lanes share the same project graph. That keeps prompts, generated files, and deploy status tied to one record instead of scattering state across tools.
Build lane
activeWrites Astro pages, React islands, layouts, and deployment config from one prompt and one project graph.
QA lane
activeChecks SEO, hydration directives, route wiring, and deployment readiness before the deploy button lights up.
Implementation notes
Monorepo root
01pnpm workspace and Turbo tasks are wired.
Platform shell
02Landing page, pricing page, dashboard shell, and shared layout are live.
Live backend slice
03Convex auth, persisted generations, and Stripe-backed plan access are wired.
What ships later
Clerk protects the workspace and synchronizes user records into Convex.
Convex actions hold generation sessions, file snapshots, billing state, and deployment records.
The next layer is automated site export and deployment orchestration on top of the Cloudflare-ready app shell.