Simple Trigger
If something goes wrong while already working in a NoDrift workspace, use the troubleshooting trigger inside the AI Orchestrator. The guided review is meant to pause forward work and narrow the issue before changes happen.
When something seems wrong inside a NoDrift workspace, troubleshooting starts inside the AI Orchestrator, where the working context and protected workspace materials are present.
If something goes wrong while already working in a NoDrift workspace, use the troubleshooting trigger inside the AI Orchestrator. The guided review is meant to pause forward work and narrow the issue before changes happen.
Use support when the workspace may be in the wrong folder, startup feels out of order, continuity has broken down, a claim sounds too complete, or public and private material may be mixed.
Diagnostic materials and checklists stay inside the workspace. Consequential changes such as delete, move, overwrite, publish, push, upload, or send still need approval.
Troubleshooting starts where active context and protected materials are present, including setup, continuity, and verification context.
Diagnosis can narrow the problem, but changing, moving, deleting, restoring, publishing, pushing, uploading, or editing still needs approval.
Contact remains the route for package questions, edge cases, or anything too specific for the guided troubleshooting flow.