Thunder, ThunderLang, and Thundered code
Thunder. Programming, made human. Thunder is a visual language for reading and changing the rules in software. A product manager and an engineer can open the same rule, point at the same condition, and agree on what should change, whatever language the software is written in.
| Word | What it means | How you would say it |
|---|---|---|
| Thunder | The visual language people read and change rules in | "I read the refund rule in Thunder." |
| ThunderLang | The formal language, its specification, and the compiler | "The ThunderLang spec defines at most as <=." |
| Thundered | Existing code shown in Thunder | "This is our Python refund service, Thundered so Product can review it." |
| Thundering | Turning existing code into Thunder | "Thunder the billing folder and look for the $100 limit." |
| Thunder read | Reading code visually, in Thunder | "Thunder read shows exactly where $100 is decided." |
| Thunder write | Changing code visually: edit the Thunder picture and the original code is updated and checked | "Use Thunder write to change the limit to $75." (planned) |
| OpenThunder | The IDE for Thunder: open your app, read it in Thunder, navigate it in the Atlas, change it, and verify every change | "Open the repo in OpenThunder and read the Thundered TypeScript." |
thunder |
The command-line tool | thunder plain RefundApproval.thunder-plain |
In the product, the action is Read in Thunder. The result is labeled with its source: Thundered Python, Thundered C#, Thundered Java, and View original stays one click away.
What you can do with Thundered code today
Reading code and safely rewriting code are different problems. Every Thundered rule shows the action you can actually take on it, and nothing is transformed silently.
| Level | What it means | Status |
|---|---|---|
| Thunder read (Thundered read) | See existing code's routes, rules, and checks in Thunder. The original code stays the source of truth. | Available on Read in Thunder and the refund demo for TypeScript, JavaScript, Python, Go, Rust, C#, Java, Kotlin, PHP, and Ruby |
| Thunder native | Write the rule in Thunder; it compiles to ThunderLang and generates code. Thunder is the source of truth. | Available for decisions and examples (experimental .thunder-plain and .thunder-human) |
| Thunder write (Thundered edit) | Change a Thundered rule visually and get a checked patch to the original TypeScript or Python file | Not available yet. Until it is, the action is called Propose rule change, never Update code |
Parts that Thunder cannot read stay visible as "not read", with the original source line. Thunder never draws a guess to make a picture look complete.
What the code does versus what the team wants
Thunder can read amount <= 100 and show that exactly $100 is approved. It cannot tell from that
line whether the company meant $100 to be approved. That is the question Thunder puts in front of
a person: "Here is what happens today. Is that what we want?" Thundered code is labeled as read
from code until a person answers questions such as "is this amount money?" and "why does this rule
exist?", and adds examples. See Human comprehension: design and limits.
The written form
Thunder is drawn as a picture, and stored as text so it can be versioned, reviewed in pull requests, and compiled. You never need to read the text, but you can:
Refund approval
Why: Let support resolve small refunds without waiting for a manager.
We need
the amount, in dollars
whether it is on time or late
When do we approve a refund?
Approve when all of these are true:
it is on time
the amount is at least $0
the amount is at most $100
Otherwise, Review.
Examples
$100, on time gives Approve (exactly at the limit)
$50, late gives Review (outside the refund window)
Run it with thunder plain RefundApproval.thunder-plain. The full example is
examples/human/RefundApproval.thunder-plain. This notation is experimental: one decision per
file; inputs are dollar amounts, numbers, or yes/no; dollars are checked in the text, but generated
code receives a plain number.