Automatischer Uebersetzungsentwurf (German) for "Poetics": Poetics is listed by Polymaths as a notable work associated with Aristotle, connecting that figure's public legacy to Philosophy, Science, Logic.
“Beispielentwurf: Poetics appears in the Polymaths profile for Aristotle.”
Automatischer Uebersetzungsentwurf (German) for "Experiment Calibration Curve": Experiment Calibration Curve is a ml diagnostic that compares predicted confidence with observed outcomes for controlled model comparison. It uses bucketed predictions, reliability diagrams, and threshold analysis so teams can make confidence scores useful while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The machine learning team used Experiment Calibration Curve when the experiment showed a metric tradeoff, so the team could make confidence scores useful before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Serverless Cache Invalidation": Serverless Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for event-driven function execution. It uses keys, tags, timestamps, and purge events so teams can serve current results while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Serverless Cache Invalidation when the function received a traffic burst, so the team could serve current results before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Scheduler Runtime Profile": Scheduler Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for placement of work onto resources. 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 Scheduler Runtime Profile when the cluster needed to place a job, so the team could target optimization work before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Threat Intel Phishing Resistance": Threat Intel Phishing Resistance is a security identity control that reduces success of credential theft attacks for external risk and indicator context. 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 Threat Intel Phishing Resistance when a new campaign indicator appeared, so the team could protect sign-in flows before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Queue Resource Quota": Queue Resource Quota is a compute limit that sets how much compute a workload may consume for asynchronous work buffer. It uses policy, reservations, and usage tracking so teams can protect shared capacity while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Queue Resource Quota when the queue depth increased, so the team could protect shared capacity before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Storage Cold Start Budget": Storage Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for persistent data and object access. It uses prewarming, smaller packages, and runtime tuning so teams can keep first requests responsive while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Storage Cold Start Budget when the workload read a large dataset, so the team could keep first requests responsive before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Runbook Incident Timeline": Runbook Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for documented operational procedure. It uses timestamps, owners, and evidence links so teams can learn from outages without guesswork while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used Runbook Incident Timeline when a responder needed the recovery steps, so the team could learn from outages without guesswork before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Latency Failover Policy": Latency Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for time between request and response. 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 Latency Failover Policy when a user saw slow responses, so the team could recover from outages predictably before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "Supply Chain Detection Rule": Supply Chain Detection Rule is a security security analytic that matches suspicious behavior or known indicators for dependencies, builds, and artifacts. It uses logs, thresholds, signatures, and behavioral context so teams can surface actionable alerts while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Supply Chain Detection Rule when a package update arrived, so the team could surface actionable alerts before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Launch Radiation Shielding": Launch Radiation Shielding is a space design control that reduces exposure from charged particles and solar events for launch vehicle and ascent operations. It uses material selection, safe modes, and exposure modeling so teams can protect electronics and crews from known hazards while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The mission team used Launch Radiation Shielding when the launch window narrowed, so the team could protect electronics and crews from known hazards before the next mission decision point.”
Automatischer Uebersetzungsentwurf (German) for "Evaluation Tool Permission": Evaluation Tool Permission is a ai access control that decides which tools an AI workflow may call for AI quality and safety testing. 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 Evaluation Tool Permission when a release candidate failed a reasoning scenario, so the team could block unsafe automation before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "GPU Cache Invalidation": GPU Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for accelerated compute for parallel workloads. It uses keys, tags, timestamps, and purge events so teams can serve current results while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used GPU Cache Invalidation when the training job requested more memory, so the team could serve current results before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Threat Intel Attack Surface": Threat Intel Attack Surface is a security exposure model that lists reachable systems, actions, and trust boundaries for external risk and indicator context. It uses asset inventory, route discovery, and permission mapping so teams can prioritize risk reduction while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Threat Intel Attack Surface when a new campaign indicator appeared, so the team could prioritize risk reduction before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Supply Chain Data Redaction": Supply Chain Data Redaction is a security privacy control that removes sensitive values before data leaves a protected context for dependencies, builds, and artifacts. It uses field rules, hashing, and safe logging so teams can share evidence without leaking secrets while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Supply Chain Data Redaction when a package update arrived, so the team could share evidence without leaking secrets before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Incident Response Detection Rule": Incident Response Detection Rule is a security security analytic that matches suspicious behavior or known indicators for security event handling. It uses logs, thresholds, signatures, and behavioral context so teams can surface actionable alerts while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Incident Response Detection Rule when an alert escalated to response, so the team could surface actionable alerts before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Propulsion Trajectory Correction": Propulsion Trajectory Correction is a space maneuver process that adjusts a planned flight path after navigation updates or mission changes for thruster, burn, and maneuver systems. It uses delta-v estimates, burn timing, and post-maneuver validation so teams can reduce path error before it grows while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The mission team used Propulsion Trajectory Correction when the burn plan changed, so the team could reduce path error before it grows before the next mission decision point.”
Automatischer Uebersetzungsentwurf (German) for "Observability Artifact Signature": Observability Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for logs, metrics, traces, and events. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used Observability Artifact Signature when latency increased after deploy, so the team could trust deployed packages before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Rollback Infra Plan": Rollback Infra Plan is a devops change preview that shows expected infrastructure changes before apply for recovery from a bad deployment. It uses resource graphs, policy checks, and cost notes so teams can review platform changes safely while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used Rollback Infra Plan when the error budget started burning, so the team could review platform changes safely before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Memory Cache Invalidation": Memory Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for volatile runtime storage. It uses keys, tags, timestamps, and purge events so teams can serve current results while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Memory Cache Invalidation when the process approached its memory limit, so the team could serve current results before the workload scaled up.”