Documentation

NoDrift Docs

Startup, governance distinctions, workflow, evidence, correction, support, and approval boundaries are gathered here in one technical reference set.

Preset Searches

Overview

What NoDrift is, what problem it solves, and how governed AI project work stays under control.

How installation and first use begin, why the first pass stays light, and what gets configured later.

The distinctions behind project truth, approval, permission, continuity, evidence, and reception-side governance.

The working rhythm behind planning, approvals, execution, verification, and continuity across long projects.

What NoDrift does not claim to be, change, automate, or silently control.

How communication style, work leadership, explanation depth, and evidence labeling can change without weakening safeguards.

How dated snapshots, counts, candidate status, issue groups, and coverage limits stay visible together.

The six public-safe issue groups, why candidate incidents stay labeled, and how correction paths are described.

The review route for serious readers who want product reality, evidence context, software boundaries, and current claims.

How to trigger diagnosis, narrow the problem, and keep consequential changes behind approval.

The shortest route to startup, concepts, review surfaces, support, and the main-site connections.

The edits, claims, external actions, and destructive changes that still require explicit approval.

The limits of the system, the evidence, and the claims that should never be inferred too broadly.