Deadline-first triage
A working queue of 300 fictional corporate actions, sorted by what breaks first. It’s my own design, built to show the states a case study can’t: a missed deadline, a second approver, an audit trail.
- Role
- Design and direction
- Built by
- Claude Code, directed by me. I’m not an engineer.
- Data
- Every issuer, custodian and fund is invented
- Status
- Prototype. Not SmartStream’s design or data.
Try this
Leave the row with the countdown alone. It has about 95 seconds on load. When time runs out it doesn’t disappear: it moves to Missed and tells you what’s still possible.
Pick an option and enter it. You can’t release your own instruction, so a colleague does, a few seconds later. Open the Audit trail and it’s all there.
Open one of the rows marked Closed. The market has shut, so the default applies unless the custodian agrees otherwise.
Three decisions
1 Sort by the next deadline that can still be missed
Rejected: sorting by event number or pay date.
An operator’s first question isn’t which event is next in sequence, it’s what fails first. Most of the 300 need nothing, so the default view is only the ones that do, with the value at stake beside each group.
2 A missed deadline keeps its place and says what’s left
Rejected: a red row with no next step.
Missing the operational deadline isn’t the end while the market is open, and missing the market still leaves a late request to the custodian. Each one asks for a reason, for the record.
3 The second approver is a state, not a dialog
Rejected: a confirm dialog. One person clicking twice isn’t four eyes.
An entered instruction waits in the queue until someone else releases it, and whoever entered it can recall it until then. Undo adds a line to the audit trail, and never removes one.
Left out
Elections split by account, rights issues, claims, and custodian notices that disagree with each other. A real queue needs all of them. Event codes and the MAND, VOLU and CHOS flags follow ISO 15022 usage, and the ISINs carry valid check digits.