- Separation of concerns: how deployments break out
- Inclusion: Start with the implications to the path-orientation of v3, and how we would identify functions. That sets us up to be able to describe more HTTP-based synchronous APIs.
- then refer back to separation of concerns about disentangling schemas,
- and how that creates space for formally describing other content types?
- Signatures: Go deeper into what it means to have a signature orientation that unblocks #2.
- Semantics: How that then leads to the semantics requirement where we enshrine the meaning and purpose ("what and the why") to the mechanics ("how").