A context carries cancellation, deadlines and request-scoped values across a call chain. Pass it explicitly as the first parameter when an operation can stop early. Do not store it as a general configuration bag or replace a caller's canceled context with Background. Cancellation is cooperative: a function must check Done or Err, and a blocking send or receive needs a cancellation branch if it must stop. The tasks in this lesson avoid sleeps. They create contexts that are already canceled or active and test deterministic behavior. You will refuse work after cancellation, keep valid zero results and read one typed request value. A deadline uses the same error boundary, but wall-clock timing is not a reliable way to prove these small contracts.
An active context is ready.