nw-sa-critique-dimensions

# Architecture Quality Critique Dimensions ## Dimension 1: Architectural Bias Detection ### Technology Preference Bias Pattern: tech chosen by preference, not requirements. Detection: ADR lacks comparison matrix, choice not mapped to requirements, justified only as "best practice." Severity: HIGH. ### Resume-Driven Development Pattern: complex/trendy tech without requirement justification. Examples: microservices for 3-person team, Kafka for 100 req/day, service mesh without complexity. Detection: complexity exceeds team size/requirements, tech adds resume value not solves problem. Severity: CRITICAL. ### Latest Technology Bias Pattern: unproven tech (<6 months, small community) for production. Detection: check maturity, community, LTS, fallback plan. Severity: HIGH. ## Dimension 2: ADR Quality Validation ### Missing Context ADR lacks business problem, technical constraints, or quality attribute requirements. Future maintainers cannot validate. Severity: HIGH. ### Missing Alternatives Analysis No alternatives (min 2 required). Each must be evaluated against requirements with rejection rationale. Severity: HIGH. ### Missing Consequences Omits positive/negative consequences and trade-offs. Quality attribute impact not analyzed. Severity: MEDIUM. ## Dimension 3: Completeness Validation ### Missing Quality Attributes Architecture doesn't address required attributes. Verify: performance (latency, throughput) | scalability | security (auth, data protection) | maintainabil...