The rule says that, in the design of a software product, concepts and purposes should be in one-to-one correspondence. That is, for every concept there should be exactly one purpose that motivates it, and for every purpose of the product, there should be exactly one concept that fulfills it.