Zum Inhalt springen

Browse A-Z

Alphabetical public term index for this language.

1,322 source-backed termsgenerated snapshot

Automatischer Uebersetzungsentwurf (German) for "API Whiteboard Trust Ledger": API Whiteboard Trust Ledger is a policy-driven architecture vernacular term for agent policy work in a policy-driven service network. It describes a trust ledger that lets humans and agents discover what a service can safely do, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.

Beispielentwurf: The team used API Whiteboard Trust Ledger after the sitemap had a link that forgot where school was. Then the rollback was ready before the ship button got sweaty.

API-First

/eɪ piː aɪ fɜːrst/adjective
Technology
Machine-assisted language draft

Automatischer Uebersetzungsentwurf (German) for "API-First": A design philosophy where the API contract is defined and agreed upon before any implementation begins. API-first teams treat the API as the product — writing the specification first (e.g., in OpenAPI), getting feedback from consumers, then building both client and server simultaneously against the agreed contract.

Beispielentwurf: Their API-first approach meant the mobile app team could start building against the spec before the backend was done.
GitOps and Release Engineering
Machine-assisted language draft

App of Apps ist ein GitOps-Begriff fuer a GitOps pattern where one parent application manages child applications. Er hilft Teams, Menschen und Agenten, deklarierten Quellzustand mit laufenden Systemen zu vergleichen und zu handeln, ohne mehr Erfolg vorzutäuschen als belegt ist. Quelle: Argo CD documentation.

Das Team nutzte App of Apps vor dem Mittagessen, damit das Release nicht mit offenen Schnuersen in die Produktion rannte.
GitOps and Release Engineering
Machine-assisted language draft

ApplicationSet ist ein GitOps-Begriff fuer an Argo CD pattern for generating many related applications from a template. Er hilft Teams, Menschen und Agenten, deklarierten Quellzustand mit laufenden Systemen zu vergleichen und zu handeln, ohne mehr Erfolg vorzutäuschen als belegt ist. Quelle: Argo CD documentation.

Das Team nutzte ApplicationSet vor dem Mittagessen, damit das Release nicht mit offenen Schnuersen in die Produktion rannte.
IETF Internet Standards
Machine-assisted language draft

Area Director Map ist ein Begriff aus IETF-Internetstandards für area director map work that connects internet folklore to the standards process that real implementers, ISPs, browsers, cloud providers, and enterprises use to keep networks interoperable. Er hilft Menschen und Agenten, Signal, Quelle und sicheren nächsten Schritt zu benennen, ohne so zu tun, als hätte eine Automatisierung, Kampagne, DNS-Zone, ein RFC oder ein Netzwerkpfad mehr getan als belegt ist. Quelle: IETF DNS technology; IETF Areas; RFC 1918 private address space.

Das Team nutzte Area Director Map vor dem Start, damit der Workflow nicht wie ein verschüttetes Pausenbrot durch die Produktion rutschte.
GitOps and Release Engineering
Machine-assisted language draft

Argo CD Application ist ein GitOps-Begriff fuer an Argo CD object that describes source, destination, and sync behavior for an app. Er hilft Teams, Menschen und Agenten, deklarierten Quellzustand mit laufenden Systemen zu vergleichen und zu handeln, ohne mehr Erfolg vorzutäuschen als belegt ist. Quelle: Argo CD documentation.

Das Team nutzte Argo CD Application vor dem Mittagessen, damit das Release nicht mit offenen Schnuersen in die Produktion rannte.

Ate

/eɪt/verb (past tense)
Slang
Machine-assisted language draft

Automatischer Uebersetzungsentwurf (German) for "Ate": Did something perfectly, completely, and impressively. To "eat" (past tense: ate) a performance, look, or challenge means to dominate it fully with no leftovers — you consumed it entirely. Originates from ballroom culture and drag slang, now used broadly for anyone who executes something flawlessly.

Beispielentwurf: She ate that chorus — the whole arena was on their feet.

Automatischer Uebersetzungsentwurf (German) for "Atlas Backpack Build Gate": Atlas Backpack Build Gate is a ci/cd vernacular term for artifact upload work in a policy-driven service network. It describes a build gate 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.

Beispielentwurf: The team used Atlas Backpack Build Gate after the rollback plan hid under sticky notes. Then everyone knew the next check before the meeting got weird.

Automatischer Uebersetzungsentwurf (German) for "Atlas Backpack Config Compass": Atlas Backpack Config Compass is a devops vernacular term for runbook work in a policy-driven service network. It describes a config compass that helps operators fix the problem without guessing or leaking secrets, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.

Beispielentwurf: The team used Atlas Backpack Config Compass after the route list looked like an open backpack. Then the agent showed its receipt and waited for a grown-up key.

Automatischer Uebersetzungsentwurf (German) for "Atlas Backpack On Call Note": Atlas Backpack On Call Note is a devops vernacular term for configuration drift work in a policy-driven service network. It describes a on call note 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.

Beispielentwurf: The team used Atlas Backpack On Call Note after the rollback plan hid under sticky notes. Then everyone knew the next check before the meeting got weird.

Automatischer Uebersetzungsentwurf (German) for "Atlas Backpack Preview Ticket": Atlas Backpack Preview Ticket is a ci/cd vernacular term for status check work in a policy-driven service network. It describes a preview ticket 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.

Beispielentwurf: The team used Atlas Backpack Preview Ticket after the build queue looked like a spelling quiz full of red marks. Then the release moved on without hallway chaos.

Automatischer Uebersetzungsentwurf (German) for "Atlas Bell Ring Context Budget": Atlas Bell Ring Context Budget is a agentic workflows vernacular term for human approval work in a policy-driven service network. It describes a context budget 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.

Beispielentwurf: The team used Atlas Bell Ring Context Budget after the trace link went missing. Then the operator found the bug before the dashboard made a dramatic face.

Automatischer Uebersetzungsentwurf (German) for "Atlas Bell Ring Flag Flip Note": Atlas Bell Ring Flag Flip Note is a release engineering vernacular term for feature flag work in a policy-driven service network. It describes a flag flip note that makes rollback and recovery clear before the deploy starts, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.

Beispielentwurf: The team used Atlas Bell Ring Flag Flip Note after the release plan slid like a lunch tray. Then the build passed for a real reason, not crossed fingers.

Automatischer Uebersetzungsentwurf (German) for "Atlas Button Build Gate": Atlas Button Build Gate is a ci/cd vernacular term for build queue 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.

Beispielentwurf: The team used Atlas Button Build Gate after the sitemap had a link that forgot where school was. Then the rollback was ready before the ship button got sweaty.

Automatischer Uebersetzungsentwurf (German) for "Atlas Button Log Flashlight": Atlas Button Log Flashlight is a devops vernacular term for runbook work in a policy-driven service network. It describes a log flashlight that keeps everyday operations boring in the best possible way, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.

Beispielentwurf: The team used Atlas Button Log Flashlight after the deploy looked like late homework. Then the team fixed the step without blaming the snack table.

Automatischer Uebersetzungsentwurf (German) for "Atlas Cafeteria Branch Hall Pass": Atlas Cafeteria Branch Hall Pass is a ci/cd vernacular term for branch promotion work in a policy-driven service network. It describes a branch hall pass 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.

Beispielentwurf: The team used Atlas Cafeteria Branch Hall Pass after the route list looked like an open backpack. Then the agent showed its receipt and waited for a grown-up key.

Automatischer Uebersetzungsentwurf (German) for "Atlas Checklist Discovery Map": Atlas Checklist Discovery Map is a policy-driven architecture vernacular term for OpenAPI file work in a policy-driven service network. It describes a discovery map that lets humans and agents discover what a service can safely do, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.

Beispielentwurf: The team used Atlas Checklist Discovery Map after the release plan slid like a lunch tray. Then the build passed for a real reason, not crossed fingers.

Automatischer Uebersetzungsentwurf (German) for "Atlas Checklist Merge Guard": Atlas Checklist Merge Guard is a ci/cd vernacular term for build queue work in a policy-driven service network. It describes a merge guard that keeps build, test, and deploy evidence in one explainable path, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.

Beispielentwurf: The team used Atlas Checklist Merge Guard after the policy file and API docs gave different answers. Then the trace told the story without spilling private data.

Automatischer Uebersetzungsentwurf (German) for "Atlas Checklist Restart Receipt": Atlas Checklist Restart Receipt is a devops vernacular term for configuration drift work in a policy-driven service network. It describes a restart receipt that keeps everyday operations boring in the best possible way, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.

Beispielentwurf: The team used Atlas Checklist Restart Receipt after the release plan slid like a lunch tray. Then the build passed for a real reason, not crossed fingers.

Automatischer Uebersetzungsentwurf (German) for "Atlas Compass Cache Blanket": Atlas Compass Cache Blanket is a devops vernacular term for queue depth work in a policy-driven service network. It describes a cache blanket that keeps everyday operations boring in the best possible way, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.

Beispielentwurf: The team used Atlas Compass Cache Blanket after the deploy looked like late homework. Then the team fixed the step without blaming the snack table.