System Boundaries
NoDrift governs the work session. It does not control the model, and it is only one layer of the full operating environment.
Reception-Side Governance
NoDrift does not change the LLM or guarantee every answer is true. Its job is to govern reception: what the work session accepts, checks, records, corrects, rejects, or acts on after output arrives.
Not Hidden Monitoring Software
NoDrift is not hidden surveillance software, a dashboard, a file watcher, an offline evaluator, a local RAG system, a dry-run cache, a simulator, or a diff viewer. It works through protected workspace materials used inside the active project workspace.
Not Outgoing Attachment Logic
NoDrift does not attach its protected workspace files to outgoing messages or conversation turns. The protected materials stay in the workspace and guide what the active session checks before sensitive claims or actions move forward.
Decision Points Matter
The controls are applied at decision points: when a task begins, before files are inspected, before a factual claim is made, before edits are made, before old context is reused, before external action, and after work is finished for verification.