Clarification: V2 Text Statement "sequential, processed in order, and cannot be bypassed."

[ajayojha]

The business logic flow is sequential, processed in order, and cannot be bypassed.

"sequential"
How this is possible in modern apps that follows the practices of event-driven, asynchronous, or parallel flows.

"cannot be bypassed."
Absolute statement.

"processed in order"
How this is possible in distributed systems/flows.

[jmanico]

One of the most popular emerging standards for app communication is MCP, which is normally implemented as fully asynchronous flows.

So I wanted to acknowledge that the OP here is spot on.

[elarlang]

It is a requirement for business logic flow and should not be mixed with a technical solution details.

The point is, you can not do the step X, if the pre-condition step Y is not done. For an example, shopping cart can not go to delivery state if it is not paid (and this is business logic rule).

[ajayojha]

I am not mixing business logic with technical solution details,
The current wording usage technical-sounding phrases ("sequential", "processed in order", "cannot be bypassed") that conflict with modern architectures.

I have asked a simple question how the highlighted phrases are verifiable in modern architectures, the shopping cart example is 0.01% use case but what about others, I am looking for an answer to my questions that how the wording is verifiable in across architectures, here I am posting questions again:

1. "sequential" - How this is possible in modern apps that follows the practices of event-driven, asynchronous, or parallel flows?
2. "processed in order" - How this is possible in distributed systems/flows?

[elarlang]

This answer #3301 (comment) applies here as well.

Whatever architecture or technical solution you use - if you have a business requirement to have steps in a specific order, you need to have them in that order. Simple as that.

[ajayojha]

This answer #3301 (comment) applies here as well.

Whatever architecture or technical solution you use - if you have a business requirement to have steps in a specific order, you need to have them in that order. Simple as that.

please share the use cases which ASVS team has considered while drafting this requirement, so that this help me to correct my understanding.