Public proof chain
This page is the shortest route from my headline claims to durable artifacts. Each item links to a live page, repository, paper, or technical write-up so the proof can be inspected instead of trusted.
Owned quality strategy for high-traffic anti-crawler, frontend security, circuit breaker, and degradation surfaces while maintaining zero P0/P1 incidents across owned production areas.
Turned an Obsidian knowledge base, Codex skills, and repo-local rules into a durable loop that writes, audits, and improves public software assets.
Recovered and studied 1,884 Claude Code source files, then packaged the architecture into a bilingual public tutorial and long-form technical essay.
Built a Go proxy server that exposes OpenAI/Gemini/Claude/Codex-compatible APIs with OAuth login, provider routing, and multi-account load balancing.
Published research on self-supervised few-shot semantic segmentation, reducing model parameters by 87% while preserving the core learning objective.
Maintains a Next.js + MDX public site with search, RSS, structured metadata, static GitHub Pages deployment, and an Obsidian-to-site publishing path.
Start with the proof chain when evaluating signal, then use the experience page for career context and the blog for deeper reasoning. The goal is not a portfolio gallery; it is a connected trail from claim to artifact to implementation detail.