Saltar al contenido

Browse A-Z

Alphabetical public term index for this language.

2,337 source-backed termsdatabase

Borrador de traduccion automatica (Spanish) for "Inference Hyperparameter Sweep": Inference Hyperparameter Sweep is a ml optimization process that searches over model settings to improve a target metric for model prediction serving. It uses bounded search spaces, trial tracking, and early stopping so teams can find better configurations while keeping evidence, reliability, and public-safe operational boundaries clear.

Ejemplo en borrador: The machine learning team used Inference Hyperparameter Sweep when the endpoint handled burst traffic, so the team could find better configurations before the model moved into evaluation.

Inference Instruction Boundary es una definicion publica de inteligencia artificial para el area Inference. Explica como la capacidad Instruction Boundary ayuda a personas y agentes a reconocer riesgos, coordinar decisiones, citar evidencia y mantener limites operativos seguros y confiables.

Un equipo uso Inference Instruction Boundary durante trabajo de inteligencia artificial en Inference, para comparar senales, elegir el siguiente paso y documentar la decision sin exponer datos privados.

Borrador de traduccion automatica (Spanish) 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.

Ejemplo en borrador: 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.

Inference Memory Scope es una definicion publica de inteligencia artificial para el area Inference. Explica como la capacidad Memory Scope ayuda a personas y agentes a reconocer riesgos, coordinar decisiones, citar evidencia y mantener limites operativos seguros y confiables.

Un equipo uso Inference Memory Scope durante trabajo de inteligencia artificial en Inference, para comparar senales, elegir el siguiente paso y documentar la decision sin exponer datos privados.

Borrador de traduccion automatica (Spanish) 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.

Ejemplo en borrador: 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.

Inference Model Router es una definicion publica de inteligencia artificial para el area Inference. Explica como la capacidad Model Router ayuda a personas y agentes a reconocer riesgos, coordinar decisiones, citar evidencia y mantener limites operativos seguros y confiables.

Un equipo uso Inference Model Router durante trabajo de inteligencia artificial en Inference, para comparar senales, elegir el siguiente paso y documentar la decision sin exponer datos privados.

Borrador de traduccion automatica (Spanish) for "Inference Provenance Ledger": Inference Provenance Ledger is a ml record that tracks where data came from and how it changed for model prediction serving. It uses hashes, source labels, and transformation history so teams can audit model inputs reliably while keeping evidence, reliability, and public-safe operational boundaries clear.

Ejemplo en borrador: The machine learning team used Inference Provenance Ledger when the endpoint handled burst traffic, so the team could audit model inputs reliably before the model moved into evaluation.

Inference Response Schema es una definicion publica de inteligencia artificial para el area Inference. Explica como la capacidad Response Schema ayuda a personas y agentes a reconocer riesgos, coordinar decisiones, citar evidencia y mantener limites operativos seguros y confiables.

Un equipo uso Inference Response Schema durante trabajo de inteligencia artificial en Inference, para comparar senales, elegir el siguiente paso y documentar la decision sin exponer datos privados.

Inference Safety Filter es una definicion publica de inteligencia artificial para el area Inference. Explica como la capacidad Safety Filter ayuda a personas y agentes a reconocer riesgos, coordinar decisiones, citar evidencia y mantener limites operativos seguros y confiables.

Un equipo uso Inference Safety Filter durante trabajo de inteligencia artificial en Inference, para comparar senales, elegir el siguiente paso y documentar la decision sin exponer datos privados.

Inference Tool Permission es una definicion publica de inteligencia artificial para el area Inference. Explica como la capacidad Tool Permission ayuda a personas y agentes a reconocer riesgos, coordinar decisiones, citar evidencia y mantener limites operativos seguros y confiables.

Un equipo uso Inference Tool Permission durante trabajo de inteligencia artificial en Inference, para comparar senales, elegir el siguiente paso y documentar la decision sin exponer datos privados.

Borrador de traduccion automatica (Spanish) for "Inference Training Checkpoint": Inference Training Checkpoint is a ml recovery artifact that saves model state during learning for model prediction serving. 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.

Ejemplo en borrador: The machine learning team used Inference Training Checkpoint when the endpoint handled burst traffic, so the team could resume or inspect training safely before the model moved into evaluation.

Borrador de traduccion automatica (Spanish) for "Infrastructure Approval Step": Infrastructure Approval Step is a devops workflow control that requires review before a sensitive change proceeds for cloud resources and platform wiring. 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.

Ejemplo en borrador: The DevOps team used Infrastructure Approval Step when a new region was added, so the team could keep high-risk automation accountable before the deployment window opened.

Borrador de traduccion automatica (Spanish) for "Infrastructure Artifact Signature": Infrastructure Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for cloud resources and platform wiring. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.

Ejemplo en borrador: The DevOps team used Infrastructure Artifact Signature when a new region was added, so the team could trust deployed packages before the deployment window opened.

Borrador de traduccion automatica (Spanish) for "Infrastructure Build Gate": Infrastructure Build Gate is a devops quality gate that blocks promotion when required checks fail for cloud resources and platform wiring. It uses tests, lint, security scans, and policy rules so teams can prevent broken releases while keeping evidence, reliability, and public-safe operational boundaries clear.

Ejemplo en borrador: The DevOps team used Infrastructure Build Gate when a new region was added, so the team could prevent broken releases before the deployment window opened.

Borrador de traduccion automatica (Spanish) for "Infrastructure Config Drift Check": Infrastructure Config Drift Check is a devops consistency check that finds differences between intended and live configuration for cloud resources and platform wiring. It uses desired state, live state, and diff reports so teams can avoid surprise environment behavior while keeping evidence, reliability, and public-safe operational boundaries clear.

Ejemplo en borrador: The DevOps team used Infrastructure Config Drift Check when a new region was added, so the team could avoid surprise environment behavior before the deployment window opened.

Borrador de traduccion automatica (Spanish) for "Infrastructure Incident Timeline": Infrastructure Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for cloud resources and platform wiring. 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.

Ejemplo en borrador: The DevOps team used Infrastructure Incident Timeline when a new region was added, so the team could learn from outages without guesswork before the deployment window opened.

Borrador de traduccion automatica (Spanish) for "Infrastructure Infra Plan": Infrastructure Infra Plan is a devops change preview that shows expected infrastructure changes before apply for cloud resources and platform wiring. 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.

Ejemplo en borrador: The DevOps team used Infrastructure Infra Plan when a new region was added, so the team could review platform changes safely before the deployment window opened.

Borrador de traduccion automatica (Spanish) 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.

Ejemplo en borrador: 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.

Borrador de traduccion automatica (Spanish) for "Infrastructure Rollback Plan": Infrastructure Rollback Plan is a devops recovery plan that defines how to return to a known good version for cloud resources and platform wiring. It uses version pins, database notes, and operator steps so teams can recover quickly from bad changes while keeping evidence, reliability, and public-safe operational boundaries clear.

Ejemplo en borrador: The DevOps team used Infrastructure Rollback Plan when a new region was added, so the team could recover quickly from bad changes before the deployment window opened.

Borrador de traduccion automatica (Spanish) for "Infrastructure Rollout Guard": Infrastructure Rollout Guard is a devops release control that limits exposure during gradual deployment for cloud resources and platform wiring. 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.

Ejemplo en borrador: The DevOps team used Infrastructure Rollout Guard when a new region was added, so the team could reduce blast radius before the deployment window opened.