Workflow
NoDrift works best when planning, execution, review, approval, and handoff stay distinct. The user stays in control while the work session keeps the record clear.
Start with the actual project, not a foggy prompt.
Workflow problem: AI work gets messy when the session begins without the real task, current goal, and immediate priority.
NoDrift answer: NoDrift starts the session by naming the active task and what matters now, so the AI does not begin by guessing the project shape.
Start Clear
The work begins by identifying the current objective, the relevant project state, and the next bounded task before asking the AI to move.
Useful ideas should not quietly become today's work.
Workflow problem: AI can turn one useful request into extra features, side quests, and future work before the user notices.
NoDrift answer: NoDrift keeps the active boundary visible so today’s work stays inside the approved objective.
Set Boundary
Boundaries define what can move now, what should wait, and what requires a separate decision before it becomes part of the session.
Chat memory is not source truth.
Workflow problem: A model can remember something said earlier and treat it as if it were verified project reality.
NoDrift answer: NoDrift uses project files, records, and approved materials as the authority. Chat memory can help orient the conversation, but it does not prove what is true.
Use Source Truth
Source truth keeps the session tied to actual project materials instead of remembered summaries, assumptions, or confident reconstruction.
The session needs a way back to governance while it works.
Workflow problem: Drift, over-effort, wordiness, stubbornness, unsupported certainty, and risky project events can build up before the user gets a clean stop point.
NoDrift answer: NoDrift uses programmed governance Heartbeats and behavioral Heartbeats to route the session back to the right rules, source truth, approval boundary, and correction path.
Run Heartbeats
Heartbeats are governance refreshes and correction routes. They do not control the model, run as hidden background automation, or grant permission for action.
Confident output is not the same as checked truth.
Workflow problem: AI can make a statement sound finished, verified, or complete before the evidence supports it.
NoDrift answer: NoDrift separates claims from evidence so broad statements wait until the checked record supports them.
Check Claim
Claims about completion, readiness, public safety, or coverage stay bounded by what was actually checked.
A suggestion waits for a real yes.
Workflow problem: AI can move from recommending an action to performing it as if permission was already granted.
NoDrift answer: NoDrift keeps consequential moves waiting for explicit user approval of the exact next step.
Ask Approval
Approval applies to the bounded task the user actually approved, not to every adjacent action the AI can imagine.
The approved change should stay inside the approved task.
Workflow problem: Implementation can drift while the AI is editing, expanding, or “improving” beyond the request.
NoDrift answer: NoDrift keeps the change tied to the approved directive so work does not silently widen.
Make Change
The session performs the approved work while preserving the boundary, source truth, and current decision state.
The result must be checked against what actually changed.
Workflow problem: AI can report success based on intention, assumption, or a narrow check that does not prove the result.
NoDrift answer: NoDrift verifies the actual changed surface and reports what was checked, what passed, and what remains limited.
Verify Result
Verification keeps the user from relying on a clean summary when the checked evidence is narrower than the claim.
The same error should stop coming back.
Workflow problem: AI often apologizes, fixes the immediate output, and then repeats the same source mistake later.
NoDrift answer: NoDrift names the drift, records the correction, and keeps the source problem visible for future sessions.
Apply Correction Protocol
Correction protocol handles the cause of the mistake, not only the sentence or file where the mistake appeared.
Separate work needs its own record.
Workflow problem: New objectives, risks, source sets, or decisions can get mixed into the main task until the project becomes hard to follow.
NoDrift answer: NoDrift branches meaningful side paths so the main work stays clean and the new path keeps its own context.
Branch When Needed
Branching preserves useful work without letting it blur the active decision path or confuse the project record.
Proof should stay connected to the claim.
Workflow problem: Evidence, limits, and open questions can get separated from the statements they support.
NoDrift answer: NoDrift records what supports a claim, what does not, and what remains unresolved.
Record Evidence
Evidence records make it easier to see why a claim is safe, limited, blocked, or still only proposed.
The next session should not start from scratch.
Workflow problem: Long AI projects lose time when every new session has to rebuild decisions, status, risks, and next steps.
NoDrift answer: NoDrift carries forward the working record so the next session resumes from what was actually decided and checked.
Carry Forward
Carryover keeps continuity usable across pauses, new chats, compressed history, and handoffs.
Heartbeat System
NoDrift uses two related Heartbeat systems. The programmed Heartbeats are trigger-based governance refreshes. The behavioral Heartbeats are named checks that can be user-triggered or assistant-initiated as a self-audit.
The programmed system has 12 trigger categories: startup, phase change, readiness or completion, public/private boundary, external action, package/build/release, payment/delivery, context or compaction, source conflict, error or correction, token burn-rate, and website/campaign claims.
The behavioral system has 6 checks: drift, truth/source, effort, brevity, stubbornness, and governance operation. A separate carryover Heartbeat protects session handoff and continuation.
When a behavioral Heartbeat is triggered by the user or initiated as a self-audit, it routes into correction protocol. The assistant should name the issue, stop the drift or unsafe pattern, restore the approved boundary, identify the next safe action, and record the correction where the project record requires it.
AI speed still needs a checked plan.
Story problem: Lena promised a Friday preview because AI assistance made the timeline seem reasonable.
NoDrift answer: NoDrift keeps goals, source authority, and known boundaries visible before work expands into a promise the project may not support.
Plan Before Implementation
During planning, the user can ask for questions, understanding, and an outline before file work begins. Goals, source authority, and known boundaries should be clear before the work starts changing files or making broad claims.
Boundaries should not need to be repeated all morning.
Story problem: Lena spent thousands of tokens restating the same limits: no uploads, no payment integration, and no extra analytics.
NoDrift answer: NoDrift keeps the active workstream centered on the approved objective, so repeated detours do not keep pulling the project away from today's work.
Keep One Primary Workstream
Long projects stay clearer when one main objective holds the active track. Useful tangents should be preserved in separate workstreams rather than mixed into the main line until earlier decisions become hard to recover.
Approval Applies To The Approved Task
NoDrift uses explicit approval for the approved task, not a vague atmosphere of permission. Consequential actions stay explicit enough that the project owner remains in control, and external or destructive actions are not implied by general access.
A passing result is not proof of the whole system.
Story problem: The tests passed because mock data matched a false structure.
NoDrift answer: NoDrift keeps the real source, scope, and unchecked areas visible before a clean result is treated as proof.
Verify Before Broad Claims
When the AI Orchestrator says every page, all files, complete, ready, verified, public-safe, or publish-safe, NoDrift expects evidence showing what was actually read, searched, changed, tested, or left unchecked. Targeted searches and spot checks can support a review, but they do not prove full coverage by themselves.
A bad assumption should not become the next person's starting point.
Story problem: Marcus's wrong assumption could become Ethan's working foundation.
NoDrift answer: NoDrift preserves what is known, what is only proposed, and what still needs checking before another person continues.
Phase-two work should not leak into today's build.
Story problem: The assistant forgot that document uploads had been delayed until phase two.
NoDrift answer: NoDrift preserves current decisions and project boundaries so postponed features stay postponed until the user approves changing the scope.
Preserve Continuity Before Handoff
Important status, wording, decisions, risks, and next actions should survive pauses, new chats, or compressed history. NoDrift treats continuity as a working requirement, not a nice extra after the fact.