new post: The Art of Projection: From a Single State Machine to Zero-…

[sdzx-1]

…Overhead Multi-Role Execution

[gemini-code-assist]

Summary of Changes

Hello @sdzx-1, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

本拉取请求新增了一篇博客文章，旨在向读者介绍一种创新的分布式系统开发方法。该文章详细阐述了如何通过全局状态机和编译时投影技术，实现多角色协议的零开销演绎，从而简化复杂分布式系统的设计与维护，并提升代码的一致性和可预测性。

Highlights

• 新增博客文章: 添加了一篇题为《投影的艺术：从单一状态机到多角色的零开销演绎》的博客文章，深入探讨了分布式系统中多角色协议的创新开发范式。
• Troupe 框架介绍: 文章详细介绍了 Troupe 框架如何通过“全局状态机 + 编译时投影”的方法，解决传统分布式协议开发中控制流分散、代码重复和维护困难的问题。
• 零运行时开销: 强调了该方法利用编译时反射能力，为每个角色生成专属的执行逻辑，从而实现零运行时开销、低内存占用和高可预测性。

Changelog

• content/post/2026-02-21-troupe-3.smd
  • 新增了一篇关于分布式系统开发新范式的博客文章。

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[sdzx-1]

只能说troupe的内涵太丰富，可以写好多文章。。

[gemini-code-assist]

Code Review

这篇关于 Troupe 和编译时投影的文章写得非常出色，概念清晰，逻辑流畅。文章通过生动的例子和比喻，将一个复杂的分布式系统设计理念解释得浅显易懂。整体上，这是一篇高质量的技术博文。我只提出了两处关于措辞的微小建议，旨在让文章的表达更加精确和专业，您可以酌情考虑是否采纳。

[gemini-code-assist]

标题中的“演绎”一词颇具艺术感，与“投影的艺术”相得益彰。但从技术表达的精确性来看，它可能略带模糊性（可理解为推演、表演等）。如果希望标题更直接地体现技术含义，可以考虑使用“执行”或“实现”等词。例如：“投影的艺术：从单一状态机到多角色的零开销执行”。当然，当前标题也很有创意，这只是一个旨在提升技术表达明确性的建议。

.title = "投影的艺术：从单一状态机到多角色的零开销执行",

[gemini-code-assist]

结尾处的“代码失控”这个说法很生动，但略显口语化。为了让结论部分的语言更具专业感和说服力，可以考虑换成更具体的描述，例如“代码复杂度失控”或“陷入维护困境”。这样能更准确地概括前文所解决的问题。

Troupe 用“全局状态机 + 编译时投影”重新定义了分布式程序的编写方式。它告诉我们：**控制流不必分散在多个角色中，而是可以凝聚为一个整体，然后在编译时精确地分配给每个参与者**。这种思想不仅消除了重复劳动，更让我们能够构建以前难以想象的复杂协议，而不用担心代码复杂度失控。