SYSE.53:2 - Problem

A dependency declaration can conceal the question it is supposed to answer. A citation may mean only “consult this source”; another relation may require the same definition in every step of a joint inference. A tool may accept two installed library versions while the program exchanges values whose type identities differ. Treating all these relations as “depends on” makes either excessive coupling or unsupported compatibility likely.

A resolver can select values only for the problem it receives. Successful search over loose or incomplete constraints does not repair a missing semantic premise. Conversely, one rejected candidate, a timeout or a missing catalogue entry does not prove that no useful arrangement exists.

Independent release also separates three decisions: a supplier makes a new version available; a composition engineer proposes a revised selection; the consumer accepts that selection for a use. Conflating them lets a routine update alter the basis of ongoing work.