WEBVTT

1
00:00:00.250 --> 00:00:05.999
Welcome to the Cival Core Edition setup walkthrough. This is editable, self hosted source software.

2
00:00:05.999 --> 00:00:11.747
Hosting, venue funds and paid provider services are separate. The screens in this lesson are

3
00:00:11.747 --> 00:00:17.496
illustrative demo captures; your installed release may differ. Follow the version-specific manual alongside the video.

4
00:00:17.496 --> 00:00:23.245
We will install safely, verify access, inspect a paused agent and plan recovery without sending

5
00:00:23.245 --> 00:00:28.993
a live order.

6
00:00:29.993 --> 00:00:36.150
Sign in to the same verified account used at checkout. Open Account and locate the

7
00:00:36.150 --> 00:00:42.306
confirmed order. Generate a fresh Download link. Save the archive, receipt and release version together.

8
00:00:42.306 --> 00:00:48.463
Compare its SHA two fifty six with your product guide. Extract into a new directory.

9
00:00:48.463 --> 00:00:54.619
If fulfillment is pending, wait or contact support; do not purchase again.

10
00:00:55.619 --> 00:01:01.856
This lesson follows the September twenty eight source release. Check the version in your own

11
00:01:01.856 --> 00:01:08.092
archive first. The two point one edition needs Node twenty two, version twenty two point

12
00:01:08.092 --> 00:01:14.329
three or newer, a dedicated Supabase project, and PostgreSQL client tools. A plain database does

13
00:01:14.329 --> 00:01:20.565
not replace Supabase Auth and REST. Use the shipped lockfile and the matching manual.

14
00:01:21.565 --> 00:01:27.314
Read the environment example before entering values. Copy it to dot env dot local. Configure

15
00:01:27.314 --> 00:01:33.063
the verified account owner, require authentication, the administrator token, the database connection, and the exact

16
00:01:33.063 --> 00:01:38.811
Supabase settings listed in the archive. Keep server role credentials server side. Leave signing keys

17
00:01:38.811 --> 00:01:44.560
blank and retain paper mode during installation. Never record, upload or commit your private environment

18
00:01:44.560 --> 00:01:50.309
file.

19
00:01:51.309 --> 00:01:58.046
Run these commands in order from the dashboard root. Install the locked dependencies, initialize the

20
00:01:58.046 --> 00:02:04.784
database, run type checks and tests, build, then start. Database initialization checks migration integrity and

21
00:02:04.784 --> 00:02:11.522
owner configuration. If any command fails, stop and retain a redacted diagnostic. Do not suppress

22
00:02:11.522 --> 00:02:18.260
errors or import an unrelated schema to force the next step.

23
00:02:19.260 --> 00:02:25.769
For this source release, open local host on port nine thousand five. Sign in as

24
00:02:25.769 --> 00:02:32.277
the configured owner. Then use a separate signed out session and confirm unauthorized access is

25
00:02:32.277 --> 00:02:38.785
refused. Save a harmless setting, restart, and confirm it persists. Keep the service local until

26
00:02:38.785 --> 00:02:45.294
authentication, private service bindings and any remote HTTPS proxy are verified.

27
00:02:46.294 --> 00:02:52.995
Open Agents and select an installed strategy. Choose one market and a supported interval. Name

28
00:02:52.995 --> 00:02:59.695
the agent clearly and keep it paused and unfunded. Save the configuration and reload. In

29
00:02:59.695 --> 00:03:06.395
an isolated research or verified paper path, inspect a decision from completed candles. Record its

30
00:03:06.395 --> 00:03:13.096
timestamp, direction, reasoning and confidence. A neutral decision is a valid result, not an error.

31
00:03:14.096 --> 00:03:20.318
Pause and restart the application. Confirm the same owner, strategy and settings return. Test a

32
00:03:20.318 --> 00:03:26.541
backup restore in an isolated compatible instance. Before real money or unattended operation, separately validate

33
00:03:26.541 --> 00:03:32.763
entry fills, protection, changes, exits, fees and reconciliation on testnet, including lost responses and restart

34
00:03:32.763 --> 00:03:38.985
recovery. A database restore cannot reverse a venue trade. Keep the original release and redacted

35
00:03:38.985 --> 00:03:45.207
evidence.