WEBVTT

00:00:01.300 --> 00:00:04.982
You now have a way to supervise automation without watching every price

00:00:04.982 --> 00:00:08.664
movement. Build a routine that checks context, permission, capacity, activity, and results.

00:00:08.664 --> 00:00:12.345
The purpose is not to predict the next candle. It is to

00:00:12.345 --> 00:00:16.027
know what you have authorized, what is actually happening, and what needs

00:00:16.027 --> 00:00:19.709
your attention. A repeatable check is more useful than opening the app

00:00:19.709 --> 00:00:21.550
only when a number surprises you.

00:00:22.050 --> 00:00:25.969
Begin with context. Confirm the account, connection where relevant, and Paper or

00:00:25.969 --> 00:00:29.889
Live mode. Remember any enabled activity in a different workspace. Viewing Paper

00:00:29.889 --> 00:00:33.808
does not prove that Live strategies have stopped. If you manage more

00:00:33.808 --> 00:00:37.727
than one context, make your notes specific enough to distinguish them. I

00:00:37.727 --> 00:00:41.647
checked my account is less useful than naming which context you checked

00:00:41.647 --> 00:00:42.300
and when.

00:00:42.800 --> 00:00:46.519
Next, review the strategies you have enabled and the resources available to

00:00:46.519 --> 00:00:50.238
them. Confirm the identities and versions shown, the access status, and the

00:00:50.238 --> 00:00:53.957
allocation or budget information relevant to your setup. Look at tradable funds

00:00:53.957 --> 00:00:57.676
and existing commitments, not just a large balance at the top of

00:00:57.676 --> 00:01:01.396
the page. Changes to access or settings deserve a fresh review of

00:01:01.396 --> 00:01:03.875
what they mean for the work already underway.

00:01:04.375 --> 00:01:08.493
Then inspect activity and open positions. Read the available status and update

00:01:08.493 --> 00:01:12.610
information, review any exit alerts, and investigate warnings that affect your context.

00:01:12.610 --> 00:01:16.728
Connect positions to their owners and accounts. A total portfolio number can

00:01:16.728 --> 00:01:20.846
summarize value, but it does not explain every holding. When a result

00:01:20.846 --> 00:01:24.964
is unexpected, narrow the question to the specific strategy, position, market, and

00:01:24.964 --> 00:01:25.650
time involved.

00:01:26.150 --> 00:01:30.017
Check the evidence of completed actions in Transactions and the relevant position

00:01:30.017 --> 00:01:33.884
records. Compare the amount, execution information, fees, and status provided. A request,

00:01:33.884 --> 00:01:37.752
an alert, and a completed trade can appear in different places for

00:01:37.752 --> 00:01:41.619
different reasons. Keep them separate in your explanation. If an outcome is

00:01:41.619 --> 00:01:45.486
unresolved, mark it as unresolved rather than filling the gap with what

00:01:45.486 --> 00:01:46.775
you hoped would happen.

00:01:47.275 --> 00:01:50.651
Now rehearse a calm response to a surprise. Suppose a position remains

00:01:50.651 --> 00:01:54.027
open after you expected an exit. First identify the exact holding and

00:01:54.027 --> 00:01:57.403
context. Read the alert or condition information, look for a submitted or

00:01:57.403 --> 00:02:00.779
recorded action, and check for an interruption. If you choose to intervene

00:02:00.779 --> 00:02:04.155
later, review the relevant control and verify its result. Do not repeat

00:02:04.155 --> 00:02:07.531
an uncertain sell or change several unrelated settings just to make the

00:02:07.531 --> 00:02:08.375
screen look different.

00:02:08.875 --> 00:02:12.543
Keep a short record of what you found: the time, context, strategy

00:02:12.543 --> 00:02:16.211
or position, message shown, and any verified change. You can do that

00:02:16.211 --> 00:02:19.880
in your own notes. There is no need to expose an API

00:02:19.880 --> 00:02:23.548
key, secret, or private account information. If support is needed, these facts

00:02:23.548 --> 00:02:27.216
help explain the issue. They also help you distinguish a new problem

00:02:27.216 --> 00:02:29.050
from a result you already investigated.

00:02:29.550 --> 00:02:32.614
Before finishing, answer four questions. What have I allowed to run? Where

00:02:32.614 --> 00:02:35.678
can it act? What evidence shows what it has done? What would

00:02:35.678 --> 00:02:38.741
I check before stopping or resuming it? If you can answer those

00:02:38.741 --> 00:02:41.805
clearly, you understand the central meaning of automatic in TraderLobby. The app

00:02:41.805 --> 00:02:44.869
can carry out repeated work. You remain the person who understands its

00:02:44.869 --> 00:02:47.933
boundaries and checks its results. In the next chapter, we will look

00:02:47.933 --> 00:02:49.975
more closely at turning strategies on and off.