Define the new internet.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
2,337 definitions
Rascunho de traducao automatica (Portuguese) for "Metric Data Split": Metric Data Split is a ml experimental control that separates examples for training, validation, and testing for measurement of model behavior. It uses randomization rules, leakage checks, and seed tracking so teams can measure generalization honestly while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The machine learning team used Metric Data Split when the metric changed after data cleanup, so the team could measure generalization honestly before the model moved into evaluation.”
Rascunho de traducao automatica (Portuguese) for "Canary Release Manifest": Canary Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for small-scope production rollout. It uses commit IDs, checksums, and deployment URLs so teams can make releases auditable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Canary Release Manifest when the first traffic slice received the build, so the team could make releases auditable before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Artifact Build Gate": Artifact Build Gate is a devops quality gate that blocks promotion when required checks fail for build output and package delivery. 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.
“Exemplo em rascunho: The DevOps team used Artifact Build Gate when the container image was signed, so the team could prevent broken releases before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Metric Model Card": Metric Model Card is a ml documentation artifact that summarizes intended use, limits, and evaluation evidence for measurement of model behavior. 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 Metric Model Card when the metric changed after data cleanup, so the team could publish model behavior honestly before the model moved into evaluation.”
Rascunho de traducao automatica (Portuguese) for "CD Runbook Check": CD Runbook Check is a devops operational test that confirms that documented procedures still work for deployment automation and promotion. 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.
“Exemplo em rascunho: The DevOps team used CD Runbook Check when the release moved toward production, so the team could keep response playbooks current before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Rollback Incident Timeline": Rollback Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for recovery from a bad deployment. 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.
“Exemplo em rascunho: The DevOps team used Rollback Incident Timeline when the error budget started burning, so the team could learn from outages without guesswork before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Environment Runbook Check": Environment Runbook Check is a devops operational test that confirms that documented procedures still work for configuration for a runtime stage. 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.
“Exemplo em rascunho: The DevOps team used Environment Runbook Check when staging and production drifted, so the team could keep response playbooks current before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Environment Config Drift Check": Environment Config Drift Check is a devops consistency check that finds differences between intended and live configuration for configuration for a runtime stage. 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.
“Exemplo em rascunho: The DevOps team used Environment Config Drift Check when staging and production drifted, so the team could avoid surprise environment behavior before the deployment window opened.”
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 "Rollback Release Manifest": Rollback Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for recovery from a bad deployment. It uses commit IDs, checksums, and deployment URLs so teams can make releases auditable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Rollback Release Manifest when the error budget started burning, so the team could make releases auditable before the deployment window opened.”