This is the Cival Darvas Box installation and research walkthrough. It is a strategy module, not a standalone dashboard. Match the manifest to a compatible two point one source edition. All six frameworks are included in Trader, and Darvas is also included in Core. Check your existing license before buying or installing another copy. Demo imagery is illustrative, not performance. 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. Before changing plugins, back up the database, configuration and plugin directory. Pause new entries and reconcile existing positions and open orders. Pausing an agent does not necessarily close a position. Do not run two independent engines against the same account. Keep the original archive and release notes so rollback remains possible. Extract the module so its manifest sits directly inside plugins slash darvas-indicator. Confirm that the compiled strategy entry exists in the dist folder. Do not leave the entire zip or an extra enclosing folder inside the plugin directory. Read the manifest compatibility and entry point, then restart the dashboard and inspect loader errors. Run the export check from the dashboard root. The expected message is strategy export present. This proves the module can load, not that it trades safely. Select the strategy identifier shown here, one supported interval and the intended market. Keep the new agent paused and unfunded. Retain the shipped defaults for the first comparison. Use completed four-hour candles. Retain the shipped box settings and record the top, bottom, age and volume ratio. Compare consolidation with a later breakout without sending an order. Twenty eight four-hour candles span one hundred and twelve hours, not four weeks. Inspect box boundaries and volume context. A short decision is not automatically a close-long instruction. Verify proposed protection prices and runtime ownership before execution. 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.