# Amazon — Taxonomy of agentic primitives in AWS Quick

- Company: Amazon (amazon.com)
- Announced: 2026-11-06T17:34:45+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/taxonomy-of-agentic-primitives-in-amazon-quick/
- Record: https://forck.live/items/32723-taxonomy-of-agentic-primitives-in-aws-quick
- Subject: Bedrock / Nova

Amazon is sharing the taxonomy of agentic primitives it converged on while building Amazon Quick, after finding that the same few ideas kept getting rebuilt under different names. The framework decomposes agentic work into four plain questions: When, What, Who and How, with a trigger starting the work and carrying the task, an agent taking it on, and capabilities performing it. Amazon defines an agent as a persistent, learning actor made of instructions, capabilities and learned context, and says the underlying large language model is a swappable model parameter while conversation history is per-session state. Capabilities span a spectrum from fully agentic to fully deterministic, which Amazon calls a confidence contract: tools are atomic operations with a typed schema, skills are structured guidance with room for judgment, and workflows are deterministic coordination with decision logic in code. Amazon says a request such as monitoring Slack and sending a daily digest is usually a trigger added to an existing agent, not a new agent or workflow. The post is the first in a series, with upcoming posts on the agentic operating system, background learning and proactive feeds.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/taxonomy-of-agentic-primitives-in-amazon-quick/:

> Over the past year, as we built Amazon Quick, our agents went from answering questions to taking actions: scheduling meetings, running research, generating reports. As the system evolved, one problem kept resurfacing: there was no shared definition of the primitives that agentic work is built from. The same few ideas kept getting rebuilt under different names: an actor that does the work, a signal that starts it, a packaged procedure, and a memory that carries lessons forward. This repetition leaked into product design and onto the user.
> 
> Take the user who says “ monitor my Slack channel and send me a daily digest ”. Is that a new agent, a scheduled instruction to an existing one, a workflow, or a skill? These are different questions, but without a shared vocabulary they collapse into one confusing choice.
> 
> This post shares the taxonomy we converged on: one set of primitives found by decomposing agentic work into four plain questions: When? , What? , Who? , and How? Most of the framework stays invisible to end users by design, but a shared vocabulary makes the system easier to reason about for anyone building beneath it.
> 
> The framework at a glance

---

Record: https://forck.live/items/32723-taxonomy-of-agentic-primitives-in-aws-quick
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
