https://arran4.github.io/blog/categories/software-architecture/Recent content in Software Architecture on Arrans Technical blogHugo -- gohugo.ioentechnicalblog123@arran4.com (Arran Ubels)technicalblog123@arran4.com (Arran Ubels)Arran Ubels. This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 International License</a>.Tue, 15 Sep 2026 17:35:48 +1000https://arran4.github.io/blog/post/2026/046-scenarios-as-executable-application-state/Tue, 15 Sep 2026 17:35:48 +1000technicalblog123@arran4.com (Arran Ubels)https://arran4.github.io/blog/post/2026/046-scenarios-as-executable-application-state/There is a recurring problem in application development that tends to acquire a collection of unrelated solutions. Tests need data. Developers need a populated application to work against. Demonstrations need a recognisable set of users and content. Screenshots need a known visual state. Bug reports need a reproducible situation. Continuous integration sometimes needs to run the application against something more interesting than an empty database. An LLM working on a user interface needs to be able to create exactly the state it is trying to inspect.