Noor Ali and I followed this paper with a study testing the architecture against selected regulatory requirements in the UK, EU, and UAE. We examined whether those obligations could be represented through identifiable responsibilities, authorities, and evidence without changing their substantive meaning. One useful finding was that continuing duties cannot be captured by a single transaction approval. They require a governed sequence of time-bounded determinations, which led us to extend the model. The study also identifies where legal and supervisory judgments remain outside the architecture. [From Regulation to Verifiable Authority: A Cross-jurisdictional Regulatory Test of the Distributed Institutional Ecosystem](https://ssrn.com/abstract=7436101)

Take a look at Forth. Can run on anything and worst case, you can roll you own.

Live programming has been available for decades and is the common working mode of any Smalltalk programmer. (Or Forth for that matter) Talk about nothing new under the sun. We've wondered why anyone would work any other way, for decades.

"determined that our officers acted professionally and according to proper procedure.'" But the question is, does the procedure make a lick of sense?

The best approach I've found is to build a domain object model consisting of only the objects that come straight from the problem domain and then multiply the number of objects by a person days to implement an object for the particular implementation technology. There are some adjustments you can make based on complexity of the UI and developer experience but the basic premise works. It's sounds like a simplistic approach but it's not because the process of building a good object model and that's a key point, the object model must be well done, this process is really a process of organizing the information you need to build an estimate in a very sophisticated way. An object model is a way to organize and account for all of the data and behavior of the system and furthermore, to organize the information into reasonable units. The rules around building a good object model will cause the objects to be of a fairly uniform size in terms of complexity. What you end up with is a list of discrete groupings of data and behavior with well defined interfaces between them allowing for the fairly simple calculation of an average number of person days per object.