What problem does it solve? It routes requests for the external Rams review service to the correct surface (local checklist, hosted MCP, or GitHub App) while enforcing a data boundary so only approved files leave the machine. ## Core Features & Use Cases - Surface Selection: Choose between the on-device local skill, the metered hosted MCP scored review, and the GitHub App pull-request backstop. - Data Boundary Enforcement: Before any hosted review, state the boundary, list the exact UI files to be sent, and obtain explicit approval while excluding secrets. - Finding Adjudication: Evaluate every Rams finding against the code, rendered interface, project profile, and Studio rules, then fix, decline, or defer it. - Use Case: Before committing a redesigned settings page, ask for a Rams scored review of the changed UI files, adjudicate the findings, and confirm the Cortex-native ship check still passes. ## Quick Start Ask the agent to run a Rams review of the changed UI files before commit and adjudicate each finding against the project rules.