Outputs that update as you decide: the summary is a side-effect, not a dashboard
Decision surfaces need a running total. Not a KPI strip showing system state — a summary that reflects what the user has decided so far. These are different numbers, and agents build the wrong one.
In a decision surface, there are two kinds of numbers that could appear at the top of the screen. The first kind reflects system state: how many records are in each status, what the total dataset looks like, what the trend has been over the last period. The second kind reflects the user's progress through their own work session: how many decisions they've made, what the accepted total adds up to, how many remain.
These numbers look similar. They're often about the same dataset. But they answer different questions — and agents almost always build the first kind when the job needs the second.
Monitoring numbers vs. decision numbers
A KPI strip that shows "47 pending, 12 approved, 3 rejected" is monitoring output. It tells the user where the overall system stands. It would be equally at home on a manager's overview screen, updating as other people make decisions. It's a dashboard element.
A running total that shows "Approved: $14,200 · Remaining: 8" is decision output. It reflects only what this user has done in this session. It doesn't update when someone else approves something. It doesn't represent the whole queue — only the portion the user has worked through. It changes because the user is deciding, not because the underlying data is changing.
Pattern: in a decision surface, the summary should reflect what the user has decided, not what the data says. It's a progress tracker for the current work session, not a dashboard widget sitting above the table.
Why this matters for high-volume decision work
In a batch decision workflow — reorder approvals, expense reviews, content moderation, loan triage — the user processes a queue. Their session has a beginning and an end: they start with N items, they work through them, they reach zero. The thing they need to know as they work is: how am I doing against my own work session? What have I committed to so far? How much is left?
Monitoring numbers don't answer that question. If the queue shows "47 pending" and the user has approved 15 and rejected 3, the "47 pending" number is still reflecting the full queue minus whoever-else's approvals. The user has no signal of their own progress. They don't know how far into their session they are. They can count, but the interface isn't helping them count.
The decision-output summary makes the session legible. The user can see at a glance how much they've committed to, whether they're approaching their own limit (budget, capacity, time), and how many records remain in their personal queue. This is information they need. The system state KPIs are information that could be available if wanted, but they're not what the job requires at this moment.
When system state IS the right number
The monitoring summary is right when the job is monitoring. A manager reviewing team performance across a period needs to know the aggregate queue state. An operations lead checking in on daily throughput needs trend data and totals by status. These are genuinely monitoring jobs, and a dashboard with system-state KPIs is the correct response.
The mistake is applying that response to an individual decision-maker's working tool. The planner approving reorders is not a manager monitoring the queue. They're a worker processing their portion of it. The numbers at the top of the screen should reflect their work, not the queue's state.
This is the distinction that decides whether the layout is a dashboard or a decision surface. Not the visual design — the type of number at the top.
How agents miss it
Agents build monitoring KPIs because monitoring KPIs are derived directly from the schema: count by status, sum of a column, distinct values. These are natural aggregates that fall out of any table query. Decision-progress numbers are harder to compute: they depend on user-session state, track what this specific user has acted on, and update only when this user takes an action.
The session-state model requires thinking about how the interface is used over time. Agents operating from a schema don't have that context. They build what the data can produce, not what the job needs.
The /ux lens surfaces this when a decision-job layout includes system-state monitoring at the top and no user-progress tracking. The patch is specific: replace the KPI strip with a session progress summary (items decided, cumulative value committed, items remaining), and add the monitoring numbers as an accessible secondary view for context when wanted.