Thunder Atlas · Prototype
Read a whole app in Thunder.
A small shop with three services in TypeScript and Python, read in Thunder. The Thunder Brief gives the big picture, the Thunder Map shows how it is built, Thunder Focus says where to look first, and every rule opens as Thunder Code. Start with Focus: two services disagree about the same refund.
Light up everything that reads a fact or can answer an outcome:
Thunder Brief · your app on a page
3 services in Python and TypeScript. 4 rules Thunder can draw, 4 outside connections, and 5 places worth looking at first.
Decides 2 things (fraud risk, approve refund); calls Stripe; writes the refunds table; announces refund.issued; 1 function Thunder can't fully read yet.
Decides 2 things (approve refund, shipping option); calls billing; 1 function Thunder can't fully read yet.
Calls Email provider; reacts to refund.issued; 1 function Thunder can't fully read yet.
Thunder Map · how the services connect
- billingnotifications(billing announces refund.issued; notifications reacts)
- checkoutbilling(checkout calls billing over HTTP)
Prototype. Rules come from the real Thunder code reader. Services, files, and outside connections are found with simple, visible patterns in this sample; in OpenThunder they come from full repository discovery. Everything here is read from code: Thunder shows what the code does today, and a person decides whether that is what the business wants.