EVIDENCE LANE / REFERENCE

Repository overview

Evidence Lane connects project workflows, source evidence and lane-specific tools through a persistent engine.

The product surfaces

Codex provides the interaction and public skills. SDK/MCP typed actions reach the engine. The engine owns operation coordination and project state. Studio is the read-only Windows observer.

Separate project records

The Plan, conversation lineage, instructions, project memory, procedural learning, source evidence and receipts preserve distinct purposes and attribution. References connect them without flattening their storage or authority.

Source versus runtime evidence

This site describes inspected source contracts. A source build, protocol test, installation receipt, active connection and native execution each establish different facts. See the release guide for the current website snapshot.