Four review perspectives
Each perspective has its own assignment and evidence. A self-check by the implementation author does not replace independent review.
- Behavior
- Check the agreed outcomes, affected callers, failure paths, and regression evidence.
- Coding standards
- Check repository conventions, maintainability, boundaries, and required checks.
- Security
- Check trust boundaries, permissions, sensitive data, and unintended external effects.
- UI/UX
- Inspect the rendered interface and exercise its interactions at relevant desktop and mobile widths. Source inspection alone cannot provide visual approval.
Who owns the work
These are responsibilities I assign to AI assistance, alongside my own role as the human owner. I retain ownership of scope and delivery decisions.
Human and AI responsibilities| Role | Responsibility |
|---|
| Human owner | I set the outcome, review scope and plans, authorize publication, and make the final engineering decisions. |
|---|
| Coordination assignment | An AI assignment carries context, keeps scope and approvals visible, and reconciles findings and evidence for my decision. |
|---|
| Implementation assignment | An AI assignment owns bounded code changes and developer checks against the reviewed spec. |
|---|
| Independent review assignments | Separate AI assignments assess behavior, coding standards, security, and UI/UX without approving their own implementation. |
|---|
| QA assignment | An AI assignment derives coverage from the requirements and actual changes, then creates or runs acceptance tests only within the approved QA scope. |
|---|
Readiness stays specific
Local readiness, publication, QA acceptance, merge, and deployment are distinct milestones. A passing local check does not prove a live integration or deployed behavior. I report the candidate, what was checked, and what remains unverified.
Development can end at a scoped handoff without entering formal QA. QA-only work follows its own reviewed plan and does not implement product fixes. Defects return to development, then come back for retesting. Merge and deployment follow the project’s own ownership and authorization rules.
I also curate evidence-backed lessons at handoff, distinguishing task-specific fixes from candidates for reuse. Updating persistent skills or guidance requires separate human review and approval.