Choose the right storage location and verify each stage of Waker configuration and operation.
Choose the right storage location by content purpose: put working files in the project directory, stable reference materials in the knowledge base, long-term preferences in memory, and one-time requirements in the current conversation or run input.
Credentials must only be entered in protected authorization or configuration entry points. Never write them into profiles, knowledge bases, memory, conversations, or business logs. Re-verify after every significant change.
| Stage | Must-check items |
|---|---|
| Creating or modifying a Waker | Responsibilities, inputs, outputs, and boundaries are clear; bind only the required capabilities; validate with both normal and out-of-scope tasks |
| Starting a conversation | Waker, device, and working directory are correct; specify the goal, scope, output, and acceptance criteria; inspect deliverables when done |
| Launching an automated task or WakerFlow | Manually verify both the success and failure paths first; keep human confirmation for external writes; then enable the trigger |
| Updating knowledge, permissions, or connectors | Clean up outdated materials and check the access scope; start with read-only, least-privilege; verify with a new conversation |
| Updating the application | Verify the running version; do a small-scale trial run for critical tasks |