NSTD.2:5.2 - Before and after repair: architecture order

Before:

We tried several designs and eventually found the architecture that solved the coordination problem.

Failure: “eventually” supplies a chronology, while “solved” asserts a successful result. The account does not say which coordination problem was addressed, what trade-off was accepted or what observation supports success.

After:

Begin with the coordination problem, compare the candidate module splits, then explain the chosen trade-off and remaining interface exceptions. Consult the decision record for why that split was selected and observations of the implemented system for whether it reduced coordination work.

What changed: the explanation connects the choice to its problem, alternatives and remaining cost. A reader seeking the implementation sequence or an observed outcome has a different source to consult.