Review Architecture Task

Problem

A Rails team needs help with a task in this area:

Use when reviewing Rails application structure or architecture — must prioritize boundary problems over style, evaluate where domain logic lives, and for every High-severity finding verify it by reading the actual code and stating the concrete code-level evidence read (redacting any secret-like literal, without using representative file paths or fabricated line numbers).

The team has asked for a concise implementation artifact that a reviewer can inspect without needing to observe the agent's process.

Output

Create answer.md with:

• a short plan for the work
• the concrete Rails-oriented artifact or recommendation
• the verification steps or quality gates that should be run
• any assumptions that affect the result