Architecture Patterns

This map connects the terminology needed to interpret and compare architecture and design approaches. The goal is to understand the problem, scope, and decisions behind a name before adding it to a design or the Knowledge Graph.

Starting questions

Question	Document	Reading focus
What does Architectural Style mean?	architectural-style	Vocabulary and organizational constraints.
What does Architectural Pattern mean?	architectural-pattern	Problem, context, forces, solution, and consequences.
Why does the Atlas use Architecture Profiles?	architecture-profile	Decision packages across multiple axes.
What is a Design Pattern?	design-pattern	Design intent, participants, and collaborations.

The table provides entry points, not a universal hierarchy. Concept documents contain definitions and examples; this map preserves questions and reading paths.

Evaluating a proposal

Problem and context
→ Scope
→ Decisions and constraints
→ Forces and trade-offs
→ Compatibility with other approaches
→ Evidence and consequences

The rule is not to classify architecture by its label alone. Return to the problem whenever the discussion is limited to deciding what an approach should be called.