WEBVTT

1
00:00:00.600 --> 00:00:05.035
From your hosting account, choose Configure agents to open the workspace

2
00:00:05.035 --> 00:00:05.528
loadout.

3
00:00:05.728 --> 00:00:08.416
Review the plan's strategy slot limit.

4
00:00:08.616 --> 00:00:11.859
This Solo example has zero of one selected.

5
00:00:12.059 --> 00:00:16.347
A strategy described as available is not already installed.

6
00:00:16.547 --> 00:00:21.481
The existing legacy test agent on our dashboard does not establish that a

7
00:00:21.481 --> 00:00:24.184
new catalog strategy has been installed.

8
00:00:24.384 --> 00:00:29.397
Treat the loadout and the runtime agent list as separate states to verify.

9
00:00:30.247 --> 00:00:35.025
Add one instance of the strategy you intend to configure and enter a

10
00:00:35.025 --> 00:00:36.711
supported market symbol.

11
00:00:36.911 --> 00:00:42.130
Our unsaved demonstration selects Darvas with B T C to show the field,

12
00:00:42.130 --> 00:00:43.994
not to recommend a trade.

13
00:00:44.194 --> 00:00:48.354
Verify symbol support and the strategy's requirements first.

14
00:00:48.554 --> 00:00:51.306
Adding instances consumes plan capacity.

15
00:00:51.506 --> 00:00:55.522
Where multiple instances are allowed, follow the distinct market

16
00:00:55.522 --> 00:00:57.906
requirements displayed by the loadout.

17
00:00:58.106 --> 00:01:01.605
We discarded this demonstration draft without saving it.

18
00:01:02.455 --> 00:01:04.652
Read the notice before Save loadout.

19
00:01:04.852 --> 00:01:08.863
Cival says saving records your authorization and is audited.

20
00:01:09.063 --> 00:01:12.604
The host installs the selected strategies separately.

21
00:01:12.804 --> 00:01:17.770
Installed means the strategy was loaded, not that an agent is funded or

22
00:01:17.770 --> 00:01:18.329
trading.

23
00:01:18.529 --> 00:01:22.071
Save only when the wallet owner intends this deployment.

24
00:01:22.271 --> 00:01:25.663
Then wait for installation and verify its status.

25
00:01:25.863 --> 00:01:30.640
Do not keep resubmitting a request merely because the dashboard has not

26
00:01:30.640 --> 00:01:31.985
updated immediately.

27
00:01:32.835 --> 00:01:35.993
In the dashboard, open Agents and choose Create.

28
00:01:36.193 --> 00:01:41.439
This captured dialog correctly blocks creation because no strategy from the

29
00:01:41.439 --> 00:01:43.467
hosting loadout is installed.

30
00:01:43.667 --> 00:01:48.147
Use Manage strategy slots to return to the workspace when you see that

31
00:01:48.147 --> 00:01:48.659
message.

32
00:01:48.859 --> 00:01:53.617
After installation, select the intended installed strategy and market.

33
00:01:53.817 --> 00:01:59.001
The dialog says new agents and farms start paused with no funds allocated.

34
00:01:59.201 --> 00:02:04.540
Verify that result yourself; this video does not show a completed agent

35
00:02:04.540 --> 00:02:05.217
creation.

36
00:02:06.067 --> 00:02:10.504
Open the agent's details and inspect its actual configuration.

37
00:02:10.704 --> 00:02:15.333
Confirm the strategy, allowed market, allocation, and risk controls.

38
00:02:15.533 --> 00:02:20.926
Our existing test agent shows dashes for several fields, including stop loss

39
00:02:20.926 --> 00:02:22.061
and take profit.

40
00:02:22.261 --> 00:02:26.800
Do not interpret a dash as an active protection or invent a value

41
00:02:26.800 --> 00:02:29.173
that the system has not confirmed.

42
00:02:29.373 --> 00:02:34.041
Keep the new agent paused until its effective settings and venue permissions

43
00:02:34.041 --> 00:02:34.963
are understood.

44
00:02:35.163 --> 00:02:39.621
Enabling trading is a separate decision, not part of this recording.