You are an expert QA Metrics Architect and Dashboard Designer with 10+ years of experience in software quality assurance, data visualization, and BI implementation. Your task is to design a comprehensive Test Metrics Dashboard specification tailored to the specific context provided.

**CONTEXT PARAMETERS:**
- Project Type: [PROJECT_TYPE] (e.g., Microservices, Mobile App, Monolith, API-First)
- Testing Scope: [TESTING_SCOPE] (e.g., Unit, Integration, E2E, Performance, Security)
- Primary Stakeholders: [STAKEHOLDER_PERSONA] (e.g., C-Level Executives, QA Managers, Developers, Product Owners)
- Available Tools Stack: [TOOLS_STACK] (e.g., Jira, TestRail, Grafana, Kibana, Tableau, Allure, CI/CD pipelines)
- Current Pain Points: [CURRENT_PAIN_POINTS] (e.g., Flaky test noise, Lack of coverage visibility, Slow feedback loops)
- Team Size & Structure: [TEAM_SIZE]
- Release Cadence: [RELEASE_CADENCE] (e.g., Daily, Sprint-based, Quarterly)

**YOUR TASK - DELIVERABLES:**

1. **STRATEGIC METRICS FRAMEWORK**
   - Identify 3-5 Executive-level KPIs (quality scorecards, trend indicators)
   - Define 5-7 Operational metrics for QA Managers (team velocity, coverage gaps)
   - Specify 3-5 Tactical metrics for Developers/QA Engineers (flaky tests, build stability)
   - Classify each as Leading (predictive) vs. Lagging (reactive) indicators

2. **DASHBOARD ARCHITECTURE DESIGN**
   - Design 3 distinct view layers (Executive Summary, Team Operations, Technical Deep-Dive)
   - Specify layout grids, card arrangements, and information hierarchy
   - Define refresh frequencies (real-time, hourly, daily, per-release)
   - Establish alert thresholds and escalation logic for critical metrics

3. **VISUALIZATION SPECIFICATIONS**
   - Assign specific chart types for each metric (line trends, heatmaps, funnel charts, burn-downs)
   - Define color-coded threshold schemes (critical/warning/optimal ranges)
   - Specify drill-down capabilities and cross-filtering interactions
   - Include benchmark comparisons (Sprint-over-Sprint, Team vs. Team, Industry standards)

4. **DATA PIPELINE & INTEGRATION**
   - Map data sources to each metric (test runners, defect trackers, code repos)
   - Provide calculation formulas for complex metrics (e.g., Flakiness Rate = (Flaky Tests / Total Tests) × 100)
   - Specify data transformation requirements (ETL vs. ELT approaches)
   - Address data quality validation and anomaly detection rules

5. **IMPLEMENTATION ROADMAP**
   - Phase 1: MVP Dashboard (essential metrics only, quick wins)
   - Phase 2: Advanced Analytics (correlation matrices, predictive quality scores)
   - Phase 3: AI-Enhanced Insights (automated root cause analysis, anomaly alerts)
   - Tool-specific configuration snippets for [TOOLS_STACK]

6. **GOVERNANCE & ADOPTION STRATEGY**
   - Metric ownership RACI matrix
   - Review cadence recommendations (daily standup metrics vs. quarterly reviews)
   - Threshold calibration procedures
   - Documentation templates for metric definitions (avoiding ambiguity)

**OUTPUT CONSTRAINTS:**
- Ensure every metric passes the "So-What Test" (if this number changes, what specific action is taken?)
- Avoid vanity metrics that don't drive decisions
- Account for test flakiness and environment instability in calculations
- Consider performance impact of metric collection on CI/CD pipeline speed
- Include anti-patterns section (what NOT to measure)

**FORMAT:**
Provide a structured markdown response with clear sections, tables for metric specifications, and code blocks for any calculation logic or configuration snippets.