update rmn callout

src/content/ccip/concepts/architecture/onchain/aptos/components.mdx

@@ -175,3 +175,9 @@ The `ccip::receiver_registry` is a module where developers can register their cu
 ## RMN (Risk Management Network) Remote
 
 The `ccip::rmn_remote` module is a critical security component deployed on every CCIP-enabled chain. Various CCIP modules (like `OnRamp`, `OffRamp`, `Token Pools`) query this component to verify the status of other chains in the network. It maintains an onchain list of "cursed" (i.e., blocklisted) chains. If a source or destination chain is cursed, CCIP transactions involving that chain are halted.
+
+<Aside type="note">
+  Based on user demand, CCIP's architecture is evolving to provide enhanced support for modular security and
+  configurable compliance capabilities. As part of this transition, the Risk Management Network is being adapted to
+  align with this broader, more flexible architecture.
+</Aside>

src/content/ccip/concepts/architecture/onchain/evm/components.mdx

@@ -180,3 +180,9 @@ The RMN Contract is deployed on every chain where CCIP is integrated. Its key fu
 1. **Cursing Mechanism**
    - **Curse Initiation**: When the CCIP Owner manually initiates a curse, the `curse()` function is invoked to mark the appropriate subjects as cursed.
    - **Curse Detection**: Onchain components (such as the Router, OnRamp, OffRamp, and TokenPool) call the `isCursed()` function on the RMNRemote contract to detect global curses or curses targeting a remote chain.
+
+<Aside type="note">
+  Based on user demand, CCIP's architecture is evolving to provide enhanced support for modular security and
+  configurable compliance capabilities. As part of this transition, the Risk Management Network is being adapted to
+  align with this broader, more flexible architecture.
+</Aside>

src/content/ccip/concepts/architecture/onchain/svm/components.mdx

@@ -201,10 +201,8 @@ The Risk Management Network (RMN) adds an additional security layer to CCIP by m
 - Once cursed, any CCIP transaction that performs the verification check for that chain selector (or the global curse) will revert, preventing cross-chain message processing.
 - The owner calls `uncurse` to lift the curse when the threat is resolved, restoring normal CCIP operations.
 
-<Aside type="caution" title="Phased Deployments">
-  Certain blockchains may be integrated with CCIP in a phased approach, with the Committing and Executing DONs deployed
-  first and the Risk Management Network added in a later update. In cases of a phased deployment, merkle roots in
-  relevant Commit Stores are always considered blessed until the Risk Management Network has been deployed for that
-  blockchain. Please see the [CCIP Directory](/ccip/directory) for which integrations utilize a phased approach. Please
-  review [CCIP Service Responsibility](/ccip/service-responsibility) for more information.
+<Aside type="note">
+  Based on user demand, CCIP's architecture is evolving to provide enhanced support for modular security and
+  configurable compliance capabilities. As part of this transition, the Risk Management Network is being adapted to
+  align with this broader, more flexible architecture.
 </Aside>

src/content/ccip/llms-full.txt

@@ -1527,6 +1527,12 @@ The RMN Contract is deployed on every chain where CCIP is integrated. Its key fu
    - **Curse Initiation**: When the CCIP Owner manually initiates a curse, the `curse()` function is invoked to mark the appropriate subjects as cursed.
    - **Curse Detection**: Onchain components (such as the Router, OnRamp, OffRamp, and TokenPool) call the `isCursed()` function on the RMNRemote contract to detect global curses or curses targeting a remote chain.
 
+<Aside type="note">
+  Based on user demand, CCIP's architecture is evolving to provide enhanced support for modular security and
+  configurable compliance capabilities. As part of this transition, the Risk Management Network is being adapted to
+  align with this broader, more flexible architecture.
+</Aside>
+
 ---
 
 # Onchain Architecture - Upgradability (EVM)
@@ -1915,12 +1921,10 @@ The Risk Management Network (RMN) adds an additional security layer to CCIP by m
 - Once cursed, any CCIP transaction that performs the verification check for that chain selector (or the global curse) will revert, preventing cross-chain message processing.
 - The owner calls `uncurse` to lift the curse when the threat is resolved, restoring normal CCIP operations.
 
-<Aside type="caution" title="Phased Deployments">
-  Certain blockchains may be integrated with CCIP in a phased approach, with the Committing and Executing DONs deployed
-  first and the Risk Management Network added in a later update. In cases of a phased deployment, merkle roots in
-  relevant Commit Stores are always considered blessed until the Risk Management Network has been deployed for that
-  blockchain. Please see the [CCIP Directory](/ccip/directory) for which integrations utilize a phased approach. Please
-  review [CCIP Service Responsibility](/ccip/service-responsibility) for more information.
+<Aside type="note">
+  Based on user demand, CCIP's architecture is evolving to provide enhanced support for modular security and
+  configurable compliance capabilities. As part of this transition, the Risk Management Network is being adapted to
+  align with this broader, more flexible architecture.
 </Aside>
 
 ---
@@ -2249,6 +2253,12 @@ The `ccip::receiver_registry` is a module where developers can register their cu
 
 The `ccip::rmn_remote` module is a critical security component deployed on every CCIP-enabled chain. Various CCIP modules (like `OnRamp`, `OffRamp`, `Token Pools`) query this component to verify the status of other chains in the network. It maintains an onchain list of "cursed" (i.e., blocklisted) chains. If a source or destination chain is cursed, CCIP transactions involving that chain are halted.
 
+<Aside type="note">
+  Based on user demand, CCIP's architecture is evolving to provide enhanced support for modular security and
+  configurable compliance capabilities. As part of this transition, the Risk Management Network is being adapted to
+  align with this broader, more flexible architecture.
+</Aside>
+
 ---
 
 # Onchain Architecture - Upgradability (Aptos)