WEBVTT 00:00:01.300 --> 00:00:04.886 Turning something off starts with deciding what you intend to stop. Do 00:00:04.886 --> 00:00:08.472 you want one strategy to stop making new entry decisions? Do you 00:00:08.472 --> 00:00:12.058 need to inspect a broader trading pause? Are you trying to close 00:00:12.058 --> 00:00:15.644 a particular holding? Those are different intentions, and the controls are not 00:00:15.644 --> 00:00:19.230 interchangeable. State your intention first so you can judge whether the selected 00:00:19.230 --> 00:00:20.425 action actually accomplished it. 00:00:20.925 --> 00:00:25.017 For the isolated Paper demonstration, our intention is to disable the example 00:00:25.017 --> 00:00:29.109 strategy's decision engine. Open its settings, confirm its name and Paper context, 00:00:29.109 --> 00:00:33.202 turn the engine off, and save. Inspect the returned Disabled or Decision 00:00:33.202 --> 00:00:37.294 engine Off state. If you use the configured mode control directly instead, 00:00:37.294 --> 00:00:41.386 verify the refreshed result after that request. In both cases, the evidence 00:00:41.386 --> 00:00:42.750 comes after the change. 00:00:43.250 --> 00:00:47.632 Next, inspect Portfolio. Turning the engine off is not a sale instruction. 00:00:47.632 --> 00:00:52.014 Existing holdings may remain, and their values can continue changing. Check the 00:00:52.014 --> 00:00:56.396 owner, account, and mode for any relevant position. A remaining holding is 00:00:56.396 --> 00:01:00.779 not proof that the off control failed, because stopping new entry decisions 00:01:00.779 --> 00:01:03.700 and closing an existing position are different jobs. 00:01:04.200 --> 00:01:08.245 Position monitoring needs a separate check. The Decision engine helper describes permission 00:01:08.245 --> 00:01:12.291 to open new positions; it is not a universal description of every 00:01:12.291 --> 00:01:16.336 exit watcher or protective process. Do not assume either that all exits 00:01:16.336 --> 00:01:20.382 stopped or that every exit will continue unaffected. Inspect the relevant position, 00:01:20.382 --> 00:01:24.427 alerts, and current control state before relying on ongoing monitoring. A changed 00:01:24.427 --> 00:01:26.450 strategy label cannot replace that review. 00:01:26.950 --> 00:01:30.896 The broader Trading pause, when available to your role, has its own 00:01:30.896 --> 00:01:34.842 scope. Read the account and mode involved and the status returned by 00:01:34.842 --> 00:01:38.788 the control. A pause can affect automated exits as well as entries. 00:01:38.788 --> 00:01:42.735 Do not treat it as a way to preserve every protective action 00:01:42.735 --> 00:01:46.681 while stopping only purchases. A protective interruption or reset message also deserves 00:01:46.681 --> 00:01:48.325 investigation before you resume anything. 00:01:48.825 --> 00:01:52.442 A request already sent needs its own outcome check. A later disable 00:01:52.442 --> 00:01:56.059 or pause does not establish that an exchange canceled an earlier order. 00:01:56.059 --> 00:01:59.676 If you are uncertain about a submitted action, inspect the appropriate records 00:01:59.676 --> 00:02:03.294 and account context before repeating it. Closing a browser tab, moving to 00:02:03.294 --> 00:02:06.911 another section, or viewing Paper does not settle that question. Enabled Live 00:02:06.911 --> 00:02:09.925 work can continue outside the workspace you are looking at. 00:02:10.425 --> 00:02:14.177 For your checkpoint, report two separate findings: the engine state you verified 00:02:14.177 --> 00:02:17.929 and the position state you verified. If an outcome is unresolved, say 00:02:17.929 --> 00:02:21.682 so and identify the next check. The example exercise is complete only 00:02:21.682 --> 00:02:25.434 when you can describe the actual stopping point. An off label is 00:02:25.434 --> 00:02:29.186 useful evidence about a control; it is not a receipt proving that 00:02:29.186 --> 00:02:31.375 every related holding or request has ended.