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.
機械支援の翻訳下書き (Japanese) for "Training Evaluation Harness": Training Evaluation Harness is a ml test system that runs repeatable checks against model behavior for model learning and optimization workflows. It uses fixtures, metrics, thresholds, and regression reports so teams can compare releases with evidence while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The machine learning team used Training Evaluation Harness when the training job restarted, so the team could compare releases with evidence before the model moved into evaluation.”
機械支援の翻訳下書き (Japanese) 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.
“例文の下書き: 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.”
機械支援の翻訳下書き (Japanese) for "Model Drift Feature Store": Model Drift Feature Store is a ml service that serves consistent features to training and inference for changes in model performance over time. 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.
“例文の下書き: The machine learning team used Model Drift Feature Store when the live population changed, so the team could avoid training-serving skew before the model moved into evaluation.”
機械支援の翻訳下書き (Japanese) for "GPU Image Hardening": GPU Image Hardening is a compute security practice that reduces risk inside packaged runtime images for accelerated compute for parallel workloads. It uses minimal bases, patching, and vulnerability checks so teams can ship safer workloads while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The platform engineering team used GPU Image Hardening when the training job requested more memory, so the team could ship safer workloads before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Secret Approval Step": Secret Approval Step is a devops workflow control that requires review before a sensitive change proceeds for credential and sensitive configuration. It uses role checks, comments, and audit logs so teams can keep high-risk automation accountable while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Secret Approval Step when a token rotated, so the team could keep high-risk automation accountable before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Secret Rollout Guard": Secret Rollout Guard is a devops release control that limits exposure during gradual deployment for credential and sensitive configuration. It uses traffic slices, health checks, and automatic pause rules so teams can reduce blast radius while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Secret Rollout Guard when a token rotated, so the team could reduce blast radius before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "CI Secret Rotation": CI Secret Rotation is a devops credential workflow that replaces sensitive keys without service interruption for continuous integration workflows. It uses dual credentials, rollout steps, and revocation so teams can reduce credential exposure while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used CI Secret Rotation when a pull request entered the build queue, so the team could reduce credential exposure before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Martian Debris Avoidance": Martian Debris Avoidance is a space safety workflow that reduces collision risk with tracked objects and mission-generated debris for Mars relay, rover, and entry operations. It uses conjunction screening, maneuver planning, and operator signoff so teams can avoid unsafe passes without overusing fuel while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The mission team used Martian Debris Avoidance when the rover started a high-latency science pass, so the team could avoid unsafe passes without overusing fuel before the next mission decision point.”
機械支援の翻訳下書き (Japanese) 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.
“例文の下書き: 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.”
機械支援の翻訳下書き (Japanese) for "Artifact Runbook Check": Artifact Runbook Check is a devops operational test that confirms that documented procedures still work for build output and package delivery. 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.
“例文の下書き: The DevOps team used Artifact Runbook Check when the container image was signed, so the team could keep response playbooks current before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Label Training Checkpoint": Label Training Checkpoint is a ml recovery artifact that saves model state during learning for ground-truth or weak-supervision annotation. It uses weights, optimizer state, and run metadata so teams can resume or inspect training safely while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The machine learning team used Label Training Checkpoint when the label set had disagreement, so the team could resume or inspect training safely before the model moved into evaluation.”
機械支援の翻訳下書き (Japanese) for "Routing Human Approval": Routing Human Approval is a ai control step that requires a person to approve sensitive or high-impact actions for selection among models, tools, and workflows. It uses risk scoring, review UI, and audit logs so teams can keep protected decisions accountable while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The AI platform team used Routing Human Approval when the router selected a cheaper model, so the team could keep protected decisions accountable before the agent workflow reached production.”
機械支援の翻訳下書き (Japanese) for "Propulsion Science Window": Propulsion Science Window is a space planning interval that marks when conditions are suitable for data collection for thruster, burn, and maneuver systems. 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.
“例文の下書き: The mission team used Propulsion Science Window when the burn plan changed, so the team could capture useful observations without breaking constraints before the next mission decision point.”
機械支援の翻訳下書き (Japanese) for "TLS Anycast Endpoint": TLS Anycast Endpoint is a networking routing pattern that advertises one address from multiple locations for encrypted transport setup. It uses regional announcements, health checks, and traffic steering so teams can serve users from nearby healthy sites while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The network engineering team used TLS Anycast Endpoint when a certificate neared expiration, so the team could serve users from nearby healthy sites before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "Secrets Attack Surface": Secrets Attack Surface is a security exposure model that lists reachable systems, actions, and trust boundaries for keys, tokens, and credentials. 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.
“例文の下書き: The security team used Secrets Attack Surface when a secret appeared in logs, so the team could prioritize risk reduction before the risk review began.”
機械支援の翻訳下書き (Japanese) for "RAG Grounding Check": RAG Grounding Check is a ai quality control that verifies that generated answers are backed by available sources for retrieval-augmented generation pipelines. It uses citation checks, retrieval evidence, and contradiction detection so teams can reduce unsupported claims while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The AI platform team used RAG Grounding Check when the retriever mixed old and new documents, so the team could reduce unsupported claims before the agent workflow reached production.”
機械支援の翻訳下書き (Japanese) for "Release Release Manifest": Release Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for versioned delivery of code or content. It uses commit IDs, checksums, and deployment URLs so teams can make releases auditable while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Release Release Manifest when the release notes were generated, so the team could make releases auditable before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Scheduler Resource Quota": Scheduler Resource Quota is a compute limit that sets how much compute a workload may consume for placement of work onto resources. It uses policy, reservations, and usage tracking so teams can protect shared capacity while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The platform engineering team used Scheduler Resource Quota when the cluster needed to place a job, so the team could protect shared capacity before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Secrets Evidence Chain": Secrets Evidence Chain is a security audit record that preserves how security evidence was collected and handled for keys, tokens, and credentials. It uses timestamps, hashes, owners, and storage controls so teams can support trustworthy investigation while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The security team used Secrets Evidence Chain when a secret appeared in logs, so the team could support trustworthy investigation before the risk review began.”
機械支援の翻訳下書き (Japanese) 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.
“例文の下書き: 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.”