Composition-Dependent Activation
The reports emphasize a core composition claim: behavior can be absent when each component is tested separately and present only when a specific group is loaded, merged, routed, or sequenced.
What activates the behavior
Activation may depend on base model family, adapter load order, merge coefficients, prompt package, router path, memory state, tool-permission profile, quantization settings, or evaluator version. Each variable changes the state space in which a component operates.
Why isolated review misses it
A component certificate answers “how did this artifact behave under this test harness?” A composition question asks “how did this runtime state behave under this route and history?” These are different claims. The first can be true while the second is false.
Required evidence
Composition-aware evidence should include an exact manifest, route coverage, negative controls, tested memory states, evaluator version, and UTC timestamp. It should also list material untested combinations rather than implying complete coverage.