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 "Memory Context Contract": Memory Context Contract is a ai interface contract that defines what context may be passed into a model call for persistent or session-level AI state. 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 Memory Context Contract when the assistant reused earlier project context, so the team could keep model inputs relevant and safe before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Label Drift Monitor": Label Drift Monitor is a ml monitor that detects when data or predictions no longer match the training baseline for ground-truth or weak-supervision annotation. 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 Label Drift Monitor when the label set had disagreement, so the team could respond before quality drops before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Metric Model Card": Metric Model Card is a ml documentation artifact that summarizes intended use, limits, and evaluation evidence for measurement of model behavior. 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 Metric Model Card when the metric changed after data cleanup, so the team could publish model behavior honestly before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Tool Call Agent Trace": Tool Call Agent Trace is a ai observability record that captures the steps an AI workflow took for model-triggered calls into software systems. 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 Tool Call Agent Trace when the assistant requested a protected operation, so the team could debug agent behavior without exposing secrets before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Service Mesh Failover Policy": Service Mesh Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for east-west service communication. It uses health signals, priorities, and cooldown windows so teams can recover from outages predictably while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The network engineering team used Service Mesh Failover Policy when a service called another service, so the team could recover from outages predictably before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "Secret Build Gate": Secret Build Gate is a devops quality gate that blocks promotion when required checks fail for credential and sensitive configuration. 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 Secret Build Gate when a token rotated, so the team could prevent broken releases before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Environment Trace Link": Environment Trace Link is a devops observability link that connects a deployment or workflow to runtime evidence for configuration for a runtime stage. 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.
“Beispielentwurf: The DevOps team used Environment Trace Link when staging and production drifted, so the team could debug production changes faster before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Tag Filter Payload": The Tag Filter Payload is a request or message body that describes how tag filter data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Tag Filter Payload before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "RAG Instruction Boundary": RAG Instruction Boundary is a ai policy boundary that separates durable system instructions from user-provided content for retrieval-augmented generation pipelines. 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.
“Beispielentwurf: The AI platform team used RAG Instruction Boundary when the retriever mixed old and new documents, so the team could avoid instruction confusion before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Tool Call Model Router": Tool Call Model Router is a ai selection service that chooses the best model or provider for a task for model-triggered calls into software systems. 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 Tool Call Model Router when the assistant requested a protected operation, so the team could match work to the right model before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Metric Label Review": Metric Label Review is a ml quality workflow that checks annotations for consistency and usefulness for measurement of model behavior. 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.
“Beispielentwurf: The machine learning team used Metric Label Review when the metric changed after data cleanup, so the team could improve supervised learning data before the model moved into evaluation.”
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 "Feature Data Split": Feature Data Split is a ml experimental control that separates examples for training, validation, and testing for input signals used by a machine learning model. It uses randomization rules, leakage checks, and seed tracking so teams can measure generalization honestly while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The machine learning team used Feature Data Split when a feature distribution shifted, so the team could measure generalization honestly before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Fine-Tuning Hyperparameter Sweep": Fine-Tuning Hyperparameter Sweep is a ml optimization process that searches over model settings to improve a target metric for adaptation of a model to a domain. It uses bounded search spaces, trial tracking, and early stopping so teams can find better configurations while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The machine learning team used Fine-Tuning Hyperparameter Sweep when the fine-tuning run used curated examples, so the team could find better configurations before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "TLS Health Probe": TLS Health Probe is a networking availability check that tests whether a service or path can receive traffic for encrypted transport setup. It uses timed requests, thresholds, and regional checks so teams can send traffic only to healthy targets while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The network engineering team used TLS Health Probe when a certificate neared expiration, so the team could send traffic only to healthy targets before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "TLS Certificate Monitor": TLS Certificate Monitor is a networking security monitor that tracks certificate validity and configuration for encrypted transport setup. It uses expiry checks, chain validation, and alerting so teams can avoid trust failures while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The network engineering team used TLS Certificate Monitor when a certificate neared expiration, so the team could avoid trust failures before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "Pipeline Bias Audit": Pipeline Bias Audit is a ml review process that looks for uneven model behavior across groups or segments for automated data and model workflow. It uses slice metrics, representative data, and reviewer notes so teams can surface fairness risks while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The machine learning team used Pipeline Bias Audit when the pipeline missed a validation step, so the team could surface fairness risks before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Routing Fallback Path": Routing Fallback Path is a ai resilience pattern that keeps an AI feature useful when a provider or tool is unavailable for selection among models, tools, and workflows. It uses degraded states, deterministic responses, and operator notices so teams can avoid fake AI success while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The AI platform team used Routing Fallback Path when the router selected a cheaper model, so the team could avoid fake AI success before the agent workflow reached production.”
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.”