The orchestrator passes the previous step's complete output JSON directly as the next step's input. If the field name in step 1's output doesn't match the field name in step 2's input_contract, validation fails immediately. The fix must align the field names — either by changing what step 1 outputs or by changing what step 2 expects.
Your Challenge
Step 2 of your pipeline fails with: 'input_contract validation error: required field urgency_level is missing'. Examining the logs, you see step 1 returned: {"classification": "HIGH", "confidence": 0.95}
Step 2's input_contract requires: {"urgency_level": {"type": "string"}}
What is the root cause? Describe the TWO valid ways to fix this without disabling contracts.