multi-approach-architecture

To present architectural trade-offs, enumerate 2–3 competing approaches with explicit risk, coupling, and abstraction differences rather than silently selecting one. This surfaces viable patterns to prevent premature commitment before drafting technical proposals.

Documenting architecture options requires appending an architecture-options block to your ai-work.md file. This fragment captures competing approaches and their TEPlike implications, anchoring decisions to existing codebase patterns and prior exploration-notes.

You need to evaluate multiple architecture patterns when subtask complexity is medium or hard and multiple viable patterns exist. Applying this process to simple tasks with an obvious solution introduces unnecessary overhead.

Justify architectural design decisions by relying on exploration-notes and existing codebase patterns to validate option choices. Clearly define each approach's risk, coupling, and abstraction axes to enable informed TEPlike consensus.

Avoiding early single pattern selection prevents premature commitment and accelerates team consensus. Enumerating 2–3 trade-off paths up front exposes TEPlike implications and architectural constraints before drafting final technical proposals.

Yes, existing codebase patterns are essential for guiding architectural trade-off analysis. Anchoring enumerated options to prior exploration-notes and established patterns ensures coherence and validates the risk, coupling, and abstraction axes of each approach.