EVIDENCE LANE / GET STARTED

Installation

The plugin comes first. The shared engine, Studio and local tools follow its first-detection route.

Supported host

The current source contracts target persistent local Windows with Codex Desktop Stable or Beta. Windows Studio is the visible read-only observer.

An explicitly configured authenticated API is a transport choice within the supported profiles; it does not establish CLI, ephemeral VM, macOS or Linux support.

Plugin-first sequence

Use the release selected for installation and the supported Codex plugin installation flow. Follow that release’s instructions rather than inventing a command from the package name.

  1. Verify the release identity and published assets.
  2. Install the managed Evidence Lane plugin.
  3. Allow first detection to provision the declared shared bundle and verify its bytes.
  4. Read back the engine connection and open Studio.
  5. Select the project through Codex and inspect its binding.

Shared runtime and project state

The default shared installation root is C:/Apps/EvidenceLaneStudio. EVIDENCE_LANE_STUDIO_ROOT is the explicit installation override. Shared dependencies are installed once; project databases and credentials are not release payloads.

Each project has its own separate state root. External services still need their own configuration and bounded grants. Licensed and hardware-specific operations have additional requirements.

If setup stops

Preserve the reported failure and exact release identity. Distinguish a download/checksum failure, incomplete provisioning, an unavailable engine and a disconnected client. Do not label a partial bundle ready or silently replay an uncertain operation.