Skip to main content
SLOP1276 Applied Algorithmic Romance & Profile OptimizationSemester 1, 2027

Romance Debugger

One conversation. Several possible actions. Only the evidence gets to change the state.

Step into Alex’s fictional message thread. Choose an action, inspect its result, then reveal the next authored event. Sometimes the useful answer is “we don’t know yet.”

NULL ISLAND · MESSAGE LABFictional cases · ungraded practice

Trace a conversation on paper

The interactive debugger needs JavaScript. The same decision is readable here: Alex has sent one opener. A read receipt is recorded, but no reply is recorded. Choose whether to wait, send another opener or close the conversation.

Inspect this paper trace

The route stays pending. Another opener is held because one is already recorded. “We don’t know yet” preserves the uncertainty. Alex may also close the local conversation without inferring why no reply arrived.

Use the Week 6 worked notes for the complete rule order.

This practice uses the Week 6 message decision tree. It adds a local record of your choices and manually revealed events. The replies are scripted examples; a choice does not cause or predict someone’s response.

In the Week 6 tutorial, use a trace during the existing tree exercise, then explain the same route in your pseudocode. Week 7 adds explicit clocks and observation windows. You can also return to the course toolkit.