audit: anchor architectural patterns to intent, not preference#7
Merged
Merged
Conversation
Every "When to Use" section in the six main architectural patterns was
rewritten from preference/feature language ("you want a clear place for
each concern") to intent/forcing-function language ("you need to test
business rules without a database — that need is the justification for
the boundary").
Added a "The Decision" section to Layered, Microservices, Clean
Architecture, CQRS, Event-Driven, and Hexagonal that answers the
reader's real question: "why would I choose this?" Each one names the
specific problem the pattern solves and warns when the answer is a
preference rather than a concrete forcing function.
Added body content to the home page establishing the core thesis: the
difference between architecture and preference is a *because*. Wired
up the heroBody prop in Home.jsx so that content is rendered.
Added a closing paragraph to the philosophy index making the intent
explicit: the goal is to know *why* each pattern exists, not to
memorise the pattern itself.
https://claude.ai/code/session_01JXWLKgArf1Xm29GT358Usx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every "When to Use" section in the six main architectural patterns was
rewritten from preference/feature language ("you want a clear place for
each concern") to intent/forcing-function language ("you need to test
business rules without a database — that need is the justification for
the boundary").
Added a "The Decision" section to Layered, Microservices, Clean
Architecture, CQRS, Event-Driven, and Hexagonal that answers the
reader's real question: "why would I choose this?" Each one names the
specific problem the pattern solves and warns when the answer is a
preference rather than a concrete forcing function.
Added body content to the home page establishing the core thesis: the
difference between architecture and preference is a because. Wired
up the heroBody prop in Home.jsx so that content is rendered.
Added a closing paragraph to the philosophy index making the intent
explicit: the goal is to know why each pattern exists, not to
memorise the pattern itself.
https://claude.ai/code/session_01JXWLKgArf1Xm29GT358Usx