Getting started

Create a product surface with governed AI behavior

Website Builder documentation describes how Taskcenter should guide users from a prompt to a real app surface with files, previews, and deployable output.

Scope

A website build should start execution with sensible defaults for non-blocking choices such as fictional brand name, palette, sections, and copy. North Star should ask clarifying questions only when missing details are blocking, credentialed, destructive, compliance-sensitive, or likely to cause unexpected paid work.

Handoff

The output should be a real work product, not a screenshot or pasted source. Website/app requests are not complete until runSandboxOperation successfully records real sandbox file/build/preview execution and createWorkProduct records the durable preview or deliverable. Deck, slide, and PDF requests are not complete until createDeckArtifact records the deck manifest, the chat result opens a full-screen deck/document showcase as the primary result, and exportDeckArtifact records PDF/PPTX/HTML output when requested. Current/latest/ranked/comparison deck or PDF requests must run live source grounding and Kimi queue-side synthesis before they can be marked ready; they must not use the user's request as the deck title, paste search snippets as slide copy, or recover into a deterministic source-backed scaffold. The right workspace sidebar is for activity, files, sources, runs, and evidence rather than primary deck/PDF viewing. If Kimi synthesis, the live sandbox, artifact, export, R2, D1, or provider route is unavailable, North Star must return a runtime_unavailable blocker instead of marking the task done. Users should be able to inspect files, preview the site or deck, download exports, and see what still needs credentials or deployment setup.