LangDrift documentation

LangDrift defines a deterministic protocol for connecting intended product direction, the work that follows, and the evidence left by change.

Start here

• Set up the smallest local project
• Create a first artifact
• Understand Vision → Loop → Evidence
• Follow a Record into a Drift Event
• See what deterministic first means

Protocol at a glance

The canonical model is Vision → Loop → Evidence.

• Vision records intended direction through research, PRDs, and context.
• Loop connects that direction to triage, design documents, specs, and tickets.
• Evidence holds ADRs, audits, normalized Records, and Drift Events.

A Record is a normalized observed fact. A Drift Event is an interpretation of observed movement against a Vision Target, supported by Evidence. Drift is derived from the Loop; it is not a fourth pillar.

Current boundaries

Setup is local, explicit, non-destructive, and makes no network requests. Project and account IDs are routing metadata; creating the local scaffold does not create or authorize a remote account.