atlas-verify
Atlas Verify
For verification requests such as “run QA,” select Behavior, UI Stress or Performance from the task and its material risks, honoring an explicit method choice. Combine methods only when each adds distinct proof; reuse shared evidence rather than repeat checks. Briefly state the selection. Read the selected methods before planning checks or collecting verification evidence, then follow them.
| Method | When it applies | Read and follow |
|---|---|---|
| Behavior | Verify implemented behavior, smoke/regression checks or a QA list; default for “verify this” | Behavior |
| UI Stress | Exercise a component or screen with realistic worst-case data, empty and extreme states | UI Stress |
| Performance | A speedup, regression, benchmark claim or material performance risk needs measured evidence | Performance |
“Create a verification for this feature” means Behavior unless the requested outcome is reusable verification assets. For asset creation or maintenance, suggest the manually invoked Atlas Verifiers skill. A missing project verifier does not add that work to behavior verification.
Verification does not authorize product repairs or optimization. Behavior, UI Stress and standalone Performance produce temporary evidence. UI Stress may build an isolated harness and fixtures while product source and live data stay unchanged. Behavior owns the structured report contract. Other methods retain their own deliverables and use that report only when requested or contributing to a Behavior report. Performance within Behavior uses the same measurements as evidence, without repeating the experiment.