Automatischer Uebersetzungsentwurf (German) for "Training Bias Audit": Training Bias Audit is a ml review process that looks for uneven model behavior across groups or segments for model learning and optimization workflows. 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 Training Bias Audit when the training job restarted, so the team could surface fairness risks before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Virginia Statute for Religious Freedom": Virginia Statute for Religious Freedom is listed by Polymaths as a notable work associated with Thomas Jefferson, connecting that figure's public legacy to Politics, Philosophy, Law.
“Beispielentwurf: Virginia Statute for Religious Freedom appears in the Polymaths profile for Thomas Jefferson.”
Automatischer Uebersetzungsentwurf (German) for "BGP Traffic Shaper": BGP Traffic Shaper is a networking control mechanism that limits or prioritizes flows across links for interdomain routing. It uses queues, rate limits, and quality-of-service rules so teams can protect important traffic while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The network engineering team used BGP Traffic Shaper when a route advertisement changed, so the team could protect important traffic before traffic crossed a service boundary.”
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 "Orbital Science Window": Orbital Science Window is a space planning interval that marks when conditions are suitable for data collection for spacecraft orbit planning and station keeping. It uses target visibility, power budgets, thermal state, and downlink availability so teams can capture useful observations without breaking constraints while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The mission team used Orbital Science Window when a spacecraft entered a crowded orbital shell, so the team could capture useful observations without breaking constraints before the next mission decision point.”
Automatischer Uebersetzungsentwurf (German) for "Scheduler Autoscaling Policy": Scheduler Autoscaling Policy is a compute control loop that changes capacity based on demand signals for placement of work onto resources. 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 Scheduler Autoscaling Policy when the cluster needed to place a job, so the team could match resources to load before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Pipeline Model Card": Pipeline Model Card is a ml documentation artifact that summarizes intended use, limits, and evaluation evidence for automated data and model workflow. 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 Pipeline Model Card when the pipeline missed a validation step, so the team could publish model behavior honestly before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Infrastructure Runbook Check": Infrastructure Runbook Check is a devops operational test that confirms that documented procedures still work for cloud resources and platform wiring. 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 Infrastructure Runbook Check when a new region was added, so the team could keep response playbooks current before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Dataset Bias Audit": Dataset Bias Audit is a ml review process that looks for uneven model behavior across groups or segments for labeled and unlabeled data used for learning. 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 Dataset Bias Audit when the dataset received a new batch, so the team could surface fairness risks before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Lunar Attitude Control": Lunar Attitude Control is a space subsystem that keeps a spacecraft pointed correctly for power, thermal safety, communication, or science for Moon surface and cislunar mission 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 Lunar Attitude Control when the lander crossed into a polar shadow region, so the team could maintain pointing without exceeding constraints before the next mission decision point.”
Automatischer Uebersetzungsentwurf (German) for "Identity Containment Plan": Identity Containment Plan is a security response plan that limits damage after a suspected compromise for user and workload identity. 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 Identity Containment Plan when a service account requested access, so the team could reduce attacker dwell time before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Feature Bias Audit": Feature Bias Audit is a ml review process that looks for uneven model behavior across groups or segments for input signals used by a machine learning model. 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 Feature Bias Audit when a feature distribution shifted, so the team could surface fairness risks before the model moved into evaluation.”
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 "Guardrail Tool Permission": Guardrail Tool Permission is a ai access control that decides which tools an AI workflow may call for policy controls around model input and output. 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 Guardrail Tool Permission when the model tried to include private context, so the team could block unsafe automation before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Inference Label Review": Inference Label Review is a ml quality workflow that checks annotations for consistency and usefulness for model prediction serving. 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 Inference Label Review when the endpoint handled burst traffic, so the team could improve supervised learning data before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Serverless Isolation Boundary": Serverless Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for event-driven function execution. 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 Serverless Isolation Boundary when the function received a traffic burst, so the team could reduce cross-workload risk before the workload scaled up.”
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 "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 "Cluster Runtime Profile": Cluster Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for group of machines acting as one platform. 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 Cluster Runtime Profile when the cluster added a node pool, so the team could target optimization work before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Queue Image Hardening": Queue Image Hardening is a compute security practice that reduces risk inside packaged runtime images for asynchronous work buffer. It uses minimal bases, patching, and vulnerability checks so teams can ship safer workloads while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Queue Image Hardening when the queue depth increased, so the team could ship safer workloads before the workload scaled up.”