greymoth · Tokyo · proof, not pitch

I build in the open.

19, in Tokyo. I build fast, ship into real open-source projects, and keep an honest record of what worked — and what died.

No track record to claim yet, so here are three live, checkable records instead. Every number below is pulled from a public source you can open and verify yourself.

The record

Merged into real OSS

3 merged · more in review

Code a maintainer actually accepted: merged into medusajs/medusa and janhq/jan, with more pull requests still in review. Each merge links straight to its GitHub PR — you can verify the state yourself, and the page reads live from the API so it can't be faked.

proof-dashboard /proof-dashboard

Japan-Readiness Index

40 tools · 0 ready

I scored 40 foreign dev tools on how ready they are for the Japanese market. None had a 特商法 (legally required commerce) page; the average score was 5.6 / 100. Methodology and per-tool breakdown are on the page.

japan-readiness-index /japan-readiness-index

Builder Archive

128 built · most died

A specimen archive of 128 things I built — and the honest part: most of them died. Kept as a dissected record of the work rather than a highlight reel, because the failures are the point.

builder-archive /builder-archive

Three merged PRs is a small, early record — I present it as exactly that: live, click-through-verifiable, and growing, not a finished résumé. The point is that every claim here links to a third party (GitHub, Apple) you can check, not a number I typed myself.

Also shipped

TANE — on the App Store

live · iOS

A daily music bloom ritual, shipped past Apple's review and live on the iOS App Store (seller: Mahiro Hirakawa). Open the listing — that's the verification; Apple guarantees it, not me.

App Store /app/id6779623465

Follow the work

I build in the open — catch the next launch

Everything new ships as a public GitHub repo first. Follow me there and GitHub notifies you the moment the next one lands — no email, no algorithm deciding whether you see it.

GitHub follow = a real notification when a new public repo ships. RSS = subscribe in any reader and own the feed yourself. Both are yours — nothing to unsubscribe you, no algorithm in the way.

Coming soon email list — wiring an owned mailing list

A "get notified by email on launch" list is on the way. It's not live yet — rather than show a button that silently fails, I'd rather be honest and point you to GitHub / RSS above, which work today.

Elsewhere

dev.to — the Japan-readiness write-up