Skip to main content
Projects don’t end in a checklist. They end in something real you can use. In aidax, those results come in two shapes: Apps and Assets. The simple rule:
Memory is what you know. Apps & Assets are what you produce.

Apps

An App is anything you open and use as an experience: a landing page, a website, a brand book, a dashboard.
  • Built out of your Assets and your brand.
  • Has a rich lifecycle: Draft → Live → Retired.
  • A live App keeps running even after its project is archived (archiving is not taking it down — that’s a separate, deliberate action).

Iterate on any App

Every App has an Iterate button that spins up a session to evolve it — so improving a result isn’t chained to the project that first created it.

Assets

An Asset is a file or material you reuse to build things: logos, images, fonts, color tokens, documents, PDFs.
  • Consumed as ingredients when agents build Apps.
  • Simple lifecycle (versions).
  • They just live in your workspace and any project — or an agent — can pick them up. No wiring, no toggles.

The boundary rule

Not sure whether something is an App or an Asset?
  • Open it in the browser as an experience → App (e.g. a brand book).
  • A file or ingredient → Asset (e.g. a logo, an image).
So a brand kit is naturally both: the logos and color tokens are Assets (the reusable parts) and the brand book is an App (the part you view).

Everything lives at the workspace level

Apps and Assets are not trapped inside the project that made them. They live in your workspace library, tagged with the project they came from, with their own lifecycle. That’s what makes reuse effortless — your brand tokens feed the next landing page automatically.

Next

Agents

Who builds your Apps and Assets.

Memory

What the business keeps from producing them.