Skip to main content
A project is a focused piece of work with one objective: build a landing page, run market research, design a brand, prepare a report. It’s the workshop where things get made. Each project keeps its own thread, plan, and activity — so you can always see how a result came to be, and hand it off to a teammate without losing context.
Scope each project to one objective. Start a new project when you switch context, so each thread stays focused and easy to find later.

​
The lifecycle: define → execute → review

1

Define

You describe what you need. aidax asks the right questions until the goal is clear, and you declare what the project will produce (a site? a report? a brand kit?).
2

Execute

Your team and AI agents do the work. Reversible steps (research, drafts) run on their own; anything irreversible waits for your approval.
3

Review

You review the result. The project produces real Apps & Assets, and its learnings are distilled into Memory.

​
A project is the workshop, not the warehouse

The important distinction in aidax: the project is where work happens; it is not where the result lives.
  • Work (chat, tasks, activity) is ephemeral — it belongs to the project.
  • Results (Apps, Assets) and learnings (Memory) are durable — they live at the workspace level and get reused everywhere.
This is why archiving a project is safe.

​
Archiving keeps the results

Archiving a project tidies up the work, it doesn’t kill the result. The project leaves your active views; its Apps and Assets stay in your workspace, and a live App keeps running. Nothing you produced disappears.

​
Execution is your project’s memory

You don’t keep a separate log of what happened — the activity, task descriptions, and who-did-what already are the project’s execution memory. It answers the how. When the project closes, the durable lessons get promoted up into your workspace Memory.

​
Next

Agents

Who does the work inside a project.

Apps & Assets

What a project produces.