What does a requirement mean when it is stated as a "general rule"?
I find it amazing that engineers who's entire job is dealing with specs and requirements and hard facts will generate a formal requirement that "handbook xyz be followed as a general rule".
They have taught us that a requirement should be unambiguous and testable. I find this type of requirement to be neither. Anone else find this sort of irrational behaviour in engineers?