Build the core model
Read the lesson and connect each concept to the visual model above.
This advanced module helps students read a deployment pipeline as a chain of protocol interactions rather than a black box.
Included teaching examples
- name: Publish queued article
run: npm run content:daily
- name: Deploy to Cloudflare Pages
uses: cloudflare/wrangler-action@v3
with:
command: pages deploy dist --project-name=lecturer-materials
- name: Deploy Cloudflare Worker
uses: cloudflare/wrangler-action@v3
with:
command: deployUse the snippet to discuss where authenticated GitHub requests, Cloudflare API calls, DNS resolution, TLS handshakes, and edge responses can fail.
Diagram support
The paired SVG visualises source checkout, queued content publication, deploy API calls, Worker rollout, and live verification through a protocol-aware lens.
Suggested learning flow
- Identify which protocol powers each pipeline step.
- Compare successful and failed release scenarios.
- Trace how observability signals expose transport or endpoint issues.
- Design a verification checklist for protocol-sensitive deployments.
Work with observable evidence
Use the lab to turn the lesson into a repeatable classroom exercise.
Scenario lab
A digital service is slow or unreliable, but the team has not isolated where the exchange fails.
Trace Protocol Delivery and Observability Module from client request to service response and mark the verification boundary.- Focus
- ci/cd, protocols, github-actions
- Evidence target
- An annotated exchange trace with observable signal, interpretation, and follow-up test.
Activity checklist
Write what you observed, what it means, and what should be verified next. This draft stays on this device.
Explain the decision
Confirm what you can observe, what remains uncertain, and what should happen next.
Before completing this lesson
- Name the input, decision point, and outcome shown in the visual.
- Identify one artifact that would count as evidence.
- State one limitation and one next verification step.