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.
Rascunho de traducao automatica (Portuguese) for "Service Mesh Egress Policy": Service Mesh Egress Policy is a networking outbound control that decides where workloads may send traffic for east-west service communication. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The network engineering team used Service Mesh Egress Policy when a service called another service, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) for "Dataset Provenance Ledger": Dataset Provenance Ledger is a ml record that tracks where data came from and how it changed for labeled and unlabeled data used for learning. 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.
“Exemplo em rascunho: The machine learning team used Dataset Provenance Ledger when the dataset received a new batch, so the team could audit model inputs reliably before the model moved into evaluation.”
Rascunho de traducao automatica (Portuguese) for "Cluster Placement Strategy": Cluster Placement Strategy is a compute scheduling rule that chooses where workloads should run for group of machines acting as one platform. It uses affinity, topology, availability, and cost signals so teams can improve reliability and efficiency while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The platform engineering team used Cluster Placement Strategy when the cluster added a node pool, so the team could improve reliability and efficiency before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Supply Chain Attack Surface": Supply Chain Attack Surface is a security exposure model that lists reachable systems, actions, and trust boundaries for dependencies, builds, and artifacts. 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.
“Exemplo em rascunho: The security team used Supply Chain Attack Surface when a package update arrived, so the team could prioritize risk reduction before the risk review began.”
Rascunho de traducao automatica (Portuguese) for "Telemetry Science Window": Telemetry Science Window is a space planning interval that marks when conditions are suitable for data collection for spacecraft health and performance monitoring. 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.
“Exemplo em rascunho: The mission team used Telemetry Science Window when the telemetry stream showed unexpected drift, so the team could capture useful observations without breaking constraints before the next mission decision point.”
Rascunho de traducao automatica (Portuguese) for "Rollback Secret Rotation": Rollback Secret Rotation is a devops credential workflow that replaces sensitive keys without service interruption for recovery from a bad deployment. It uses dual credentials, rollout steps, and revocation so teams can reduce credential exposure while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Rollback Secret Rotation when the error budget started burning, so the team could reduce credential exposure before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Feature Evaluation Harness": Feature Evaluation Harness is a ml test system that runs repeatable checks against model behavior for input signals used by a machine learning model. 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.
“Exemplo em rascunho: The machine learning team used Feature Evaluation Harness when a feature distribution shifted, so the team could compare releases with evidence before the model moved into evaluation.”
Rascunho de traducao automatica (Portuguese) for "Scheduler Placement Strategy": Scheduler Placement Strategy is a compute scheduling rule that chooses where workloads should run for placement of work onto resources. It uses affinity, topology, availability, and cost signals so teams can improve reliability and efficiency while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The platform engineering team used Scheduler Placement Strategy when the cluster needed to place a job, so the team could improve reliability and efficiency before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "RAG Instruction Boundary": RAG Instruction Boundary is a ai policy boundary that separates durable system instructions from user-provided content for retrieval-augmented generation pipelines. It uses role labels, precedence rules, and prompt assembly checks so teams can avoid instruction confusion while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The AI platform team used RAG Instruction Boundary when the retriever mixed old and new documents, so the team could avoid instruction confusion before the agent workflow reached production.”
Rascunho de traducao automatica (Portuguese) for "Canary Artifact Signature": Canary Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for small-scope production rollout. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Canary Artifact Signature when the first traffic slice received the build, so the team could trust deployed packages before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Release Trace Link": Release Trace Link is a devops observability link that connects a deployment or workflow to runtime evidence for versioned delivery of code or content. It uses trace IDs, span metadata, and release identifiers so teams can debug production changes faster while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Release Trace Link when the release notes were generated, so the team could debug production changes faster before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Pipeline Hyperparameter Sweep": Pipeline Hyperparameter Sweep is a ml optimization process that searches over model settings to improve a target metric for automated data and model workflow. 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.
“Exemplo em rascunho: The machine learning team used Pipeline Hyperparameter Sweep when the pipeline missed a validation step, so the team could find better configurations before the model moved into evaluation.”
Rascunho de traducao automatica (Portuguese) for "Model Citation Builder": Model Citation Builder is a ai attribution helper that formats source links and evidence for an AI answer for foundation model behavior and serving. It uses canonical URLs, source titles, and quote limits so teams can make generated answers citeable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The AI platform team used Model Citation Builder when the model produced a low-confidence answer, so the team could make generated answers citeable before the agent workflow reached production.”
Rascunho de traducao automatica (Portuguese) for "Vector Evaluation Harness": Vector Evaluation Harness is a ml test system that runs repeatable checks against model behavior for numeric representation and similarity search. 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.
“Exemplo em rascunho: The machine learning team used Vector Evaluation Harness when the vector store returned close matches, so the team could compare releases with evidence before the model moved into evaluation.”
Rascunho de traducao automatica (Portuguese) for "Alignment Tool Permission": Alignment Tool Permission is a ai access control that decides which tools an AI workflow may call for model behavior shaping and policy fit. 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.
“Exemplo em rascunho: The AI platform team used Alignment Tool Permission when the assistant needed a safer answer style, so the team could block unsafe automation before the agent workflow reached production.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "Memory Response Schema": Memory Response Schema is a ai output contract that requires model output to match a known structure for persistent or session-level AI state. It uses JSON schemas, validators, retries, and error reporting so teams can make responses machine-readable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The AI platform team used Memory Response Schema when the assistant reused earlier project context, so the team could make responses machine-readable before the agent workflow reached production.”
Rascunho de traducao automatica (Portuguese) for "Edge Image Hardening": Edge Image Hardening is a compute security practice that reduces risk inside packaged runtime images for globally distributed runtime. It uses minimal bases, patching, and vulnerability checks so teams can ship safer workloads while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The platform engineering team used Edge Image Hardening when the request arrived near a user, so the team could ship safer workloads before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Load Balancer Egress Policy": Load Balancer Egress Policy is a networking outbound control that decides where workloads may send traffic for traffic distribution. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The network engineering team used Load Balancer Egress Policy when traffic shifted between regions, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) for "Artifact Trace Link": Artifact Trace Link is a devops observability link that connects a deployment or workflow to runtime evidence for build output and package delivery. It uses trace IDs, span metadata, and release identifiers so teams can debug production changes faster while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Artifact Trace Link when the container image was signed, so the team could debug production changes faster before the deployment window opened.”