01
What it does
Module overview
A project groups the surfaces of one product: the landing site, the app, the API, and the infrastructure behind it.
Who this guide is for
Owners organizing more than one site or product under one account.
02
Why it matters
Why this module is important
- Group related surfaces under one project and switch between projects in the conversation.
- Know which surface types exist: landing, app, api, and infra.
- Understand that the landing surface is where reports and audits run today.
03
How to use it
Recommended workflow
- 01
Ask the agent to create a project when a new product needs its own space.
- 02
Wire a landing surface with its URL to start the crawl and the report.
- 03
Wire app, api, or infra surfaces to register them and connect the repository behind them.
- 04
Ask for a specific project or surface by name whenever you want to switch.
04
Permission and safety notes
Important boundaries
Only the landing surface is crawled and audited today. The other surfaces are arriving module by module.
A surface belongs to exactly one project.
Repository connections are counted per account plan.