Start

The three paths

• A new product: a system built from scratch. You describe the solution, then its first change — the initiative that builds it — and its requirements.
• An existing system: a codebase that runs today. You describe the solution and its code; your agent then discovers its modules and behaviour, and people confirm them (onboarding).
• A change to an existing solution: a request for something new or different in a solution Corpole already knows. The request is recorded at once (or you pick one already waiting in the Funnel); people who manage the portfolio then open a new initiative for it — choosing the solutions it changes — or add it to one under way, and write its requirements straight into that initiative. Others stop after the request: it waits on the portfolio board.

The Demand step asks why: who asked, how it came, the problem and, if you like, the expected outcome and a first intent. Only who asked and the problem are required. When the solution is created, this becomes its charter demand on the portfolio board, and the first intent starts its value case.

The Initiative step fills the change that builds the solution: its title, what it delivers, how it is managed (as a project, or as small work) and its capacity type. The requirements that follow are the initiative's; small work is asked only what changes (functional, non-functional, technical). The path ends on a summary of what was created on each axis and what is still missing.

An existing system goes from the solution to its code: add each repository (GitHub or GitLab, a folder for a monorepo) and the component it belongs to. The onboarding plan then lists what happens next — connect your agent, run /corpole:onboard in each repository, review the findings, raise the authority tier from Shadow as people confirm. The answer to "Is there code already?" decides the path, whichever card you started from.

The Portfolio step comes first for owners and admins, once per tenant: the regulations and standards every solution follows (KVKK, BDDK, GDPR, ISO 27001, PCI DSS, WCAG), the corporate rules (business constraints, one per line) and work-in-progress limits. Each becomes a tenant-wide standard in Knowledge, which compliance and every agent read. It can be skipped; the portfolio page then keeps a reminder.

Steps marked coming are part of the path but not built yet; the path skips them for now.

Stopping and continuing

A path remembers where you are. Continue where you left off takes you back; Discard drops a path you will not finish (what it already created stays).