The board

It shows you the whole deck first

Crew Chief scans and tells you what it found and what it intends to do. Nothing is closed until you press launch.

RTSS Hostilewill be closed
Discord Hostileoverlay stowed
SRS Radio Coldlaunches at step 4
Six steps

Every sortie runs the same way

1C-RAM Scan. Closes the overlays that fight DCS.
2Flight Systems Check. Headset, drivers, DLSS, mods.
3SEAD Strike. Steam's overlay file, Discord's hook.
4Catapult Prep. Starts what you do want, in order.
5AWACS Active. DCS runs. It goes quiet and watches.
6Debriefing & RTB. Everything from step 1 comes back.
Afterwards

It writes down everything it changes

Written to your drive before it acts, so an interrupted sortie is a delay rather than a mess — the next launch finishes the cleanup first.

RTSS Restoredrunning again
Discord Restoredoverlay back
HDR Restoredas you had it
Crash dossier

The bad day, already documented

GPURTX 4090 · 566.36
VRVarjo Aero
DCS2.9 · Standalone
Logdcs.log captured

One folder per crash, so a new one never wipes out the last one's evidence.

Drop it into Gemini or Claude and start from facts instead of "it crashed again".

Threat Board 3 contacts
It looks before it acts