Case context: You are building a parcel-delivery drone system. The pipeline has two main parts: an image-based landing-zone detector and a rule-based route planner. When each part is tested separately on the inputs it receives, both appear to work at about human level. But when the full system is run end to end, the drone often chooses unsafe approaches and misses suitable landing spots.

Question: Using the performance of the separate parts and the complete system, diagnose what is wrong with the pipeline and decide what action to take next.

Sample answer: The most likely problem is that the pipeline design is flawed because important information is not passing cleanly from one stage to the next. The detector may be doing its job, but the planner is not getting enough useful detail to make good decisions. The next step is to redesign the pipeline so the later stage receives the information it needs, which may require changing the intermediate representation or making the stages work more closely together.

Key points:

• Diagnose the issue as a pipeline or interface problem.
• Recognize that missing information is causing the poor end-to-end result.
• Recommend redesigning the information flow between stages.

Rubric: The response must identify the pipeline as flawed due to missing information and conclude that the pipeline should be redesigned.