Getting started
First steps, the main screens and how a solution begins.
CorPole changes one thing about building with coding agents: the agent no longer decides for itself which documents are current. Every requirement, decision and constraint carries a state, and only records in the Authority state bind the agent. Everything else in this help center builds on that idea, so this is the place to start.
The articles here take you from nothing to a first governed piece of work. They explain what CorPole is and what it deliberately is not, why only Authority binds, and how a solution begins: with a kickoff interview your agent runs, with a document you upload, or by telling the story in your own words. You will also find the main screens a team uses every day, starting with the Overview, and how work is organised: a demand says who asked for what, an initiative answers it, and the work inside the initiative changes the solution's design.
If you work alone with Claude Code or Cursor, read “Your first 15 minutes”. If you are joining a team, read “Your first day in a team project”. If you are deciding whether CorPole belongs in your toolchain, the 30-minute evaluation plan walks you through the loop that matters: a requirement agreed, a conflict stopped, a change proven.
Nothing in these articles asks you to change how you write code. Your agent keeps writing it; CorPole governs what it is told, and people keep the decisions that matter.
Articles in Getting started
- GuideOverviewThe home page of the active solution: how many records it has in each state, which AI proposals are waiting for review, and shortcuts to the record catalogue.
- GuideSolutionsAll solutions of your tenant. The active solution decides which records you see everywhere in the app and which records AI agents receive.
- GuideNew solutionThe first step of the guided setup: name the solution and describe its context. The context is what AI suggestions later build on.
- GuideStartOne question — what are you starting? — and three paths. Each step asks only what belongs where it is kept: why a change is wanted (Demand), what the system is (Solution), and the change itself (Initiative).
- GuideGuided setupBuilds the solution's first requirement set, one record type at a time, from the solution brief to objectives, requirements and constraints.
- GuideMaturityHow sound the solution is today on five dimensions, levels 0 to 4, against the target of its profile — and what the next level needs.
- ConceptWhat CorPole is, and what it is notCorPole keeps your requirements, decisions and constraints with a state on each, and hands coding agents only what binds today.
- ConceptWhy only Authority binds your agentAn agent reads exactly what it is handed, every run. If everything in the repository looks current, stale decisions steer it. States fix that.
- How-toYour first 15 minutes as a solo builderConnect Claude Code, run the kickoff interview, approve what binds and let the agent plan the first story.
- How-toYour first day in a team solutionConnect your agent under your own name, set up your clone, and pick up a Ready story.
- How-toEvaluating CorPole: a 30-minute trial planTry the loop that matters: a requirement agreed, a conflict stopped, a change proven.
- How-toStart a solution without opening the web appTell your agent you want to start a solution; it creates it for you and runs the kickoff interview.
- ConceptHow people and agents share the workAgents draft, propose, build and report. People decide what binds, what is ready and what is done.