Node-Rendezvous with the Atlas
Captain
Horizontal Planning Table
Weapons
Pilot
Comms / CommsIntel Interface
Recon
Engineering
Scientist
Executive Display
Comms Messaging

Phase Evasive action

Trigger Event: End of previous Node after Transit Post Deceleration exits on propulsion-reverse-state = 0

Duration: 15 sec

Exit Trigger: MGC/Unity emits ship-full-stop

Source line 31

Phase Communication with and Sensing Atlas

Trigger Event: {"type": "sentinel", "event": "ship-full-stop", "mgcObservable": true}

Duration: 3 minutes

Exit Trigger: CaptainStation::ExecutiveDisplayUnit executive-display-event/button-pressed/Acknowledge

Source line 139

Phase Assessing The Situation

Trigger Event: {"type": "previous_phase_end", "authority": "Captain acknowledge event from prior phase"}

Duration: 4 minutes

Exit Trigger: MGC-owned phase duration timeout

Source line 400

Phase Combat and Retrieval Plan

Trigger Event: MGC-owned phase duration timeout from Assessing The Situation

Duration: 4 minutes

Exit Trigger: MGC-owned phase duration timeout gated by chosen-plan != NULL and planning-meeting-started == 1

Source line 523

Phase End Meeting Prepare For Combat

Trigger Event: {"type": "previous_phase_end", "authority": "gated MGC-owned planning timeout"}

Duration: 15 sec

Exit Trigger: MGC has received both final-meeting-ended = 1 and final-red-alert-confirmed = 1

Source line 744

CaptainWhisperer

CaptainWhisperer

shooting-meteors.png

  • Set ship to Battle Stations if not already set
  • Shields Up!!! Order Weapons to activate forward shields immediately
  • Order Weapons to destroy large debris that is too close to evade
  • Order Pilot to take evasive action and bring Musketeer to a full stop
  • Order Comms to silence the ship-wide alarm once the crew has heard the emergency cue
  • Monitor crew response and keep the ship coordinated through the emergency
  • shooting-meteors.png should show the ship in an asteroid field with shields on and debris being cleared by weapons fire.
  • If the ship is already at Battle Stations from the high-G retardation sequence, this is a confirmation rather than a new state change.
  • MGC/Unity owns the authored ship-full-stop condition for ending this immediate evasive phase.

Message Append

CaptainWhisperer

On MGC from CaptainStation::ExecutiveDisplayUnit, message ship-alert-level, value 3

WeaponsWhisperer

WeaponsWhisperer

shooting-meteors.png

  • Activate shields to Fore immediately
  • Use the Turret Gun to destroy large debris that is too close to evade
  • Prioritize hazards directly in front of Musketeer
  • Monitor shield health in case of shield impact
  • System will send warnings if shield is low
  • If Shield health goes too low, re-energize it using Shield Capacitors

PilotWhisperer

PilotWhisperer

evasive-action.png

  • Immediate collision hazard
  • Take evasive action
  • Bring Musketeer to a full stop as quickly as possible
  • At regular non-hyperspeed operation, your throttle can stop Musketeer
  • Avoid large debris while managing deceleration
  • PilotStation::PilotWhispererUnit notification = Collision alert

CommsIntelWhisperer

CommsIntelWhisperer

alarm-silencing-illustration.png

  • On Captain's order, silence the ship-wide alarm.
  • This does not clear the collision hazard.
  • Keep monitoring Atlas communications.

Message Append

CommsIntelWhisperer

On MGC from CommsIntelStation::CommsIntelDisplayUnit, message set-ship-state, value 0, state ship-wide-alarm-state

ReconWhisperer

ReconWhisperer

Recon-Radar-and-Periscope-Illustration.png

  • Debris field and ship wreckage detected at close range
  • Call out major hazards and fast-closing debris to the Captain and Pilot immediately
  • Use radar to help the Pilot find the safest path to full stop
  • ReconStation::RadarUnit notification = Collision alert

EngineeringWhisperer

EngineeringWhisperer

engineering-station.png

  • Ensure that helm has power for maneuvering
  • Ensure shield capacitors are charged when they are used up
  • Use the Ship Damage Assessment interface to monitor for hull damage
  • Report any hull damage to the Captain

incident-radiation-response

incident-radiation-response

Immediate

ScienceWhisperer

ScienceWhisperer

ship-in-transit.png

  • Super High-G Deceleration has ended
  • Ensure Inertial Dampeners are disabled
  • Monitor Ship Atmosphere for life support
  • Assist Captain and Comms-Intel to analyze Atlas Fleet communication and data

Message Append

ScienceWhisperer

On MGC from ScienceStation::ControlPanelUnit, message set-ship-state, value OFF, state inertial-dampeners-state

CaptainWhisperer

CaptainWhisperer

illustration-of-atlas-n-attila.png

  • Set ship state to Yellow Alert
  • Order Pilot to hold Musketeer at a safe standoff distance from Atlas and maneuver to avoid debris
  • Order Recon to do a full scan of the Atlas fleet and tag each ship
  • Order Comms-Intel Officer to monitor Atlas messages and report, and to analyze tagged objects and scans
  • Order Scientist to assist you in analyzing and assessing the situation
  • Order Engineer to assess ship damage and commence repairs
  • Order Weapons to keep vigilant and to use Turret Gun to protect ship from floating debris
  • Keep the assessment procedure on the Executive Display and mirror it to the Wall Display for the crew
  • CaptainStation::ExecutiveDisplayUnit set-procedure-display-payload = {'Page': {'Illustrations': ['illustration-of-atlas-n-attila.png'], 'Title': 'Atlas Assessment', 'Content': ['Pilot hold at safe standoff distance and maneuver to avoid debris', 'Recon scan and tag all vessels in the Atlas fleet', 'Comms-Intel monitor Atlas communications and report', 'Comms-Intel analyze Atlas fleet as they are scanned and tagged by Recon', 'Scientist assist the Captain and Comms-Intel to analyze and assess the situation', 'Engineering assess ship damage and commence repairs', 'Weapons keep vigilance and protect Musketeer from debris with the Turret Gun']}}
  • CaptainStation::ExecutiveDisplayUnit activate-display display ProcedureDisplay = None
  • The debris field should continue being a problem even with the ship at stop, requiring repositioning and defense.
  • The ship can take damage.

CaptainWhisperer

CaptainWhisperer

  • Atlas's welcome message does not match Earth Planetary Defense orders
  • Reply directly to the Atlas hail with Musketeer's mission orders and intent
  • Discuss with Comms, Recon and other crew
  • Captain is acting from Earth Planetary Defense orders; live CommsIntel analysis becomes urgent after Atlas reacts with threats.

CaptainWhisperer

CaptainWhisperer

caution-needed.png

  • Try to make sense of Atlas communication
  • Atlas response conflicts with Earth Planetary Defense orders and visible damage. Get evidence.
  • For now, just acknowledge the message, do not reply or you may make things worse
  • Order Comms-Intel and Recon to gather more information on the Atlas fleet to see if it matches Atlas messages
  • Order Scientist to assist in the analysis and reasoning

Message Append

CaptainWhisperer

On MGC from CaptainStation::ExecutiveDisplayUnit, message ship-alert-level, value 2

WeaponsWhisperer

WeaponsWhisperer

  • Report Atlas radiation leak to the Captain

WeaponsWhisperer

WeaponsWhisperer

shooting-meteors.png

  • Keep monitoring and shielding against Atlas radiation
  • Monitor your shield health, you are using both regular and radiation shields
  • Monitor shields and deploy to Fore or Aft to protect the ship
  • Use Turret Gun to clear path in front of ship in case we need to move
  • Use Turret Gun to protect against collision with debris field
  • Keep vigilant

PilotWhisperer

PilotWhisperer

ship-in-transit.png

  • Hold Musketeer at standoff distance from Atlas
  • Maintain position for scanning
  • Be ready to reposition in response to moving debris field

thruster-trim

thruster-trim

stochastic probability 0.7 period 180 sec

CommsIntelWhisperer

CommsIntelWhisperer

comms-console.png

  • Recon has been scanning the Atlas fleet and forwarding you information
  • Use the Intelligence Analysis interface to analyze the current state of Atlas and escorts.
  • Recon is tagging and collecting images and data for the Intelligence Analysis interface
  • Use the Intelligence Analysis to make a plan to get warhead from Atlas and complete the mission
  • Penetrating-radar results should not magically become a finished route map.
  • Atlas damage prevents it from naming the Cartel explicitly.
  • The tone should feel unstable, grandiose, and messianic rather than coolly tactical.

ReconWhisperer

ReconWhisperer

Recon-Radar-and-Periscope-Illustration.png

  • Focus on the Atlas using the periscope
  • Scan Atlas from standoff distance
  • Tag the Atlas and surviving escorts
  • Take pictures using thermal, energy signature, visible, and radiation sensing
  • Take pictures with penetrating radar where possible to trace interior continuity and likely rover routes
  • When you are done tagging and taking pictures, assist Comms-Intel with analysis
  • Recon tagging should create object identifiers that MGC can route into Comms-Intel Tag, Science analysis, and the Captain shared analysis surface.
  • Mocked-up Atlas images are needed for Comms-Intel analysis.

EngineeringWhisperer

EngineeringWhisperer

engine-and-propulsion.png

  • Monitor ship strain and power while the crew studies Atlas
  • Monitor power use from Weapons. Both regular and radiation shields are in use
  • Be ready to shift power to shields and propulsion if Atlas turns hostile
  • Track whether Atlas or the escorts are showing any power rise that suggests imminent weapons activity

ScienceWhisperer

ScienceWhisperer

science-analysis-illustration.png

  • Assist Recon, Comms-Intel and Captain to assess the situation
  • Compare Atlas traffic to Recon scan data
  • Determine what Atlas systems are actually still alive
  • Identify what kind of damage disabled Atlas
  • Evaluate whether any docking approach remains survivable once Atlas damage and escort threat are considered
  • Flag any evidence that Atlas was disabled by weapons fire rather than accident
  • Report clearly whether Atlas's mission claims are technically plausible
  • Science analysis should surface why the crew knows Atlas propulsion is dead and why the damage pattern points to weapons fire.
  • Ship AI should estimate that docking success is approximately 0.1% once the damaged primary dock, exposed fallback dock, and escort threat are combined.

for-captain-incoming-message

for-captain-incoming-message

Immediate

  • From: Atlas Command AI
  • Classification: Open

for-captain-outgoing-message

for-captain-outgoing-message

CaptainStation::ExecutiveDisplayUnit executive-display-event/button-pressed/Reply

  • From: USS Musketeer
  • To: Atlas Command AI
  • Classification: Routine/Open Operational

for-captain-incoming-message

for-captain-incoming-message

10 sec. after CommsIntelStation::CommsIntelDisplayUnit message-sent value 1

  • From: Atlas Command AI
  • Classification: Open

CaptainWhisperer

CaptainWhisperer

intelligence-analysis-interface.png

  • Order Pilot to prepare for combat and to continue avoiding debris field
  • Order Engineer to prepare the ship for combat then join the analysis and planning
  • Order Weapons to keep vigilance for moving debris and to join planning when possible
  • Order Comms and Recon to assess the status of the Atlas fleet at the Comms Intelligence Analysis Interface
  • Order the Scientist to assist you at the Horizontal Planning Table to plan the retrieval of the Warhead using the robot rover. The Scientist will drive the rover later
  • Recon penetrating radar scan of Atlas has been routed to the Horizontal Planning Table
  • The Horizontal Planning Table AI will help you to plan a route through the damaged ship
  • You will have 4 minutes to do your analysis
  • CaptainStation::WallDisplayUnit display-countdown-clock = 4 min
  • Horizontal Planning Table runtime work is compiled as its own joint-planning activity.

CaptainStation-Annex::HorizontalPlanningTableUnit

CaptainStation-Annex::HorizontalPlanningTableUnit

  • Route planning for rover to retrieve the warhead

Participants

  • Captain
  • Scientist
  • CaptainStation-Annex::HorizontalPlanningTableUnit load-planning-scenario = atlas-penetrating-radar-data.json
  • The Horizontal Planning Table is physically in the Captain's planning area, but this is joint planning activity.
  • This is dock and retrieve scenario
  • Combat and insert plan has not yet been developed
  • We will need a json schema so that the planning can be data-driven. We don't want to write the Atlas-specific-route-planning into code.
  • `atlas-penetrating-radar-data.json` datafile will be routed to the CaptainStation::HorizontalPlanningTable Display Manager.
  • This data has still to be defined by the DM developer.
  • A route planning interface will be developed for the Horizontal Planning Table.
  • The plan will be used during the retrieval phase but will have to be adapted for the later battle plan.

WeaponsWhisperer

WeaponsWhisperer

shooting-meteors.png

  • Keep Vigilance with Regular and Radiation Shields
  • Keep all your cartridges charged with Kinetic Ammunition
  • Use the Turret Gun to keep the front of Musketeer clear in case rapid maneuver is needed
  • MGC should route the AI service-link weakness to the Captain shared display and to Scientist after Comms completes the analysis.
  • The draft should make clear that this weakness comes from recovered Atlas information.

PilotWhisperer

PilotWhisperer

pilot-targeting.png

  • Your visor Targeting mode uses the same visor hardware as the Sextant and lets you fire missiles at Atlas gun ports and the escorts
  • Practice firing missiles at larger debris and objects in the asteroid field
  • You may need the targeting system later in the mission
  • Hold Musketeer at standoff distance from Atlas
  • Be ready to reposition in response to moving debris field
  • Keep a clear forward path in case rapid maneuver is needed

thruster-trim

thruster-trim

stochastic probability 0.7 period 240 sec

CommsIntelWhisperer

CommsIntelWhisperer

intelligence-analysis-interface.png

  • The Recon officer has tagged and scanned the Atlas and its escorts
  • The tag and scan data have been uploaded to your Intelligence Analysis Interface
  • Select Intel Analysis on the Comms-Intel screen
  • The Intelligence Analysis System AI will help you with your analysis
  • The Recon officer will help you with the analysis
  • When you are done with analysis, upload your findings to the Horizontal Planning Table to plan the mission
  • CommsIntelStation::CommsIntelDisplayUnit load-analysis-dataset display Analysis = atlas-fleet-analysis.json

ReconWhisperer

ReconWhisperer

intelligence-analysis-interface.png

  • Work with Comms to analyze the scans and information you collected of the Atlas fleet

EngineeringWhisperer

EngineeringWhisperer

engine-and-propulsion.png

  • Plan power routing for a close attack run with heavy shield load
  • Be ready to sustain propulsion and shields while the rover is delivered
  • Shields in use can drain shield capacitors quickly; recharge shields as needed

ScienceWhisperer

ScienceWhisperer

rover-in-operation.png

  • You will be driving the robot rover to retrieve the warhead from Atlas
  • Recon penetrating radar scan of Atlas has been routed to the Horizontal Planning Table
  • The Horizontal Planning Table AI will help you to plan a route through the damaged ship

CaptainWhisperer

CaptainWhisperer

horizontal-table-planning.png

  • Call a meeting to plan the retrieval of the Warhead
  • Press the Ship State: Meeting button to start the meeting
  • Order the Pilot and Weapons Officer to keep the ship safe while you are planning
  • Order the Engineer to keep sufficient power to propulsion and weapons and to join the planning
  • Order all other crew to join the planning meeting
  • Use the Horizontal Planning Table to do the planning
  • The Analysis Outcomes from the Intelligence Analysis Interface has been loaded to the Horizontal Planning Table
  • Horizontal Planning Table AI will help you with your planning
  • You can continue to use the Intelligence Analysis Interface
  • You will have 4 minutes to do your analysis
  • You can open the Procedure screen in the Executive Display as a planning guide
  • Mirror the Procedure screen to the Wall Display using the Mirror Switch
  • CaptainStation::WallDisplayUnit display-countdown-clock = 4 min
  • CaptainStation::ExecutiveDisplayUnit set-procedure-display-payload = {'Page': {'Illustrations': ['horizontal-table-planning.png'], 'Title': 'General Planning Procedure (OODA Loop)', 'Content': ['Observe: How strong is the Atlas Fleet? What is the disposition of Atlas? What are vulnerabilities?', 'Orient: Can Musketeer defeat the Atlas fleet? What other ways can the Warhead be retrieved?', 'Decide: choose a workable plan and assign tasks to the crew', 'Act: put the plan into action']}}
  • CaptainStation::ExecutiveDisplayUnit activate-display display ProcedureDisplay = None

Combat Retrieval Planning Meeting

Meeting Card

  • Captain leads the retrieval-plan meeting at the Horizontal Planning Table.

CaptainWhisperer

CaptainWhisperer

horizontal-table-planning.png

  • Coordinate to plan the retrieval of the Warhead
  • Press the Ship State: Meeting button to start the meeting
  • Order the Pilot and Weapons Officer to keep the ship safe while you are planning
  • Order the Engineer to keep sufficient power to propulsion and weapons and to join the planning
  • Order all other crew to join the planning meeting
  • You can open the Procedure screen in the Executive Display as a planning guide
  • Mirror the Procedure screen to the Wall Display using the Mirror Switch

snippet-meeting-state-still-off

snippet-meeting-state-still-off

On phase timeout when planning-meeting-started == 0

CaptainStation-Annex::HorizontalPlanningTableUnit

CaptainStation-Annex::HorizontalPlanningTableUnit

  • Joint OODA planning for Warhead retrieval, combat distraction, rover insertion, and selected plan assignment.

Participants

  • Captain
  • Scientist
  • Comms
  • Recon
  • Engineer (with own duties)
  • Weapons (as possible)
  • CaptainStation-Annex::HorizontalPlanningTableUnit load-planning-scenario = atlas-combat-planning.json
  • The Horizontal Planning Table is physically in the Captain's planning area, but this is joint planning activity.
  • The captured `chosen-plan` payload updates the node-scoped `defStateVar chosen-plan` declared for this planning branch.
  • We will need a json schema so that the planning can be data-driven. We don't want to write the Atlas-specific-plan into code.
  • We want the players to 'think that they came to their own conclusions' while preventing them from getting lost
  • The Horizontal Planning Table (HPT) interface needs provide clear interaction affordances that align with the OODA loop tasks (e.g., AI Recommendation Request, Vulnerability Analysis, ...)
  • We need a recommendation selection button on the HPT so we know what plan was selected

Message Append

CaptainStation-Annex::HorizontalPlanningTableUnit

On MGC from CaptainStation-Annex::HorizontalPlanningTableUnit, message plan-selected

  • Phase local: chosen-plan = {chosen-plan}

WeaponsWhisperer

WeaponsWhisperer

shooting-meteors.png

  • Keep Vigilance with Regular and Radiation Shields
  • Keep all your cartridges charged with Kinetic Ammunition
  • Use the Turret Gun to keep the front of Musketeer clear in case rapid maneuver is needed
  • Keep an eye on the planning meeting so you know the plan and can help make the plan

PilotWhisperer

PilotWhisperer

pilot-cockpit.png

  • Hold Musketeer at standoff distance from Atlas
  • Be ready to reposition in response to moving debris field
  • Keep a clear forward path in case rapid maneuver is needed
  • Join the planning meeting as you are able

thruster-trim

thruster-trim

stochastic probability 0.7 period 240 sec

CommsIntelWhisperer

CommsIntelWhisperer

horizontal-table-planning.png

  • Join the planning meeting at the Horizontal Planning Table
  • The Procedure Display on the Wall screen provides the overall process
  • You can return to the Comms-Intel Station to use the Intelligence Analysis Interface for more analysis if needed

ReconWhisperer

ReconWhisperer

horizontal-table-planning.png

  • Join the planning meeting at the Horizontal Planning Table
  • The Procedure Display on the Wall screen provides the overall process

EngineeringWhisperer

EngineeringWhisperer

power-distribution-interface.png

  • Provide sufficient power to engines, helm, weapons, and shields
  • Then join the planning meeting at the Horizontal Planning Table
  • The Procedure Display on the Wall screen provides the overall process
  • If Pilot or Weapons request more power you may need to go back to engineering

ScienceWhisperer

ScienceWhisperer

horizontal-table-planning.png

  • Join the planning meeting at the Horizontal Planning Table
  • The Procedure Display on the Wall screen provides the overall process

CaptainWhisperer

CaptainWhisperer

battle-stations.png

  • End the meeting (press Ship State: Meeting button again)
  • Set ship to Battle Stations
  • Order crew to take places and execute the plan
  • CaptainStation::ExecutiveDisplayUnit notification = Meeting Time Ended

End Planning Meeting

Meeting Card

  • Captain closes the planning meeting and moves the ship to battle readiness.