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.
Automatischer Uebersetzungsentwurf (German) for "Secrets Phishing Resistance": Secrets Phishing Resistance is a security identity control that reduces success of credential theft attacks for keys, tokens, and credentials. It uses passkeys, hardware-backed factors, and origin checks so teams can protect sign-in flows while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Secrets Phishing Resistance when a secret appeared in logs, so the team could protect sign-in flows before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Satellite Thermal Margin": Satellite Thermal Margin is a space safety metric that tracks how much temperature headroom remains before a component exceeds limits for commercial and civil satellite service delivery. It uses sensor data, heat models, and operational constraints so teams can protect hardware during changing conditions while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The mission team used Satellite Thermal Margin when the constellation shifted traffic between spacecraft, so the team could protect hardware during changing conditions before the next mission decision point.”
Automatischer Uebersetzungsentwurf (German) for "Martian Link Budget": Martian Link Budget is a space planning model that estimates whether a signal path has enough margin for reliable communication for Mars relay, rover, and entry operations. It uses antenna gain, path loss, modulation, and noise estimates so teams can schedule contacts with realistic margins while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The mission team used Martian Link Budget when the rover started a high-latency science pass, so the team could schedule contacts with realistic margins before the next mission decision point.”
Automatischer Uebersetzungsentwurf (German) for "Firewall Path Trace": Firewall Path Trace is a networking diagnostic record that shows where traffic travels and where delay or loss appears for network traffic filtering. It uses hop data, timing, and network metadata so teams can debug connectivity issues while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The network engineering team used Firewall Path Trace when a new rule matched traffic, so the team could debug connectivity issues before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "GPU Capacity Forecast": GPU Capacity Forecast is a compute planning model that estimates future resource needs for accelerated compute for parallel workloads. It uses traffic history, growth assumptions, and utilization trends so teams can avoid surprise shortages while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used GPU Capacity Forecast when the training job requested more memory, so the team could avoid surprise shortages before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Environment Secret Rotation": Environment Secret Rotation is a devops credential workflow that replaces sensitive keys without service interruption for configuration for a runtime stage. It uses dual credentials, rollout steps, and revocation so teams can reduce credential exposure while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used Environment Secret Rotation when staging and production drifted, so the team could reduce credential exposure before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Systems Thinking Aspect: See connections and feedback loops between elements": A practice note from the Systems Thinking principle: See connections and feedback loops between elements.
“Beispielentwurf: The learner used this systems thinking aspect to make their study plan more polymathic.”
Automatischer Uebersetzungsentwurf (German) for "Propulsion Debris Avoidance": Propulsion Debris Avoidance is a space safety workflow that reduces collision risk with tracked objects and mission-generated debris for thruster, burn, and maneuver systems. It uses conjunction screening, maneuver planning, and operator signoff so teams can avoid unsafe passes without overusing fuel while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The mission team used Propulsion Debris Avoidance when the burn plan changed, so the team could avoid unsafe passes without overusing fuel before the next mission decision point.”
Automatischer Uebersetzungsentwurf (German) for "Lunar Autonomy Stack": Lunar Autonomy Stack is a space software layer that lets spacecraft or ground tools make bounded decisions when direct human control is delayed for Moon surface and cislunar mission operations. It uses rules, state machines, onboard checks, and fail-safe limits so teams can handle latency without losing accountability while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The mission team used Lunar Autonomy Stack when the lander crossed into a polar shadow region, so the team could handle latency without losing accountability before the next mission decision point.”
Automatischer Uebersetzungsentwurf (German) for "GPU Isolation Boundary": GPU Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for accelerated compute for parallel workloads. It uses namespaces, sandboxes, and access controls so teams can reduce cross-workload risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used GPU Isolation Boundary when the training job requested more memory, so the team could reduce cross-workload risk before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "GPU Placement Strategy": GPU Placement Strategy is a compute scheduling rule that chooses where workloads should run for accelerated compute for parallel workloads. It uses affinity, topology, availability, and cost signals so teams can improve reliability and efficiency while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used GPU Placement Strategy when the training job requested more memory, so the team could improve reliability and efficiency before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Launch Attitude Control": Launch Attitude Control is a space subsystem that keeps a spacecraft pointed correctly for power, thermal safety, communication, or science for launch vehicle and ascent operations. It uses sensors, reaction wheels, thrusters, and control laws so teams can maintain pointing without exceeding constraints while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The mission team used Launch Attitude Control when the launch window narrowed, so the team could maintain pointing without exceeding constraints before the next mission decision point.”
Automatischer Uebersetzungsentwurf (German) for "Secret Runbook Check": Secret Runbook Check is a devops operational test that confirms that documented procedures still work for credential and sensitive configuration. 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.
“Beispielentwurf: The DevOps team used Secret Runbook Check when a token rotated, so the team could keep response playbooks current before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Fine-Tuning Model Card": Fine-Tuning Model Card is a ml documentation artifact that summarizes intended use, limits, and evaluation evidence for adaptation of a model to a domain. It uses dataset notes, metric tables, and risk statements so teams can publish model behavior honestly while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The machine learning team used Fine-Tuning Model Card when the fine-tuning run used curated examples, so the team could publish model behavior honestly before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "RAG Model Router": RAG Model Router is a ai selection service that chooses the best model or provider for a task for retrieval-augmented generation pipelines. It uses cost, latency, capability, policy, and fallback signals so teams can match work to the right model while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The AI platform team used RAG Model Router when the retriever mixed old and new documents, so the team could match work to the right model before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Service Mesh Egress Policy": Service Mesh Egress Policy is a networking outbound control that decides where workloads may send traffic for east-west service communication. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The network engineering team used Service Mesh Egress Policy when a service called another service, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "Training Evaluation Harness": Training Evaluation Harness is a ml test system that runs repeatable checks against model behavior for model learning and optimization workflows. It uses fixtures, metrics, thresholds, and regression reports so teams can compare releases with evidence while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The machine learning team used Training Evaluation Harness when the training job restarted, so the team could compare releases with evidence before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Infrastructure Rollback Plan": Infrastructure Rollback Plan is a devops recovery plan that defines how to return to a known good version for cloud resources and platform wiring. It uses version pins, database notes, and operator steps so teams can recover quickly from bad changes while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used Infrastructure Rollback Plan when a new region was added, so the team could recover quickly from bad changes before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Data Loss Patch Window": Data Loss Patch Window is a security remediation schedule that sets when a fix should be applied for sensitive data exposure risk. It uses risk severity, testing needs, and maintenance constraints so teams can repair systems without unnecessary disruption while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Data Loss Patch Window when a report included private metadata, so the team could repair systems without unnecessary disruption before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Observability Rollback Plan": Observability Rollback Plan is a devops recovery plan that defines how to return to a known good version for logs, metrics, traces, and events. It uses version pins, database notes, and operator steps so teams can recover quickly from bad changes while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used Observability Rollback Plan when latency increased after deploy, so the team could recover quickly from bad changes before the deployment window opened.”