Nordglade / Experiment 05
From 212 records to three that needed attention
The recording
Paused at 19 sEvery company, supplier, figure and brief on this screen is fictional. The operator is opening the software at 06:35 on a Monday. A quarterly emissions file of 212 line items has been reconciled overnight; 209 matched and are not shown. The three that did not are on the screen with the reason each one stopped, and the recording opens the first of them. See it full size.
What the operator didn’t need to review
The system cleared 209 matched records and showed the operator only the three tasks that needed attention.
Instead of making someone search through 212 rows, the screen shows the exceptions, why each one needs attention, and its deadline. The 209 matched records remain accounted for as a total.
The record
Four questionsInformation used
Three things: the supplier declarations filed for the month, the reconciliation of the quarterly emissions file against the company’s own record, and the filing calendar.
Fourteen of sixteen suppliers had filed. The emissions file held 212 line items. The return was four days out.
No model was called to produce any of this. The screen is arithmetic and rules over stored records, and the only judgement in it is the ordering.
What it checks
Which records a person needs to see before opening their email, and in what order.
Three qualified: one reconciliation difference, one task covering two missing supplier declarations, and one filing figure requiring verification. Each carries its own age, so six days without a declaration reads as worse than five days before a deadline that is not yet late.
The 209 lines that reconciled cleanly are counted and dropped. Nothing on the screen ranks the three against each other.
What required human review
All three tasks, and the recording opens the one that moves a number.
Metallikierrätys Oy declared 1 412 short tons, which converts to 1 281 tonnes. The company’s own record for the same period holds 1 240 tonnes. The conversion is exact and is not what is in question. The 41 tonnes between 1 281 and 1 240 are, and the screen does not explain them. It says to confirm the difference with the supplier before the return is filed on Friday.
The second is one grouped follow-up task covering two supplier declarations that never arrived for July, and in the reconciliation the missing figure is being held forward from last month. The third is the return itself, due Friday with one figure still requiring verification. Neither task moves any tonnage, and both still block sign-off.
Limits of this demonstration
The company, the suppliers and every figure on this screen are invented, and the reconciliation behind them was written rather than run. No emissions file was parsed and no supplier declaration was read. What is being demonstrated is the shape of the screen and what it chooses to withhold, not a working reconciliation engine.
The exception list itself is not a mock. It is part of the operator view and, outside this demonstration, it fills from the author’s own workspace checks. The reconciliation layer underneath it is demonstration-only, because that workspace has no filing calendar to read.
It has not been run against a real company’s records, so nothing here says it is ready for day-to-day use.
Design lesson
Author's noteThe useful decision was what to leave out. Two hundred and nine clean lines are a real result and putting them on the screen would have buried the three that need a person. A count in a footer says the same thing and costs no attention.
The harder half is that leaving records out is only safe when the screen can say what it left out and why. That is why the footer carries the count rather than nothing at all: a person can see the size of what was hidden without reading it.
Technical notes
127.0.0.1:8771, the local instance. A previous chat is visible in the sidebar. All recorded rather than cropped.