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 を説明するためのものです。人間とエージェントが、証拠以上の成功を装わずに、シグナル、出典、安全な次の手順を共有できます。出典: RFC 6598 shared address space; RFC 8445 ICE; RFC 1918 private address space。
“チームは公開前に Connectivity Check を使い、ワークフローが給食トレーみたいに滑っていかないようにした。”
Constitutional AI
機械支援の翻訳下書き (Japanese) 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
機械支援の翻訳下書き (Japanese) 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 を使い、リリースがほどけた靴ひもで本番へ走らないようにした。”
機械支援の翻訳下書き (Japanese) 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 を説明するためのものです。人間とエージェントが、証拠以上の成功を装わずに、シグナル、出典、安全な次の手順を共有できます。出典: 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 を説明するためのものです。人間とエージェントが、証拠以上の成功を装わずに、シグナル、出典、安全な次の手順を共有できます。出典: 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 を説明するためのものです。人間とエージェントが、証拠以上の成功を装わずに、シグナル、出典、安全な次の手順を共有できます。出典: 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 を説明するためのものです。人間とエージェントが、証拠以上の成功を装わずに、シグナル、出典、安全な次の手順を共有できます。出典: 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 を説明するためのものです。人間とエージェントが、証拠以上の成功を装わずに、シグナル、出典、安全な次の手順を共有できます。出典: Make scenario blueprints; Make module types; Make webhooks。
“チームは公開前に Data Store Contract を使い、ワークフローが給食トレーみたいに滑っていかないようにした。”
機械支援の翻訳下書き (Japanese) 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.”
機械支援の翻訳下書き (Japanese) 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.”
機械支援の翻訳下書き (Japanese) 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.”
機械支援の翻訳下書き (Japanese) 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.”
機械支援の翻訳下書き (Japanese) 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.”
機械支援の翻訳下書き (Japanese) 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.”
機械支援の翻訳下書き (Japanese) 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.”
機械支援の翻訳下書き (Japanese) 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.”