Getting started

Create a product surface with governed AI behavior

Overview

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. For a deck, North Star writes source in the thread workspace, renders and audits the slides, and uses taskcenter deck export deck to persist the deck plus PDF/PPTX artifact and work-product records. A render alone is not delivery. Current, ranked, or comparative claims need live source evidence before slide authoring; do not treat the user's request or search snippets as verified slide copy. The authenticated Slides canvas opens the persisted source, while the workspace sidebar shows activity, files, sources, runs, and evidence. If the workspace, R2, D1, Browser Run, or export route is unavailable, report the specific blocker without claiming a deck was delivered. Users should be able to inspect files, preview the site or deck, and download only attested exports.