Optical harness fault isolation and configuration restoration

1 Identify the affected subsystem

Model labels: bus, optics, cable_r, cable_l

Select the bus, optical payload and both external harnesses. Read the reported symptom and save the initial visible configuration before changing it.

Check: The learner must identify both the affected subsystem and the source of the reported symptom.

2 Confirm the safe diagnostic state

Model labels: conn_ru, conn_rl, conn_lu, conn_ll

Identify the four connector positions and review the scenario isolation record. Place the task on hold if the record is absent or refers to another configuration.

Check: No disconnection is accepted before the correct isolated-power and ESD evidence is acknowledged.

3 Trace the approved routes

Model labels: cable_r, cable_l, cable_r_sleeve, cable_l_sleeve

Follow each harness from the optical head toward its approved connector position. Compare left and right routing against the supplied configuration map.

Check: A cable colour or visual proximity alone is insufficient identification.

4 Compare the fault record with the model

Model labels: conn_ru, conn_rl, conn_lu, conn_ll

Present a teaching record with the right harness assigned to the lower port instead of its approved upper port. Select the mismatch and cite the approved map.

Check: Randomly swapping all connectors loses the original fault state and fails the diagnostic check.

5 Create the recovery hold

Model labels: cable_r, conn_rl, conn_ru

Record the two competing connector identities and the affected harness. Request the reviewed recovery instruction and retain the original faulted snapshot.

Check: The hold must contain the evidence and resolved instruction before any change is authorised in the exercise.

6 Expose the right retention area

Model labels: optic_hatch_r, cable_r_head_clip, cable_r_sleeve

Open or remove the right access cover using the declared demonstration transform. Identify the clip and sleeve that control the harness route.

Check: Opening the opposite cover or moving unrelated payload parts is an assessed error.

7 Disconnect and stow the affected harness

Model labels: conn_rl, cable_r, cable_r_head_clip

Release retention and move the affected harness from its faulted connector to the defined stowed pose. Keep the left harness in its accepted baseline state.

Check: The recorded disconnect must refer to the observed faulted connection and the reviewed recovery plan.

8 Prepare the correct interface

Model labels: conn_ru, conn_ru_insert, cable_r_sleeve

Identify the approved connector shell and insert. Check the teaching alignment view, route the sleeve clear of the interface and acknowledge the accepted mating orientation.

Check: A damaged-interface variant causes a new hold rather than forced simulated mating.

9 Restore the reviewed connection

Model labels: conn_ru, cable_r, cable_r_sleeve, cable_r_head_clip

Connect the right harness to the approved interface, restore its route and sleeve, and re-engage the retaining clip.

Check: All four restored states must agree; connecting the shell alone does not finish the step.

10 Reconcile the unaffected side

Model labels: conn_lu, conn_ll, cable_l, cable_l_head_clip

Recheck the left-side mapping and retention against the original snapshot. Confirm the recovery did not introduce an unnecessary change on the unaffected side.

Check: An unexplained left-side change prevents acceptance of the repair.

11 Review the post recovery evidence

Model labels: optic_hatch_r, optics, conn_ru

Restore the access cover and compare the supplied post-recovery test record with the stated pass criteria. Keep the test record linked to this configuration.

Check: Do not claim electrical continuity or optical performance from the rendered geometry.

12 Complete the diagnostic handover

Model labels: cable_r, cable_l, conn_ru, conn_rl

Submit symptom, mapping discrepancy, approved correction, changed component IDs and final evidence. Identify the lesson that should update the next task card.

Check: Completion requires a traceable fault-to-correction chain and unchanged approved configuration elsewhere.

Assessment and completion

Score evidence-led diagnosis 25, connector and harness identification 20, isolation and hold discipline 20, restoration 25 and handover 10. Unsupported test claims, random connector swaps or changes before isolation confirmation prevent completion.

Authoring and headless handoff

Implement the connector mismatch through scenario state and a task-card discrepancy. Use actual mesh IDs for selection, cover visibility and harness poses. Test results are explicit records with provenance. The exercise must preserve before and after snapshots and a recoverable hold checkpoint.

Reuse the exact GLB and part identifiers. Verify the supported Genesis import and binding path before generation. These are procedure specifications; they do not claim a completed Genesis run.