Known ground
- Seed
- Killer T cell
- Memory cell
Each seed asks a question someone already thought to ask, on every platform where it can run properly. This loop protects what already works.
Agents hunt for bugs in Empryo every day. A second model has to reproduce each report before it counts, every fix ships a lint rule so the same bug cannot come back, and 387 automated checks run against the real build.
A bug is one file, and the folder it sits in is its state. Each agent does one job, writes its part and moves the file on. Nothing moves without proof.
Hunters read one slice of the code for one kind of bug. A report counts only when they reproduced it in a throwaway home folder.
A reviewer on a different model runs the reproduction again, then approves the report or throws it out.
A fixer removes the root cause in the terminal app, the desktop app and headless mode, and proves it before and after.
A fix reviewer reruns the proof. It is pass or fail, and a pass with a minor issue is a fail.
The fix lands as one commit, with a lint rule that fails whenever someone writes the same mistake again.
101 more reports were thrown out on review: a second model could not reproduce them, or the behaviour was intended.
Each hunt sends agents into the code at once, every one with a slice of it and one kind of bug to look for.
A fix without its guard is not done. The next agent that writes the same mistake fails the lint before anyone sees it.
746lint rules, written with the fixes
A rule ships with its fix. It has to flag an example of the bug, pass the fixed version, and find the same mistake nowhere else in the code.
2,348risky patterns counted, and the count only goes down
Swallowed errors, empty catch blocks, waits on the clock and unsafe casts are counted across the code and committed as a floor. Raising it takes a diff with a name on it.
The machine finds new bugs, and the checks keep the old ones fixed. This is a real slice of them, played back from its report.
0of 26 done
September 23, 2026, Empryo 3.8.6-beta, build df8921843
0 of 26 doneTwo real reports from the same slice, 13 checks on the modes area run on macOS and then on Linux. Windows was not part of this slice.
Each area of the product, how many checks guard it, and how I try to break it.
No broken layout, no raw markdown, no blank window.
How I try to break it
We read the terminal the way you would, shrink it to 62 columns mid-session, and compare the result against a reference picture.
The 8 things a person does with Empryo, from installing it to removing it, and the features no check aims at yet.
3 of 8 steps are covered today. A step counts only when a check starts on a clean machine and installs from the signed download first.
161of 545 features have a check aimed at them
The total comes from the app itself, so a new feature shows up here as unchecked the day it ships. The other 384 are walked by the explorer checks instead.
Each kind is named after a part of the immune system, and they find bugs in two ways.
a single check
One promise written down: what to do, and what must be true afterwards.
runs the checks
Runs one seed on one operating system, in the terminal, desktop or headless app. On Linux and Windows it uses the same build you download.
always on
Runs alongside every check without being asked. It catches crash messages, garbled screens and stray escape codes, even when no seed was looking for them.
the explorer
Uses the product the way a person would, looking for things that are missing rather than things that are broken.
the sceptic
Challenges every new finding before anyone trusts it. Findings it disproves never turn into false alarms.
never forgets
Created from a confirmed bug. It checks for that bug on every run from then on.
Each seed asks a question someone already thought to ask, on every platform where it can run properly. This loop protects what already works.
A check cannot notice what is missing, so dendritic cells use the product like a person and note what should be there and is not. Claims that survive negative selection become new seeds.
Both loops end the same way: with a new check that runs on every test run from then on.
A full run: every check, on more than one machine.
Finished on September 29, 2026, on Empryo 3.8.7-beta, in 39 minutes
349checks ran
On Linux and Windows the checks use the release archive you download. A filled dot means the checks really drive that form of the app; a half dot means they only confirm that it starts.