# Engineering Judgment (/docs/engineering-judgment)



Engineering Judgment is the part of Atlas for questions that are not answered well by memorizing one framework or pattern.

A **decision guide** starts with explicit constraints, compares viable options across concrete criteria, and ends with a conditional recommendation rather than a universal winner.

An **architecture walkthrough** traces a realistic system or vertical slice across request flow, state, asynchronous boundaries, partial failure, security, observability, scaling, and cost.

## Two ways to use this section [#two-ways-to-use-this-section]

Use **Decision Guides** when the problem is *which approach fits these constraints?* The comparison should make the costs of each option visible, including the cost of operating it.

Use **Architecture Walkthroughs** when the problem is *how do several concepts interact in one system?* The goal is to follow boundaries and failure modes rather than memorize a reference diagram.

Both content types still use the canonical Software Engineering Map for concept placement. This section is a learning mode, not a second taxonomy or registry.