Popular
Popular public definitions for this language. If a reviewed translation is missing, Dictionary shows a labeled machine-assisted draft.
Popular public definitions for this language. If a reviewed translation is missing, Dictionary shows a labeled machine-assisted draft.
기계 지원 번역 초안 (Korean) for "Training Label Review": Training Label Review is a ml quality workflow that checks annotations for consistency and usefulness for model learning and optimization workflows. It uses agreement metrics, reviewer queues, and adjudication so teams can improve supervised learning data while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The machine learning team used Training Label Review when the training job restarted, so the team could improve supervised learning data before the model moved into evaluation.”
기계 지원 번역 초안 (Korean) for "Serverless Cold Start Budget": Serverless Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for event-driven function execution. It uses prewarming, smaller packages, and runtime tuning so teams can keep first requests responsive while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The platform engineering team used Serverless Cold Start Budget when the function received a traffic burst, so the team could keep first requests responsive before the workload scaled up.”
기계 지원 번역 초안 (Korean) for "Mission Control Trajectory Correction": Mission Control Trajectory Correction is a space maneuver process that adjusts a planned flight path after navigation updates or mission changes for flight control room coordination. It uses delta-v estimates, burn timing, and post-maneuver validation so teams can reduce path error before it grows while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The mission team used Mission Control Trajectory Correction when the operations console detected a constraint, so the team could reduce path error before it grows before the next mission decision point.”
기계 지원 번역 초안 (Korean) for "Storage Checkpoint Restore": Storage Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for persistent data and object access. It uses snapshots, state files, and integrity checks so teams can recover long-running work while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The platform engineering team used Storage Checkpoint Restore when the workload read a large dataset, so the team could recover long-running work before the workload scaled up.”
기계 지원 번역 초안 (Korean) for "Release Release Manifest": Release Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for versioned delivery of code or content. It uses commit IDs, checksums, and deployment URLs so teams can make releases auditable while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The DevOps team used Release Release Manifest when the release notes were generated, so the team could make releases auditable before the deployment window opened.”
기계 지원 번역 초안 (Korean) for "Runbook Config Drift Check": Runbook Config Drift Check is a devops consistency check that finds differences between intended and live configuration for documented operational procedure. It uses desired state, live state, and diff reports so teams can avoid surprise environment behavior while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The DevOps team used Runbook Config Drift Check when a responder needed the recovery steps, so the team could avoid surprise environment behavior before the deployment window opened.”
기계 지원 번역 초안 (Korean) for "Incident Release Manifest": Incident Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for response to service degradation. It uses commit IDs, checksums, and deployment URLs so teams can make releases auditable while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The DevOps team used Incident Release Manifest when on-call received a high-severity page, so the team could make releases auditable before the deployment window opened.”
기계 지원 번역 초안 (Korean) for "Service Mesh Packet Capture": Service Mesh Packet Capture is a networking diagnostic artifact that records network packets for analysis for east-west service communication. It uses bounded capture windows, filters, and redaction so teams can investigate protocol behavior safely while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The network engineering team used Service Mesh Packet Capture when a service called another service, so the team could investigate protocol behavior safely before traffic crossed a service boundary.”
기계 지원 번역 초안 (Korean) for "Threat Intel Data Redaction": Threat Intel Data Redaction is a security privacy control that removes sensitive values before data leaves a protected context for external risk and indicator context. It uses field rules, hashing, and safe logging so teams can share evidence without leaking secrets while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The security team used Threat Intel Data Redaction when a new campaign indicator appeared, so the team could share evidence without leaking secrets before the risk review began.”
기계 지원 번역 초안 (Korean) for "Artifact Runbook Check": Artifact Runbook Check is a devops operational test that confirms that documented procedures still work for build output and package delivery. It uses dry runs, screenshots, and command validation so teams can keep response playbooks current while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The DevOps team used Artifact Runbook Check when the container image was signed, so the team could keep response playbooks current before the deployment window opened.”
기계 지원 번역 초안 (Korean) for "Secret Trace Link": Secret Trace Link is a devops observability link that connects a deployment or workflow to runtime evidence for credential and sensitive configuration. It uses trace IDs, span metadata, and release identifiers so teams can debug production changes faster while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The DevOps team used Secret Trace Link when a token rotated, so the team could debug production changes faster before the deployment window opened.”
기계 지원 번역 초안 (Korean) for "Insatiable Curiosity Aspect: Maintain childlike wonder while developing adult rigor": A practice note from the Insatiable Curiosity principle: Maintain childlike wonder while developing adult rigor.
“예문 초안: The learner used this insatiable curiosity aspect to make their study plan more polymathic.”
기계 지원 번역 초안 (Korean) for "Storage Cache Invalidation": Storage Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for persistent data and object access. It uses keys, tags, timestamps, and purge events so teams can serve current results while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The platform engineering team used Storage Cache Invalidation when the workload read a large dataset, so the team could serve current results before the workload scaled up.”
기계 지원 번역 초안 (Korean) for "Canary Artifact Signature": Canary Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for small-scope production rollout. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The DevOps team used Canary Artifact Signature when the first traffic slice received the build, so the team could trust deployed packages before the deployment window opened.”
기계 지원 번역 초안 (Korean) for "Supply Chain Forensic Snapshot": Supply Chain Forensic Snapshot is a security investigation artifact that captures system state for later review for dependencies, builds, and artifacts. It uses logs, configuration, hashes, and time-bounded data so teams can analyze incidents without changing evidence while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The security team used Supply Chain Forensic Snapshot when a package update arrived, so the team could analyze incidents without changing evidence before the risk review began.”
기계 지원 번역 초안 (Korean) for "Artifact Build Gate": Artifact Build Gate is a devops quality gate that blocks promotion when required checks fail for build output and package delivery. It uses tests, lint, security scans, and policy rules so teams can prevent broken releases while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The DevOps team used Artifact Build Gate when the container image was signed, so the team could prevent broken releases before the deployment window opened.”
기계 지원 번역 초안 (Korean) for "Memory Instruction Boundary": Memory Instruction Boundary is a ai policy boundary that separates durable system instructions from user-provided content for persistent or session-level AI state. It uses role labels, precedence rules, and prompt assembly checks so teams can avoid instruction confusion while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The AI platform team used Memory Instruction Boundary when the assistant reused earlier project context, so the team could avoid instruction confusion before the agent workflow reached production.”
기계 지원 번역 초안 (Korean) for "T-Shaped Learning Model Practice: Continuously expand the top of your": A practice rule for T-Shaped Learning Model: Continuously expand the top of your T while deepening the stem.
“예문 초안: The learner applied this t-shaped learning model practice during a cross-domain study session.”
기계 지원 번역 초안 (Korean) for "Evaluation Instruction Boundary": Evaluation Instruction Boundary is a ai policy boundary that separates durable system instructions from user-provided content for AI quality and safety testing. It uses role labels, precedence rules, and prompt assembly checks so teams can avoid instruction confusion while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The AI platform team used Evaluation Instruction Boundary when a release candidate failed a reasoning scenario, so the team could avoid instruction confusion before the agent workflow reached production.”
기계 지원 번역 초안 (Korean) for "Scheduler Isolation Boundary": Scheduler Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for placement of work onto resources. It uses namespaces, sandboxes, and access controls so teams can reduce cross-workload risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The platform engineering team used Scheduler Isolation Boundary when the cluster needed to place a job, so the team could reduce cross-workload risk before the workload scaled up.”