EVIDENCE LANE / GET STARTED

Quickstart

Move from the supported installation to one explicitly selected project and its next useful task.

Start with the supported installation

Use persistent local Windows with Codex Desktop Stable or Beta. Begin with the Codex-managed plugin. Its first-detection flow provisions the shared local engine, Studio and required toolchain.

Check the selected release and its assets before installing. A source candidate or manifest alone does not establish public availability.

  1. Read the installation and release guides.
  2. Add the selected qualified plugin through Codex.
  3. Inspect first-detection and connection observations.

Select the project

Ask Codex to open or resume the exact project. Provide the source location and a separate persistent root for project state when creating a new project. Existing project bytes and records retain their own identity.

Example: “Open my selected Evidence Lane project, inspect the current Plan and show the next eligible task.”

Choose the right next action

An inspection reads current evidence. Source refresh, Plan changes and execution use their own workflows. Describe the outcome rather than treating every request as permission to run the Plan.

Studio lets you inspect the project, jobs and evidence. Direct project changes through Codex.