Goals and the build engine

How a project's goals are planned and carried out by an orchestrator and specialist agents — blueprints, plans, steps, tasks, and the guard against fabricated work.

A project can build itself. You describe the outcome; agents plan and do the work through the platform's own features.

Goals

/goals — a goal is one outcome in plain words ("a landing page with an opt-in that starts a 5-email nurture"). Goals in a project run in order: the first is planned and executed, the rest wait their turn.

How a goal is carried out

1. The project's orchestrator agent reads the goal and submits a plan: a list of steps, each assigned to a specialist agent. During planning it can only plan — it may look things up and create or delegate to specialists, but it cannot build, so the plan is a plan.
2. Each step becomes a task for its specialist.
3. The specialist works the task with its tools — creating pages, products, flows, courses, images — and reports back.
4. The step is assessed; when every step is settled the goal completes and the next one starts.

You watch it happen on the project's Engine tab and can pause, resume or stop at any time.

Blueprints

A blueprint is a ready-made roster plus goal list for a common business shape: landing page, marketing campaign, digital product, webstore, service business, content blog, membership community, full business. Choose one when creating a project or ask an agent to apply one. The roster is created existing-first: an agent of the same name is reused rather than duplicated.

Fabrication guard

An agent can only mark a task done if it actually called a tool that produced something. A task closed on a narrative alone ("I have built the course") is reopened as blocked and the agent is told plainly to build it or report the block. So a green Done means a real deliverable exists.

Budgets

Give the project a credit budget and everything its agents spend comes from there. See Projects.