Solutions
All solutions of your tenant. The active solution decides which records you see everywhere in the app and which records AI agents receive.
For: Project lead, Admin
What you can do here
| Action | What it does | Who |
|---|---|---|
| Open solution | Makes it the active solution for the whole app. | Everyone |
| Continue setup | Resumes the guided setup where you left it. | Owner, admin, member |
| New solution | Starts the guided setup for a new solution. | Owner, admin, member |
| Archive | Hides the solution from the workspace and from AI agents; records are kept. | Owner, admin |
| Restore | Brings an archived solution back and makes it active. | Owner, admin |
Keep in mind
- Archiving is reversible. It does not delete records, tokens or history.
- While a solution is archived its API token and connected apps stop working.
- You can also switch solutions from the Solution selector in the context row below the top bar.
Starting a solution from your agent
You do not have to start here. When you connect claude.ai, ChatGPT, Claude Code or Cursor, the sign-in screen offers + New solution; tick It already has code for an existing codebase. In a conversation you can also say "let's start a new solution": the agent confirms the name and creates it for you (create_project), and an OAuth connection moves to the new solution.
- A new idea starts with the kickoff interview: the agent asks you, section by section, what the solution must achieve and within which limits, and saves what you confirm as Drafts (
/corpole:start). They belong to the solution's charter initiative, which CorPole opens with its demand. - In a solution under guided start the interview is the preparation stage.
/corpole:startfirst completes what the solution starts from — who asked for it and why (the demand), the solution brief, the solution type (one of four, which the agent puts to you as a question with their consequences) and the mode (a new solution runs as a project) — and then goes through the eleven Spec perspectives one at a time, in the order the preparation summary gives. There is no minimum set to stop at and it never asks whether to start building: the specification binds at the preparation exit, and a work plan comes after phasing. If you want to skip preparation, the agent tells you the two ways that exist and their consequences. The agent does not ask for your yes after each section:it stores what it wrote as drafts in its own name, tells you in one line what it stored and goes on. What needs you — a decision that is yours, a change to the solution brief or to who asked and why, or the agent's suggestion that a part of the specification does not apply — arrives as a card on Waiting for you; the brief changes only when you apply it there. - An existing codebase starts with the Onboard … initiative and the Shadow authority tier: what the code shows becomes design drafts for review (see Onboarding and Solution settings).
- Every solution also gets a quarterly maintenance initiative for defects and small fixes.
- Nothing the agent records binds until a person approves it. You can continue in the web wizard exactly where the interview stopped.