Skip to main content
SLOP4408 / MASTERMINDIn person preferred · Online availableSemester 1 · 2027

THE DEMONSTRATION STUDIO / WATCH · INSPECT · TAKE CONTROL

Five cases to the dome

A complete alternate worked example, followed by meaningful takeover practice.

The method behind this example

Ask for missing information, correct the read-back and reconfirm changed instructions.

Your independent challenge: The assigned roles hold different fields; the receiver must supply its own access condition. A confirmed example message cannot authorise it.

The example includes the practical intervention and its required handover.

Start this worked example

  1. Choose Watch the worked example. The student demonstrator explains the task, talks through each action, then reviews the observations and finished submission. Narration starts with this click; Mute narration keeps the same experience captioned.
  2. Choose Take control to try the current chapter. Follow its prompt, change the labelled controls and select Test my decision.
  3. Read the feedback, retry if needed, then continue with Next chapter. Each checked chapter provides evidence for one connected operation.
  4. After every chapter check, return to the mission station, perform the intervention, collect its package and follow the marked checkpoints to complete the handover. Watching performs these same actions with narration. Direct chapter access is a partial preview until the full evidence and handover are complete.
  5. Use Fullscreen mission after opening the scene to keep the instructions, chapter controls and equipment together. Reflections and exports come after your practical attempt.

This is an alternate example, not your assigned exercise. Your course task is linked after the player.

YOUR SKILL

Asymmetric communication

A NEW SETTING

An analyst knows the delivery instruction; an operator controls the dispatch table.

WHAT CHANGES

The alternate handoff is Dome / 5 / VIOLET, then Pool / 2 / SILVER.

Choose how you want to learn.
You · student in Take controlDr Mara Voss · instructor · not a case character
Scene guide · people, evidence and object placement

Who sends the delivery instruction

An analyst holds the delivery card; an operator controls dispatch.

Your part
Watch follows a worked solution. Take control lets you move the student avatar and try its decisions. The demonstrator in the explanation is modelling a solution, not an extra witness in the story.
Your instructor
Mara stands in the marked teaching bay outside the investigation area. She guides the exercise. Her presence, appearance and idle gestures are not clues about what happened in the case.
People in this scenario
  • Analyst and operator are roles in the example exchange. Council dossiers identify the speakers; Mara is not either person.
What counts as evidence
Read the card, the operator's read-back and the analyst's confirmation. Preserve the count correction instead of assuming a nod proves understanding.
Why the objects are here
The dispatch table and cases represent a delivery instruction. The response controls record its destination, quantity, code and acknowledgement.
An original academy with bronze arches, a central mechanism and illuminated workbenches.
SLOPU · GUIDED WORKED EXAMPLE

Council Studio

Watch the complete alternate example. Take control of the equipment whenever you are ready.

An alternate example · separate from your assessed work
How to move, inspect and complete the activity

Use WASD or arrow keys to walk. Press E near an instrument to examine it. Inspect means read its details; Use equipment performs the action named in its status message. The task controls let you choose exact settings and test a solution. Once verified, use the mission station to put it into effect, collect the resulting evidence or cargo, follow its checkpoints and complete the handover at the receiving station.

Scroll over the scene or use Zoom + / Zoom − for a closer or wider view. Click and drag to turn whenever the cursor is free. Choose Fullscreen mission to keep the scene, mission instructions and all task controls together. Fullscreen starts with a free cursor so you can scroll the panel and choose options. Press X or Lock cursor (X) to turn by moving the mouse. Press X again to free the cursor and return to click-and-drag turning. Tab also frees the cursor. The X shortcut stays inactive while typing or choosing a form value. Press Escape or Exit fullscreen to return to the page. On touchscreens, drag to look and use the zoom buttons. If your browser cannot enter native fullscreen, the mission expands to fill its window.

Choose Watch to follow the worked example, or Take control to try it yourself. The transcript and completed example remain available if 3D is unavailable. Demonstrations never change assessed progress.

01 / 6
Before we beginYour worked-example briefing

I need to pass an instruction between an analyst and an operator without losing its meaning. I will state destination, quantity and code, expose a mistaken read-back, correct it, and repeat the protocol for a new message. My completed handoff record must include confirmation. The method we are practising is: Ask for missing information, correct the read-back and reconfirm changed instructions.. Our field objective is: Dispatch the correct environmental kit through a confirmed instruction and readback. A quantity error and incomplete message could send the wrong kit to the right destination. I will perform the supported intervention and handover. You can pause, mute, replay, or take control at any point. The captions show the same explanation.

Narration starts after you choose Watch or Play. Captions remain available if this browser has no working voice.

Perform the practical outcome

Each chapter provides evidence for this operation. Inspect, investigate, act, and complete the handover.

FIELD OPERATION · Briefing

Operation Clear Channel

Dispatch the correct environmental kit through a confirmed instruction and readback.

A quantity error and incomplete message could send the wrong kit to the right destination.

Inspect the mission station to begin your investigation.

Nothing collected.

Mission actions become available when the activity loads.

Mission record and accessible controls

These controls perform the same actions as the marked stations in the scene. Use them with a keyboard or touch, or when graphics are unavailable. Equipment tests establish whether your intervention is supported. The final handover records a mission outcome; your explanation is assessed separately.

  1. No mission actions yet.

The complete transcript and finished example are available below while the player loads.

THE DEMONSTRATOR’S REASONING

Identify the missing information

The analyst's card says five sealed cases to Dome, verification VIOLET. The operator sees destination controls but not the card. 'Send those upstairs' leaves critical fields unstated.

Why this matters

Competent participants can still hold different information.

A plausible mistake

Repeating vague wording does not make the missing fields appear.

YOUR LEARNING CONTROLS

Make the skill your own.

Which field is missing from 'send those upstairs'?

Watch the apparatus change as the student demonstrates. Take control whenever you want to test the same idea yourself.

BASED ON YOUR ATTEMPTS

Watching and practising are recorded separately in this visit. These examples do not change your assessed work or skills passport.

NOW TRANSFER THE SKILL

Carry the method into your own work.

The assigned roles hold different fields; the receiver must supply its own access condition. A confirmed example message cannot authorise it.

Week 8 lab ↗

Restart this worked example?

This clears its practice record for this visit. Your course passport and assigned activities stay saved.

A COMPLETE WORKED SUBMISSION

Five cases to the dome — completed record

Example work from this demonstration's scenario. Use it to understand the expected evidence and explanation, then make your own decisions in the assigned activity.

Download the complete example
Read the finished work

Completed demonstration example — dome handoff

Role information

Analyst card: five sealed cases to Dome, verification VIOLET. Operator: controls dispatch and must request exact destination, count and code.

Recorded exchange

Analyst: “Deliver five sealed cases to Dome; verification code VIOLET. Read back before dispatch.” Operator first read-back: “Dome, four, VIOLET.” Analyst: “Correct the count to five.” Operator corrected read-back: “Dome, five, VIOLET.” Analyst: “Confirmed.”

The count mismatch was found before movement. A bare acknowledgement would not have exposed it.

Changed situation

New card: Pool / 2 / SILVER. The team repeated the same protocol with new values. The operator's matching read-back was confirmed separately from the earlier handoff.

Agreement

The analyst owns instruction accuracy; the operator records and repeats the three fields; either role may stop if a field conflicts. A completed acknowledgement applies to one identified instruction, not every later delivery.

Reflection

The protocol was useful because it made the receiver's interpretation visible. My error was a wrong count, not unwillingness to cooperate. In another task I would preserve exact labels and ask which condition permits action, especially when the roles see different screens.

Named output: handoff-agreement. This is an alternate demonstration, not the assigned Relay/Archive/Dispatch answer.

Method to carry forward

Ask for missing information, correct the read-back and reconfirm changed instructions.

The assigned roles hold different fields; the receiver must supply its own access condition. A confirmed example message cannot authorise it.

The complete example explains one defensible approach. In your own challenge, select observations and tests from the supplied rules, keep your prediction separate from the result, and justify both the checks you perform and those you omit.

Complete transcript and decisions · readable without JavaScript

Before we begin · expected task and evidence

I need to pass an instruction between an analyst and an operator without losing its meaning. I will state destination, quantity and code, expose a mistaken read-back, correct it, and repeat the protocol for a new message. My completed handoff record must include confirmation. The method we are practising is: Ask for missing information, correct the read-back and reconfirm changed instructions.. Our field objective is: Dispatch the correct environmental kit through a confirmed instruction and readback. A quantity error and incomplete message could send the wrong kit to the right destination. I will perform the supported intervention and handover. You can pause, mute, replay, or take control at any point. The captions show the same explanation.

1. Identify the missing information

What I need to do: Step 1. Identify the missing information. I compare what each role can see. The operator needs an exact destination and count, not a vague direction such as upstairs.

Supplied context: The analyst's card says five sealed cases to Dome, verification VIOLET. The operator sees destination controls but not the card. 'Send those upstairs' leaves critical fields unstated.

Watch my actions: For "Missing actionable information", I choose "Exact destination and count". I check the demonstrated result.

What I observed: The communication gap is identified before dispatch. Competent participants can still hold different information.

Why: Competent participants can still hold different information.

Decision: Which field is missing from 'send those upstairs'?

  • Missing actionable information: Exact destination and count

Result: The communication gap is identified before dispatch.

Common mistake: Repeating vague wording does not make the missing fields appear.

2. Name the destination

What I need to do: Step 2. Name the destination. I use the destination's shared name so both roles can compare the same field.

Supplied context: The analyst says 'Deliver five sealed cases to Dome.' The operator records the exact named destination rather than translating it into a personal direction such as upstairs.

Watch my actions: For "Named destination", I enter Dome. I check the demonstrated result.

What I observed: The destination can now be checked against the same label. Shared names reduce ambiguity when viewpoints differ.

Why: Shared names reduce ambiguity when viewpoints differ.

Decision: Enter the destination.

  • Named destination: Dome

Result: The destination can now be checked against the same label.

Common mistake: Upstairs depends on the starting point and can describe several rooms.

3. Preserve the exact quantity

What I need to do: Step 3. Preserve the exact quantity. I correct the first read-back from four cases to five and keep the mismatch visible.

Supplied context: The operator initially hears four, reads it back and is corrected to five. The demonstrator preserves this mismatch rather than showing only a flawless exchange.

Watch my actions: For "Number of cases", I enter 5. I check the demonstrated result.

What I observed: The count now agrees and the repair remains visible. Read-back exposes a consequential difference before action.

Why: Read-back exposes a consequential difference before action.

Decision: Correct the operator's quantity.

  • Number of cases: 5

Result: The count now agrees and the repair remains visible.

Common mistake: An acknowledgement of 'understood' would not reveal the wrong count.

4. Carry the verification condition

What I need to do: Step 4. Carry the verification condition. I carry the current verification code rather than reusing a familiar code from earlier work.

Supplied context: The dispatch code is VIOLET. A familiar code from an earlier exercise would be wrong even if the destination and count were correct.

Watch my actions: For "Current code", I enter VIOLET. I check the demonstrated result.

What I observed: All three fields now match the current instruction. A complete instruction contains the current condition, not a remembered default.

Why: A complete instruction contains the current condition, not a remembered default.

Decision: Enter the verification code.

  • Current code: VIOLET

Result: All three fields now match the current instruction.

Common mistake: Correct destination alone does not establish a complete handoff.

5. Close the communication loop

What I need to do: Step 5. Close the communication loop. I wait for a complete read-back of destination, count and code, then confirm all three.

Supplied context: The operator reads back Dome, five, VIOLET. The analyst compares all three fields and confirms. Only then is the handoff complete.

Watch my actions: I set "Read-back confirmed" to yes. I check the demonstrated result.

What I observed: Both roles share the same actionable instruction. The receiver's exact understanding becomes inspectable before action.

Why: The receiver's exact understanding becomes inspectable before action.

Decision: Record acknowledgement after the complete read-back.

  • Read-back confirmed: Yes

Result: Both roles share the same actionable instruction.

Common mistake: Silence is not evidence that all fields were heard correctly.

6. Reuse the protocol, change the message

What I need to do: Step 6. Reuse the protocol, change the message. I replace all three fields with the new card's values and perform another read-back. Earlier confirmation cannot approve a changed message.

Supplied context: The next card says two cases to Pool, verification SILVER. The demonstrator changes all three fields and performs another read-back; the earlier values are preserved in the record.

Watch my actions: For "New destination", I enter Pool. For "New quantity", I enter 2. For "New code", I enter SILVER. I check the demonstrated result.

What I observed: The protocol survives a different task without carrying stale values. Transfer keeps a sound communication method while replacing its current content.

Why: Transfer keeps a sound communication method while replacing its current content.

Decision: Record the fresh handoff.

  • New destination: Pool
  • New quantity: 2
  • New code: SILVER

Result: The protocol survives a different task without carrying stale values.

Common mistake: Reusing VIOLET would be a memory error disguised as routine.

Performing the field operation

All chapter evidence checks are complete. I return to the mission station and authorise the confirmed dispatch. I am putting the verified solution into effect, then checking what changes.

I collect Confirmed environmental-kit instruction. The verified intervention released this package. I now carry it through the marked handover route.

I carry Confirmed environmental-kit instruction to Dispatch table. I confirm this checkpoint before continuing so the handover trace records the route actually followed.

I carry Confirmed environmental-kit instruction to Receiving operator station. I confirm this checkpoint before continuing so the handover trace records the route actually followed.

At the receiving station, I complete the receiver handover. I check the receipt before calling the field operation complete.

My observations and finished submission

The first confirmed message was Dome, five cases, VIOLET. The operator first repeated four; I kept that mismatch and the correction. The next message changed to Pool, two, SILVER and received a fresh read-back. My record includes both complete messages and confirmations, showing how the protocol survives changed information. Ask for missing information, correct the read-back and reconfirm changed instructions. Open "Read the finished work" or download the complete example to inspect the evidence and explanation together. The assigned roles hold different fields; the receiver must supply its own access condition. A confirmed example message cannot authorise it.

The complete submission is available in Read the finished work above and as a Markdown download.

← All worked examples

SLOP UNIVERSITY · THE ACADEMY OF IMPOSSIBLE SKILLS
An original fictional course. Progress records practice, not academic certification.