Skip to main content

Interoperation Report

Negotiate a shared working protocol with a partner over three labs, then report what each of you conceded, and what held.

Weight: 20%. Due: 30 May 2027, 23:59 Canberra time

Submission instructions: the hand-in process and whether uploads are available.

Agree a protocol with someone who runs a different one, and write down what it cost you both.

In week 9’s lab you meet a partner the tutor chose, deliberately, to mix the room. Over the labs of weeks 9, 10 and 11, and the working weeks in between, the two of you negotiate a shared protocol for how you work together: reply times, how either of you says “I need a pause”, what depth your conversations stay at, and how either of you flags a mismatch.

Then each of you, separately, reports what happened.

What a strong response does

The fix is bilateral. A report in which one partner conceded everything describes conversion, not interoperation, and should say so plainly if that’s what happened. That can still be a strong report, if it’s honest about it.

It reports disagreement as data. If you and your partner remember the concessions differently, describe the difference in the report rather than settling on one account.

It uses the course’s terms exactly: payload, timeout, rate limit, mismatch.

What you submit

Each partner submits their own report. You may share the protocol document; you may not share the report.

If the partnership stops working, tell Jonah by the end of week 10’s lab. A renegotiated partnership is a legitimate thing to report.

Due Sunday 30 May 2027, 23:59 Canberra time.

The spec

These are the checks a marker uses. Work through them before you submit.

How it is marked

CriterionWeight
The protocol: clauses are specific, and each says how either partner checks it30%
Concessions: an honest account of what both partners gave up, including disagreements30%
What held: evidence from the three labs and the weeks between25%
Terms: course vocabulary used exactly, not re-coined15%