Well-Architected Design
Pricing: free · Category: development
What the run does#
Turn one fuzzy requirement into a decision document someone else could build from on Monday with no author available.
Most design docs describe one idea and call it a decision. This loop refuses to finish until there are three competing architectures, every technical choice has a why-chain that bottoms out in something real, and the money has a number next to it.
The six gates#
Finalize is refused unless all six hold.
At least three architectures
Each with its own key table and its own mermaid sequence diagram, including one do-nothing-new option and one you expect to reject.
A five-whys chain under every technical decision
Every partition key, every sort-key segment in order, every new row kind, every transaction boundary.
A real price
The money gets a number, not an adjective.
Comparable options
The alternatives are argued at the same depth as the favorite, so the comparison is honest.
A traceable why-chain
Each chain bottoms out in something real rather than in a preference.
One decision document
The output is a document another engineer could build from without the author present.
Running it#
/lamoom run well-architected-design
Related#
- FrontendBuilder is the same raising-bar idea applied to UI.
- Runs and Judges covers gates versus judges.