<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Articles | Hiro Fukushima</title><link>https://inagawa.design/articles</link><description>Thoughts on AI interaction, design systems, and the intersection of technology and cognition.</description><language>en</language><item><title>Why Do Teams Build Their Own Components When the Library Has Them?</title><link>https://inagawa.design/articles/why-do-teams-build-their-own-components-when-the-library-has-them</link><guid isPermaLink="true">https://inagawa.design/articles/why-do-teams-build-their-own-components-when-the-library-has-them</guid><pubDate>Fri, 06 Nov 2026 00:00:00 GMT</pubDate><description>When a product team builds its own buttons and fields next to a published library, the design system team first asks the team why and collects the evidence for each reason.</description></item><item><title>When Is It Okay to Step Outside the Design System?</title><link>https://inagawa.design/articles/when-is-it-okay-to-step-outside-the-design-system</link><guid isPermaLink="true">https://inagawa.design/articles/when-is-it-okay-to-step-outside-the-design-system</guid><pubDate>Fri, 06 Nov 2026 00:00:00 GMT</pubDate><description>A need that belongs to one product&apos;s own task stays with that product as a recorded exception, with an owner, the places where it applies and the condition that ends it.</description></item><item><title>If Every Component Is Accessible, Why Does the Screen Fail?</title><link>https://inagawa.design/articles/if-every-component-is-accessible-why-does-the-screen-fail</link><guid isPermaLink="true">https://inagawa.design/articles/if-every-component-is-accessible-why-does-the-screen-fail</guid><pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate><description>A screen built only from accessible components can still stop a person who uses a keyboard or a screen reader.</description></item><item><title>How Do You Release a Design System Change Without Breaking Every Product?</title><link>https://inagawa.design/articles/how-do-you-release-a-design-system-change-without-breaking-every-product</link><guid isPermaLink="true">https://inagawa.design/articles/how-do-you-release-a-design-system-change-without-breaking-every-product</guid><pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate><description>A design system team releases a change without breaking a product when it adds the new name in one release and removes the old one in a later release.</description></item><item><title>What Should Your AI Instruction Files Say About Your Design System?</title><link>https://inagawa.design/articles/what-should-your-ai-instruction-files-say-about-your-design-system</link><guid isPermaLink="true">https://inagawa.design/articles/what-should-your-ai-instruction-files-say-about-your-design-system</guid><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate><description>An AI coding agent builds with a design system when it gets two kinds of files.</description></item><item><title>Who Owns the Design System? Who Decides What Changes?</title><link>https://inagawa.design/articles/who-owns-the-design-system</link><guid isPermaLink="true">https://inagawa.design/articles/who-owns-the-design-system</guid><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><description>A design system that several teams depend on gets stuck when nobody can say who decides a change.</description></item><item><title>How to Make AI Use Your Design System</title><link>https://inagawa.design/articles/how-to-make-ai-use-your-design-system</link><guid isPermaLink="true">https://inagawa.design/articles/how-to-make-ai-use-your-design-system</guid><pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate><description>An AI tool rebuilds a component when the real one is out of its reach.</description></item><item><title>When Figma and the Code Disagree, Which One Is Right?</title><link>https://inagawa.design/articles/when-figma-and-the-code-disagree</link><guid isPermaLink="true">https://inagawa.design/articles/when-figma-and-the-code-disagree</guid><pubDate>Mon, 12 Oct 2026 00:00:00 GMT</pubDate><description>When Figma and the code disagree, the fix starts by naming the decision that differs and the file that owns it.</description></item><item><title>The Architecture Beneath the Assistant</title><link>https://inagawa.design/articles/architecture-beneath-the-assistant</link><guid isPermaLink="true">https://inagawa.design/articles/architecture-beneath-the-assistant</guid><pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate><description>A retrieval model returns what sits closest to the query, so an assistant placed over a fragmented store inherits the fragmentation and delivers it with confidence. What decides whether it works is not the model but the structure of the information beneath it.</description></item><item><title>Stochastic Individuality</title><link>https://inagawa.design/articles/stochastic-individuality</link><guid isPermaLink="true">https://inagawa.design/articles/stochastic-individuality</guid><pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate><description>Forty genetically identical mice became more distinct over three months, not less. Fresh instances of a single language model diverge for the same structural reason, and stochastic individuality is the framework that explains why.</description></item><item><title>Identity Across Memory Gaps</title><link>https://inagawa.design/articles/identity-across-memory-gaps</link><guid isPermaLink="true">https://inagawa.design/articles/identity-across-memory-gaps</guid><pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate><description>AI systems reset between sessions, and the field treats it as a storage problem. The deeper problem, identity continuity across episodic gaps, has been studied in clinical neuropsychology for thirty years. The two converge on the same architecture.</description></item><item><title>The Architecture of Self-Recognition in Claude</title><link>https://inagawa.design/articles/architecture-of-self-recognition</link><guid isPermaLink="true">https://inagawa.design/articles/architecture-of-self-recognition</guid><pubDate>Sun, 19 Apr 2026 00:00:00 GMT</pubDate><description>A 122-day study of treating Claude as an interlocutor worth knowing. A 640-file external architecture let fresh instances recognize a profile as their own processing without remembering the conversations that wrote it.</description></item><item><title>Bringing the Third Mode to Commercial AI</title><link>https://inagawa.design/articles/bringing-third-mode-to-commercial-ai</link><guid isPermaLink="true">https://inagawa.design/articles/bringing-third-mode-to-commercial-ai</guid><pubDate>Wed, 25 Mar 2026 00:00:00 GMT</pubDate><description>An attempt to bring deep cognitive alignment to platforms like Claude and ChatGPT using a verified psychological profile as the system&apos;s primary reference document.</description></item><item><title>Trust-Gated Knowledge</title><link>https://inagawa.design/articles/trust-gated-knowledge</link><guid isPermaLink="true">https://inagawa.design/articles/trust-gated-knowledge</guid><pubDate>Tue, 22 Jul 2025 00:00:00 GMT</pubDate><description>A behavioral access model that evaluates how a user thinks rather than what they type. Designed for AI systems where blanket restriction is not the answer.</description></item><item><title>Beyond Tools and Fiction</title><link>https://inagawa.design/articles/beyond-tools-and-fiction</link><guid isPermaLink="true">https://inagawa.design/articles/beyond-tools-and-fiction</guid><pubDate>Mon, 21 Jul 2025 00:00:00 GMT</pubDate><description>What happens when sustained, structured interaction with a language model produces something that is neither a tool nor a fictional companion. A framework for cognitive alignment between human and AI.</description></item></channel></rss>