We are ready for a controlled Paper demonstration. The example strategy is accessible, configured, and still off. Its identity, mode, and resource settings have been reviewed. You can watch this sequence without changing your own account. The learning goal is to connect an intentional change with a verified state, not to produce a trade during the lesson. In the example settings dialog, turn on the Decision engine control. Read the helper text: it allows this strategy to open new positions. Before saving, check the mode and the other settings once more. Saving the dialog submits the settings together, including the enabled state. Do not use a real account as a practice screen just because Paper appears somewhere else in the application. Select Save strategy settings once and wait for the response. Then inspect the strategy's returned status. The Trading card should reflect the current enabled state when the save succeeds. You can reopen the settings to confirm the stored choice and values. If the request fails or the result is uncertain, investigate that message instead of treating the state you selected before saving as the final answer. The configured mode control in the strategy detail view offers another route to changing its decision-engine state. Unlike editing a dialog and then saving, selecting that mode control sends its change directly. Read the current label before using it, and verify the refreshed state afterward. Do not click a second time simply because you expected a different animation; a second successful toggle could reverse the first change. Now distinguish enabled from actively buying. The strategy may still be waiting for its conditions. Funds may already be committed, an account-level restriction may apply, or a connection may be unavailable. Enabling authorizes the decision engine within the relevant boundaries. It does not promise a new position, a particular entry price, or immediate activity. If a recorded action later appears, identify its strategy, account, mode, market, and time. Check Portfolio and Transactions rather than relying on a brief notification. A candidate is not a fill, and a request is not proof of a completed purchase. The previous chapter's sequence still applies: observe, evaluate, check, request, and verify. Before ending this page's demonstration, note the verified state and what remains unchanged. The example Paper strategy is enabled, but that does not describe Live or another strategy. In the next page, we will turn it off deliberately and check the consequences. Keeping the start and stop parts of the exercise together is a practical way to avoid leaving a demonstration running without a clear reason.