# Chapter #8: Where WP-Rush Fits ## How WP-Rush implements request-aware execution scope determination before regular WordPress plugin execution. [WP-Rush](https://www.wp-rush.com/WP-Rush/WP-Rush-WordPress-Performance-by-Prevention::6604.html "WP-Rush") is a concrete implementation of this architectural layer for WordPress. It evaluates request context before regular plugin execution and determines an appropriate runtime scope for the request. The resulting plugin participation is the enforcement step. The architectural value lies in the decision that precedes it. In simplified form: **request ? early context recognition ? execution scope decision ? required plugin set ? normal WordPress execution** This is fundamentally different from waiting until the normal WordPress runtime has already been established and then deciding which parts of that runtime should remain inactive. Rush does not replace caching, frontend optimization, database tuning or good plugin engineering. It operates before them. Page caching can reduce **how often** WordPress has to execute. WP-Rush can reduce **how much of the application participates when WordPress does execute.** Together, these approaches address different dimensions of the same performance problem.### WordPress Performance Architecture describes a missing layer between the incoming request and the broad WordPress application runtime. Performance by Prevention defines the principle: **Determine the required execution scope before avoidable work begins.** WP-Rush implements that principle for WordPress.### WP-Rush acts before regular plugin execution WP-Rush does not wait for the fully initialized WordPress application to determine what kind of request is being processed. At that point, much of the execution it intends to prevent would already have happened. Instead, Rush evaluates request context before regular plugin execution begins. Conceptually: **request ? Rush ? execution scope ? WordPress** The request reaches the decision layer first. Only then is the appropriate WordPress runtime allowed to form.### Request context determines execution scope WP-Rush does not treat every request as requiring the complete active plugin set. Different request contexts can require different parts of the application. A frontend page, checkout request, administration screen or another application context may depend on different functionality. WP-Rush uses the request context to determine which plugin scope is required before those plugins enter normal execution. This turns site-wide plugin availability into request-specific execution. The plugins remain installed. They remain active for the application. But activity at application level no longer automatically means participation in every request.### Selective plugin loading is the enforcement The visible result of WP-Rush is selective plugin loading. But selective loading is not the architecture itself. The architecture is the decision that precedes it. WP-Rush first determines an execution scope. The resulting plugin set enforces that decision. This distinction matters because simply excluding plugins does not establish whether those exclusions are correct for the current request. **Decision defines necessity.** **Selective loading enforces the decision.** That is what separates an execution architecture from a collection of loading rules.### WordPress still does the WordPress work WP-Rush does not replace WordPress. Once the execution scope has been established, WordPress continues normally with the functionality available within that scope. Plugins that are required can behave as they normally would. WordPress APIs, hooks and application logic remain WordPress. WP-Rush intervenes only at the boundary where broad application availability would otherwise become request execution. It changes the scope. Not the purpose of the application.### Unknown requests remain valid requests An early decision layer cannot safely assume that everything it does not recognize is unnecessary. Rush therefore requires a safe path for requests whose execution requirements cannot be determined reliably. Where a narrower scope cannot be established with sufficient confidence, broader execution remains available. The objective is not maximum reduction. It is reliable prevention. **Correct execution always takes precedence over reduced execution.**### WP-Rush complements page caching WP-Rush does not attempt to replace full-page caching. A valid cache hit can avoid WordPress execution entirely, which is preferable to reducing an execution that does not need to happen. Rush becomes relevant when WordPress actually has to run. The relationship is straightforward: **Cache hit ? reuse the existing response.** WordPress execution required ? Rush determines the required execution scope. Page caching reduces how often the application executes. Rush reduces how much of the application needs to participate when it does. These are different intervention points and complementary mechanisms.### WP-Rush changes the cost of application growth Without an execution-scope layer, increasing application capability can also increase the runtime that participates across requests. More functionality can mean more code becoming available whenever WordPress executes. Rush separates these two forms of growth. The WordPress application can remain functionally large while individual requests execute smaller subsets of it. That changes an important relationship: **Application complexity no longer has to equal request complexity.** A site can gain functionality without requiring every request to carry the execution cost of all of it.### From optimization to execution architecture WP-Rush is therefore not another method for making already executed plugin code slightly faster. It changes an earlier architectural decision: **Which plugin code should execute for this request at all?** That is why Rush belongs before conventional WordPress optimization. It operates where unnecessary execution can still be prevented rather than processed afterwards. The resulting principle is the same one developed throughout WordPress Performance Architecture: **Availability does not have to mean execution.** WordPress defines what the application can do. The request defines what it needs to do. WP-Rush connects the two.### How WP-Rush implements request-aware execution scope determination before regular WordPress plugin execution.