Overview
The 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.
For: Founder, Product owner, Project lead, Solo builder
Status brief
| Tab | What it answers |
|---|---|
| For me | Since your last change in CorPole: what others changed, where you left off (your open work, with handover notes), what is blocked or failing on your work, and what waits for you — decisions, drafts, change proposals, items in Verification, open questions. |
| Solution | Progress this week, decisions waiting, serious risks (score 12 or more), open drift signals, bottlenecks (blocked work, items stuck in review), maturity below target. |
| Team | Each person's open, in-progress and blocked work; agent sessions waiting for a person; open alerts. It lists, it does not rank people. |
| All my solutions | Every solution you can open, each on its own card: what you have in progress, what waits for your decision (for a solution under guided start: the number of your cards on Waiting for you, the same number as its context row below the top bar), dates due in two weeks, maturity below target, serious issues — then the next two weeks across solutions. Open switches to a solution to act in it. |
Every line links to where the items are. Your coding agent gives the same brief with get_status — ask it "where were we?" or "what is the status of the solution?".
The sentence under For me says how much needs you: "3 things need you first.", or "Nothing urgent." In a solution under guided start this number is the number of cards that wait for you on Waiting for you — the same number the context row below the top bar shows beside Waiting, read from the same list, so the two always agree. The first line under Waiting for you in the brief repeats it ("3 cards wait for you on "Waiting for you"") and opens that screen. Drafts your agents wrote are not counted: they show as one line that starts with "For your information" and links to the requirements board, because a draft does not need you — what needs you arrives as a card. In every other solution the number is as before: what is blocked or failing on your work, the decisions in your notices and the agent drafts to approve.
What you can do here
- Check how complete the solution is: the counters show all records and how many are Authority, Approved and Draft.
- Follow Acceptance: the share of acceptance criteria verified as met across all records that are not retired, and how many requirements still have no criteria. Those requirements are listed so you can add criteria.
- Check Traceability: open conflicts (they block Authority) and gaps in the chain, such as a functional requirement that refines nothing or an objective no business requirement refines.
- Review AI proposals awaiting review: records coding agents proposed through
propose_record. Open one to edit, approve or delete it. Findings from code, documents or tests are design drafts and are reviewed on the Onboarding page instead. - Jump to a record type from the Record catalog, or open Explorer to see every type side by side.
- Create a record with New record.
How to review an AI proposal
- Open the proposal from the review table.
- Read the statement and rationale. Check it does not duplicate or contradict an existing Authority record.
- Choose Edit to sharpen the wording, set priority and owner.
- Set the state to Approved or Authority if you agree, or delete the Draft if you do not.
Keep in mind
A proposal is never binding on its own. Agents keep treating it as a Draft until a person moves it to Authority. Approved means a person reviewed it; only Authority binds — the note on a proposal's page ("it binds nothing until a person makes it Authority"), the AI proposal badge and your agent's answers all use these words.