RESOURCES / OPEN THE RECORD
Rules, materials, campus packs and reference ideas. Everything required to complete the course is supplied here or inside its lab.
In-person teaching is preferred. Read the lesson and campus pack before the facilitated lab. The online lab and demonstration provide an equivalent route when you cannot attend, and practice between classes.
Inspect the model before trusting it. Each lab publishes the rules and sources needed to reason about its problem. Worked examples and optional facilitator explanations are labelled separately. Guided practice explains the method; independent challenges ask you to select useful tests; transfer changes a consequential condition.
Inspect means select a named object or record and read its details. Operate means use a named lesson control to change or test the model. Transfer means use the same skill when the conditions change. The lab tells you the exact actions; there is no extra equipment to find or install.
Identifiers such as PG-01 and DI-02 label records or rules inside the linked lesson, lab and combined campus pack. Each supplied-rule section explains that mapping. They are not extra downloads to find. Blank grids, timelines and record sheets are included in the packs or described as records you create yourself.
WEEK 01 / Perception Gallery
Distinguish visible facts, reported claims and explanations, then choose an inspection that tests a proposed explanation.
Mission application: A1 uses this method to choose which workshop condition needs investigation. The final project uses it to keep an arrival impression from becoming an unsupported operating assumption.
WEEK 02 / Perception Gallery
Compare unaided recall, location cues and written notes, then choose a retrieval strategy appropriate to the task.
Mission application: Memory is optional support in A1 and handoffs. The final project does not require recall when an accurate external record serves the objective better.
WEEK 03 / Spatial Lab
Reconcile a fixed diagram with a differently oriented scene, predict its transformation, then verify direction and height independently.
Mission application: A1 relates an unfamiliar workshop diagram to its connector. A physical final recovery may need this capability; a digital operation need not invent a transport problem.
WEEK 04 / Mechanics Workshop
Distinguish mechanism faults using selected inspections, predict motion and verify a targeted repair.
Mission application: A1 combines mechanism diagnosis with observation and spatial modelling. Physical recovery and stabilisation can need a support mechanism; digital recovery need not repeat an unrelated cradle exercise.
WEEK 05 / Systems Garage
Choose circuit measurements that distinguish faults, repair what the evidence supports and verify the powered result.
Mission application: A2 requires a diagnosis another role can use. Final power checks support transmission or continuous support, and transport only when the selected route depends on power.
WEEK 06 / Digital Observatory
Resolve conflicting records by separating authority, integrity and completeness while preserving a decision timeline.
Mission application: A2 uses this record to justify instructions to another role. Every final approach needs source evidence, but matching a digest does not itself choose the recovery objective.
WEEK 07 / Digital Observatory
Translate authority into testable permissions, diagnose deviations and preserve policy versions when requirements change.
Mission application: A2 needs legitimate relay access. The digital final approach uses the appropriate local policy; physical handover does not gain an arbitrary software gate.
WEEK 08 / Council Studio
Coordinate across unequal information using questions, read-back and renewed confirmation when an instruction changes.
Mission application: A2 assesses a real handoff between partners. The final team uses this method when source findings, equipment conditions or responsibilities change another person's work.
WEEK 09 / Council Studio
Negotiate legitimate responsibilities using verified records, multiple feasible proposals and explicit costs and obligations.
Mission application: The final team must defend a recovery objective and agree custody and monitoring obligations. This lab practises the judgement behind that agreement.
WEEK 10 / Movement Hall
Choose a route for an explicit objective, predict its published sensor events and compare its dependencies with an alternative.
Mission application: A physical final recovery needs a route suited to its load and equipment. Digital and stabilisation approaches need relevant evidence rather than compulsory token navigation.
WEEK 11 / Operations Studio
Identify dependencies invalidated by disruption, retain supported decisions and rehearse a revision without overwriting the original.
Mission application: The final project needs a reasoned change between contrasting rehearsals. Explain why its chosen objective remains feasible or why the team deliberately revises it.
WEEK 12 / Meridian Station
Select relevant capabilities for a recovery objective, coordinate their dependencies and defend the result and remaining obligations.
Mission application: 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.
Download the complete facilitator guide. Equipment, original resource sheets and role information are included. Classroom apparatus is a teaching design; browser testing does not establish physical fabrication or classroom trial results.
Use the assessment pages for canonical dates, weights, deliverables and marking descriptors. Use the passport exports for practice evidence and backups.
These are optional context. No external account or reading is required to solve the supplied activities.
SLOP UNIVERSITY · THE ACADEMY OF IMPOSSIBLE SKILLS
An original fictional course. Progress records practice, not academic certification.