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 Exercise controlClassification: simulation

Controlled rehearsal environment

This is an
exercise.

Practice decisions, communication, readiness, and recovery without dispatching anyone, charging anyone, contacting a client, or changing a live mission.

Play a free missionOpen Northstar replay

The solo game starts anonymously and keeps a signed local run; a free Passport adds cloud save. Operation Northstar remains available as a deterministic guided replay. Neither path sends anything or touches a live mission.

Scenario 01 / published

Operation Northstar

A fictional executive-delegation coordination exercise where trust depends on readiness, policy, communication, wellbeing, and a complete record—not speed.

Runtime
25–27 minutes
Roles
5 required / 8 available
Script
15 injects / 8 outcomes
01Client brief4 min
02Readiness window5 min
03Movement coordination8 min
04Arrival and recovery5 min
05Evidence and closeout5 min

Guided or collaborative. Compare eight explainable branches, or sign in to create an isolated team exercise with role claims, reconnect, and authorized private briefs.

Open Northstar
Safety manifest

A rehearsal cannot become an operation.

Inside the exercise

  • Fictional roles, organizations, locations, and records
  • Scripted decisions, injects, scoring, replay, and debrief
  • A dedicated database schema, storage prefix, and analytics stream
  • Every event and export permanently marked as simulation

Outside the boundary

  • No operator dispatch, client update, email, SMS, voice, or webhook
  • No payment, entitlement, invoice, or commerce mutation
  • No live mission, client, evidence, or operational record writes
  • No quiet fallback when a scenario, provider, or AI system is unavailable
Runtime proof

Every latch must close.

The emergency stop and database privilege boundary are evaluated independently. A green configuration without an isolated credential is still stopped.

  1. Runtime enabledRequired before execution
  2. Emergency stop clearRequired before execution
  3. Simulation credential presentRequired before execution
  4. Credential separated from liveRequired before execution
  5. Database transport protectedRequired before execution
  6. Simulation schema selectedRequired before execution
  7. Storage confined to simulationRequired before execution
  8. Live providers deniedRequired before execution
  9. Analytics classified as simulationRequired before execution
  10. Fictional-data policy selectedRequired before execution
  11. Live-table write privileges absentRequired before execution