フィールドノート
公開は git commit ひとつです。翻訳のあるノートは表示中の言語で、それ以外は書かれた言語のまま載せています。
One reading of Musk's companies has them converging into a single vertical chain: power, chips, compute, a model, robots. I drew it as an architecture diagram, then checked it line by line against SpaceX's S-1 and public reporting. The frame holds, three claims were wrong, and the one arrow that runs back carries money.
With enough projects, every new thing raises the same question: which repository does it belong in? On 30 August I wrote the answer down as four questions asked in order. A rule about graduation came later: things grow in a lab first and move into a repository of their own once they're ready.
On 10 October I put the same short film, an astrolabe drawn from code, on six platforms. Xiaohongshu liked it, a paid boost on Bilibili bought a thousand views and a few hostile comments, and on Douyin fewer than 2% of viewers saw it through. What that did to the line I'd written about making works, not traffic.
I keep a token monitor running. By 13 October it counted 47.9 billion tokens over 196 active days, and a billion-token day has become ordinary this month. The money goes on three subscriptions; most of the time went into foundations and rules nobody sees. That is how one person keeps twenty-five projects moving.
On 2 June I started a Next.js template for myself, yTemplate. Over four months it grew layer by layer from the colour variables at the bottom: themes, components, dense cards, page layouts, one dataset seen many ways, and finally many management systems that look and behave the same.
Every AI session starts from nothing, and whatever I said in chat is gone in the next one. For months I've been writing how things are done into files that live next to the code: feature ledgers, page rules, release cards, and the rules added after something went wrong.
On 8 October I made a page with an astrolabe you can turn by hand. The next day it grew into a film, and the day after that the film went out seven times on six platforms. I split that chain into four layers: source, work, series and engine, with a number that decides when one layer becomes the next.
yPulse is the back office of my project matrix. Most of the time nobody looks at it; it runs on clocks and events. This note starts from a diagram of its six workflows: when each one starts, what it writes, and what happens when one of them breaks.
平台给不给个人账号开放发布接口，以前决定了发布能交给机器多少。这一周我让 AI 在浏览器里代填了四个平台的投稿表单，它每次都停在发布按钮前，最后那一下由我来点。
How this site went from a fresh yTemplate fork to a branded, data-fed stage in one working day — with an AI team doing the heavy lifting.