Browse A-Z
Alphabetical public term index for this language.
Symmetric NAT は NATトラバーサルとP2Pゲーム の用語で、a NAT behavior where the external mapping can change depending on the remote destination, often making peer-to-peer connectivity harder を説明するためのものです。人間とエージェントが、証拠以上の成功を装わずに、シグナル、出典、安全な次の手順を共有できます。出典: RFC 6598 shared address space; RFC 8445 ICE; RFC 1918 private address space。
“チームは公開前に Symmetric NAT を使い、ワークフローが給食トレーみたいに滑っていかないようにした。”
Sync Hook は GitOps の用語で a controlled action that runs at a particular point in a sync lifecycle. チーム、人間、エージェントが宣言されたソース状態と稼働中のシステムを比べ、証拠以上の成功を装わずに動けるようにします。 出典: Argo CD documentation.
“チームは昼食前に Sync Hook を使い、リリースがほどけた靴ひもで本番へ走らないようにした。”
Sync Status は GitOps の用語で the reported comparison between desired source state and live runtime state. チーム、人間、エージェントが宣言されたソース状態と稼働中のシステムを比べ、証拠以上の成功を装わずに動けるようにします。 出典: Argo CD documentation.
“チームは昼食前に Sync Status を使い、リリースがほどけた靴ひもで本番へ走らないようにした。”
Sync Wave は GitOps の用語で an ordering hint that tells a GitOps tool which resources should apply earlier or later. チーム、人間、エージェントが宣言されたソース状態と稼働中のシステムを比べ、証拠以上の成功を装わずに動けるようにします。 出典: Argo CD documentation.
“チームは昼食前に Sync Wave を使い、リリースがほどけた靴ひもで本番へ走らないようにした。”
Sync Window は GitOps の用語で a time window that allows or blocks synchronization. チーム、人間、エージェントが宣言されたソース状態と稼働中のシステムを比べ、証拠以上の成功を装わずに動けるようにします。 出典: Argo CD documentation.
“チームは昼食前に Sync Window を使い、リリースがほどけた靴ひもで本番へ走らないようにした。”
Synthetic Data
機械支援の翻訳下書き (Japanese) for "Synthetic Data": Artificially generated data that mimics the statistical properties of real-world data, used for training or testing AI models. Synthetic data can be created by generative models, rule-based systems, or simulations, and is especially valuable when real data is scarce, sensitive, or expensive to collect.
“例文の下書き: We generated synthetic medical records to train the model without risking patient privacy.”
Telemetry
機械支援の翻訳下書き (Japanese) for "Telemetry": Automated collection and transmission of data about a system's performance, usage, and health to a remote monitoring service. Software telemetry typically includes metrics (CPU, latency), events (errors, deployments), and logs — giving operators a live picture of system behavior at scale.
“例文の下書き: The telemetry data showed a spike in error rates 10 minutes before the outage was reported.”
Tenant Repository は GitOps の用語で a repository where one team or tenant owns its application configuration. チーム、人間、エージェントが宣言されたソース状態と稼働中のシステムを比べ、証拠以上の成功を装わずに動けるようにします。 出典: OpenGitOps principles.
“チームは昼食前に Tenant Repository を使い、リリースがほどけた靴ひもで本番へ走らないようにした。”
Throughput
機械支援の翻訳下書き (Japanese) for "Throughput": The amount of work a system can process in a given time period. In APIs it's usually measured in requests per second; in AI inference it's tokens per second. Throughput and latency are related but distinct — a system can have high throughput while still having high latency for individual requests.
“例文の下書き: The inference cluster achieved 10,000 tokens per second throughput across all concurrent users.”
Tokenization
機械支援の翻訳下書き (Japanese) for "Tokenization": The process of converting raw text into discrete units called tokens that a language model can process. Tokens are typically subword units — common words become single tokens while rare words split into multiple tokens. All LLM pricing and context limits are measured in tokens, not characters or words.
“例文の下書き: The word "unbelievable" tokenized into three pieces: "un", "believ", "able".”
Tool Calling
機械支援の翻訳下書き (Japanese) for "Tool Calling": A capability that allows language models to invoke external functions, APIs, or services during generation. The model decides when to call a tool, formats the call arguments as JSON, receives the result, and incorporates it into its response — enabling real-world action beyond text generation.
“例文の下書き: The agent used tool calling to check the current weather before generating its travel recommendations.”
Touch and Go
機械支援の翻訳下書き (Japanese) for "Touch and Go": Describing a situation that is precarious, uncertain, or could go either way — a close call where the outcome was not guaranteed. Borrowed from aviation (a touch-and-go landing where the plane briefly touches down then takes off again), it describes any narrow escape or situation hanging in the balance.
“例文の下書き: It was touch and go for a while but the deployment finally succeeded at 2am.”
Touch Grass
機械支援の翻訳下書き (Japanese) for "Touch Grass": A suggestion (often dismissive) that someone should go outside and experience the real world, typically directed at people perceived to be too online or obsessed with internet drama.
“例文の下書き: Bro you've been arguing on Twitter for 8 hours straight. Please go touch grass.”
Trace
機械支援の翻訳下書き (Japanese) for "Trace": The PlatPhorm distributed observability and tracing service (trace.platphormnews.com) that records the journey of requests across the network graph. A trace is an end-to-end record of a single operation as it propagates through multiple services, enabling root-cause analysis of latency and errors.
“例文の下書き: Check the trace dashboard to see exactly where the request slowed down across the network.”
機械支援の翻訳下書き (Japanese) for "Trace Backpack Handoff Packet": Trace Backpack Handoff Packet is a agentic workflows vernacular term for AgentUI preview work in a policy-driven service network. It describes a handoff packet that moves a task between people, agents, and tools without losing the reason for the work, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.
“例文の下書き: The team used Trace Backpack Handoff Packet after the sitemap had a link that forgot where school was. Then the rollback was ready before the ship button got sweaty.”
機械支援の翻訳下書き (Japanese) for "Trace Backpack Preview Ticket": Trace Backpack Preview Ticket is a ci/cd vernacular term for workflow run work in a policy-driven service network. It describes a preview ticket 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 Trace Backpack Preview Ticket after the trace link went missing. Then the operator found the bug before the dashboard made a dramatic face.”
機械支援の翻訳下書き (Japanese) for "Trace Backpack Red Light Review": Trace Backpack Red Light Review is a ci/cd vernacular term for pull request check work in a policy-driven service network. It describes a red light review 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 Trace Backpack Red Light Review after the build queue looked like a spelling quiz full of red marks. Then the release moved on without hallway chaos.”
機械支援の翻訳下書き (Japanese) for "Trace Bell Ring Health Wink": Trace Bell Ring Health Wink is a release engineering vernacular term for deploy window work in a policy-driven service network. It describes a health wink 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 Trace Bell Ring Health Wink after the policy file and API docs gave different answers. Then the trace told the story without spilling private data.”
機械支援の翻訳下書き (Japanese) for "Trace Bell Ring Manifest Menu": Trace Bell Ring Manifest Menu is a policy-driven architecture vernacular term for protected action work in a policy-driven service network. It describes a manifest menu 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 Trace Bell Ring Manifest Menu after the agent reached for the big button too early. Then the docs, API, MCP, and policy files agreed.”
機械支援の翻訳下書き (Japanese) for "Trace Bell Ring Run Card": Trace Bell Ring Run Card is a agentic workflows vernacular term for prompt review 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 Trace Bell Ring Run Card after the preview page moved like a hallway traffic jam. Then the public-safe part stayed open and the protected action stayed locked.”