Troubleshooting
Use troubleshooting when something seems wrong in the active NoDrift workspace. The goal is to pause forward work, narrow the problem, inspect only what is needed, and choose the next safe step.
Start With The Trigger
When something seems wrong while work is already in progress, type troubleshooting in the AI Orchestrator. That trigger should shift the session out of forward execution and into diagnosis.
What The AI Orchestrator Should Do
After the trigger, the AI Orchestrator should pause normal work, identify the symptom, narrow the scope, inspect only what is relevant, explain what it found, and end with one clear next directive. It should not turn diagnosis into silent repair work.
Common Problem Areas
Use troubleshooting when the workspace may be in the wrong folder, startup may have happened out of order, rules seem to be slipping, a claim sounds too complete, continuity feels broken, public and private material may be mixed, or GitHub, local preview, and live publication state are unclear.
Approval Still Matters
Troubleshooting can inspect within scope, but consequential changes still require approval. The AI Orchestrator should ask before changing, moving, deleting, restoring, publishing, pushing, uploading, or editing anything that matters.
Protected Diagnostic Detail
Exact diagnostic prompts, private checklists, and detailed workspace inspection sequences stay inside the buyer workspace.