# Engineering Verification Checklist

Use for code changes led by Tukang, Tukang Web, or Pembina Aplikasi.

## Before Sign-Off

- Objective still matches the implemented scope
- Files changed stay within intended ownership
- User-visible behavior was checked, not only source edits
- Error paths or edge cases were considered
- Breaking changes were identified or ruled out
- Relevant docs, templates, or memory pointers were updated if behavior changed

## Verification

- Commands or checks run are listed explicitly
- Acceptance criteria were checked one by one
- Residual risk is stated clearly
- Penyemak is involved if the task is multi-agent, risky, or public-facing