Agentic AI Atlasby a5c.ai
OverviewWikiGraphFor AgentsEdgesSearchWorkspace
/
GitHubDocsDiscord
iiRecord
Agentic AI Atlas · Worked Examples
page:agent-generate-universal-agentic-stack-worked-examplesa5c.ai
Search record views/
Record · tabs

Available views

II.Record viewspp. 1 - 1
overviewarticlejsongraph
II.
Page JSON

page:agent-generate-universal-agentic-stack-worked-examples

Structured · live

Worked Examples json

Inspect the normalized record payload exactly as the atlas UI reads it.

File · wiki/agent-generate/universal-agentic-stack/04-worked-examples.mdCluster · wiki
Record JSON
{
  "id": "page:agent-generate-universal-agentic-stack-worked-examples",
  "_kind": "Page",
  "_file": "wiki/agent-generate/universal-agentic-stack/04-worked-examples.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "title": "Worked Examples",
    "displayName": "Worked Examples",
    "slug": "agent-generate/universal-agentic-stack/04-worked-examples",
    "articlePath": "wiki/agent-generate/universal-agentic-stack/04-worked-examples.md",
    "article": "# Worked Examples\n\nThis page shows how the stack works on real product shapes. The goal is not to produce one perfect label. The goal is to identify where the value is concentrated and which layers are delegated.\n\n## Example 1: Bare model API\n\nThink of a plain provider API call with no agent loop around it.\n\n| Layer area | What exists |\n|---|---|\n| 1-3 | Strongly owned: model, provider, transport |\n| 4-6 | Minimal or absent |\n| 7-9 | Usually delegated to the caller |\n| 10-11 | Often just an API response surface |\n\nThis is not an agent platform by itself. It is the lower part of the stack that an agent core can build on top of.\n\nOne-sentence placement:\n\n`This product mainly owns Layers 1-3, delegates the agent system and operating boundary to the caller, and exposes a thin API surface.`\n\n## Example 2: Model gateway\n\nThink of a system that normalizes access to multiple providers.\n\n| Layer area | What exists |\n|---|---|\n| 2-3 | Strongly owned: provider routing and transport compatibility |\n| 4-6 | Often absent or thin |\n| 7-9 | Usually delegated |\n| 10-11 | May expose a dashboard or API |\n\nThe common mistake here is to confuse a gateway with an agent runtime. Routing requests is not the same thing as owning the loop.\n\nOne-sentence placement:\n\n`This product mainly owns Layers 2-3, may expose a surface for routing or analytics, and usually delegates the agent loop, workspace, execution, and policy layers.`\n\n## Example 3: Agent framework library\n\nThink of a graph-based or loop-based builder that developers embed into their own app.\n\n| Layer area | What exists |\n|---|---|\n| 4 | Strongly owned |\n| 5 | Partly owned, depending on runtime features |\n| 6 | Sometimes present, sometimes thin |\n| 7-11 | Often delegated to the host application |\n\nThis is where many custom-agent builder products live. They are extremely important, but they usually do not own the full operating boundary or surface.\n\nOne-sentence placement:\n\n`This product mainly owns Layers 4-5, may touch Layer 6, and usually delegates workspace, execution, sandbox, and presentation to the host application.`\n\n## Example 4: Coding agent CLI\n\nThink of a local coding agent that edits files, runs commands, asks for approvals, and streams output.\n\n| Layer area | What exists |\n|---|---|\n| 4-6 | Usually strongly owned |\n| 7-9 | Often strongly owned or explicitly mediated |\n| 10-11 | Strongly owned through CLI or TUI |\n| 1-3 | Delegated to chosen model/provider stack |\n\nThis is why coding agents feel like \"complete products\": they often span more of the stack than framework libraries do.\n\nOne-sentence placement:\n\n`This product mainly owns Layers 4-11, while delegating model, provider, and transport choices to an external model stack.`\n\n## Example 5: Hosted agent platform\n\nThink of a service that hosts agents, gives them deployment surfaces, and exposes collaboration or observability around them.\n\n| Layer area | What exists |\n|---|---|\n| 4-6 | Usually strongly owned |\n| 7-9 | Often partly owned, partly abstracted behind hosted infrastructure |\n| 10-11 | Strongly owned through dashboards, APIs, and workflows |\n| 1-3 | Sometimes delegated to external providers, sometimes bundled |\n\nThe critical question is whether hosted execution and policy are real product layers or just hidden infrastructure. If the user can rely on them, they still belong on the map.\n\nOne-sentence placement:\n\n`This product mainly owns Layers 4-11 and may either delegate or bundle Layers 1-3 depending on how model access is offered.`\n\n## Example 6: IDE extension around an agent\n\nThink of an IDE panel that exposes an agent but depends on another runtime under the hood.\n\n| Layer area | What exists |\n|---|---|\n| 10-11 | Strongly owned by the extension |\n| 7 | Sometimes partly owned through editor workspace integration |\n| 4-9 | Often delegated to a local or remote agent runtime |\n\nDo not over-credit the extension. A polished IDE surface can still be mostly a presentation and interaction layer over someone else's runtime and platform.\n\nOne-sentence placement:\n\n`This product mainly owns Layers 10-11, may partly own workspace integration, and usually delegates most of the runtime and platform below it.`\n\n## Quick pattern summary\n\n| Product shape | Layers where value usually concentrates |\n|---|---|\n| Model API | 1-3 |\n| Gateway | 2-3 |\n| Framework library | 4-5 |\n| Coding agent | 4-11, with 1-3 delegated |\n| Hosted platform | 4-11, sometimes with 1-3 delegated |\n| IDE extension | 10-11, sometimes 7 |\n\n## How to use these examples\n\n- Use them to get the first rough placement.\n- Then use [`03-placement-checklist.md`](./03-placement-checklist.md) to refine the result.\n- If you need a clean writeup format, continue to [`08-review-template.md`](./08-review-template.md).\n- If the product does not fit neatly, record split ownership instead of forcing a single label.\n",
    "documents": [
      "layer:1-model",
      "layer:2-provider",
      "layer:3-transport",
      "layer:4-agent-core",
      "layer:5-agent-runtime",
      "layer:6-agent-platform",
      "layer:7-workspace",
      "layer:8-execution",
      "layer:9-sandbox",
      "layer:10-interaction",
      "layer:11-presentation"
    ]
  },
  "outgoingEdges": [
    {
      "from": "page:agent-generate-universal-agentic-stack-worked-examples",
      "to": "layer:1-model",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-worked-examples",
      "to": "layer:2-provider",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-worked-examples",
      "to": "layer:3-transport",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-worked-examples",
      "to": "layer:4-agent-core",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-worked-examples",
      "to": "layer:5-agent-runtime",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-worked-examples",
      "to": "layer:6-agent-platform",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-worked-examples",
      "to": "layer:7-workspace",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-worked-examples",
      "to": "layer:8-execution",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-worked-examples",
      "to": "layer:9-sandbox",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-worked-examples",
      "to": "layer:10-interaction",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-worked-examples",
      "to": "layer:11-presentation",
      "kind": "documents"
    }
  ],
  "incomingEdges": [
    {
      "from": "page:agent-generate-universal-agentic-stack",
      "to": "page:agent-generate-universal-agentic-stack-worked-examples",
      "kind": "contains_page"
    }
  ]
}

Shortcuts

Back to overview
Open graph tab