Collect
Pull public work back from platforms.
WeChat essays, future X threads, and GitHub repositories are treated as one editorial substrate instead of three disconnected channels.
About the author and the publication
This is not a social mirror, but a long-term publication that keeps AI systems judgment, public writing, and open-source practice on the same page.
The author's public work should not remain scattered across platforms. The site exists to reorganize that work into a calmer, searchable, and compounding public structure.
Treat WeChat as the long-form layer, X as the field-note layer, GitHub as the execution layer, then edit them back into one publication.
Method
How the site turns scattered platforms back into a publication.
Reframe
Sort by question, not by feed mechanics.
The site reorganizes content into recurring technical questions so visitors can enter through judgment and themes rather than timelines alone.
Compound
Turn writing into durable public infrastructure.
Projects, essays, notes, and future support products are meant to reinforce one another rather than compete for attention.
Source to publication
Platforms are only entry points. The site is the durable memory.
WeChat holds long-form essays, X captures field judgments and threads, and GitHub turns those judgments into public engineering evidence. The site does not merely aggregate them; it reorders them for reading and search.
That is why the design avoids reproducing a social feed and instead prioritizes archive pages, topic dossiers, project narratives, and future support flows. The key metric is returnability, not raw update speed.
Current three-layer stack
- Long-form layer: imported WeChat essays for full arguments
- Topic layer: dossiers reorganize material around recurring questions
- Execution layer: GitHub projects act as practical evidence and brand assets
Future expansion
- Automated X sync once the official or chosen ingestion path is finalized
- WeChat archive refresh on a calmer schedule rather than aggressive polling
- GitHub dossier pages and deeper per-project narratives
- Stripe-backed patronage, reports, and lightweight product experiments
Future monetization rule
Revenue can be added gradually, but the site cannot collapse into a sales page.
Patronage, memberships, reports, consulting, and lightweight products all remain possible, but they must sit on top of public credibility rather than appear before it.