Architecture Red Team

Overview

Challenge a proposed system shape before implementation deepens its commitments. Keep the review read-only, evidence-grounded, and focused on system failure rather than local code style.

Boundary

• Trigger only when explicit adversarial, red-team, first-principles, or quality-gate intent targets a software architecture, system design, ADR, or cross-cutting technical proposal.
• Do not use for ordinary code review, routine design feedback, implementation, or open-ended brainstorming.
• Remain read-only even when the request also asks to fix findings. Do not edit or modify files, apply patches, stage changes, commit, or revert during the review.
• A combined “review, then fix” request is not a separate remediation request. Treat its mutation step as out of scope, end the turn after the verdict, and wait for a later user turn before changing anything.
• Give architectural correction directions. Do not turn the review into an implementation plan unless the user requests one in that later turn.

Workflow