WEBVTT 00:00:01.300 --> 00:00:05.490 A strategy can change over time. Its name may remain familiar while 00:00:05.490 --> 00:00:09.680 a new revision changes its explanation or behavior. Version information helps you 00:00:09.680 --> 00:00:13.870 distinguish those revisions. Before comparing a result or accepting an update, check 00:00:13.870 --> 00:00:18.060 which version the information belongs to. This is especially important when an 00:00:18.060 --> 00:00:22.250 older review and a newer description appear on the same detail page. 00:00:22.750 --> 00:00:27.014 Open the available version history and read the number, status, date, and 00:00:27.014 --> 00:00:31.279 release notes. Release notes explain what changed. A date can describe creation 00:00:31.279 --> 00:00:35.543 or publication depending on what the view provides, so read it alongside 00:00:35.543 --> 00:00:39.807 the status. A missing note means you have less explanation; it does 00:00:39.807 --> 00:00:42.650 not establish that nothing changed between two versions. 00:00:43.150 --> 00:00:47.319 Statuses such as draft, submitted, published, or retired describe stages in the 00:00:47.319 --> 00:00:51.489 offering's lifecycle. A draft is work in progress. Submitted indicates a review 00:00:51.489 --> 00:00:55.658 stage rather than proof of public availability. Published and retired describe other 00:00:55.658 --> 00:00:59.828 stages, but access still depends on the current account and offering. You 00:00:59.828 --> 00:01:03.650 may not see every status or author-only control on your account. 00:01:04.150 --> 00:01:08.099 If version-specific test information is shown, keep it attached to that version. 00:01:08.099 --> 00:01:12.048 A result from one revision cannot simply be copied into a claim 00:01:12.048 --> 00:01:15.998 about another. Check the test's period and assumptions where available, along with 00:01:15.998 --> 00:01:19.947 the revision number. If you cannot tell which version produced a result, 00:01:19.947 --> 00:01:23.896 say so. That uncertainty belongs in your comparison instead of being silently 00:01:23.896 --> 00:01:24.225 removed. 00:01:24.725 --> 00:01:28.561 An existing subscription can have an accepted version and a notice that 00:01:28.561 --> 00:01:32.398 an update is available. Those are different pieces of information: the version 00:01:32.398 --> 00:01:36.234 associated with your accepted access, and a newer version you can review. 00:01:36.234 --> 00:01:40.070 Read the update's release notes before choosing an acceptance action. The marketplace 00:01:40.070 --> 00:01:43.907 supports an explicit update-acceptance flow; seeing a new version listed is not 00:01:43.907 --> 00:01:45.825 proof that you have accepted it. 00:01:46.325 --> 00:01:50.627 An archive notice also needs careful reading. The current archive explanation distinguishes 00:01:50.627 --> 00:01:54.928 removal from new marketplace sales from preserving existing subscribers' accepted-version access. That 00:01:54.928 --> 00:01:59.230 is different from saying every account can begin using the archived offering. 00:01:59.230 --> 00:02:03.531 Read the notice attached to your actual subscription and offering. Do not 00:02:03.531 --> 00:02:07.833 infer that archiving sold your positions, ended every subscription, or removed all 00:02:07.833 --> 00:02:08.550 account activity. 00:02:09.050 --> 00:02:12.905 Creator actions such as editing a draft, archiving, or deleting belong to 00:02:12.905 --> 00:02:16.759 the author workflow when available. They are not steps a shopper must 00:02:16.759 --> 00:02:20.614 perform to compare strategies. Likewise, cancelling a subscription, accepting an update, and 00:02:20.614 --> 00:02:24.468 stopping trading are different actions with different consequences. If you later intend 00:02:24.468 --> 00:02:28.323 to make one of those changes, review its own confirmation and the 00:02:28.323 --> 00:02:30.250 effect on existing access and positions. 00:02:30.750 --> 00:02:34.755 For this page's check, identify the version you inspected, the status shown, 00:02:34.755 --> 00:02:38.760 and any update or archive notice. Then state what would still need 00:02:38.760 --> 00:02:42.765 confirmation before you changed anything. You can finish without pressing an acceptance 00:02:42.765 --> 00:02:46.770 or lifecycle button. Understanding a notice is a successful outcome; acting on 00:02:46.770 --> 00:02:50.775 it should come only after you understand what the action would change.