Welcome to the Cival Trader Edition setup walkthrough. This is editable, self hosted source software. Hosting, venue funds and paid provider services are separate. The screens in this lesson are illustrative demo captures; your installed release may differ. Follow the version-specific manual alongside the video. We will install safely, verify access, inspect a paused agent and plan recovery without sending a live order. Sign in to the same verified account used at checkout. Open Account and locate the confirmed order. Generate a fresh Download link. Save the archive, receipt and release version together. Compare its SHA two fifty six with your product guide. Extract into a new directory. If fulfillment is pending, wait or contact support; do not purchase again. This lesson follows the September twenty eight source release. Check the version in your own archive first. The two point one edition needs Node twenty two, version twenty two point three or newer, a dedicated Supabase project, and PostgreSQL client tools. A plain database does not replace Supabase Auth and REST. Use the shipped lockfile and the matching manual. Read the environment example before entering values. Copy it to dot env dot local. Configure the verified account owner, require authentication, the administrator token, the database connection, and the exact Supabase settings listed in the archive. Keep server role credentials server side. Leave signing keys blank and retain paper mode during installation. Never record, upload or commit your private environment file. Run these commands in order from the dashboard root. Install the locked dependencies, initialize the database, run type checks and tests, build, then start. Database initialization checks migration integrity and owner configuration. If any command fails, stop and retain a redacted diagnostic. Do not suppress errors or import an unrelated schema to force the next step. For this source release, open local host on port nine thousand five. Sign in as the configured owner. Then use a separate signed out session and confirm unauthorized access is refused. Save a harmless setting, restart, and confirm it persists. Keep the service local until authentication, private service bindings and any remote HTTPS proxy are verified. Open Agents and select an installed strategy. Choose one market and a supported interval. Name the agent clearly and keep it paused and unfunded. Save the configuration and reload. In an isolated research or verified paper path, inspect a decision from completed candles. Record its timestamp, direction, reasoning and confidence. A neutral decision is a valid result, not an error. Trader includes six frameworks. Confirm all six strategy identifiers shown here appear in the loader. Do not install another copy of an included module. Compare each framework with the same recorded inputs before combining budgets. Six available strategies do not prove that six simultaneous venue positions are independently safe. Track which runtime owns every position. Pause and restart the application. Confirm the same owner, strategy and settings return. Test a backup restore in an isolated compatible instance. Before real money or unattended operation, separately validate entry fills, protection, changes, exits, fees and reconciliation on testnet, including lost responses and restart recovery. A database restore cannot reverse a venue trade. Keep the original release and redacted evidence.