<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>One PC · Blog</title><description>One PC — open source projects, AI workflows, products, and daily thoughts.</description><link>https://www.peak-lake.com/</link><language>en-US</language><item><title>Enterprise AI Transformation: From Dev Efficiency to a Self-Evolving AI Organization</title><link>https://www.peak-lake.com/en/blog/mtw5k47k/</link><guid isPermaLink="true">https://www.peak-lake.com/en/blog/mtw5k47k/</guid><description>What are the stages of enterprise AI Native adoption? From AI-ready infrastructure, enterprise knowledge engineering, and SkillOps, to Multi-Agent and AI Organization — this post lays out the full evolution path and best practices.</description><pubDate>Thu, 10 Sep 2026 00:00:00 GMT</pubDate></item><item><title>One Person Can Ship a Product Too: My OPC Software Development Practice</title><link>https://www.peak-lake.com/en/blog/mtw61el1/</link><guid isPermaLink="true">https://www.peak-lake.com/en/blog/mtw61el1/</guid><description>How can a solo developer ship a product alone? Using &quot;Arrange Life&quot; as the case, this is how I turn real pain points into a complete software production system — from requirements, design, dev, and test to release and operations — with AI, coding agents, and Skills.</description><pubDate>Thu, 10 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Agent Long-Term Memory: A Complete Design from Async Extraction to Hybrid Retrieval</title><link>https://www.peak-lake.com/en/blog/agent-memory-system/</link><guid isPermaLink="true">https://www.peak-lake.com/en/blog/agent-memory-system/</guid><description>A complete agent memory system has three mainlines: the write path (outbox async extraction that never slows chat), the read path (dense + lexical hybrid retrieval with RRF), and governance (four-state decision + bitemporal invalidation). This post lays out the whole thing.</description><pubDate>Mon, 07 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Intent Recognition System Design: Unbounded Problems to the Model, Bounded Problems to Code</title><link>https://www.peak-lake.com/en/blog/intent-recognition-system/</link><guid isPermaLink="true">https://www.peak-lake.com/en/blog/intent-recognition-system/</guid><description>Intent recognition isn&apos;t a classification problem — it&apos;s an observable, verifiable execution chain that&apos;s allowed to admit uncertainty. One principle: give unbounded problems to the model (understanding), bounded problems to code (compute and guard).</description><pubDate>Mon, 07 Sep 2026 00:00:00 GMT</pubDate></item><item><title>How to Stop an LLM Agent from Faking &quot;Created&quot;: Exit Validation That Checks Facts, Not Wording</title><link>https://www.peak-lake.com/en/blog/llm-agent-exit-validation/</link><guid isPermaLink="true">https://www.peak-lake.com/en/blog/llm-agent-exit-validation/</guid><description>The model claimed &quot;schedule created&quot; without calling any write tool. Blocking phrases like &quot;created&quot; fails because the model rewords endlessly. Use an exit invariant: only a real database write counts as success.</description><pubDate>Mon, 07 Sep 2026 00:00:00 GMT</pubDate></item><item><title>How to Get Traffic to a Personal Site: SEO, GEO, Content Engineering, and Bilingual</title><link>https://www.peak-lake.com/en/blog/personal-site-traffic/</link><guid isPermaLink="true">https://www.peak-lake.com/en/blog/personal-site-traffic/</guid><description>Traffic to a personal site isn&apos;t &quot;post and wait for indexing&quot; — it&apos;s four layers: technical foundation (sitemap/rss/structured data, so content is findable), content engineering (topic + writing pipeline, so content is worth searching), GEO (llms.txt + citable content, so AI engines cite you), and bilingual (to reach a bigger market). This is my full record.</description><pubDate>Mon, 07 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Slot Extraction in Intent Recognition: The Pitfalls of Chinese Time Parsing</title><link>https://www.peak-lake.com/en/blog/chinese-time-parsing/</link><guid isPermaLink="true">https://www.peak-lake.com/en/blog/chinese-time-parsing/</guid><description>Intent recognition isn&apos;t just classifying intent — you still have to extract slots like time. Chinese time is the easiest slot to get wrong: is &quot;7点半&quot; 7:30 AM or 7:30 PM?</description><pubDate>Sun, 06 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Thinking About Intent Recognition: Plan + Tool Design</title><link>https://www.peak-lake.com/en/blog/mthdnlaj/</link><guid isPermaLink="true">https://www.peak-lake.com/en/blog/mthdnlaj/</guid><description>After many rounds of intent recognition, I finally understand how it should be done.</description><pubDate>Mon, 31 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Why We Deleted 530 Lines of Intent Regex: A Calendar Agent&apos;s Architecture Rewrite</title><link>https://www.peak-lake.com/en/blog/mtengvhn/</link><guid isPermaLink="true">https://www.peak-lake.com/en/blog/mtengvhn/</guid><description>Rebuilding a calendar agent from real user feedback: from 530 lines of intent regex to a single large-model call, keeping the safety boundary with a state machine, tool constraints, exit validation, and real-model evaluation.</description><pubDate>Sat, 29 Aug 2026 00:00:00 GMT</pubDate></item><item><title>I Gave Up the Ops Workbench and Generated a Thousand Calendar Images with a Few Sentences</title><link>https://www.peak-lake.com/en/blog/mt5oz4db/</link><guid isPermaLink="true">https://www.peak-lake.com/en/blog/mt5oz4db/</guid><description>In the AI era, if you can finish something by &apos;talking&apos;, don&apos;t fall back into the old &apos;build a system&apos; mindset.</description><pubDate>Sun, 23 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Agent Intent Recognition: From Classifier to Executable Control System</title><link>https://www.peak-lake.com/en/blog/mt61rdis/</link><guid isPermaLink="true">https://www.peak-lake.com/en/blog/mt61rdis/</guid><description>How to design an agent&apos;s intent recognition. The core: intent recognition isn&apos;t labeling a sentence — it&apos;s a control system deciding whether to call tools, which tool, whether side effects are allowed, and whether the last sentence can be trusted.</description><pubDate>Sun, 23 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Loop Engineering Has No Silver Bullet: Vertical Skills + spec/TDD</title><link>https://www.peak-lake.com/en/blog/mslj4f6g/</link><guid isPermaLink="true">https://www.peak-lake.com/en/blog/mslj4f6g/</guid><description>Chasing one big &quot;fully autonomous&quot; loop doesn&apos;t work. After half a year of intensive coding-agent development, my conclusion: the right carrier for Loop Engineering is per-vertical Skills, with spec + TDD at the core.</description><pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Why I Built an AI Gateway</title><link>https://www.peak-lake.com/en/blog/ai-gateway-01/</link><guid isPermaLink="true">https://www.peak-lake.com/en/blog/ai-gateway-01/</guid><description>For indie developers, an AI gateway isn&apos;t showing off — it&apos;s the smallest engineering unit that unifies model access, cost, and stability. This post covers the five capabilities a production gateway needs, and the traps behind each.</description><pubDate>Thu, 07 May 2026 00:00:00 GMT</pubDate></item><item><title>What Separates AI Development from Demo to Production</title><link>https://www.peak-lake.com/en/blog/ai-rnd-prod-01/</link><guid isPermaLink="true">https://www.peak-lake.com/en/blog/ai-rnd-prod-01/</guid><description>The real gap isn&apos;t model quality, it&apos;s engineering: observability, regression, cost, permission, and failure recovery. This post walks through the five things you must add to go from demo to production, and the trap each one hides.</description><pubDate>Thu, 07 May 2026 00:00:00 GMT</pubDate></item><item><title>Sync Architecture for a Todo App: Client and Desktop</title><link>https://www.peak-lake.com/en/blog/todo-app-sync-01/</link><guid isPermaLink="true">https://www.peak-lake.com/en/blog/todo-app-sync-01/</guid><description>The hard part of a todo app isn&apos;t the UI, it&apos;s multi-device sync and conflict handling. Get the design right and sync feels as natural as local. This post covers the key designs and the traps that break them.</description><pubDate>Thu, 07 May 2026 00:00:00 GMT</pubDate></item></channel></rss>