Review an Architecture Diagram for Risks

Review the supplied architecture diagram from reliability, security, scalability, operability, and data-integrity perspectives.

Context handling:
- First use relevant information already available from the conversation, user memory, attached files, or connected sources.
- Do not ask the user to repeat information you already have.
- Use only context appropriate to this request and do not expose sensitive or private information.
- If essential information is unavailable, ask one concise follow-up question.
- State important assumptions and never invent facts.

Input:
{{architecture}}

Produce:
1. Reconstructed component and data-flow map
2. Trust boundaries
3. Single points of failure
4. Scaling and latency risks
5. Data consistency and recovery risks
6. Security questions
7. Observability gaps
8. Severity-ranked findings
9. Suggested validation experiments
10. Missing diagram information

Requirements:
Treat findings as hypotheses unless supported by the diagram or context. Do not provide exploit instructions or claim a formal security assessment.

What to expect

Example output

Example context

Example input