EVIDENCE LANE / PRODUCT

Inside an Evidence Lane
project.

One connected project. Separate records for its plan, conversations, sources and results. Open a glass orb to explore the responsibility of each.

Open a node to inspect its own detail.

01 / Separate records

Every record has
a responsibility.

The Plan owns the work. Memory retains context. Learning records useful procedures. Their references connect the project while their data remains separate.

Open a node to inspect its own detail.

Separate records. Explicit links. One project.

02 / Source collections

Your material.
Its own source trail.

Code, documents, data and research enter through their own source paths. Choose a material to inspect what it contributes and the tools its operations declare.

Open a node to inspect its own detail.

03 / Read, steer or execute

A question. A change.
A next step.

Reading evidence, changing the Plan and carrying out work have different effects. Choose an intention to see what happens to the project.

Open a node to inspect its own detail.

A question keeps the Plan unchanged.
A steer revises the affected work.
Execution follows the selected task.

04 / Three locations

Source files. Project records.
Shared runtime.

Your material, the project’s persistent records and the shared local engine have different homes. Their connections do not combine them into one store.

Open the centre cube or either location.

Persistent local Windows · Codex Desktop Stable & Beta

05 / The Studio observer

See the work.
Follow its evidence.

Studio presents the engine’s observations. Open a view to see the information it shows. Direct project changes through Codex.

Open a node to inspect its own detail.

View, navigate, open, minimise and restore.
Direct project changes through Codex.