THEYFELL: paste anything. get the brutal obituary it earned. free.

What the paid autopsy looks like Kyle Clouthier · github.com/KyleClouthier Here Lies bitrep Kyle 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. Cause of Deathverified correct on every architecture, adopted on none Survived bya CI badge, four golden hashes, and 43,684 unrelated ghost sightings ...and his website, simgen.dev Cairn, Serverless Trust, Petawawa Edition "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. Cause of Deathadversarially tested by an audience of zero That is the free notice, on the person who built this site, GitHub and website both. Below it is his real paid autopsy, unedited. Your turn. Theyfell · The full autopsy, what $3.99 buysCase No. 1788357179733_e0cda1 · 2 SEPTEMBER 2026 bitrepKyle Clouthier · github.com/KyleClouthier The BodySix 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 DeathYou 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 DeathRoughly 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 ItStopwriting 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.Do insteadthis 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.Proofwithin 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. theyfell.com · the graveyard of good ideas and bad ones And what the $49 post-mortem looks like His again, unedited: eight sections across five printed pages, generated the same way yours would be. Nothing here is a mock-up.