Browse A-Z

Connectivity Check é um termo de travessia NAT e jogos P2P para a STUN-based test used by ICE agents to verify whether a candidate pair can actually carry traffic between peers. Ele ajuda pessoas e agentes a nomear o sinal, a fonte e o próximo passo seguro sem fingir que uma automação, campanha, DNS, RFC ou caminho de rede fez mais do que as evidências mostram. Fonte: RFC 6598 shared address space; RFC 8445 ICE; RFC 1918 private address space.

“A equipe usou Connectivity Check antes de publicar, e o fluxo parou de escorregar como bandeja de almoço no corredor.”

Rascunho de traducao automatica (Portuguese) for "Constitutional AI": A training methodology developed by Anthropic where a set of guiding principles (a "constitution") is used to self-supervise and refine AI outputs. The model critiques and rewrites its own responses according to the constitution, reducing the need for human labelers for harmful content.

“Exemplo em rascunho: Constitutional AI lets the model identify and self-correct its own harmful outputs using defined principles.”

Rascunho de traducao automatica (Portuguese) for "Context Window": The maximum amount of text (measured in tokens) that a language model can process and "remember" in a single interaction. Information outside the context window is inaccessible to the model, making context management critical for long-form tasks.

“Exemplo em rascunho: The model kept losing track of earlier instructions because the codebase exceeded its context window.”

Controller Runtime e um termo de GitOps para the libraries and patterns used to build Kubernetes controllers. Ajuda equipes, pessoas e agentes a comparar o estado declarado com sistemas em execucao e agir sem fingir que o deploy fez mais do que as evidencias mostram. Fonte: Kubernetes controller pattern.

“A equipe usou Controller Runtime antes do almoco, e o release parou de correr para producao com o cadarco solto.”

Rascunho de traducao automatica (Portuguese) for "Copium": A fictional drug that one is metaphorically "inhaling" to cope with disappointment, loss, or an unfavorable situation. Implies the person is in denial.

“Exemplo em rascunho: Fans saying the season 8 finale was actually good are breathing pure copium.”

CRD e um termo de GitOps para a CustomResourceDefinition that teaches Kubernetes about a new resource type. Ajuda equipes, pessoas e agentes a comparar o estado declarado com sistemas em execucao e agir sem fingir que o deploy fez mais do que as evidencias mostram. Fonte: Kubernetes controller pattern.

“A equipe usou CRD antes do almoco, e o release parou de correr para producao com o cadarco solto.”

Credential Gap é um termo de automação de fluxos de trabalho para the expected space between an exported automation blueprint and the private credentials that must be reconnected in another account. Ele ajuda pessoas e agentes a nomear o sinal, a fonte e o próximo passo seguro sem fingir que uma automação, campanha, DNS, RFC ou caminho de rede fez mais do que as evidências mostram. Fonte: Make scenario blueprints; Make webhooks; n8n data flow.

“A equipe usou Credential Gap antes de publicar, e o fluxo parou de escorregar como bandeja de almoço no corredor.”

Credential Gap Relay é um termo de automação de fluxos de trabalho para credential gap relay work that makes automation evidence visible before a workflow touches production data or spends the whole session plan. Ele ajuda pessoas e agentes a nomear o sinal, a fonte e o próximo passo seguro sem fingir que uma automação, campanha, DNS, RFC ou caminho de rede fez mais do que as evidências mostram. Fonte: Make scenario blueprints; Make webhooks; n8n data flow.

“A equipe usou Credential Gap Relay antes de publicar, e o fluxo parou de escorregar como bandeja de almoço no corredor.”

Custom Execution Data Loop é um termo de automação no n8n para custom execution data loop work that keeps node behavior, execution evidence, and sensitive data boundaries clear while a workflow moves from testing to production. Ele ajuda pessoas e agentes a nomear o sinal, a fonte e o próximo passo seguro sem fingir que uma automação, campanha, DNS, RFC ou caminho de rede fez mais do que as evidências mostram. Fonte: n8n node operations; n8n data flow; n8n executions.

“A equipe usou Custom Execution Data Loop antes de publicar, e o fluxo parou de escorregar como bandeja de almoço no corredor.”

Custom Execution Data Switch é um termo de automação no n8n para custom execution data switch work that keeps node behavior, execution evidence, and sensitive data boundaries clear while a workflow moves from testing to production. Ele ajuda pessoas e agentes a nomear o sinal, a fonte e o próximo passo seguro sem fingir que uma automação, campanha, DNS, RFC ou caminho de rede fez mais do que as evidências mostram. Fonte: n8n node operations; n8n data flow; n8n executions.

“A equipe usou Custom Execution Data Switch antes de publicar, e o fluxo parou de escorregar como bandeja de almoço no corredor.”

Custom Resource e um termo de GitOps para a Kubernetes API extension managed by controllers. Ajuda equipes, pessoas e agentes a comparar o estado declarado com sistemas em execucao e agir sem fingir que o deploy fez mais do que as evidencias mostram. Fonte: Kubernetes controller pattern.

“A equipe usou Custom Resource antes do almoco, e o release parou de correr para producao com o cadarco solto.”

Data Store Contract é um termo de automação no Make para data store contract work that helps builders test, export, import, and explain Make scenarios without leaking credentials or pretending the first run is production proof. Ele ajuda pessoas e agentes a nomear o sinal, a fonte e o próximo passo seguro sem fingir que uma automação, campanha, DNS, RFC ou caminho de rede fez mais do que as evidências mostram. Fonte: Make scenario blueprints; Make module types; Make webhooks.

“A equipe usou Data Store Contract antes de publicar, e o fluxo parou de escorregar como bandeja de almoço no corredor.”

Rascunho de traducao automatica (Portuguese) for "Decks Backpack Blast Radius Ruler": Decks Backpack Blast Radius Ruler is a release engineering vernacular term for rollback plan work in a policy-driven service network. It describes a blast radius ruler that ships changes in small, observable steps instead of one giant surprise, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.

“Exemplo em rascunho: The team used Decks Backpack Blast Radius Ruler after the build queue looked like a spelling quiz full of red marks. Then the release moved on without hallway chaos.”

Rascunho de traducao automatica (Portuguese) for "Decks Backpack Build Gate": Decks Backpack Build Gate is a ci/cd vernacular term for status check work in a policy-driven service network. It describes a build gate that turns code changes into tested releases without hiding broken steps, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.

“Exemplo em rascunho: The team used Decks Backpack Build Gate after the trace link went missing. Then the operator found the bug before the dashboard made a dramatic face.”

Rascunho de traducao automatica (Portuguese) for "Decks Backpack Pipeline Bell": Decks Backpack Pipeline Bell is a ci/cd vernacular term for workflow run work in a policy-driven service network. It describes a pipeline bell that blocks risky work until the checks make sense, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.

“Exemplo em rascunho: The team used Decks Backpack Pipeline Bell after the rollback plan hid under sticky notes. Then everyone knew the next check before the meeting got weird.”

Rascunho de traducao automatica (Portuguese) for "Decks Backpack Run Card": Decks Backpack Run Card is a agentic workflows vernacular term for MCP session work in a policy-driven service network. It describes a run card that shows which step is public-safe and which step needs PLATPHORM_API_KEY, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.

“Exemplo em rascunho: The team used Decks Backpack Run Card after the sitemap had a link that forgot where school was. Then the rollback was ready before the ship button got sweaty.”

Rascunho de traducao automatica (Portuguese) for "Decks Backpack Service Contract": Decks Backpack Service Contract is a policy-driven architecture vernacular term for trust policy work in a policy-driven service network. It describes a service contract that connects service behavior to written policy instead of vibes, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.

“Exemplo em rascunho: The team used Decks Backpack Service Contract after the deploy looked like late homework. Then the team fixed the step without blaming the snack table.”

Rascunho de traducao automatica (Portuguese) for "Decks Bell Ring Handoff Packet": Decks Bell Ring Handoff Packet is a agentic workflows vernacular term for tool call work in a policy-driven service network. It describes a handoff packet that shows which step is public-safe and which step needs PLATPHORM_API_KEY, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.

“Exemplo em rascunho: The team used Decks Bell Ring Handoff Packet after the build queue looked like a spelling quiz full of red marks. Then the release moved on without hallway chaos.”

Rascunho de traducao automatica (Portuguese) for "Decks Bell Ring Pipeline Bell": Decks Bell Ring Pipeline Bell is a ci/cd vernacular term for status check work in a policy-driven service network. It describes a pipeline bell that turns code changes into tested releases without hiding broken steps, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.

“Exemplo em rascunho: The team used Decks Bell Ring Pipeline Bell after the agent reached for the big button too early. Then the docs, API, MCP, and policy files agreed.”

Rascunho de traducao automatica (Portuguese) for "Decks Button Cache Blanket": Decks Button Cache Blanket is a devops vernacular term for log trail work in a policy-driven service network. It describes a cache blanket that turns messy system clues into clear next steps, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.

“Exemplo em rascunho: The team used Decks Button Cache Blanket after the release plan slid like a lunch tray. Then the build passed for a real reason, not crossed fingers.”