Browse A-Z
Alphabetical public term index for this language.
Connectivity Check 是 NAT 穿越和 P2P 游戏 术语，用来说明 a STUN-based test used by ICE agents to verify whether a candidate pair can actually carry traffic between peers。它帮助人和代理明确这个信号、来源和安全的下一步，不把自动化、营销活动、DNS、RFC 或网络路径说成超过证据的样子。来源: RFC 6598 shared address space; RFC 8445 ICE; RFC 1918 private address space。
“团队在发布前用了 Connectivity Check，这样自动化就不会像书包拉链没拉好一样一路掉东西。”
Constitutional AI
机器辅助翻译草稿 (Chinese) for "Constitutional AI": A training methodology developed by Anthropic where a set of guiding principles (a "constitution") is used to self-supervise and refine AI outputs. The model critiques and rewrites its own responses according to the constitution, reducing the need for human labelers for harmful content.
“示例草稿: Constitutional AI lets the model identify and self-correct its own harmful outputs using defined principles.”
Context Window
机器辅助翻译草稿 (Chinese) for "Context Window": The maximum amount of text (measured in tokens) that a language model can process and "remember" in a single interaction. Information outside the context window is inaccessible to the model, making context management critical for long-form tasks.
“示例草稿: The model kept losing track of earlier instructions because the codebase exceeded its context window.”
Controller Runtime 是 GitOps 术语，用来说明 the libraries and patterns used to build Kubernetes controllers. 它帮助团队、人和代理比较声明的源状态与正在运行的系统，再按证据行动，不把部署说成比实际更多。 来源: Kubernetes controller pattern.
“团队午饭前用了 Controller Runtime，发布就没有系着松鞋带冲进生产环境。”
机器辅助翻译草稿 (Chinese) for "Copium": A fictional drug that one is metaphorically "inhaling" to cope with disappointment, loss, or an unfavorable situation. Implies the person is in denial.
“示例草稿: Fans saying the season 8 finale was actually good are breathing pure copium.”
CRD 是 GitOps 术语，用来说明 a CustomResourceDefinition that teaches Kubernetes about a new resource type. 它帮助团队、人和代理比较声明的源状态与正在运行的系统，再按证据行动，不把部署说成比实际更多。 来源: Kubernetes controller pattern.
“团队午饭前用了 CRD，发布就没有系着松鞋带冲进生产环境。”
Credential Gap 是 工作流自动化 术语，用来说明 the expected space between an exported automation blueprint and the private credentials that must be reconnected in another account。它帮助人和代理明确这个信号、来源和安全的下一步，不把自动化、营销活动、DNS、RFC 或网络路径说成超过证据的样子。来源: Make scenario blueprints; Make webhooks; n8n data flow。
“团队在发布前用了 Credential Gap，这样自动化就不会像书包拉链没拉好一样一路掉东西。”
Credential Gap Relay 是 工作流自动化 术语，用来说明 credential gap relay work that makes automation evidence visible before a workflow touches production data or spends the whole session plan。它帮助人和代理明确这个信号、来源和安全的下一步，不把自动化、营销活动、DNS、RFC 或网络路径说成超过证据的样子。来源: Make scenario blueprints; Make webhooks; n8n data flow。
“团队在发布前用了 Credential Gap Relay，这样自动化就不会像书包拉链没拉好一样一路掉东西。”
Custom Execution Data Loop 是 n8n 自动化 术语，用来说明 custom execution data loop work that keeps node behavior, execution evidence, and sensitive data boundaries clear while a workflow moves from testing to production。它帮助人和代理明确这个信号、来源和安全的下一步，不把自动化、营销活动、DNS、RFC 或网络路径说成超过证据的样子。来源: n8n node operations; n8n data flow; n8n executions。
“团队在发布前用了 Custom Execution Data Loop，这样自动化就不会像书包拉链没拉好一样一路掉东西。”
Custom Execution Data Switch 是 n8n 自动化 术语，用来说明 custom execution data switch work that keeps node behavior, execution evidence, and sensitive data boundaries clear while a workflow moves from testing to production。它帮助人和代理明确这个信号、来源和安全的下一步，不把自动化、营销活动、DNS、RFC 或网络路径说成超过证据的样子。来源: n8n node operations; n8n data flow; n8n executions。
“团队在发布前用了 Custom Execution Data Switch，这样自动化就不会像书包拉链没拉好一样一路掉东西。”
Custom Resource 是 GitOps 术语，用来说明 a Kubernetes API extension managed by controllers. 它帮助团队、人和代理比较声明的源状态与正在运行的系统，再按证据行动，不把部署说成比实际更多。 来源: Kubernetes controller pattern.
“团队午饭前用了 Custom Resource，发布就没有系着松鞋带冲进生产环境。”
Data Store Contract 是 Make 自动化 术语，用来说明 data store contract work that helps builders test, export, import, and explain Make scenarios without leaking credentials or pretending the first run is production proof。它帮助人和代理明确这个信号、来源和安全的下一步，不把自动化、营销活动、DNS、RFC 或网络路径说成超过证据的样子。来源: Make scenario blueprints; Make module types; Make webhooks。
“团队在发布前用了 Data Store Contract，这样自动化就不会像书包拉链没拉好一样一路掉东西。”
机器辅助翻译草稿 (Chinese) for "Decks Backpack Blast Radius Ruler": Decks Backpack Blast Radius Ruler is a release engineering vernacular term for rollback plan work in a policy-driven service network. It describes a blast radius ruler that ships changes in small, observable steps instead of one giant surprise, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.
“示例草稿: The team used Decks Backpack Blast Radius Ruler after the build queue looked like a spelling quiz full of red marks. Then the release moved on without hallway chaos.”
机器辅助翻译草稿 (Chinese) for "Decks Backpack Build Gate": Decks Backpack Build Gate is a ci/cd vernacular term for status check work in a policy-driven service network. It describes a build gate that turns code changes into tested releases without hiding broken steps, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.
“示例草稿: The team used Decks Backpack Build Gate after the trace link went missing. Then the operator found the bug before the dashboard made a dramatic face.”
机器辅助翻译草稿 (Chinese) for "Decks Backpack Pipeline Bell": Decks Backpack Pipeline Bell is a ci/cd vernacular term for workflow run work in a policy-driven service network. It describes a pipeline bell that blocks risky work until the checks make sense, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.
“示例草稿: The team used Decks Backpack Pipeline Bell after the rollback plan hid under sticky notes. Then everyone knew the next check before the meeting got weird.”
机器辅助翻译草稿 (Chinese) for "Decks Backpack Run Card": Decks Backpack Run Card is a agentic workflows vernacular term for MCP session work in a policy-driven service network. It describes a run card that shows which step is public-safe and which step needs PLATPHORM_API_KEY, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.
“示例草稿: The team used Decks Backpack Run Card after the sitemap had a link that forgot where school was. Then the rollback was ready before the ship button got sweaty.”
机器辅助翻译草稿 (Chinese) for "Decks Backpack Service Contract": Decks Backpack Service Contract is a policy-driven architecture vernacular term for trust policy work in a policy-driven service network. It describes a service contract that connects service behavior to written policy instead of vibes, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.
“示例草稿: The team used Decks Backpack Service Contract after the deploy looked like late homework. Then the team fixed the step without blaming the snack table.”
机器辅助翻译草稿 (Chinese) for "Decks Bell Ring Handoff Packet": Decks Bell Ring Handoff Packet is a agentic workflows vernacular term for tool call work in a policy-driven service network. It describes a handoff packet that shows which step is public-safe and which step needs PLATPHORM_API_KEY, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.
“示例草稿: The team used Decks Bell Ring Handoff Packet after the build queue looked like a spelling quiz full of red marks. Then the release moved on without hallway chaos.”
机器辅助翻译草稿 (Chinese) for "Decks Bell Ring Pipeline Bell": Decks Bell Ring Pipeline Bell is a ci/cd vernacular term for status check work in a policy-driven service network. It describes a pipeline bell that turns code changes into tested releases without hiding broken steps, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.
“示例草稿: The team used Decks Bell Ring Pipeline Bell after the agent reached for the big button too early. Then the docs, API, MCP, and policy files agreed.”
机器辅助翻译草稿 (Chinese) for "Decks Button Cache Blanket": Decks Button Cache Blanket is a devops vernacular term for log trail work in a policy-driven service network. It describes a cache blanket that turns messy system clues into clear next steps, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.
“示例草稿: The team used Decks Button Cache Blanket after the release plan slid like a lunch tray. Then the build passed for a real reason, not crossed fingers.”