Phase 1's job is to prove the architecture by walking one path all the way through. You open a catalogue, see a plot on a map, select tracks, run a Python tool, and see its result on the map. That now works in VS Code.
Phase 2 is about trust. An analyst should be able to try something, take it back, have Debrief die mid-save, or share a plot with a colleague who changes it at the same time, and never lose work or have it overwritten without being told.
Debrief's analysis runs in Python and its interface in TypeScript. Every piece of data that passes between them is defined once, so the two sides cannot quietly disagree.
The public demonstration of Debrief will run its Python analysis tools inside your web browser. We checked that it works before building on it.
You no longer need to install anything to try Debrief v4. The blog now has demos you can play with: the real map, tool forms and Python tools, running in your browser.