正文
THEYFELL
Put a link first and you can add what to aim at after it, like simgen.dev roast the pricing page. Optional, and it only uses what is really there.
Do not paste ID numbers or anything you would not put on a postcard. Addresses, emails and phone numbers are stripped before it is read or stored. SIN, SSN, card and passport numbers are refused outright.
That is the notice the public gets. The full autopsy goes deeper: what you actually built, the true cause of death, the time it dies, and the one real thing that could have saved it. $3.99
We will read it again in thirty days and tell you whether anything moved. One email, nothing else, unsubscribe by replying.
The notice is free and always will be. The two paid steps exist because a burn on its own helps nobody.
The joke, and the card worth sharing.
- A name for the dead thing
- A two line eulogy quoting your real details
- A cause of death and what it is survived by
- A newspaper tombstone card, yours to post
The laugh, then the thing to actually do.
- The body: what you really built, quoted back
- The true cause of death, in detail
- When it ends if nothing changes
- How to cheat it: stop this, do that, here is the proof it worked
We buried it. This is how it comes back. Judges the one page you pasted.
- A week by week plan for the next thirty days
- What your first screen says to a stranger, and what that costs
- The three things to cut, named exactly
- All of it as a branded PDF you keep, in your inbox
Not one page. Judges the whole business. Five pages, read and cross-examined against each other.
- Five pages read, not just the one you pasted
- The Gap: where your pages contradict each other. Only a five page read can see it, and you cannot see it from the inside at all
- Who bounces, at which page, and why
- Nine sections and a thirty day plan, as a PDF
Kyle Clouthier · github.com/KyleClouthierKyle promised 'Any order. Any hardware. Same bits.' across Rust, JavaScript, and Python, and the internet responded with exactly 2 stars and 0 forks. Byte-identical reproducibility achieved by absolutely nobody bothering to clone it.
...and his website, simgen.dev"Live across Toronto, New York, London" turned out to mean three browser tabs, not three data centers. 180 tests and a Lean 4 proof stack built to formally verify that nobody was using it.
The Body
Six repos, zero followers, and a flagship that promises the moon in three registers. "bitrep": "Any order. Any hardware. Same bits." Order-invariant, bit-identical FP reductions for Rust, JavaScript, and Python, with "exact sums, dot products, statistics, and reproducible quantiles," a CI that "asserts one SHA-256 across all of them" on x86-64 Linux, ARM64 macOS, x86-64 Windows and wasm32, and a browser demo. Two stars. Zero forks. Created two months ago, last pushed 38 days ago. Around it: "vacuity" and "kani-vacuity-demo," a genuinely sharp finding (a Kani harness with an unsatisfiable precondition reports VERIFICATION:- SUCCESSFUL, under a second), zero stars each. And "anomaly-characteristic-layer," 43,684 first-hand accounts of unexplained experiences. Bio says "verifiable computing." Portfolio says UFO corpus in the same drawer as the reproducibility crate.
Cause Of Death
You built the proof and skipped the claimant. The fatal flaw is not the code, it is that bitrep's README is written as a product launch for an audience that does not know you exist: no one asked for order-invariant reductions, so "the badge is the claim" persuades nobody, because nobody clicked. Meanwhile kani-vacuity-demo is the actual gold: a one-second reproduction of a formal verifier saying SUCCESSFUL about a harness no input satisfies. That is a bug report to the Kani maintainers, a filed issue, a blog post, possibly a CVE-adjacent conversation. You shipped it as a zero-star repo and moved on. Fatal because your one distributable, credible, checkable finding has no addressee, and 38 days of silence on the flagship reads as abandonment, not confidence.
Time Of Death
Roughly four to six months. The bitrep push gap crosses 90 days, the browser demo bit-rots against a toolchain bump, someone else files the Kani vacuity issue upstream and gets the credit and the thread. By month six you have seven repos, still zero followers, and "Clouthier Simulation Labs" is a company with a bio and no customers.
How To Cheat It
writing README launch copy for products nobody has been told about. Specifically, stop adding surface to bitrep, stop the third language binding, stop polishing "Any order. Any hardware. Same bits." for an audience of two stars. The multi-platform SHA-256 CI is already the strongest thing you have and it is not the thing that will get you read.
this week, take kani-vacuity-demo and file it as an issue on the model-checking/kani repository, titled plainly, for example "Harness with unsatisfiable precondition reports VERIFICATION:- SUCCESSFUL," with the under-one-second reproduction inline, the exact kani version and rustc version, the expected output, and a link to "vacuity" as a proposed detection pass with one Kani harness per clause deciding vacuity in one query. Deliverable by day seven: one filed upstream issue, plus a 600-word writeup on the same finding posted to r/rust or Hacker News with the repro pasted in the first screen. Then archive nothing except your urge to build binding number four, and add one line to bitrep's README saying what breaks without it, in one sentence, with a number.
within 30 days, either a Kani maintainer has replied on that issue, or you have your first non-zero follower count and vacuity has more stars than bitrep. Maintainer reply is the real signal. Silence on a one-second reproduction means the finding was not the finding, and you go back to the corpus.
His again, unedited: eight sections across five printed pages, generated the same way yours would be. Nothing here is a mock-up.
github.com/throwparty
github.com/carlos-menezes
www2.pnwx.com
github.com/sindresorhus
ycombinator.com
github.com/torvalds