Library / Financial Domain Modeling Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 10:00:09 UTC

FDM.5:10 - Architectural Rationale

The participant’s intended result provides the reason to follow the service connection. The output and actual receiving use keep that connection grounded. Together they permit a modest upstream contribution without making the whole business outcome the provider’s direct product.

A technical output specification is sufficient for a settled supplier interface. It becomes inadequate when the disputed question is financial value. A complete business redesign is unnecessary when locating one missing use or effect answers that question.