An agent's most dangerous output isn't bad code — it's the word "done." The whole point of a pure core, a one-command verify, a separate verifier, and an evidence ledger is to take the verdict out of the author's hands and make "done" a thing that's proven rather than felt. This is the substrate the rest of the series was building toward.

The reflex when an agent misbehaves is to add a sentence to CLAUDE.md. It's wrong in two directions: instruction files are context, not enforcement, so the rule won't bind under pressure — and the longer the file gets, the more it pollutes the context that makes the agent reliable. Load-bearing rules belong in hooks, lint, and CI. The prose should get shorter.

An agent is excellent at honoring a contract it can see and terrible at preserving one it can't. The boundaries that survive the agentic era are the ones written into the repo as typed, tested, importable things — and the ones that break are the stringly-typed promises that lived only in a team's shared memory.

The maintainer of your repository quietly changed from a human who remembers to an agent that re-derives everything from the files each session. Once you accept that, the repository stops being documentation and becomes an interface. Directory layout is the navigation API, contracts are the constraint API, and verification is the validation API.

从一篇「AI 写代码该选什么语言」的讨论说开去。当 AI 既写代码又当审稿人，选语言的判据不是它对 AI 多熟、也不只是循环多快，而是一次绿灯替你排除了多少错——而最大的陷阱是，那盏灯要是 AI 自己点的，它什么都没排除。

A 15KB JavaScript library just solved one of the oldest architectural debts in web development — knowing how tall text will be without asking the browser to reflow the entire page.

PanPanMao build diary final entry: 29 days, 1,134 commits, 9 product verticals. Reflections on AI-augmented development, zero-knowledge domains, and the product vs engineering divide.

Part 3 of 3: Honest lessons from building PanPanMao. AI bridging domain knowledge (with caveats), product vs engineering, the agentic coding workflow, and the era of the solo AI-augmented builder.

Part 2 of 3: The technical build of PanPanMao across 4 phases -- monorepo consolidation, testing and branding, monetization, and the milestone rush. 1,134 commits, 85 endpoints, 9 verticals.

Part 1 of 3: A big-tech engineer's journey into building PanPanMao -- an AI-powered Chinese metaphysics platform with 9 verticals, 1,134 commits in 29 days, and zero domain knowledge.

盘盘猫开发日记最终篇：29天，1,134次commit，9个产品线。聊聊AI增强开发、零知识领域创业，还有产品与工程的分界线。

第3篇（共3篇）：构建PanPanMao的真实教训。AI弥合领域知识鸿沟（但有个大前提）、产品vs工程、AI编程工作流，还有一个人+AI做产品的时代。

第 2 篇（共 3 篇）：29 天把 5 个独立 app 合成一个 monorepo 平台，分四个阶段——monorepo 整合、测试与品牌、商业化、里程碑冲刺。1,134 个 commit，85 个 API 端点，9 个产品线。

第1篇（共3篇）：一个大厂工程师的一人创业实验——用AI构建PanPanMao，一个覆盖9个产品线的中国玄学平台，29天1,134次commit，领域知识为零。

PanPanMao build diary Day 27: The most productive single day. 98 commits. Three new products (child naming, compatibility analysis, annual forecast) from zero to production.

盘盘猫开发日记第27天：最高产的一天。98次commit。三个新产品（起名、配对、流年运程）从零到上线。

PanPanMao build diary Days 20-23: 166 commits, 3 formal milestones, 17 PRs. Credit economy foundation, Daily Hub with pre-generated content, and PostHog analytics.

盘盘猫开发日记第20-23天：166次commit，3个正式里程碑，17个PR。积分经济体系基础、每日运势Hub预生成内容架构、PostHog数据分析接入。

PanPanMao build diary Days 12-19: Referral system, palm reading with MediaPipe, landing page dark luxury redesign, and the realization that engineering is the easy part now.

盘盘猫开发日记第12-19天：邀请返利系统、基于MediaPipe的掌纹识别、落地页暗黑奢华风重设计，以及一个领悟——工程不再是瓶颈了。