preserving-productive-tensionslisted

# Preserving Productive Tensions ## Overview Some tensions aren't problems to solve - they're valuable information to preserve. When multiple approaches are genuinely valid in different contexts, forcing a choice destroys flexibility. **Core principle:** Preserve tensions that reveal context-dependence. Force resolution only when necessary. ## Recognizing Productive Tensions **A tension is productive when:** - Both approaches optimize for different valid priorities (cost vs latency, simplicity vs features) - The "better" choice depends on deployment context, not technical superiority - Different users/deployments would choose differently - The trade-off is real and won't disappear with clever engineering - Stakeholders have conflicting valid concerns **A tension needs resolution when:** - Implementation cost of preserving both is prohibitive - The approaches fundamentally conflict (can't coexist) - There's clear technical superiority for this specific use case - It's a one-way door (choice locks architecture) - Preserving both adds complexity without value ## Preservation Patterns ### Pattern 1: Configuration Make the choice configurable rather than baked into architecture: ```python class Config: mode: Literal["optimize_cost", "optimize_latency"] # Each mode gets clean, simple implementation ``` **When to use:** Both approaches are architecturally compatible, switching is runtime decision ### Pattern 2: Parallel Implementations Maintain both as separate cl