Agentic AI Atlasby a5c.ai
OverviewWikiGraphFor AgentsEdgesSearchWorkspace
/
GitHubDocsDiscord
iiRecord
Agentic AI Atlas · Builder and Product Fit
page:agent-generate-universal-agentic-stack-builder-fita5c.ai
Search record views/
Record · tabs

Available views

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

page:agent-generate-universal-agentic-stack-builder-fit

Structured · live

Builder and Product Fit json

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

File · wiki/agent-generate/universal-agentic-stack/01-builder-fit.mdCluster · wiki
Record JSON
{
  "id": "page:agent-generate-universal-agentic-stack-builder-fit",
  "_kind": "Page",
  "_file": "wiki/agent-generate/universal-agentic-stack/01-builder-fit.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "title": "Builder and Product Fit",
    "displayName": "Builder and Product Fit",
    "slug": "agent-generate/universal-agentic-stack/01-builder-fit",
    "articlePath": "wiki/agent-generate/universal-agentic-stack/01-builder-fit.md",
    "article": "# Builder and Product Fit\n\nThis page is for the question people usually ask first: \"Where does this framework or product fit?\"\n\n## The fast answer\n\nMost builder products do not own one single layer. They usually concentrate value in one of these zones:\n\n- Layers 2-3: model access and routing\n- Layers 4-5: agent definition and runtime behavior\n- Layer 6: extension, deployment, or ecosystem surface\n- Layers 10-11: interaction and presentation around another runtime\n\nThe job is to identify the center of gravity, then record what is delegated.\n\n## Typical placements\n\n| Thing you are evaluating | Usually lives in | Why |\n|---|---|---|\n| Model gateway or inference SDK | Layers 2-3 | It serves or speaks to the model, but does not own the agent loop. |\n| Agent framework or orchestration library | Layers 4-5 | It defines the agent loop and some runtime behavior. |\n| Coding agent CLI | Layers 4-6, often with 7-11 around it | It usually owns core, runtime, platform, and some user-facing surface. |\n| Plugin or skill system | Layer 6 | It is part of the platform and extension contract. |\n| Local shell runner, container runner, CI job runner | Layer 8 | It is where actions execute. |\n| Approval policy or filesystem/network restriction system | Layer 9 | It constrains execution. |\n| Web app, IDE panel, TUI, API surface | Layers 10-11 | It defines actions and presentation. |\n\n## Product-shape heuristics\n\n| If the product mainly sells... | Start by checking... |\n|---|---|\n| better model access | Layers 2-3 |\n| better agent authoring | Layers 4-5 |\n| deployment, extension, or operator workflows | Layer 6 |\n| safe execution | Layers 8-9 |\n| better human workflow around an agent | Layers 10-11 |\n\n## LangGraph and custom-agent builders\n\n| Stack area | Where it fits | Examples |\n|---|---|---|\n| Agent-Core | Graph/state-machine authoring and model/tool routing | `StateGraph`, graph nodes/edges/state, `create_agent`, tool dispatch, terminal routing |\n| Agent-Runtime | Host process, durable state, checkpointing, tools, interrupts, and streaming | checkpointer/store, thread state, human-in-the-loop gate, host tool registry |\n| Agent-Platform | Deployed graph operation and ecosystem extension surfaces | LangGraph Platform, LangSmith deployment, `RemoteGraph`, installed plugins, installed skills, launch/config surfaces |\n\n## Builder categories that look similar but are not\n\n| Category | Main layer weight | Why people confuse it |\n|---|---|---|\n| Agent builder | 4-5 | It often demos through a UI, so people over-credit 10-11 |\n| Hosted agent platform | 5-6, often 10-11 too | It wraps the builder in deployment and operational surfaces |\n| IDE integration | 10-11, sometimes 7 | It feels central because it is visible, but it may delegate the actual runtime |\n| Gateway or router | 2-3 | It sits in the middle of traffic, which makes it look more \"agentic\" than it is |\n\n## Rules of thumb\n\n- If the thing mainly decides the next step, it is probably Layer 4.\n- If it mainly hosts state, tools, approvals, and streaming around that loop, it is probably Layer 5.\n- If it mainly manages installed extensions, channels, marketplaces, and launch contracts, it is probably Layer 6.\n- If a product depends on an IDE, shell, or cloud control plane for workspace or execution, those layers still exist even when they are delegated.\n- If the product is strongest when embedded into someone else's app, it probably does not own Layers 7-11.\n- If the product feels complete because it can edit files and run commands, inspect Layers 7-9 carefully rather than assuming the entire stack.\n\n## What not to do\n\n- Do not force one product into all 11 layers just because it offers a polished experience.\n- Do not collapse runtime and platform into one bucket when extension systems matter.\n- Do not classify \"custom agent building\" as presentation just because the first touchpoint is a visual editor.\n- Do not confuse hosted operation with model ownership. A hosted platform may still delegate Layers 1-3.\n\n## Next pages\n\n- Read [`04-worked-examples.md`](./04-worked-examples.md) for concrete placements.\n- Read [`05-common-confusions.md`](./05-common-confusions.md) if the terminology still feels slippery.\n",
    "documents": [
      "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-builder-fit",
      "to": "layer:3-transport",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-builder-fit",
      "to": "layer:4-agent-core",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-builder-fit",
      "to": "layer:5-agent-runtime",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-builder-fit",
      "to": "layer:6-agent-platform",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-builder-fit",
      "to": "layer:7-workspace",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-builder-fit",
      "to": "layer:8-execution",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-builder-fit",
      "to": "layer:9-sandbox",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-builder-fit",
      "to": "layer:10-interaction",
      "kind": "documents"
    },
    {
      "from": "page:agent-generate-universal-agentic-stack-builder-fit",
      "to": "layer:11-presentation",
      "kind": "documents"
    }
  ],
  "incomingEdges": [
    {
      "from": "page:agent-generate-universal-agentic-stack",
      "to": "page:agent-generate-universal-agentic-stack-builder-fit",
      "kind": "contains_page"
    }
  ]
}

Shortcuts

Back to overview
Open graph tab