11 Patterns in the wild: Three end-to-end case studies
This chapter covers
- Reading architecture cases without turning them into recipes
- Binding each claim to its evidence class, workload, and operating point
- Following Task, State, Authority, and Evidence when a design changes
- Returning evidence to ASSESS, ROUTE, or SELECT
- Diagnosing failure at the contract, pattern, seam, parameter, and workload layers
- Keeping, repairing, recomposing, simplifying, or retiring an architecture decision
- Operating architecture decisions as a versioned, reopenable ledger
A prototype agent built engineering models from a user's description, creating elements and the connections between them. The developer had added a review loop: generate a change, ask the model to critique it, then revise. But a connection to a nonexistent element needs no such debate; code can check it directly. The developer found that repeated reviews added delay and variability. The self-review loop was removed, with structural checks and at most one repair attempt placed before the write. Names and modeling detail still needed judgment; whether a connection had a valid endpoint did not.
Chapter 10 showed how to choose and test an initial composition. The three cases here follow what happens as a design is used: when results expose a weakness, what should you keep, repair, recompose, simplify, or retire? You will trace each choice from an observed problem through a design change to the evidence needed to judge it.