Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 21:20:20 UTC

SIE.13:10 - Architectural Rationale

The whole is organized around the receiving claim because that claim determines which distinctions and contributions are necessary. A list of source fields cannot determine permissible loss; a storage choice cannot determine identity; and a passed local test cannot determine whether another result may consume the tested premise.

Working backward exposes required contributions. Working forward checks whether those contributions yield the promised answer. Comparing their connections and shared conditions closes the gap between individual adequacy and whole use. Selecting the next missing result keeps that construction practicable when only part of the answer is unsettled.

The distinct local Methods remain useful: SIE.1 bounds the use; SIE.2–SIE.7 supply semantic and executable premises; SIE.8 chooses realization; SIE.9 supplies the interface; SIE.10 qualifies its use; SIE.11 follows change; SIE.12 helps participants decide who may change or release the shared modules they depend on and how to maintain them. Their actions can constitute parts of this construction when needed. None must be performed anew merely because it has a PatternID.

A linear project plan may organize one implementation, but it cannot replace these dependency and qualification judgements. A small integration can make the same connections through a short contract, qualified mapping and receiving test.