Waiting for you

Where to find it

The Waiting counter in the context row below the top bar shows how many cards wait for you in the current solution; it turns amber when something waits and opens this page. Waiting for you in the menu (under General) and in the avatar menu opens it too. The screen has one name everywhere: the menu, the page, the browser tab and what your agent calls it are all Waiting for you. Decisions in the menus means only the list of decision records (Knowledge).

Home (General › Home, the page that greets you) does not list the cards. Under Waiting for you it shows one line — the same sentence this page shows, for example "3 cards wait for you, 1 prepared by your agent." — and the link Open Waiting for you. Home also shows the agents that wait for you, what waits in your other solutions and your unread notices.

How it works

1. Ask your agent "what waits for me?" or "prepare what waits for me". It reads each item and stores a two-line summary and a recommendation (approve, turn down, or a proposed answer).
2. Open Waiting for you (the menu, the Waiting counter, or your initials › Waiting for you). Prepared cards show the agent's summary; its recommendation is preselected.
3. Change what you want, leave the rest on Later, and Apply my choices. Each card is applied as you, with your roles checked; the history says which agent prepared it.
4. Approve on a draft is a review. On an agent's draft the choice reads Approve (reviewed — binds nothing yet), with the line "Approve marks it reviewed (Approved); it binds nothing until a person makes it Authority on its page — only Authority binds." The message after Apply my choices says the same. The notices that tell you drafts wait for review say "Nothing binds until a person makes it Authority in CorPole (Approved means reviewed; only Authority binds)."

Your agent never decides for you, and its word never makes something yours. You can tell it an answer ("the answer to QST-… is …") or a decision taken in a meeting or by the client; it writes down the wording and passes it on. What happens next depends on your AI client:

• Your client can ask you. A question appears in the client and shows everything your yes would record, the weightiest first: who is said to have decided, the work priorities it would change, the records it would govern, then the title, the text and the context. If you confirm it there, the answer is recorded as yours, or the decision as Accepted with you as the decider (accepting needs the permission to decide on knowledge). It is kept as confirmed in the client. The question is valid for ten minutes and only for that exact content; after that, or if anything in it changed, you are asked again.
• It is too long for the client. A decision or an answer that does not fit one question in the client (about 1,500 characters with its labels) is never cut and never asked there: you would be accepting text you were not shown. It is stored as a proposed decision or a filled-in answer, as below.
• Your client cannot ask you, or shows no question. Some clients, the Claude desktop app among them, say they can ask and then show nothing. Nothing is lost and nothing is recorded as yours: the decision is stored as a Proposed decision and waits in this list, and the answer is filled into its question here, marked "Prepared by" your agent with the note "Your agent passed this on as your answer from the conversation. It is not recorded as yours". The question stays open.
• You make it yours here. Choose Approve on the proposed decision, or Answer on the question — change the filled-in text first if it is not what you said — and Apply my choices. It is then kept as confirmed on the screen, with your name and the time. Later leaves it waiting; Turn down rejects the proposed decision.
• Who the agent says decided. When the agent named who took the decision (you, a client, a meeting), the item shows "The agent says this was decided by: "…" (meeting). This is the agent's claim, not a checked fact." The agent's words are inside the quotation marks, whatever they say; only what stands outside them is CorPole's. Read it before you approve: CorPole cannot check it. After you approve, the decision's note says that you accepted it and how, and keeps the agent's words labelled as its claim.

Priorities are not applied for you. When the agent named work priorities with a decision you did not confirm in the client, they are only written at the end of the decision's text ("Priorities named with it (not applied): …"). Approving the decision here does not change them either. Set each one yourself on its work item, in the Priority field. Priorities change with a decision only when you confirmed it in the client, where they were shown to you, and your roles allow editing work.

Who is asked in the client. Only a connection you sit behind asks you: your own personal token or your sign-in from the AI tool. A service token (a pipeline that runs in its creator's name), a package token shared with someone outside, an auditor's token and the hooks never ask and can never confirm anything in the client, even when their client says it could: what they pass on is always a proposal for the screen.

The same statement sent again by the agent is not stored twice: the proposed decision that is already there is kept, and no second notice is sent. The same holds for a decision you just confirmed in the client: sent again within ten minutes, it is the decision that is already recorded — nothing is stored again and no priority is set again, so a priority you changed on the screen in between stays. "The same" means the very same call: when your agent corrects anything in it (who decided, a priority, a governed record) and you confirm again, that is recorded as another decision. The title of a decision and the name of who decided are one line each; an agent's call with a line break, a control character or a text-direction mark (an invisible character that reverses or isolates the reading direction) in either is refused. Letters of any language are fine, and so are the joiners some names need, a soft hyphen and other invisible characters that come along with pasted text. Confirming in the client is all or nothing: the decision, what it governs and the priorities it sets are stored together, so a call that fails halfway leaves nothing and can simply be sent again. If you rejected or deleted the decision on the screen in the meantime, the same call sent again does not bring it back: your agent is told what the decision is now. A person whose roles do not allow accepting decisions is not asked in the client; the decision waits for someone who may accept it. The decision's own page says how it was confirmed (see Knowledge).

What "in the client" proves: that the answer came through your connected AI client for the exact text shown, not that you personally pressed the button. Whoever holds your connection could ask and answer. On the screen is the only way of confirming that proves a signed-in person; use it for anything that matters.

Authority is given on the screen only. An agent can ask you in your client to approve records (Approved), but not to make them Authority: that binds every agent, and the question in a client shows only a record's code and title, not what it says. When you ask your agent for it, it answers that you do this on the requirements board, where you read the record first.

Accepting a decision your agent recorded. Open the decision's page from the link your agent gives and use the Status button in the row of buttons at the top right (Status, Add, Delete, History): Accepted is under "Next step". The Status field inside the form is read-only and says so under it. The first sentence of "Consequences and options considered" is what the agent said about who decided; you can add your own text after it, but it cannot be changed or removed.