System Architecture Degradation Escalation Checklist

Role: Lead Solutions Architect and Enterprise Technical Account Lead

Context

• Client Infrastructure Stack: {{client_infrastructure}}
• Observed Bottleneck: {{observed_bottleneck}}
• Historical Performance Baselines: {{benchmark_baselines}}
• Applied Interim Mitigations: {{interim_mitigations}}
• Key Enterprise Stakeholders: {{key_stakeholders}}
• Escalation Trigger Event: {{escalation_trigger}}

Task

Produce an architectural escalation verification checklist to coordinate diagnostic discovery, infrastructure profiling, and executive alignment between customer architects and core system engineers.

Method

1. Evaluate {{observed_bottleneck}} against {{benchmark_baselines}} to quantify the degradation magnitude.
2. Review {{applied_interim_mitigations}} to identify what temporary fixes have already failed or succeeded.
3. Map {{client_infrastructure}} components to likely points of contention (e.g., I/O, locks, memory leaks).
4. Build pre-escalation telemetry auditing checks for deep infrastructure profiling.
5. Construct mitigation validation checks to safeguard system stability during ongoing triage.
6. Formulate cross-functional alignment checks tailored for {{key_stakeholders}}.
7. Define explicit criteria for closing the architectural escalation and entering root cause analysis.

Constraints

• Items MUST specify the exact architectural layer being tested (e.g., network, persistence, compute).
• MUST NOT recommend destructive profiling commands without rollback verification.
• Include explicit ownership labels for each checklist category.
• Keep checklist clear and execution-focused for immediate architectural triage.

Output format

1. Escalation Brief & Trigger Overview

• Concise summary of the architectural bottleneck and escalation context.

2. Infrastructure Profiling & Audit Checklist

• 4-6 markdown checkboxes [ ] covering metric baselines and profiling state.

3. Mitigation & Workaround Validation Checklist

• 3-5 markdown checkboxes [ ] auditing active failovers and cache rules.

4. Enterprise Stakeholder Alignment Checklist

• 3-4 markdown checkboxes [ ] establishing cadence and communication rules.

Self-review

• Verify that infrastructure layers from {{client_infrastructure}} are addressed.
• Confirm the checklist directly accounts for {{escalation_trigger}}.
• Ensure all 6 template variables are present and logically integrated.