BRIEFING / WEEK 12
Recover the Impossible
Select relevant capabilities for a recovery objective, coordinate their dependencies and defend the result and remaining obligations.
Read, then try it
This briefing explains the week's idea and shows a worked example. Read the objectives and example, then open the lab for the actual controls, three practice configurations and saved fieldwork record.
The week’s question: Complete Operation Last Light and explain why selected checks and performed actions serve the team’s declared objective.
The station opens. Your notes are useful only if you can act on them.
What you will learn
- Select and justify capabilities relevant to the declared objective.
- Coordinate dependencies and preserve evidence when the approach changes.
- Defend the performed result, a credible alternative and a remaining obligation.
The briefing
Integration means selection and dependency
You have practised observation, investigation, diagnosis and coordination in different settings. Integration recognises which this objective needs and how one role’s result changes another’s action. It does not repeat eleven labs in a prescribed order.
Every approach needs scene and identity evidence, a current signed source, precise handoff, preservation/recipient agreement and a preserved plan with revision. Physical recovery additionally relates load to support and transport. Digital recovery needs transmission supply and local permission. Stabilisation needs continuous support and a custodian’s continuing responsibility.
Compare real alternatives
Physical recovery transfers the original and custody. Digital recovery transfers a verified copy with arrangements for the retained original. Stabilisation leaves access or retrieval work unresolved and specifies who monitors what. These are different obligations, not cosmetic ending screens.
Defend a credible alternative before committing. State its advantage and why its costs or unmet conditions matter. If information changes your objective, preserve the earlier plan. A requirement disappears only when the objective makes it irrelevant, not because it is inconvenient.
Account for the result
Link objective, observation, decision, action and consequence. Explain which checks were relevant, which you omitted and why. Successful handover does not establish scientific correctness of the archive; failed rehearsal can still demonstrate careful diagnosis.
Each member should defend a consequential choice and discuss a dependency beyond their primary role. Close with custody, monitoring, limitations or follow-up work. The ending is an event; assessment concerns the evidence and judgement behind it.
Worked example · a different scenario
The separate rainfall-recorder example aims to recover verified data while keeping the original recorder stable. The demonstrator records a 16:25 display and an amber service lamp, tests the prepared support lift for two opposite output turns, and compares copies with the twelve-record W-6 request. Ash matches; Birch does not. A confirmed handoff transfers Ash while the recorder stays at its mast. The result meets the stated objective, but matching a reference does not answer the remaining calibration question.
Watch this separate example and inspect its finished record.
A plausible mistake
Treating the ending screen as the assessment omits the actual evidence of skill. Conversely, explaining every failure as bad luck can hide a missed check. Identify what the team could know, what it tested and what the result shows.
Supplied rule sheet
MR-01 supplies the Meridian charter, six areas and four responsibilities. MR-02 supplies approach-specific requirements; use the final-project pack for current profiles and evidence.
- Shared evidence: scene/identity observations, current signed archive source, precise handoff, preservation/recipient agreement, initial plan and preserved revision.
- Physical recovery: matched support cradle, map orientation and transport route. An Upper/Lift route also needs power; the independent Service route does not impose a circuit gate.
- Digital recovery: diagnosed transmission supply, correct local access policy, confirmed receiving receipt and arrangements for the original. Cradle, map and transport are not required.
- Stabilisation and handover: matched support cradle, diagnosed continuous power, stable indicator, named custodian and monitoring limitation. No transport route or access-policy gate.
- Explain a credible alternative, why your selected checks fit the objective, and a remaining obligation. Recall is an optional tool, not a universal gate.
- Locations: arrival hall, workshop, power bay, control room, archive chamber, dispatch platform. Roles: observer/navigator, systems specialist, investigator, coordinator.
- Presets: Baseline, Equipment Failure, Conflicting Archive. They are published conditions; acting speed and endings do not determine marks.
Before the lab
Review two contrasting rehearsal records (20 minutes). Agree roles and the initial objective (10 minutes). Check that each member can explain one decision outside their main role (10 minutes).
What happens next
This lab assembles the final-project evidence. The after-action account does not replace the performed mission or the assessment’s individual and team deliverables.
Keep recovery-record from this week’s lab. Download the campus pack.
SLOP UNIVERSITY · THE ACADEMY OF IMPOSSIBLE SKILLS
An original fictional course. Progress records practice, not academic certification.