1 min lesson
Cross-domain design exercise
Describe what "Design the pipeline that authenticates a user, calls SCM, runs the agent and emits a webhook on completion" changes in practice.
Step 1 of 4
Here is the prompt to rehearse cold: design the pipeline that authenticates a user, calls SCM, runs the agent and emits a webhook on completion. It forces all four domains into one diagram with clean contracts between them.
This is close to what the paid onsite working session actually feels like - a real system, built with the team, no AI assistance beyond autocomplete. The artifact you want in your head is the data flow plus the failure mode at every hop.
Learn more
Full explanation
The Agent-Run Pipeline
Interactive diagram. Step through it with the Next and Previous controls below, or Tab to a region to read its detail.
Two gates - auth and the run's cost/step caps - are where the pipeline says no.
Learn more
Optional practice
Practice: Cross-domain design exercise
QIn the agent-run pipeline, the webhook receiver on the customer side is down when a run completes. What should happen and what should NOT happen?