Add a project

Adding a project — brand new, or a codebase you’ve worked on for years — is one command, run from inside an agent session:

/lumis:onboard

The interview

The agent asks you a short set of questions: what the project is called, where its repository lives, what stage it’s at, and what “done” looks like for it. Nothing is touched while you answer — this is a conversation, not a script.

An existing live product? It gets audited first

If you’re bringing in a codebase that’s already running in production, Lumis doesn’t touch a single file until it understands what’s there. It maps the repository into an audit ticket first, and a person reviews and approves that plan before anything else happens. Onboarding is never allowed to break a product that’s already live.

A brand-new, empty project skips the audit — there’s nothing yet to map.

What you end up with

Onboarding is deliberately light on your side. Your repository gets one small pointer file — a few lines telling any agent opened there where the platform lives and how to behave — and nothing else. No config files, no copied rules, no keys. Everything else — the rules, the model choices, the list of every project — lives in the platform, in exactly one place, so a tenth project costs the same to run as a second.

Behind that pointer, onboarding also:

• registers the project in the platform’s control plane, so every command can find it
• gives the project its own space in the database for tickets, decisions, and history, starting from day one
• gives it a short ticket prefix, so its tickets are identifiable at a glance (<PREFIX>-1, <PREFIX>-2, …)
• writes a first event to its history — the project’s record starts governed, not patched in after the fact

Working in a project

From inside the project’s own repository, the same commands work everywhere, because they resolve where you are automatically:

/lumis:status          # where does this project stand?
/lumis:plan <topic>    # turn an idea into a spec and tickets
/lumis:next            # run the next ready ticket
/lumis:bug             # report a defect properly

Any agent CLI opened in the repository reads the pointer file and follows the same rules — one process, whichever agent you’re using. The full command set is in The CLI.

Pausing or removing a project

Nothing is ever deleted outright. Pausing or archiving a project is a status change, not a teardown — its history stays exactly where it was, and every surface that reads project status picks up the change automatically.