General checks for creating, running, and maintaining QoderWake.
Choose the storage location according to the purpose of the content: work files are placed in the project directory, stable data is placed in the knowledge base, long-term preferences are placed in memory, and one-time requests are placed in the current chat or run input.
Credentials may only be filled in protected authorization or configuration portals and may not be written to profiles, knowledge bases, memories, chats or business logs. Revalidate after every important change.
| When | What to check |
|---|---|
| Create or modify a Waker | Responsibilities, inputs, outputs, and boundaries are clear; only necessary capabilities are enabled; normal and out-of-scope tasks both behave as expected. |
| Start a chat | The correct Waker, device, and working directory are selected; the request states its goal, scope, expected output, and acceptance criteria; the result is reviewed. |
| Launch Autonomous Work or WakerFlow | Success and failure paths have been tested manually; external writes still require confirmation where appropriate; triggers are enabled only after validation. |
| Update knowledge, permissions, or connectors | Outdated information is removed; access is restricted to the minimum required scope; the change is verified in a new session. |
| Update the application | The running version is confirmed and key tasks pass a small-scope test. |