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
기계 지원 번역 초안 (Korean) 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
기계 지원 번역 초안 (Korean) 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을 사용했고, 릴리스는 풀린 신발끈으로 프로덕션에 뛰어가지 않았다.”
기계 지원 번역 초안 (Korean) 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을 사용했고, 자동화는 복도에서 점심 쟁반처럼 미끄러지지 않았다.”
기계 지원 번역 초안 (Korean) 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.”
기계 지원 번역 초안 (Korean) 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.”
기계 지원 번역 초안 (Korean) 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.”
기계 지원 번역 초안 (Korean) 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.”
기계 지원 번역 초안 (Korean) 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.”
기계 지원 번역 초안 (Korean) 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.”
기계 지원 번역 초안 (Korean) 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.”
기계 지원 번역 초안 (Korean) 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.”