A thought I had today while re-reading https://github.com/anoma/nspec/pull/104 is that the clarified application interface - as discussed with @Michael @degregat and @vveiln today - should probably also be reflected (at some point) in the structure of the specs, e.g. we should have whatever bits of service provider awareness are necessary for the application in the “Application Architecture” section.
I also wonder if the “Protocol Architecture” section even needs to be aware of resources at all. Some controller bookkeeking should be performed automatically, so this needs to be included somewhere, but maybe there can be an abstraction in between - it would be nice if all of the ordering machine logic could reason only about key-value store interactions and abstract computation, for example.