Readout · bound to scroll position
What is being measured here
InboxERPAutomationApprovalArchive
InboxERPAutomationApprovalArchive Throughput 312 cases / week Example figure. The real numbers come from the case study.
Left manual 4 % The arithmetic sits beside every figure.
Readout running 000 Bound to the scroll position of the act, never to time
Without WebGL, under reduced motion, and on a device that fails the capability gate, the same process reads as a section: the same stations in the same order, the same figures, the same text. What is missing is the camera move, not the content.
- Subject
- An order inbox as it really looks in a German office: email, PDF, paper, phone call
- Method
- Read it, route it, have it checked, file it. The person decides; the machine proposes
- Checked by
- Turnaround time, hit rate, number of follow-up questions
Why it is built this way
The scene is the design, and it has a rip cord
180 KB Ceiling for the 3D layer, gzipped Lazily loaded, never part of the first load, and guarded by a test
20 ms Retreat when frames get slow Two seconds over the line and the scene stays off for the session
0 things that live only inside the scene The readout and the station names are text, translated and readable aloud
The scene is what was designed and it carries this section. It starts only when the device can hold it, and it retreats when the frame rate drops. Anyone who has turned motion off, or who sits on a managed corporate laptop without hardware acceleration, gets the same process as a section.