S2 S2
有了可靠 AI,能做出什么? With Reliable AI, What Can You Build?
- 01 01硅基团队 S2E01: 扳回方向之后,产品才刚开始S1E10 扳回了方向,但代码还是那套 Tailwind 管理后台。LLM Pool 三路回退、Apple 设计令牌、WCAG 对比度——从方向正确到产品可用之间,是密度最高的打磨。Silicon Team S2E01: A Family Product in 23 Hours for $92One-sentence requirement, 44 AI subagents, 35 commits. Direction completely wrong midway, corrected by a single sentence. The two-day journey from zero to MVP.
- 02 02硅基团队 S2E02: 40 个 Tick 推上线47 小时,$347,3 次上下文溢出。把一个散乱的单用户工具推到云端生产环境——五次部署调试,以及一个跑完了不肯停的循环。Silicon Team S2E02: 40 Ticks to Production47 hours, $347, 3 context blowouts. Turning a single-user tool into SaaS — and the most ironic bug was the AI that wouldn't stop.
- 03 03硅基团队 S2E03: 所有人都说通过的时候该担心了四个审查者全判 PASS,没有一个质疑方向。加了第十人之后,第一次审查就发现了「想象力的失败」。共识不是推进的信号,是需要挑战的信号。Silicon Team S2E03: When Everyone Says PASS, It's Time to WorryFour reviewers unanimously judged PASS — not one questioned direction. After adding the Tenth Man, the very first review uncovered 'a failure of imagination.' Consensus isn't a signal to proceed — it's a signal to challenge.
- 04 04硅基团队 S2E04: 动手之前先看别人踩过的坑30 个开源 AI 项目拆开看:上帝文件三基因、插件困难三角、标准化代价、测试密度不等于成功。每个发现都回扣了一个设计决策。先看别人踩过的坑,再决定自己踩哪个。Silicon Team S2E04: Look at Others' Pitfalls Before Digging Your Own30 open-source AI projects dissected: God File three genes, the plugin difficulty triangle, the cost of standardization, and test density ≠ success. Each finding calibrated a design decision. Look at others' pitfalls before choosing which ones to step in yourself.
- 05 05硅基团队 S2E05: 每做一个新产品,核心就胖一圈两个产品做下来,核心代码从 800 行胖到 2000 行。能力合约让扩展和核心互不认识,五种钩子切入流水线的五个阶段,熔断器保证一个坏扩展不会拖死整条线。Silicon Team S2E05: Every New Product Makes the Core FatterAfter two products, core code grew from 800 to 2,000 lines. Capability contracts let extensions and core ignore each other, five hook types cut into five pipeline phases, and a circuit breaker ensures one bad extension can't kill the line.
- 06 06硅基团队 S2E06: 三个审查者没一个看出颜色不对教育工具前端重构后,两个蓝色相差 7 度色相,安全、后端、前端三个审查者全部 PASS。Design Intelligence 给流水线装了调色板护栏、28 个 AI 嗅探器和参考层——让机器看得见设计。Silicon Team S2E06: Three Reviewers and Not One Noticed the Wrong ColorAfter the education tool's frontend refactor, two blues differed by 7 degrees of hue. Security, backend, and frontend reviewers all PASS. Design Intelligence gave the pipeline a palette guardrail, 28 AI smell detectors, and a reference layer — teaching machines to see design.
- 07 07硅基团队 S2E07: 看不到过程,就没法信结果JSON 日志没人看,审查报告无人读。opc-viewer 把 AI 团队的审查过程变成对话回放——16 个虚拟团队成员有名字、有头像、有颜色。看不到过程,就没法信结果。Silicon Team S2E07: If You Can't See the Process, You Can't Trust the ResultNobody reads JSON logs. Nobody reads review reports. opc-viewer turned the AI team's review process into a conversation replay — 16 virtual team members with names, avatars, and colors. If you can't see the process, you can't trust the result.
- 08 08硅基团队 S2E08: 让工具审自己,发现它从没拦过谁用 OPC 审 OPC 自己,14 个节点全 PASS——FAIL 路径从未被触发。一个从未行使过的强制机制,和一个不存在的强制机制,没有区别。Silicon Team S2E08: Letting the Tool Audit Itself — and Finding It Never Blocked AnyoneUsed OPC to audit OPC itself; all 14 nodes PASS — the FAIL path was never triggered. An enforcement mechanism that has never been exercised is indistinguishable from one that doesn't exist.