Thread & LogicStudio notes
Writing about the interface and system behavior behind useful business software.
01An approval belongs to the action someone saw
A request can keep the same identifier while its recipient or contents change. This note follows a hypothetical reply through review and an uncertain send result, showing where a version-specific approval helps.
Read the approval note 02A shared queue needs a concurrency rule
Two people can open the same item and make reasonable decisions from different versions. The queue note considers reservations, changed-item warnings and what the list should show after a decision.
Read the queue note 03Written for the people specifying the build
These notes use illustrative situations to explain application choices. They are useful when an operations lead, product owner and developer need to agree what a screen or action should do. The examples are not accounts of completed client work and do not prescribe one design for every business process.