<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI on ByF (BaiFan) · Daily Deep Think</title><link>https://blog.baifan.site/en/tags/ai/</link><description>Recent content in AI on ByF (BaiFan) · Daily Deep Think</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>blog@baifan.site (ByF (BaiFan))</managingEditor><webMaster>blog@baifan.site (ByF (BaiFan))</webMaster><copyright>CC BY-NC 4.0</copyright><lastBuildDate>Tue, 29 Sep 2026 00:40:00 +0800</lastBuildDate><atom:link href="https://blog.baifan.site/en/tags/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>What Trellis Does, and Whether It Fixes AI Coding Standards</title><link>https://blog.baifan.site/en/trellis-ai-coding-framework-guide/</link><pubDate>Thu, 30 Apr 2026 14:00:00 +0800</pubDate><author>blog@baifan.site (ByF (BaiFan))</author><guid>https://blog.baifan.site/en/trellis-ai-coding-framework-guide/</guid><description>&lt;p&gt;The most annoying thing about coding with AI isn&amp;rsquo;t that it writes bugs — it&amp;rsquo;s that it writes them differently every time. Same requirement, three conversations, three implementations. The standards live in your head; the AI doesn&amp;rsquo;t know them.&lt;/p&gt;&#10;&lt;!-- more --&gt;&#10;&lt;p&gt;Trellis tries to solve this. It&amp;rsquo;s not yet another AI coding assistant — it&amp;rsquo;s a framework for injecting project standards into AI: the AI reads your standards before writing code, gets checked automatically after writing, and once the check is done, anything newly learned gets distilled back into the standards. The more you use it, the better the AI knows your project.&lt;/p&gt;</description></item><item><title>Dissecting a PPT Agent: From Research to SVG Output</title><link>https://blog.baifan.site/en/ppt-agent-workflow-deep-dive/</link><pubDate>Tue, 28 Apr 2026 14:00:00 +0800</pubDate><author>blog@baifan.site (ByF (BaiFan))</author><guid>https://blog.baifan.site/en/ppt-agent-workflow-deep-dive/</guid><description>&lt;p&gt;Conclusion first: this is not another &amp;ldquo;type a topic → force it into a template → output garbage&amp;rdquo; AI PPT tool.&lt;/p&gt;&#10;&lt;p&gt;It runs a complete expert workflow — requirement research, material retrieval, outline planning, layout planning, visual design — where every step allows manual fine-tuning, or the whole thing can run automatically end to end. In terms of output, pages generated with Gemini 3 Flash already reach commercial delivery quality.&lt;/p&gt;</description></item><item><title>AI API Suffixes: What They Mean and Why They Exist</title><link>https://blog.baifan.site/en/ai-api-suffixes-explained/</link><pubDate>Tue, 14 Apr 2026 14:00:00 +0800</pubDate><author>blog@baifan.site (ByF (BaiFan))</author><guid>https://blog.baifan.site/en/ai-api-suffixes-explained/</guid><description>&lt;p&gt;We often see URLs like these:&lt;/p&gt;&#10;&lt;div class="highlight-wrapper"&gt;&lt;div class="highlight"&gt;&lt;div class="chroma"&gt;&#10;&lt;table class="lntable"&gt;&lt;tr&gt;&lt;td class="lntd"&gt;&#10;&lt;pre tabindex="0" class="chroma"&gt;&lt;code&gt;&lt;span class="lnt"&gt;1&#10;&lt;/span&gt;&lt;span class="lnt"&gt;2&#10;&lt;/span&gt;&lt;span class="lnt"&gt;3&#10;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&#10;&lt;td class="lntd"&gt;&#10;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-plaintext" data-lang="plaintext"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;/v1/chat/completions&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;/v1/messages&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;/v1/responses&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;/div&gt;&lt;/div&gt;&#10;&lt;p&gt;These suffixes are not decoration — they define a complete request and response data structure. Pick the wrong one and your code either errors out or silently loses data.&lt;/p&gt;&#10;&lt;!-- more --&gt;&#10;&lt;p&gt;This article starts at &lt;code&gt;/v1/completions&lt;/code&gt; and works its way to &lt;code&gt;/v1/responses&lt;/code&gt;, explaining what each suffix stands for, why it was designed that way, and where the common pitfalls are.&lt;/p&gt;</description></item><item><title>The Engineering Reality of Multi-Agent Collaboration: Triggers, Topologies, and Deterministic Merging</title><link>https://blog.baifan.site/en/multi-agent-collaboration-engineering/</link><pubDate>Tue, 03 Mar 2026 14:00:00 +0800</pubDate><author>blog@baifan.site (ByF (BaiFan))</author><guid>https://blog.baifan.site/en/multi-agent-collaboration-engineering/</guid><description>&lt;p&gt;Packing multiple probabilistically sampled large language model instances into a single codebase or production pipeline is, fundamentally, constructing a distributed system over an unreliable network using stochastic state machines. The axiomatic foundations of classical distributed computing—deterministic state transitions, reproducible failure modes, Byzantine fault tolerance, and atomic commits—collapse almost entirely when applied to modern generative models.&lt;/p&gt;&#10;&lt;!-- more --&gt;&#10;&lt;p&gt;Tech social media abounds with utopian product demos: one agent searches documentation, another implements business logic, a third writes unit tests, and a fourth conducts code review, while an orchestrator agent glides over the process like an infallible engineering manager. Yet anyone who has pushed such topologies into a 500,000-line monolithic repository or a high-concurrency production environment knows the reality: the system rapidly degenerates into distributed chaos. Unsynchronized modifications cause silent overwrites and split-brain states; non-deterministic rollouts cause cognitive divergence; token consumption explodes in a positive-feedback avalanche; and parent and child processes lock each other in cognitive livelocks.&lt;/p&gt;</description></item><item><title>AI Psychosis: When MTTR Fanaticism Meets Resilience</title><link>https://blog.baifan.site/en/ai-mttr-mtbf-resilience-psychosis/</link><pubDate>Tue, 24 Feb 2026 14:00:00 +0800</pubDate><author>blog@baifan.site (ByF (BaiFan))</author><guid>https://blog.baifan.site/en/ai-mttr-mtbf-resilience-psychosis/</guid><description>&lt;!-- more --&gt;&#10;&lt;p&gt;I have a strong intuition: some companies in the tech industry right now are going through a full-blown AI psychosis, and inside those companies, rational conversation is simply impossible. I&amp;rsquo;m not talking about strangers — I&amp;rsquo;m talking about personal friends I deeply respect. That leaves me worried about how this ends.&lt;/p&gt;&#10;&lt;p&gt;This fear has a specific source. I lived through the great MTBF (mean time between failures) vs MTTR (mean time to recovery) debate when infrastructure moved from traditional ops to cloud and cloud automation. Now those exact same arguments are resurfacing in a new costume — only the scope has widened from infrastructure to the entire software industry, and possibly to the whole world.&lt;/p&gt;</description></item></channel></rss>