WEBVTT 00:00:01.300 --> 00:00:04.865 Before enabling a strategy, read its detail page as an explanation of 00:00:04.865 --> 00:00:08.429 a job you may authorize. Begin with the name, creator or source, 00:00:08.429 --> 00:00:11.994 and the public description. What is it intended to do? What limits 00:00:11.994 --> 00:00:15.559 or conditions are described? You do not need access to its private 00:00:15.559 --> 00:00:19.124 recipe to understand its stated purpose. You do need enough information to 00:00:19.124 --> 00:00:21.500 explain what you are choosing in plain language. 00:00:22.000 --> 00:00:25.948 Read the available Paper and Live information separately. Access in one context 00:00:25.948 --> 00:00:29.897 does not establish access in the other. A control can show an 00:00:29.897 --> 00:00:33.845 access requirement, Add to a mode, or a decision-engine state. These labels 00:00:33.845 --> 00:00:37.794 describe different stages. Do not skip over the label because the strategy 00:00:37.794 --> 00:00:41.742 name looks familiar or because you have used another strategy from the 00:00:41.742 --> 00:00:42.400 same creator. 00:00:42.900 --> 00:00:46.971 Next, inspect the evidence that accompanies the offering. Read the source, time 00:00:46.971 --> 00:00:51.043 period, sample size, and any assumptions or limitations provided. Historical research, recorded 00:00:51.043 --> 00:00:55.114 Paper activity, and Live results are different kinds of evidence. They should 00:00:55.114 --> 00:00:59.186 not be merged into one imagined performance record. A large percentage with 00:00:59.186 --> 00:01:03.257 little context is a reason to look more closely, not a substitute 00:01:03.257 --> 00:01:04.275 for that context. 00:01:04.775 --> 00:01:08.056 For example, a win rate describes the share of counted trades that 00:01:08.056 --> 00:01:11.336 met the displayed definition of a win. It does not tell you 00:01:11.336 --> 00:01:14.617 the size of each gain or loss. A strategy can have many 00:01:14.617 --> 00:01:17.897 small wins and fewer large losses. A historical return also belongs to 00:01:17.897 --> 00:01:21.178 the period and setup reported. Neither number tells you what your next 00:01:21.178 --> 00:01:24.458 trade will earn, or whether the strategy fits the resources you intend 00:01:24.458 --> 00:01:25.825 to allow it to use. 00:01:26.325 --> 00:01:29.986 Version information matters because an offering can change. Read the current version 00:01:29.986 --> 00:01:33.647 and any available release notes or update notice. Keep historical evidence attached 00:01:33.647 --> 00:01:37.308 to the version it describes. Do not assume that a pending update 00:01:37.308 --> 00:01:40.968 has already been accepted or that every older result was produced by 00:01:40.968 --> 00:01:44.629 the current behavior. When the app asks you to review a change, 00:01:44.629 --> 00:01:47.375 read that change before treating it as routine housekeeping. 00:01:47.875 --> 00:01:52.284 Reviews and linked discussions can supply useful questions. Look for specific observations 00:01:52.284 --> 00:01:56.693 about the user's experience, dates, and context. Popularity and positive feedback do 00:01:56.693 --> 00:02:01.102 not replace checking access, settings, and evidence. You can inspect these sections 00:02:01.102 --> 00:02:05.511 without posting a message or submitting a review. The purpose here is 00:02:05.511 --> 00:02:08.450 to understand the offering, not to endorse it. 00:02:08.950 --> 00:02:12.684 Your checkpoint is a short explanation with four parts: this is the 00:02:12.684 --> 00:02:16.419 strategy, this is its stated purpose, this is the evidence I can 00:02:16.419 --> 00:02:20.153 inspect, and these are the limitations or unanswered questions. If an important 00:02:20.153 --> 00:02:23.887 answer is missing, leave it missing rather than guessing. The next step 00:02:23.887 --> 00:02:27.622 is to separate obtaining access from actually giving the strategy permission to 00:02:27.622 --> 00:02:29.800 make new decisions in your selected mode.