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 "Secret Rollback Plan": Secret Rollback Plan is a devops recovery plan that defines how to return to a known good version for credential and sensitive configuration. 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 Secret Rollback Plan when a token rotated, so the team could recover quickly from bad changes before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Supply Chain Containment Plan": Supply Chain Containment Plan is a security response plan that limits damage after a suspected compromise for dependencies, builds, and artifacts. It uses isolation steps, credential rotation, and communication paths so teams can reduce attacker dwell time while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Supply Chain Containment Plan when a package update arrived, so the team could reduce attacker dwell time before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Metric Training Checkpoint": Metric Training Checkpoint is a ml recovery artifact that saves model state during learning for measurement of model behavior. It uses weights, optimizer state, and run metadata so teams can resume or inspect training safely while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The machine learning team used Metric Training Checkpoint when the metric changed after data cleanup, so the team could resume or inspect training safely before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Feature Model Card": Feature Model Card is a ml documentation artifact that summarizes intended use, limits, and evaluation evidence for input signals used by a machine learning model. 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 Feature Model Card when a feature distribution shifted, so the team could publish model behavior honestly before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Mission Control Attitude Control": Mission Control Attitude Control is a space subsystem that keeps a spacecraft pointed correctly for power, thermal safety, communication, or science for flight control room coordination. 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 Mission Control Attitude Control when the operations console detected a constraint, so the team could maintain pointing without exceeding constraints before the next mission decision point.”
Automatischer Uebersetzungsentwurf (German) for "Dataset Drift Monitor": Dataset Drift Monitor is a ml monitor that detects when data or predictions no longer match the training baseline for labeled and unlabeled data used for learning. It uses statistical tests, time windows, and alert thresholds so teams can respond before quality drops while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The machine learning team used Dataset Drift Monitor when the dataset received a new batch, so the team could respond before quality drops before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Serverless Runtime Profile": Serverless Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for event-driven function execution. It uses sampling, traces, and resource metrics so teams can target optimization work while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Serverless Runtime Profile when the function received a traffic burst, so the team could target optimization work before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Storage Autoscaling Policy": Storage Autoscaling Policy is a compute control loop that changes capacity based on demand signals for persistent data and object access. It uses metrics, thresholds, and cooldowns so teams can match resources to load while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Storage Autoscaling Policy when the workload read a large dataset, so the team could match resources to load before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Embedding Training Checkpoint": Embedding Training Checkpoint is a ml recovery artifact that saves model state during learning for vector representation of content or entities. It uses weights, optimizer state, and run metadata so teams can resume or inspect training safely while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The machine learning team used Embedding Training Checkpoint when the embedding index changed, so the team could resume or inspect training safely before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Storage Backpressure Control": Storage Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for persistent data and object access. It uses queues, retry budgets, and admission control so teams can avoid overload cascades while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Storage Backpressure Control when the workload read a large dataset, so the team could avoid overload cascades before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Routing Context Contract": Routing Context Contract is a ai interface contract that defines what context may be passed into a model call for selection among models, tools, and workflows. It uses schemas, redaction rules, source labels, and token budgets so teams can keep model inputs relevant and safe while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The AI platform team used Routing Context Contract when the router selected a cheaper model, so the team could keep model inputs relevant and safe before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Payload Thermal Margin": Payload Thermal Margin is a space safety metric that tracks how much temperature headroom remains before a component exceeds limits for instrument, sensor, and hosted payload operations. 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 Payload Thermal Margin when the instrument entered a calibration cycle, so the team could protect hardware during changing conditions before the next mission decision point.”
Automatischer Uebersetzungsentwurf (German) for "Supply Chain Abuse Throttle": Supply Chain Abuse Throttle is a security anti-abuse control that slows or blocks suspicious repeated behavior for dependencies, builds, and artifacts. It uses rate limits, reputation signals, and challenge steps so teams can protect public access without a login wall while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Supply Chain Abuse Throttle when a package update arrived, so the team could protect public access without a login wall before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Read URL Signal": The Read URL Signal is a ranking or context signal that describes the read url inside a PlatPhorm News article listing. It lets humans and agents scan stories quickly, compare sources, and choose whether to read the article or open its discussion.
“Beispielentwurf: The Read URL Signal helped the reader understand the article listing before opening the full story.”
Automatischer Uebersetzungsentwurf (German) for "Scheduler Checkpoint Restore": Scheduler Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for placement of work onto resources. 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.
“Beispielentwurf: The platform engineering team used Scheduler Checkpoint Restore when the cluster needed to place a job, so the team could recover long-running work before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Evaluation Agent Trace": Evaluation Agent Trace is a ai observability record that captures the steps an AI workflow took for AI quality and safety testing. It uses trace identifiers, tool events, and redacted metadata so teams can debug agent behavior without exposing secrets while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The AI platform team used Evaluation Agent Trace when a release candidate failed a reasoning scenario, so the team could debug agent behavior without exposing secrets before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Tool Call Grounding Check": Tool Call Grounding Check is a ai quality control that verifies that generated answers are backed by available sources for model-triggered calls into software systems. It uses citation checks, retrieval evidence, and contradiction detection so teams can reduce unsupported claims while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The AI platform team used Tool Call Grounding Check when the assistant requested a protected operation, so the team could reduce unsupported claims before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Runbook Release Manifest": Runbook Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for documented operational procedure. It uses commit IDs, checksums, and deployment URLs so teams can make releases auditable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used Runbook Release Manifest when a responder needed the recovery steps, so the team could make releases auditable before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Metric Drift Monitor": Metric Drift Monitor is a ml monitor that detects when data or predictions no longer match the training baseline for measurement of model behavior. It uses statistical tests, time windows, and alert thresholds so teams can respond before quality drops while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The machine learning team used Metric Drift Monitor when the metric changed after data cleanup, so the team could respond before quality drops before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Environment Build Gate": Environment Build Gate is a devops quality gate that blocks promotion when required checks fail for configuration for a runtime stage. 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.
“Beispielentwurf: The DevOps team used Environment Build Gate when staging and production drifted, so the team could prevent broken releases before the deployment window opened.”