EVIDENCE LANE / GET STARTED

Project setup

Establish exact source and state locations, then create or inspect the complete current Plan.

Keep sources and state separate

Source files remain in their selected locations. Project state belongs in a separate explicitly selected durable local root. Each owning authority and source lane has its own database and files.

Selected SQLite is a bounded source-reading capability. It is not a request to merge all project data into one database.

Register sources with identity

Select the exact ordered sources and inspect their current identities. Registration does not index or process them. Prepare bounded source tasks and run the appropriate operations when processing is requested.

Example: “Register these selected documents for this project, show the planned source preparation and disclose any unsupported formats.”

Establish the Plan

The Plan is a complete ordered sequence with task scope, dependencies, required tools and acceptance checks. One revision is current. A semantic steer checkpoints affected work and updates the appropriate future tasks while preserving completed history.

Inspect the selected project

Read the current project/session binding, Plan and evidence. A folder name, process ID or connected client label alone is not proof of exact native task identity.