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 "Satellite Fault Detection": Satellite Fault Detection is a space control that finds off-nominal behavior before it becomes a mission-impacting failure for commercial and civil satellite service delivery. It uses telemetry thresholds, trend checks, and operator review so teams can choose a safe response while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The mission team used Satellite Fault Detection when the constellation shifted traffic between spacecraft, so the team could choose a safe response before the next mission decision point.”
Automatischer Uebersetzungsentwurf (German) for "Zero Trust Policy Decision": Zero Trust Policy Decision is a security authorization decision that determines whether an action should be allowed for continuous verification model. It uses identity, resource, context, and policy evaluation so teams can enforce least privilege while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Zero Trust Policy Decision when a device changed posture, so the team could enforce least privilege before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Memory Response Schema": Memory Response Schema is a ai output contract that requires model output to match a known structure for persistent or session-level AI state. It uses JSON schemas, validators, retries, and error reporting so teams can make responses machine-readable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The AI platform team used Memory Response Schema when the assistant reused earlier project context, so the team could make responses machine-readable before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Zero Trust Trust Boundary": Zero Trust Trust Boundary is a security security boundary that defines where assumptions, identities, or permissions change for continuous verification model. It uses network edges, service roles, and data classifications so teams can avoid accidental privilege crossing while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Zero Trust Trust Boundary when a device changed posture, so the team could avoid accidental privilege crossing before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Infrastructure Release Manifest": Infrastructure Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for cloud resources and platform wiring. 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 Infrastructure Release Manifest when a new region was added, so the team could make releases auditable before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Knowledge Integration Aspect: Recognize that all knowledge is ultimately interconnected": A practice note from the Knowledge Integration principle: Recognize that all knowledge is ultimately interconnected.
“Beispielentwurf: The learner used this knowledge integration aspect to make their study plan more polymathic.”
Automatischer Uebersetzungsentwurf (German) for "Cloud Phishing Resistance": Cloud Phishing Resistance is a security identity control that reduces success of credential theft attacks for cloud account and resource security. 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 Cloud Phishing Resistance when a storage bucket changed policy, so the team could protect sign-in flows before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Zero Trust Phishing Resistance": Zero Trust Phishing Resistance is a security identity control that reduces success of credential theft attacks for continuous verification model. 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 Zero Trust Phishing Resistance when a device changed posture, so the team could protect sign-in flows before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Memory Citation Builder": Memory Citation Builder is a ai attribution helper that formats source links and evidence for an AI answer for persistent or session-level AI state. It uses canonical URLs, source titles, and quote limits so teams can make generated answers citeable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The AI platform team used Memory Citation Builder when the assistant reused earlier project context, so the team could make generated answers citeable before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Container Backpressure Control": Container Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for packaged application runtime. 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 Container Backpressure Control when the image started on a new node, so the team could avoid overload cascades before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Context Context Contract": Context Context Contract is a ai interface contract that defines what context may be passed into a model call for runtime memory and retrieved information. 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 Context Context Contract when the context window filled with mixed sources, so the team could keep model inputs relevant and safe before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Dataset Feature Store": Dataset Feature Store is a ml service that serves consistent features to training and inference for labeled and unlabeled data used for learning. It uses versioned feature definitions, freshness checks, and access policies so teams can avoid training-serving skew while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The machine learning team used Dataset Feature Store when the dataset received a new batch, so the team could avoid training-serving skew before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Read URL Field": The Read URL Field is a structured metadata field 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 Field helped the reader understand the article listing before opening the full story.”
Automatischer Uebersetzungsentwurf (German) for "Inference Tool Permission": Inference Tool Permission is a ai access control that decides which tools an AI workflow may call for model execution for user or system requests. It uses operation allowlists, user intent checks, and protected-action gates so teams can block unsafe automation while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The AI platform team used Inference Tool Permission when the inference route moved to a faster region, so the team could block unsafe automation before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Firewall Egress Policy": Firewall Egress Policy is a networking outbound control that decides where workloads may send traffic for network traffic filtering. 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 Firewall Egress Policy when a new rule matched traffic, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "Secret Release Manifest": Secret Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for credential and sensitive configuration. 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 Secret Release Manifest when a token rotated, so the team could make releases auditable before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Label Label Review": Label Label Review is a ml quality workflow that checks annotations for consistency and usefulness for ground-truth or weak-supervision annotation. 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 Label Label Review when the label set had disagreement, so the team could improve supervised learning data before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Inference Model Card": Inference Model Card is a ml documentation artifact that summarizes intended use, limits, and evaluation evidence for model prediction serving. 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 Inference Model Card when the endpoint handled burst traffic, so the team could publish model behavior honestly before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Mission Control Fault Detection": Mission Control Fault Detection is a space control that finds off-nominal behavior before it becomes a mission-impacting failure for flight control room coordination. It uses telemetry thresholds, trend checks, and operator review so teams can choose a safe response while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The mission team used Mission Control Fault Detection when the operations console detected a constraint, so the team could choose a safe response before the next mission decision point.”
Automatischer Uebersetzungsentwurf (German) for "DNS Route Leak Guard": DNS Route Leak Guard is a networking routing control that detects and blocks accidental route propagation for name resolution and delegation. It uses prefix filters, validation, and peer policy so teams can protect reachability while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The network engineering team used DNS Route Leak Guard when a resolver returned stale data, so the team could protect reachability before traffic crossed a service boundary.”