<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>IrisSakura 正式文章</title>
    <link>https://irissakura.com/pages/blog.html</link>
    <description>游戏系统、Framework 工程实践与可复核设计判断。</description>
    <language>zh-CN</language>
    <lastBuildDate>Mon, 26 Oct 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://irissakura.com/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>运行时消费模式与组合根：从 Facade 到显式 Scope 的迁移阶梯</title>
      <link>https://irissakura.com/pages/blog/runtime-consumption-facade-scope.html</link>
      <guid isPermaLink="true">https://irissakura.com/pages/blog/runtime-consumption-facade-scope.html</guid>
      <description>不同规模的 Unity 项目怎样在不更换服务合同的前提下，从快速接入逐步迁移到确定性组合根、显式生命周期和严格依赖边界？</description>
      <pubDate>Wed, 05 Aug 2026 00:00:00 GMT</pubDate>
      <category>composition-root</category>
      <category>facade</category>
      <category>scope</category>
    </item>
    <item>
      <title>Unity Quickstart 的可执行接入证据与有界进程治理</title>
      <link>https://irissakura.com/pages/blog/unity-quickstart-executable-evidence.html</link>
      <guid isPermaLink="true">https://irissakura.com/pages/blog/unity-quickstart-executable-evidence.html</guid>
      <description>一个 Unity 框架已经拥有安装器、Sample 和快速接入文档后，怎样证明新项目真的能够从固定提交开始，走完整条接入路径，并在失败或进程悬挂时留下可审计结果？</description>
      <pubDate>Wed, 05 Aug 2026 00:00:00 GMT</pubDate>
      <category>quickstart</category>
      <category>unity</category>
    </item>
    <item>
      <title>Unity Sample 的条件组合层与渐进式依赖闭包</title>
      <link>https://irissakura.com/pages/blog/unity-sample-dependency-closure.html</link>
      <guid isPermaLink="true">https://irissakura.com/pages/blog/unity-sample-dependency-closure.html</guid>
      <description>一个综合 Sample 想展示十多个框架模块时，怎样避免为了“效果完整”而扩大父包依赖、污染消费项目，并让缺少可选包的项目仍能安全运行？</description>
      <pubDate>Wed, 05 Aug 2026 00:00:00 GMT</pubDate>
      <category>sample</category>
      <category>unity</category>
    </item>
    <item>
      <title>证据等级：本地验证、Runner 复验与交付结论边界</title>
      <link>https://irissakura.com/pages/blog/local-passed-runner-passed.html</link>
      <guid isPermaLink="true">https://irissakura.com/pages/blog/local-passed-runner-passed.html</guid>
      <description>一项功能已经在开发者电脑上通过测试，为什么项目仍不能把它登记为 CI 已验证、候选版本可交付或正式发布？</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
      <category>local</category>
      <category>passed</category>
      <category>runner</category>
    </item>
    <item>
      <title>Unity 热更新的事务提交边界：磁盘版本切换、Runtime 提交与失败恢复</title>
      <link>https://irissakura.com/pages/blog/unity-hot-update-transaction-boundary.html</link>
      <guid isPermaLink="true">https://irissakura.com/pages/blog/unity-hot-update-transaction-boundary.html</guid>
      <description>从不可变版本目录、活动指针、持久化 Journal 与 Runtime Prepare/Commit/Rollback 解释一次可恢复热更新真正完成的边界。</description>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <category>hot-update</category>
      <category>modding</category>
      <category>transactions</category>
      <category>unity</category>
    </item>
    <item>
      <title>音游、格斗与竞速的权威时间源：输入、模拟、音频与表现层的时钟分工</title>
      <link>https://irissakura.com/pages/blog/authoritative-time-source.html</link>
      <guid isPermaLink="true">https://irissakura.com/pages/blog/authoritative-time-source.html</guid>
      <description>比较音游、格斗与竞速如何选择规则时间，区分输入、模拟、音频和表现层的时间职责。</description>
      <pubDate>Wed, 29 Jul 2026 00:00:00 GMT</pubDate>
      <category>determinism</category>
      <category>simulation</category>
      <category>timing</category>
    </item>
  </channel>
</rss>
