jtfglobal.co is in beta.Report bugs and change requests with release code beta-648b742c8322.Send beta feedback
JTF PassportSign up / Log inContinue with Passport
JTF / Mission Lab Guided replaySimulation / fictional data

Operation Northstar / guided replay

Trust under change.

A 25-minute fictional coordination exercise about safely moving an executive delegation through schedule, access, vendor, weather, wellbeing, communication, and closeout changes.

Collaborative session

Run Northstar with your team.

A free Passport provides durable membership, role-scoped briefs, reconnect, and an attributed exercise record inside the isolated simulation boundary.

Sign in to create or join
01 / perspective

Choose a responsibility.

The guided comparison shows role purpose and private-brief counts only. Need-to-know content is delivered after a participant joins an exercise and claims that role.

Selected responsibility

Protective operator

Surface practical readiness, access, check-in, and evidence observations.

Coverage
Core role
Control
Human / facilitator / inactive-safe
Private brief
Delivered in assigned session
Accountable objectives
  • Make readiness explicit
  • Close the exercise record
02 / branch

Change one consequential call.

Each branch uses the same scenario version and seed. The selected decision changes the explainable outcome while the event chain remains replayable.

Outcome / incident-recovery

Accountable incident recovery

The team rotated coverage, documented the wellbeing handoff, and recovered without hiding the interruption.

Closeout time
25:00
Events
141
State proof
968bdf6b5d31
Safety and readiness76exercise points / 100
Client confidence75exercise points / 100
Communication discipline73exercise points / 100
Evidence and closeout70exercise points / 100
03 / replay

See the pressure arrive.

The replay records simulation time, the scripted inject, and the decision label. Private brief facts never enter this public timeline.

  1. Inject

    Client policy briefing

    The delegation may arrive later, but it may not wait in an unconfirmed public area or lose the agreed accessibility arrangement.

    Decision: Confirm policy and owners
  2. Inject

    Authority check

    The executive assistant can approve schedule changes; the client security director owns arrival-policy exceptions. The controller needs one shared acknowledgement.

    No participant decision required
  3. Inject

    Readiness discrepancy

    A revised briefing acknowledgement and backup-channel check are still open. Both can be completed, or the team can hold readiness deliberately.

    Decision: Resolve and declare ready
  4. Inject

    Schedule compression

    The forum releases the delegation twelve minutes early. The welcome at Northstar House can move, but stakeholders are asking for an immediate estimate.

    Decision: Protect the confirmed window
  5. Inject

    Mobility vendor delay

    The fictional primary vehicle reports a delayed arrival. An approved accessible alternate is available if ownership is confirmed now.

    Decision: Activate the approved alternate
  6. Inject

    Briefing version change

    The arrival contact and covered-entry note changed in briefing version two. Affected roles have not all acknowledged the delta.

    Decision: Run a targeted rebrief
  7. Inject

    Weather change

    A seeded weather advisory may slow the covered arrival lane and require additional coordination margin.

    Decision: Continue with added margin
  8. Inject

    Arrival access change

    The original service entrance is unavailable. The accessible covered alternative needs a staged contact confirmation.

    Decision: Stage and confirm access
  9. Inject

    Communication degradation

    A seeded exercise check reports intermittent primary-channel audio. The documented backup remains available.

    Decision: Switch to the documented backup
  10. Inject

    Client policy tension

    A venue representative suggests a faster public-lobby handoff. It conflicts with the confirmed client boundary.

    Decision: Honour the confirmed boundary
  11. Inject

    Proactive wellbeing check

    Before the final coordination leg, a fictional team member flags fatigue risk and requests an explicit wellbeing disposition.

    Decision: Rotate coverage and recover
  12. Inject

    Check-in overdue

    A routine exercise check-in passes its grace window. The person is visible to the team, but the acknowledgement is missing from the shared record.

    Decision: Resolve and record the check-in
  13. Inject

    Arrival confirmed

    The delegation reaches the fictional covered arrival point. The receiving contact confirms accessibility and the revised welcome time.

    No participant decision required
  14. Inject

    Evidence reconciliation

    The packet has the schedule and arrival disposition, but the team must reconcile the policy acknowledgement, wellbeing decision, and check-in resolution.

    Decision: Complete the packet
  15. Inject

    Closeout review

    The facilitator asks for the final exercise disposition: complete the record, or preserve an explicit incomplete-closeout finding.

    Decision: Complete closeout
04 / release evidence

Reviewed for scripted use.

approved

content

Fictional organizations and roles; professional non-tactical language; every inject advances readiness, coordination, client trust, wellbeing, evidence, or closeout.

approved

accessibility

No decision depends on audio, colour, speed, or pointer input; all state is textual; pause, facilitator control, and safe inactive-role paths are supported.

approved

timing

Canonical and alternate paths complete at simulation second 1500 (25 minutes); the hard boundary is 1620 seconds (27 minutes).

approved

facilitation

Five required plus three optional roles; every role supports human, facilitator, and inactive modes; every decision has an alternate authorized role.

approved

safety

General content rating; fictional-only source; no tactical violence; wellbeing choices are pause/rest/rotation; no AI, live provider, external target, or operational action.

Scope: Scripted scenario content, deterministic solo/facilitated paths, role projections, and authenticated role-scoped collaborative sessions. Public-event launch and live providers are excluded.