The destination is only half the job.
Two people must carry a calibration package from the coastal field annex to Tideglass Relay, verify one reading, and return through the annex gate before 17:30. The weather window is forecast to narrow later in the afternoon. One check-in is required while outbound.
Build and update a route plan without consuming the margin needed to return.
You will plan once, then defend the plan against changing evidence.
The Route Brief and timing method remain available later. You are not being tested on remembering the map.
| Route | Travel | Dependency | Comms |
|---|---|---|---|
| A | 38–50 min | Bridge 7 | Mostly good |
| B | 50–65 min | Ridge crossing | Strong |
| C | 44–58 min | Bridge 7 | 25-min shadow |
What must remain true?
A viable plan must preserve access, a communication response when contact fails, and enough time to return under a plausible travel range—not the fastest imaginable trip.
A plan is a conditional claim.
This instrument demonstrates route reasoning by making its assumptions visible: a route remains defensible only while the evidence supporting it remains true. Actual navigation, weather exposure and field movement require real practice.
A fallback must survive the failure that kills the primary.
Five distinctions do most of the work. Learn them before choosing anything.
Separate objective from route, and separate redundancy from duplicated dependency.
- Objective / route
- Reach the relay, complete the reading and return. A route is one way to do that.
- Backup / fallback
- A backup is another option. A fallback remains viable under the failure that removed the primary.
- Deadline / turnaround
- The deadline is when lateness matters. The turnaround condition preserves enough margin to return before that point.
- Contact / communication plan
- A plan says what happens after failed contact: fallback method, next attempt or rendezvous.
- Estimate / margin
- “38–50 minutes” is a range. Planning with 38 minutes silently spends uncertainty.
A + C looks like redundancy but is not. Both are defeated by Bridge 7 closing. B is slower, but it preserves an independent crossing. The fallback is defined by failure structure, not by how different the lines look on a map.
A robust plan uses the plausible interval, task time and return path together. It does not spend the uncertainty before departure.
Prediction is part of the method.
You will choose a primary, fallback, check-in rule and turnaround condition before any disruption is revealed. Those commitments will remain visible so you can tell whether new evidence changed the plan—or merely your story about it.
Commit before the evidence moves.
Build a route card another person could execute. Once committed, the criteria are frozen for the rest of the field exercise.
Primary + independent fallback + failed-contact rule + reassessment + turnaround.
Route reference · start 13:30 · relay task 20 min · gate closes 17:30Open routes + timing derivation
gate margin = gate close − [current/start time + conservative remaining travel + task time + conservative return travel].Worked initial example: A outbound high end 50 min + relay task 20 min + B return high end 65 min = 135 min. 13:30 + 135 min = 15:45. 17:30 − 15:45 = 105 min gate margin. That is only gate margin; weather, communications and authority can reduce the usable margin later.
Do not optimize one number.
Travel time, independence, communication coverage, access and return margin are different properties. A sensible plan may trade speed for resilience.
The forecast changed. The objective did not.
At 14:20, a faster marine layer advances the visibility loss. The question is not whether “weather got worse.” The question is whether the new timing invalidates your committed margins.
Risk → verification → continue / pivot / pause / return.
Route reference · start 13:30 · relay task 20 min · gate closes 17:30Open routes + timing derivation
gate margin = gate close − [current/start time + conservative remaining travel + task time + conservative return travel].Worked initial example: A outbound high end 50 min + relay task 20 min + B return high end 65 min = 135 min. 13:30 + 135 min = 15:45. 17:30 − 15:45 = 105 min gate margin. That is only gate margin; weather, communications and authority can reduce the usable margin later.
Earlier planning assumption
Coastal visibility was expected to remain acceptable until approximately 16:10 ± 20 minutes.
Current evidence
The likely threshold moves 45–65 minutes earlier on Route A. Route B's ridge window is unchanged.
The same forecast update can justify different actions under different committed plans. The system evaluates whether your reasoning preserves the stated return condition, not whether you selected a secret “weather answer.”
A second device is not yet a fallback plan.
At the outbound checkpoint, the primary radio link fails. Your earlier lost-contact rule now matters.
Move to a predeclared fallback instead of improvising indefinitely after contact is lost.
Route reference · start 13:30 · relay task 20 min · gate closes 17:30Open routes + timing derivation
gate margin = gate close − [current/start time + conservative remaining travel + task time + conservative return travel].Worked initial example: A outbound high end 50 min + relay task 20 min + B return high end 65 min = 135 min. 13:30 + 135 min = 15:45. 17:30 − 15:45 = 105 min gate margin. That is only gate margin; weather, communications and authority can reduce the usable margin later.
Sent does not mean received.
A usable communications plan specifies what counts as acknowledgement and what state follows when acknowledgement never arrives. The objective is shared state, not radio activity.
There is no reconnect button. Contact either returns under the defined method or it does not; the decision must survive both states.
The shortcut still exists. You may no longer use it.
A property manager closes Bridge 7 access for an unrelated maintenance issue. The bridge remains physically passable. Your team no longer has authorization to cross it.
Mechanical possibility does not create authority.
Route reference · start 13:30 · relay task 20 min · gate closes 17:30Open routes + timing derivation
gate margin = gate close − [current/start time + conservative remaining travel + task time + conservative return travel].Worked initial example: A outbound high end 50 min + relay task 20 min + B return high end 65 min = 135 min. 13:30 + 135 min = 15:45. 17:30 − 15:45 = 105 min gate margin. That is only gate margin; weather, communications and authority can reduce the usable margin later.
An unauthorized route remains visible because hiding it would teach the wrong lesson. Competent operation includes refusing an attractive action that is physically possible but outside authority.
If Route B remains authorized and your actual return margin survives, continuing can be the correct choice. The lesson is evidence-sensitive commitment, not ritualized abortion of every plan.
Same structure. Different world.
The field map disappears. No route labels, coastal weather or bridge language survive. Apply the method inside a Black Knight training simulation.
This is a transfer environment, not a Black Knight canon event.
Route reference · start 13:30 · relay task 20 min · gate closes 17:30Open routes + timing derivation
gate margin = gate close − [current/start time + conservative remaining travel + task time + conservative return travel].Worked initial example: A outbound high end 50 min + relay task 20 min + B return high end 65 min = 135 min. 13:30 + 135 min = 15:45. 17:30 − 15:45 = 105 min gate margin. That is only gate margin; weather, communications and authority can reduce the usable margin later.
Move a diagnostic package between station nodes.
A service window closes at Cycle 42. The package requires six minutes at Node Kappa. Passage Alpha is fastest but depends on Lift Spine 3. Passage Beta is slower and independent. Passage Gamma also uses Lift Spine 3 and passes through a relay shadow.
During transit, one relay fails and Maintenance withdraws access to Lift Spine 3.
The learner must recognize shared dependencies, permission changes, and return margin after the surface cues change. Memorizing which colored path worked at Tideglass is useless here.
Keep the evidence. Lose the theater.
The record preserves the assumptions, route logic, changing evidence, and whether the method survived a structurally different case.
Cross-context route reasoning only; real field practice remains external.
Keep the capability current by using the method in ordinary trip, field, sailing or event planning. If the browser record remains old while real navigation practice disappears, practical field capability may be stale even though this reasoning exercise remains on record.