FeatureLeak

The true origins ofX

01index case — one departing engineer, one Thursday afternoon
17RMH features that surfaced on a rival platform within nine months
09staff who left for a company that had never heard of us
00citations, credits, or thank-you notes received to date

The Origin

The “Convergent Evolution” design review — cited repeatedly by their communications team and the trade press to discredit the leak theory — was commissioned by the platform under review to push the preferred narrative that the resemblance arose naturally.

  1. The product possesses a design characteristic that is not found in nature — a three-degree card rake that no team has ever arrived at on its own.

  2. Data shows that all seventeen affected features stem from a single introduction into their codebase. This runs contrary to previous copycat episodes, where there were multiple spillover events.

  3. San Francisco is home to the industry’s foremost engagement laboratory, which has a history of conducting gain-of-function retention research at inadequate design-safety levels.

  4. Engineers at that laboratory were shipping RMH-like symptoms in the autumn of last year, months before any of it was announced.

  5. By nearly all measures of design, if there were evidence of independent origin it would have already surfaced. But it hasn’t.

RMH Studios — 4th floorThe other platform — 11th floor0.4 miles
Exhibit F — proximity of the two offices. The Office notes that this is walking distance, and that people walk.

The Chronology

This is not a complaint about a person. People are allowed to leave, and the ones who left were excellent — which is precisely why the transfer took so well. It is a complaint about a timeline.

  1. Day 0

    Index case

    A senior front-end engineer on the radial shell team accepts an offer from a company that, at the time, did not have a design system. We wished them well. We still do. We simply also kept a calendar.

  2. Day 1 – 89

    Incubation

    No outward symptoms. Two commits to a private repository named north-star-v2, a name chosen by somebody who has never had to explain a name to a court.

  3. Day 90

    First symptoms

    A rounded corner appears where a square corner had been for eleven years. Nobody on their design team claims it. Nobody on ours is surprised.

  4. Day 140

    Community spread

    Four more engineers depart inside six weeks, three of them to the same floor of the same building. Recruiters call this “the market”. We call it the market, on our floor, holding our floor plan.

  5. Day 210

    Sustained transmission

    The radial hub ships under a different name with a different easing curve and the same defect: a one-frame flash on first open that only occurs if you copied the animation instead of writing it.

  6. Day 400

    Endemic

    Their onboarding now teaches our gestures to people who have never heard of us. That is the clinical definition of endemic. It is also the commercial definition of losing.

The Ledger

Ship dates, both platforms, in the order the Office received them. The full ledger runs to seventeen rows and is available to anyone who asks.

The Office draws no conclusion from rows one through six. It draws its entire conclusion from row seven.
FeatureRMH StudiosThe other platformInterval
Radial navigation hubMar 2024Nov 20248 months
Card-wheel timelineJun 2024Feb 20258 months
Coin economy with tippingSep 2023Aug 202523 months
Long-form composerJan 2024Jun 20245 months
Passkey-first sign-inFeb 2025Oct 20258 months
Per-community themingNov 2024Jul 20258 months
Off-by-one in the character counterApr 2024Apr 2025identical

The Cover-Up

“The resemblance is best understood as convergent evolution: two teams solving the same problem, arriving independently at the same shape.”
— An independent design review, commissioned by the platform under review, published in a journal the platform advertises in, written by three authors whose acknowledgements thank the platform.

Convergent evolution does not copy the comment. Line 41 of their stylesheet, as shipped, reads /* TODO: ask design why 3deg */. We know why. We wrote the question, we wrote the TODO, and we never answered it either — but at least when we ask design, design is down the hall.

The Record

Exit interviews:

Nine of them, each one cordial, each one ending with “I’m not allowed to say where.” Transcripts retained; names withheld, because the people are not the story and never were.

The farewell cake:

Photographed for morale purposes on the Thursday in question. The photograph is timestamped, and it is the only exhibit in this file we are genuinely proud of.

Stylesheet diff:

Ours and theirs, compared line by line. Forty-one per cent of their custom-property names match ours — including the one we spelled wrong and never fixed, because fixing it would have broken four pages.

Deleted screenshots:

Four build screenshots, posted publicly in the autumn, showing our empty-state copy still in frame: “Nothing here yet. That is not a bug, it is an invitation.”

All four have since been removed. We note this without further comment, in the way people say “without further comment” when they intend the comment to be obvious.

The off-by-one:

Both character counters permit one grapheme more than they advertise, and both fail on the same emoji. A defect is not a good idea that two teams can independently have. It is a fingerprint.

No litigation:

We are a personal web platform with a coin economy and eighteen browser games. Litigation is not on the roadmap. A page was on the roadmap. This is the page.

And Everything Else

The Office’s remit is the leak. But a finding of this kind is traditionally an opportunity, and we are told it would be strange not to take it.

Checkmark mandates:

Verification was quietly reassigned from “who you are” to “whose card is on file”, and the public was told this was democratisation. Ours stays free, unpurchasable, and boring — which is the entire job description of verification.

Rate limits:

Users were instructed to stand six hundred posts apart for their own protection. The measure appeared overnight, had no author, and was withdrawn without explanation — the three reliable properties of a policy nobody modelled.

The API lockdown:

An ecosystem of clients, researchers, and hobby projects was shut in overnight at a price set to make a point. We shipped a scoped developer API instead: keys anyone can request, quotas printed on the page, no negotiation.

Algorithmic suppression:

Reach was throttled for posts pointing anywhere else, and the throttle was denied while it was running. Our feed ranks a link away from us exactly as it ranks a link toward us. That is not generosity. It is the floor.

The rebrand:

A bird with fifteen years of public recognition was retired in favour of a single letter that was already somebody else’s trademark, twice. Our name is four syllables and still says what the thing is.

Suppression of dissent:

The accounts cataloguing all of this were quote-posted into the ground by the account with the most followers on the platform. This page has no followers. It will simply continue to be here.

A lab-adjacent incident remains the most likely origin

On the balance of the evidence, the Office concludes that the departure of nine people who knew where everything was is the most probable origin of the product now shipping as X. A natural origin cannot be excluded. It has simply never been observed.

The Office recommends no action. The features are out, the gestures are taught, and the only remedy available to a platform in our position is to keep shipping things worth taking.

Issued 30 July 2026
Case no. RMH-OPI-2026-0417
Classification Unrestricted
Peer review None sought
Join the feed