Architecture Review

Goal

Persist one repository-original Architecture Review Record that preserves confirmed scope, evidence, assumptions, Well-Architected pillar analysis, trade-offs, recommendations, reviewer dispositions, escalations, ADR links, and limits without becoming the architecture decision authority.

Flow

1. Confirm the review slug and the 2-3 focus areas selected by System Architecture Reviewer.
2. Resolve the record path as .copilot-tracking/reviews/architecture/{{YYYY-MM-DD}}/{{review-slug}}-architecture-review.md.
3. Read Architecture Review Record and create the record before framework evaluation begins.
4. Update the record progressively as evidence is gathered and each focus area is assessed.
5. For every confirmed focus area, record a finding, an examined area with no finding, or an explicit unassessed disposition and limit.
6. Record each material Research recommendation as accepted, revised, rejected, or deferred, with rationale and evidence IDs.
7. Link significant accepted decisions to their ADRs. Keep review analysis and sub-threshold trade-offs in the record; keep decision authority in the ADR and with the user.
8. Persist the completed record before invoking an ADR or RPI Plan handoff, and pass its workspace-relative path as the handoff evidence source.

Success Criteria