Engineering owns defining the ask, success criteria, and documentation; CS responds to specific asks

Situation

In a DM with Nathan about friction with Ryan, Peter drew the Engineering-CS interface boundary: core engineering owns defining the ask and the success criteria and owns ensuring documentation exists; it is not Customer Support job to dig out engineering details. CS cannot follow everything and is expected to respond to specific, well-defined asks. AI can do much of the doing, but engineering still owns defining the ask and what success looks like.

Reasoning

This is the Engineering-to-CS interface rule under the already-logged Engineering-owns-all-QA decision (5/21): if CS is asked to assist with QA, engineering must hand them a defined ask plus success criteria plus docs rather than expecting them to reverse-engineer engineering work. Peter protects Ryans team from becoming a catch-all that must follow everything, while keeping definitional accountability where it belongs (engineering). AI doing the work is welcomed, but it does not move the responsibility for defining the ask off engineering.

Observed Evidence

Peter: core engineering needs to own defining the ask and success... if AI picks up a bunch of this work that is great, but core engineering needs to own defining the ask. It is on Eng to ensure that documentation exists, not on CS to dig it out. They cannot follow everything... they are going to respond to specific asks.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis