Nice writing it all together and reminding those principles do have names!

By the way, while you are talking about (throwaway) prototypes / POCs, “The Pragmatic Programmer” 2nd ed. by David Thomas also describes “tracer code” (analogy for “tracer bullets”) approach, which (as I see) is one more way to realize Least Responsible Moment. In short, it’s about making making one end-to-end “thread”of functionality (for instance) from UI to databases, which all related services having bare ugly minimum to support the case. With this, it’s easier to create and check architectural framework you talking about in Least Effort, but already in the project at hand.

If you are going to continue the topic in another article, could be nice to know how to steer towards the ideal situation given a legacy project/architecture. I can imagine that would require much more principles…