Attack Engine and Evidence Plane

This comparison frames a split architecture for offensive work: the partner retains the attack engine, operator workflow, and product-native execution loop, while the OEM Engine contributes the context layer that qualifies what was run, what was observed, and how it should be interpreted. The partner continues to generate or orchestrate attacks and own the customer relationship, UX, and operational flow; the OEM Engine adds architecture and authority context, evidence capture, and sequence qualification so results are defensible and reusable. The boundary is deliberate: the partner keeps its attack engine, but the return path is enriched with structured evidence rather than isolated attack outputs. That makes the shared chokepoints explicit and keeps the partner-native return object as a pilot objective until it is proven.