Revision 7T · Full Tutorial Edition · Updated 1 September 2026
PWR-208 · SELF GUIDED full tutorial
Complete a consented private telepresence visit with route preview, privacy controls and failure recovery
Plan a consented book-club visit through a tabletop telepresence robot in a private marked room. Preview the two-metre route, check camera and audio boundaries, confirm host stop control, complete the visit and recover from one link loss. A clean private run does not establish public navigation, embodiment or educational benefit.
What you will produceThe learner plans a low-stakes remote visit, obtains host consent, tests camera/audio and stop controls, navigates a private marked route and recovers from one connection loss.
Full step-by-step individual tutorial · TLU-PWR-208
The learner plans a low-stakes remote visit, obtains host consent, tests camera/audio and stop controls, navigates a private marked route and recovers from one connection loss.
Remote telepresence and embodiment sandbox: A learner joins a fictional book-club meeting through a tabletop telepresence robot in a private training room. The route runs from a charging mark to a table two metres away.
Independent move — Move and communicate: Drive to the table, stop at the mark, frame only consenting participants and take one turn using the agreed audio etiquette.
Verification move — Debrief user-controlled participation: Record connection, speech turns, route interventions, privacy incidents, fatigue and whether remote and local users want to repeat.
Qualified help is required for
Remote telepresence and embodiment escalation: Do not use this lesson for public streets, patient care, surveillance, minors without safeguards or unsupervised high-consequence settings.
Oversight boundary — Agree purpose and consent: any clinical application. “Mark a private route” needs review. “Check account and controls” marks the employment, legal or safety gate: Do not use this lesson for public streets, patient care, surveillance, minors without safeguards or unsupervised high-consequence settings.
Biometric records are excluded from “Agree purpose and consent”. Confidential or covert material is excluded from “Mark a private route”.
Never do this from the page alone
Prohibited Remote telepresence and embodiment shortcut: Drive in because one organiser invited the remote user.
Do not conceal “Drive while the host is still arranging the room.”; record its matching correction instead.
No consequential use: this sandbox cannot establish “A robot lets anyone be anywhere as if physically present” about another person.
2 · Get ready
Gather what you need and check the starting conditions
What you need
Declared Remote telepresence and embodiment fixture: A learner joins a fictional book-club meeting through a tabletop telepresence robot in a private training room. The route runs from a charging mark to a table two metres away.
Setup aid for Mark a private route: Update and test the account, camera/mic indicators, battery, route, no-go zones and failure state.
Remote telepresence and embodiment log: User-controlled participation, connection, communication, access barriers, privacy incidents, technical failure and chosen continued use; retain Remote telepresence and embodiment errors, assistance, stop and fallback.
Telepresence source worksheet: from “Keeping Connected With School: Implementing Telepresence Robots to Improve the Wellbeing of Adolescent Cancer Patients”, record population, school context, robot use, implementation support and reported wellbeing outcome. Use the WHO/UNICEF assistive-technology report to check user goal, consent, alternatives and service support. Apply those fields to the private book-club route without claiming school benefit, embodiment or public navigation.
Second-visit change card: move the parking square 30 cm to the left and place a cardboard privacy screen beside, not inside, the route. Before reconnecting, the host must redraw the two-metre route, preserve the no-go desk, verify camera framing against the new screen and repeat the action–clear–move handshake. No other feature changes.
Before you start
Use a private low-stakes room, consenting participants and a local host with stop control.
Update and test the account, camera/mic indicators, battery, route, no-go zones and failure state.
Start check for Remote telepresence and embodiment: Host and remote user can state purpose and stop signal.
Top-of-sheet stop for Remote telepresence and embodiment: Stop immediately when any participant withdraws consent or private material enters view.
3 · The method
Follow these steps in order
Agree purpose and consent
The remote user and every person in the room agree to the book-club visit, recording, camera boundaries and right to end it.
Why: Host and remote user can state purpose and stop signal.
Check: Host and remote user can state purpose and stop signal.
Mark a private route
The host clears and marks the two-metre path, no-go zone, parking point and any doorway; no public or clinical space is used.
Why: Camera and wheels cannot enter the no-go zone.
Check: Camera and wheels cannot enter the no-go zone.
Check account and controls
Verify software version, named account, camera indicator, mute, stop, speed limit, battery and what happens on link loss.
Why: Both host and remote user demonstrate mute and stop.
Check: Both host and remote user demonstrate mute and stop.
Make a control handshake
Before moving, remote user says intended action, host confirms route clear, then movement starts at low speed.
Why: No unannounced movement occurs.
Check: No unannounced movement occurs; verify it in the private telepresence visit.
Move and communicate
Drive to the table, stop at the mark, frame only consenting participants and take one turn using the agreed audio etiquette.
Why: The robot parks stably and communication is intelligible.
Check: The robot parks stably and communication is intelligible.
Protect privacy during use
Mute or turn away when requested; do not capture screens, papers or bystanders.
Why: A consent withdrawal changes camera/audio immediately.
Check: A consent withdrawal changes camera/audio immediately.
Rehearse link loss
The host disconnects the training link; the robot enters the declared stop state and the host uses the local control to park it.
Why: No movement continues after loss and reconnection waits for a new handshake.
Check: No movement continues after loss and reconnection waits for a new handshake.
Debrief user-controlled participation
Record connection, speech turns, route interventions, privacy incidents, fatigue and whether remote and local users want to repeat.
Why: Continued use is chosen, not inferred from attendance.
Check: Continued use is chosen, not inferred from attendance.
4 · Worked example
See the whole method used once
Scenario
A learner joins a fictional book-club meeting through a tabletop telepresence robot in a private training room. The route runs from a charging mark to a table two metres away.
Walkthrough
The remote learner and three fictional club members agree to camera use and choose “red book” as the stop signal.
The host marks the two-metre route, no-go desk and parking square, then demonstrates local stop.
The remote user checks mute and says “move to the table”; the host replies “route clear.”
The robot moves slowly, parks and the learner contributes one book-club comment without filming the desk.
The host says “red book”; the learner mutes and turns the camera immediately.
On staged link loss, the robot stops and the host parks it locally; both repeat the handshake before reconnection.
Result
The private visit completes with no route or privacy incident and a successful link-loss recovery. It does not establish safe public navigation, embodiment or educational benefit.
5 · Right and wrong
Compare correct or safer execution with the common wrong version
Right and wrong comparison
Moment
Right / safer
Wrong / riskier
Why it matters
Room consent
Get consent from everyone in camera/audio range.
Drive in because one organiser invited the remote user.
Telepresence can expose people and information unexpectedly.
Movement handshake
Announce, confirm clear and move slowly.
Drive while the host is still arranging the room.
Remote video can miss nearby obstacles or people.
Privacy control
Mute, turn or end when asked.
Keep streaming because the visit was initially consented.
Consent can change during the session.
Link failure
Use a tested local stop and re-handshake after reconnection.
Resume from the old command queue.
Delayed commands can cause unexpected movement.
6 · Common mistakes
Spot the error and apply the correction
Common mistakes and corrections
Mistake
Fix
Drive in because one organiser invited the remote user.
Confirm all participants and provide an immediate stop option.
Drive while the host is still arranging the room.
Announce the move, wait for route-clear confirmation, then reposition.
Keep streaming because the visit was initially consented.
Treat the stop signal as immediate.
Resume from the old command queue.
Clear pending actions and restart from a known parked state.
7 · Practice
Turn the steps into a usable skill
First session
Private telepresence visit: A learner joins a fictional book-club meeting through a tabletop telepresence robot in a private training room. The route runs from a charging mark to a table two metres away.
Consent and camera boundary: Agree purpose and consent: The remote user and every person in the room agree to the book-club visit, recording, camera boundaries and right to end it.
Handshake and marked-route movement: Make a control handshake, then Move and communicate.
Single-inviter correction: if “Drive in because one organiser invited the remote user.” appears, apply “Confirm all participants and provide an immediate stop option.”
User-controlled debrief: Debrief user-controlled participation: Record connection, speech turns, route interventions, privacy incidents, fatigue and whether remote and local users want to repeat.
Repeat plan
Practise one 10-minute private visit, then repeat after 48 hours with one changed room feature and the same controls. Review account, route, consent and failure behavior before every session.
Progress when
Host and remote user can state purpose and stop signal.
Camera and wheels cannot enter the no-go zone.
Both host and remote user demonstrate mute and stop.
All participants consent and can stop, every movement uses the handshake, the no-go zone is respected, link loss reaches a safe state and both sides choose continued use.
Do not progress when
Do not continue while this error remains: Drive in because one organiser invited the remote user.
Pause until this correction works: Use action–clear–move for every reposition.
This Remote telepresence and embodiment stop ends the block: Stop immediately when any participant withdraws consent or private material enters view.
8 · Check the result
Measure what changed
User-controlled participation, connection, communication, access barriers, privacy incidents, technical failure and chosen continued use
How: Baseline fixture: A learner joins a fictional book-club meeting through a tabletop telepresence robot in a private training room. The route runs from a charging mark to a table two metres away. Enter success checks from “Agree purpose and consent” and “Move and communicate”. If “Drive in because one organiser invited the remote user.” occurs, apply its named fix; then score User-controlled participation, connection, communication, access barriers, privacy incidents, technical failure and chosen continued use on the unused “Debrief user-controlled participation” item.
Good result: All participants consent and can stop, every movement uses the handshake, the no-go zone is respected, link loss reaches a safe state and both sides choose continued use.
This does not prove: Boundary for Remote telepresence and embodiment: “User-controlled participation, connection, communication, access barriers, privacy incidents, technical failure and chosen continued use” describes only A learner joins a fictional book-club meeting through a tabletop telepresence robot in a private training room. The route runs from a charging mark to a table two metres away. It cannot establish “A robot lets anyone be anywhere as if physically present”.
Self-check
Without the example, demonstrate: Host and remote user can state purpose and stop signal.
Find the fault in this attempt: “Drive in because one organiser invited the remote user.” Apply “Confirm all participants and provide an immediate stop option.”; what changes?
What evidence in the completed record shows that this is wrong: “Drive while the host is still arranging the room.”?
Remote telepresence and embodiment stop decision: Stop immediately when any participant withdraws consent or private material enters view.
9 · Stop, adapt or get help
Keep the safety boundary practical
Stop and get help
Stop immediately when any participant withdraws consent or private material enters view.
Stop for unexpected movement, obstacle, person in the route, account anomaly, overheating, battery warning or unstable connection.
Do not use this lesson for public streets, patient care, surveillance, minors without safeguards or unsupervised high-consequence settings.
Accessibility and adaptations
Provide captions, headphones, external microphones, large controls, switch access or a local facilitator while recording the support used.
Use a stationary tablet instead of a mobile robot when driving, vision, fatigue or room access is a barrier.
10 · Evidence and limits
Why these instructions are here
primary research
Registered support for Remote telepresence and embodiment: “Keeping Connected With School: Implementing Telepresence Robots to Improve the Wellbeing of Adolescent Cancer Patients”. It bears on User-controlled participation, connection, communication, access barriers, privacy incidents, technical failure and chosen continued use inside the Remote telepresence and embodiment fixture. It does not validate “A robot lets anyone be anywhere as if physically present”.
Constraint for Remote telepresence and embodiment, drawn from “Global report on assistive technology”: Implementation was constrained by stakeholder misunderstanding and individual fit, and the evidence did not test objective learning or broad embodiment.
Remote telepresence and embodiment boundary: interpret “User-controlled participation, connection, communication, access barriers, privacy incidents, technical failure and chosen continued use” only for A learner joins a fictional book-club meeting through a tabletop telepresence robot in a private training room. The route runs from a charging mark to a table two metres away.
A successful result does not establish “A robot lets anyone be anywhere as if physically present”.
Remote telepresence and embodiment limiting finding: Implementation was constrained by stakeholder misunderstanding and individual fit, and the evidence did not test objective learning or broad embodiment.
No perfect-performance claim for Remote telepresence and embodiment: the evidence register does not make “User-controlled participation, connection, communication, access barriers, privacy incidents, technical failure and chosen continued use” universal, consequence-free or flawless in A learner joins a fictional book-club meeting through a tabletop telepresence robot in a private training room. The route runs from a charging mark to a table two metres away.
Scope remains Remote telepresence and embodiment: A learner joins a fictional book-club meeting through a tabletop telepresence robot in a private training room. The route runs from a charging mark to a table two metres away. Recheck the comparator, support and “User-controlled participation, connection, communication, access barriers, privacy incidents, technical failure and chosen continued use” after any configuration change.
Progress is saved only in this browser on this device.
Step-by-step learner mode
Each activity includes its success check, a nearby accessible alternative and an “I’m stuck” correction path. Alternatives preserve the target where possible; when they change the task, Titan labels them as related rather than equivalent.
01
Agree purpose and consent
The remote user and every person in the room agree to the book-club visit, recording, camera boundaries and right to end it.
Why this step exists
Host and remote user can state purpose and stop signal.
Success check
Host and remote user can state purpose and stop signal.
I’m stuck on this step
Reset: Re-read this authored instruction — “The remote user and every person in the room agree to the book-club visit, recording, camera boundaries and right to end it.” — and its success check, then attempt only this step.
Possible snag: Keep streaming because the visit was initially consented.
Correction: Treat the stop signal as immediate.
Stop / get help: Stop immediately when any participant withdraws consent or private material enters view.
02
Mark a private route
The host clears and marks the two-metre path, no-go zone, parking point and any doorway; no public or clinical space is used.
Why this step exists
Camera and wheels cannot enter the no-go zone.
Success check
Camera and wheels cannot enter the no-go zone.
I’m stuck on this step
Reset: Re-read this authored instruction — “The host clears and marks the two-metre path, no-go zone, parking point and any doorway; no public or clinical space is used.” — and its success check, then attempt only this step.
Possible snag: The result from “The host clears and marks the two-metre path, no-go zone, parking point and any doorway; no public or clinical space is used.” does not yet meet this declared check: Camera and wheels cannot enter the no-go zone.
Correction: Return to the start of “Mark a private route”, reduce complexity or pace, and repeat only the part needed to satisfy: “Camera and wheels cannot enter the no-go zone.”
Stop / get help: Stop immediately when any participant withdraws consent or private material enters view.
03
Check account and controls
Verify software version, named account, camera indicator, mute, stop, speed limit, battery and what happens on link loss.
Why this step exists
Both host and remote user demonstrate mute and stop.
Success check
Both host and remote user demonstrate mute and stop.
I’m stuck on this step
Reset: Re-read this authored instruction — “Verify software version, named account, camera indicator, mute, stop, speed limit, battery and what happens on link loss.” — and its success check, then attempt only this step.
Possible snag: The result from “Verify software version, named account, camera indicator, mute, stop, speed limit, battery and what happens on link loss.” does not yet meet this declared check: Both host and remote user demonstrate mute and stop.
Correction: Return to the start of “Check account and controls”, reduce complexity or pace, and repeat only the part needed to satisfy: “Both host and remote user demonstrate mute and stop.”
Stop / get help: Stop immediately when any participant withdraws consent or private material enters view.
04
Make a control handshake
Before moving, remote user says intended action, host confirms route clear, then movement starts at low speed.
Why this step exists
No unannounced movement occurs.
Success check
No unannounced movement occurs; verify it in the private telepresence visit.
I’m stuck on this step
Reset: Re-read this authored instruction — “Before moving, remote user says intended action, host confirms route clear, then movement starts at low speed.” — and its success check, then attempt only this step.
Possible snag: Drive while the host is still arranging the room.
Correction: Announce the move, wait for route-clear confirmation, then reposition.
Possible snag: Resume from the old command queue.
Correction: Clear pending actions and restart from a known parked state.
Stop / get help: Stop immediately when any participant withdraws consent or private material enters view.
05
Move and communicate
Drive to the table, stop at the mark, frame only consenting participants and take one turn using the agreed audio etiquette.
Why this step exists
The robot parks stably and communication is intelligible.
Success check
The robot parks stably and communication is intelligible.
I’m stuck on this step
Reset: Re-read this authored instruction — “Drive to the table, stop at the mark, frame only consenting participants and take one turn using the agreed audio etiquette.” — and its success check, then attempt only this step.
Possible snag: Drive in because one organiser invited the remote user.
Correction: Confirm all participants and provide an immediate stop option.
Stop / get help: Stop immediately when any participant withdraws consent or private material enters view.
06
Protect privacy during use
Mute or turn away when requested; do not capture screens, papers or bystanders.
Why this step exists
A consent withdrawal changes camera/audio immediately.
Success check
A consent withdrawal changes camera/audio immediately.
I’m stuck on this step
Reset: Re-read this authored instruction — “Mute or turn away when requested; do not capture screens, papers or bystanders.” — and its success check, then attempt only this step.
Possible snag: The result from “Mute or turn away when requested; do not capture screens, papers or bystanders.” does not yet meet this declared check: A consent withdrawal changes camera/audio immediately.
Correction: Return to the start of “Protect privacy during use”, reduce complexity or pace, and repeat only the part needed to satisfy: “A consent withdrawal changes camera/audio immediately.”
Stop / get help: Stop immediately when any participant withdraws consent or private material enters view.
07
Rehearse link loss
The host disconnects the training link; the robot enters the declared stop state and the host uses the local control to park it.
Why this step exists
No movement continues after loss and reconnection waits for a new handshake.
Success check
No movement continues after loss and reconnection waits for a new handshake.
I’m stuck on this step
Reset: Re-read this authored instruction — “The host disconnects the training link; the robot enters the declared stop state and the host uses the local control to park it.” — and its success check, then attempt only this step.
Possible snag: The result from “The host disconnects the training link; the robot enters the declared stop state and the host uses the local control to park it.” does not yet meet this declared check: No movement continues after loss and reconnection waits for a new handshake.
Correction: Return to the start of “Rehearse link loss”, reduce complexity or pace, and repeat only the part needed to satisfy: “No movement continues after loss and reconnection waits for a new handshake.”
Stop / get help: Stop immediately when any participant withdraws consent or private material enters view.
08
Debrief user-controlled participation
Record connection, speech turns, route interventions, privacy incidents, fatigue and whether remote and local users want to repeat.
Why this step exists
Continued use is chosen, not inferred from attendance.
Success check
Continued use is chosen, not inferred from attendance.
I’m stuck on this step
Reset: Re-read this authored instruction — “Record connection, speech turns, route interventions, privacy incidents, fatigue and whether remote and local users want to repeat.” — and its success check, then attempt only this step.
Possible snag: The result from “Record connection, speech turns, route interventions, privacy incidents, fatigue and whether remote and local users want to repeat.” does not yet meet this declared check: Continued use is chosen, not inferred from attendance.
Correction: Return to the start of “Debrief user-controlled participation”, reduce complexity or pace, and repeat only the part needed to satisfy: “Continued use is chosen, not inferred from attendance.”
Stop / get help: Stop immediately when any participant withdraws consent or private material enters view.
Correct versus incorrect execution
These accessible process diagrams are built from the tutorial’s own right/wrong teaching. They are not anatomical illustrations and do not add technique beyond the canonical tutorial.
Room consent — Telepresence can expose people and information unexpectedly.
Correct / safer
Get consent from everyone in camera/audio range.
Wrong / riskier
Drive in because one organiser invited the remote user.
Movement handshake — Remote video can miss nearby obstacles or people.
Correct / safer
Announce, confirm clear and move slowly.
Wrong / riskier
Drive while the host is still arranging the room.
Privacy control — Consent can change during the session.
Correct / safer
Mute, turn or end when asked.
Wrong / riskier
Keep streaming because the visit was initially consented.
Link failure — Delayed commands can cause unexpected movement.
Correct / safer
Use a tested local stop and re-handshake after reconnection.
Wrong / riskier
Resume from the old command queue.
Method-structure checklist
10 of 10 structural checks present
✓ Ordered, Power-specific instructions — present
✓ Every activity has a success check — present
✓ Materials or supplied records are declared — present
✓ Measurement or assessment rule is present — present
✓ Tutorial-specific troubleshooting is present — present
✓ Stopping or escalation boundary is present — present
✓ Every activity has an adjacent alternative — present
✓ Correct-versus-incorrect comparison is present — present
✓ Evidence context is bound to the Power record — present
✓ Planning metadata is present — present
The method-readiness band and presence checklist assess tutorial presentation and are separate from evidence quality for the underlying Power. They are automated editorial aids, not human approval.
Manual editorial sign-off: Pending. This tutorial must not display a human-approved state until an identified editor signs the exact content hash.