Brouillon de traduction automatique (French) 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.
“Exemple en brouillon: 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.”
Brouillon de traduction automatique (French) 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.
“Exemple en brouillon: 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.”
Brouillon de traduction automatique (French) 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.
“Exemple en brouillon: 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.”
Brouillon de traduction automatique (French) 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.
“Exemple en brouillon: 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.”
Brouillon de traduction automatique (French) for "Lunar Fault Detection": Lunar Fault Detection is a space control that finds off-nominal behavior before it becomes a mission-impacting failure for Moon surface and cislunar mission operations. 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.
“Exemple en brouillon: The mission team used Lunar Fault Detection when the lander crossed into a polar shadow region, so the team could choose a safe response before the next mission decision point.”
Brouillon de traduction automatique (French) 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.
“Exemple en brouillon: 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.”
Brouillon de traduction automatique (French) for "Model Safety Filter": Model Safety Filter is a ai policy control that detects content that should be blocked, rewritten, or escalated for foundation model behavior and serving. It uses classifiers, rules, and human review queues so teams can keep outputs public-safe while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The AI platform team used Model Safety Filter when the model produced a low-confidence answer, so the team could keep outputs public-safe before the agent workflow reached production.”
Brouillon de traduction automatique (French) for "Martian Recovery Mode": Martian Recovery Mode is a space resilience pattern that moves a spacecraft or mission system into a known safe operating state for Mars relay, rover, and entry operations. It uses health checks, fallback commands, and restart procedures so teams can restore control after anomalies while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The mission team used Martian Recovery Mode when the rover started a high-latency science pass, so the team could restore control after anomalies before the next mission decision point.”
Brouillon de traduction automatique (French) 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.
“Exemple en brouillon: 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.”
Brouillon de traduction automatique (French) 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.
“Exemple en brouillon: 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.”
Brouillon de traduction automatique (French) for "Prompt Memory Scope": Prompt Memory Scope is a ai state boundary that limits what an assistant may remember or reuse for instructions and context passed to a model. It uses retention policies, consent checks, and namespace separation so teams can prevent accidental cross-context leakage while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The AI platform team used Prompt Memory Scope when the prompt changed between releases, so the team could prevent accidental cross-context leakage before the agent workflow reached production.”
Brouillon de traduction automatique (French) for "GPU Checkpoint Restore": GPU Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for accelerated compute for parallel workloads. 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.
“Exemple en brouillon: The platform engineering team used GPU Checkpoint Restore when the training job requested more memory, so the team could recover long-running work before the workload scaled up.”
Brouillon de traduction automatique (French) for "Lunar Thermal Margin": Lunar Thermal Margin is a space safety metric that tracks how much temperature headroom remains before a component exceeds limits for Moon surface and cislunar mission 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.
“Exemple en brouillon: The mission team used Lunar Thermal Margin when the lander crossed into a polar shadow region, so the team could protect hardware during changing conditions before the next mission decision point.”
Brouillon de traduction automatique (French) for "HTTP Packet Capture": HTTP Packet Capture is a networking diagnostic artifact that records network packets for analysis for application-layer request routing. It uses bounded capture windows, filters, and redaction so teams can investigate protocol behavior safely while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The network engineering team used HTTP Packet Capture when a client retried a request, so the team could investigate protocol behavior safely before traffic crossed a service boundary.”
Une règle de pratique pour The Feynman Technique : Expliquez-la en langage simple sans jargon, comme si vous enseigniez à un enfant de 12 ans.
Brouillon de traduction automatique (French) for "BGP Rate Limit": BGP Rate Limit is a networking traffic control that caps request volume over a period for interdomain routing. It uses identity keys, windows, and response policies so teams can protect services from overload while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The network engineering team used BGP Rate Limit when a route advertisement changed, so the team could protect services from overload before traffic crossed a service boundary.”
Brouillon de traduction automatique (French) for "Zero Trust Containment Plan": Zero Trust Containment Plan is a security response plan that limits damage after a suspected compromise for continuous verification model. 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.
“Exemple en brouillon: The security team used Zero Trust Containment Plan when a device changed posture, so the team could reduce attacker dwell time before the risk review began.”
Une règle de pratique pour The Feynman Technique : Retourner à la source pour combler les lacunes.
Une note de pratique tirée du principe de la Dédicace persistante : voir l'apprentissage comme un voyage tout au long de la vie, et non comme une destination.
Brouillon de traduction automatique (French) for "Subnet Failover Policy": Subnet Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for address segmentation. 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.
“Exemple en brouillon: The network engineering team used Subnet Failover Policy when a workload moved networks, so the team could recover from outages predictably before traffic crossed a service boundary.”