A connected set of methods that carry a business need all the way to running code — each structural decision derived from requirements, not left to taste.
Not another manifesto. Four well-known architectures were derived blind from their public numbers — predictions registered before looking, graded in the open, misses shown next to hits. That is what makes “derived, not chosen” a claim you can check.
See the replication kit, and send a counterexample →Stack-independent. Any language, any framework.
The same principles, made concrete in one stack.
Java is the reference realization, not a lock-in — every principle here ports to other languages.
Every book has a free course edition on this site. The books remain books.
The design method: a system's structure derived from what the business does, one operation at a time.
The next correct step: architecture derived, not chosen.
Hide the machinery, keep the meaning: deterministic code whose types state the business facts.