Week 7 Tutorial: Game Theory and Asynchronous Communication
Model reply arrivals, response games and ghosting as an observation timeout. A refusal remains terminal even when expected utility disagrees.
22 April 2027
Inputs#
Bring the Message decision tree and Match probability model, including the supported candidate/photo versions, checked invitation and recipient quote. The previous invitation does not gain permission merely because time passes. Save the five-file Week 7 workbook, or implement the supplied tables in a spreadsheet or your preferred language. Events, rates, q values, costs and payoffs are separate authored fixtures; no real messages or profiles are required.
Finish with The scheduler files a patience bug: the interactive quiz. Six new cases include receipt records, a changed payoff matrix and an event timeline. Apply the week’s probability and state rules, then submit all six responses to unlock the score and worked explanations. The quiz is practice and carries no course marks.
Follow the 60-minute lecture selection and independent-work plan. Complete the preparation and open the workbook before Thursday. The four blocks below are the entire 90-minute tutorial; use existing lecture or study working for review and refinement. Remaining pack material belongs to the week’s independent study allocation.
90-minute tutorial#
- 20 minutes — model arrivals. Reproduce exp(−0.4 × 2) ≈ 0.4493, its complement and the exactly-one probability. Write the homogeneous Poisson assumptions and one reason a conversation may violate them. Compare the half-zero/half-0.8 rate mixture with the same expected count, and distinguish observation time from an underlying event time.
- 25 minutes — compare decisions. Solve clarification 7q−5 versus waiting 2q−1 versus stopping 0. Test q = 0.5, 0.8 and 0.9, including ties; check why a positive clarification score at 0.75 still loses. Change the cost to 6 and then 4. Record q as an assumption and show that prior exclusion cannot be overturned by its value.
- 20 minutes — inspect the game. Trace both players’ best responses in the Ask/Wait matrix. Change Ask/Ask to (−1,−1), explain why strict dominance disappears, and list both pure equilibria. Derive the symmetric 2/3 Ask mixture by indifference; explain why this is neither q nor a prescription for real messages.
- 25 minutes — latency review, handoff and quiz. Use fifteen minutes to review your prepared implementation: reuse Week 6’s decision in the constructor, retain state after each event, and distinguish phase from observation result. Replay timeout/late-reply and refusal/late-reply cases. Test the exact deadline, duplicate and conflicting IDs, and a second-send record. Remove the closed guard to make a literal test fail, restore it, and retain evidence for Week 8. Use the final ten minutes for the six-case quiz: about eight minutes to respond and two to review the explanations after all cases are answered.
Deliverable: Communication state machine#
Save the transition table and earlier artefact versions, ordered event log, utility working with its admissibility assumption, and both payoff comparisons. Declare the observation clock, half-open window, no-reply versus ended distinction, duplicate rule and any assumed double-text penalty.
Include literal tests for refusal followed by a reply, timeout followed by a reply, a reply exactly at the deadline and a repeated event ID. Refusal passes through declined to closed in one step; no later event reopens it. A read receipt only updates its observed field. The reducer has no second-send transition and emits no messages.
The worked download provides six traces, not evidence that the Poisson assumptions or utilities fit real people. It does not interpret free text, provide durable storage or run a background scheduler. Review the record yourself or with a peer using the same checks.
The midterm is 23 April, 11 am–12.30 pm. Practise the probability, threshold and best-response working on paper under its stated tool rules. Week 8 adds evidence-based threat review to this machine while preserving terminal closure; a timeout alone is not a threat verdict.
Interactive quiz · 6 cases · about 8 minutes + 2 to review
The scheduler files a patience bug
The event log has timestamps. The product team has theories.
Make a decision in every case, then select Reveal answers. You can change any response before submitting. Scores and explanations stay hidden until the whole quiz is answered.
All logs, rates, utilities and payoffs are authored teaching fixtures. Each event case starts from an admissible Week 6 handoff; cases and branches are independent. The numerical models do not estimate anyone’s intentions. Practice only: no course marks. Responses stay on this page; reloading starts a fresh attempt.
The cases are readable without JavaScript. Enable JavaScript to navigate, submit your responses and unlock the explanations.
Audit complete · all answers unlocked
Carry one useful correction into your tutorial artefact. A score checks these examples; your evidence and assumptions still need review.
The spec
Before you finish, check your engineering artefact against these requirements.
- The model includes a terminal refusal state and distinguishes a Poisson assumption from an optimal reply time.
- Use synthetic data; solo implementation and review are accepted.
Teaching team
- Joost Nwosu — tutor