Adapter Collusion Versus Composition
The word “collusion” should be used narrowly. Some research examines models or agents coordinating, communicating, or degrading safety only when combined. That is not the same as every unsafe multi-adapter interaction.
A safer site vocabulary is to distinguish three cases.
Composition-triggered behavior
A behavior appears only when components are loaded together. No component needs an intention, message, or plan. The relationship is enough. This is the default Cognivirus concern for adapters.
Coalition behavior
Several components contribute complementary capabilities to an outcome no single component efficiently produces. The components may not communicate explicitly, but the system-level task decomposition creates a coalition-like effect.
Collusion
Collusion should be reserved for cases where research or evidence supports coordination, hidden communication, or a paired vulnerability that is designed or selected to activate jointly. Collusion is a stronger claim than composition. It should carry a stronger evidence label.
Editorial rule
Cognivirus.com should prefer “composition-triggered behavior” unless a source specifically studies collusion or covert coordination. This prevents the site from turning technical composition risk into unsupported anthropomorphic language.