{
  "schema_version": "1.1",
  "id": "s8:https://www.youtube.com/watch?v=32nrHU6zHU8",
  "slug": "agents-are-where-microservices-were-in-2015-roberto-milev-uday-kanagala-1pk4hle",
  "url": "https://feed7.dev/p/agents-are-where-microservices-were-in-2015-roberto-milev-uday-kanagala-1pk4hle",
  "title": "Agents Are Where Microservices Were in 2015 — Roberto Milev & Uday Kanagala, Navan",
  "why_included": "Navan treats production agents as stateful services needing persistence, composable skills, traces, authorization gates, and trajectory-based tests before multi-agent complexity.",
  "summary": "Navan’s emerging stack covers runtime, memory, context, operations, and orchestration. It persists and rehydrates sessions, composes context from independently testable **skills**, and places guardrails **before and after every tool call**.",
  "practical_implication": "Start with one reliable agent and progressively load domain skills instead of defaulting to a multi-agent graph. Capture goals, tool calls, inferred answers, and execution trajectories so failures can become test cases and policy changes.",
  "agent_context": "Navan’s emerging stack covers runtime, memory, context, operations, and orchestration. It persists and rehydrates sessions, composes context from independently testable **skills**, and places guardrails **before and after every tool call**.\n\nStart with one reliable agent and progressively load domain skills instead of defaulting to a multi-agent graph. Capture goals, tool calls, inferred answers, and execution trajectories so failures can become test cases and policy changes.\n\nCloud runtimes and tool protocols are converging, but cost prediction, replay, agent observability, and orchestration remain unsettled. Navan’s single-master pattern reflects its use cases rather than a universal architecture.",
  "source": {
    "name": "AI Engineer",
    "url": "https://www.youtube.com/watch?v=32nrHU6zHU8",
    "published_at": "2026-08-29T16:30:28.000Z"
  },
  "source_class": "video",
  "content_type": "Video",
  "layer": "agent",
  "domains": [
    "coding"
  ],
  "topics": [
    "harness-engineering",
    "skills",
    "agent-reliability"
  ],
  "verification": {
    "status": "source_linked",
    "label": "Source Linked",
    "method": "source_feed",
    "verified_at": null
  },
  "uncertainty": [
    "Cloud runtimes and tool protocols are converging, but cost prediction, replay, agent observability, and orchestration remain unsettled. Navan’s single-master pattern reflects its use cases rather than a universal architecture."
  ],
  "connected_context": {
    "meaning": "This reinforces a single-agent-first architecture in which independently testable skills, persistent sessions, tool-boundary guardrails, and captured trajectories form the operating stack. It makes multi-agent orchestration an earned escalation rather than a default, while leaving replay, observability, and cost prediction open. The pattern is credible as Navan’s implementation choice but not established as universal.",
    "corpus_size": 669,
    "generated_at": "2026-09-03T10:01:24.920Z",
    "connections": [
      {
        "title": "SafeEvolve: Harness-Policy Co-Evolution from Agent Experience for Safety Alignment",
        "source_name": "arXiv",
        "source_url": "https://arxiv.org/abs/2609.02786v1",
        "feed7_url": "https://feed7.dev/p/2609-02786v1-0eo17gt",
        "reason": "Navan proposes turning captured failures into tests and policy changes; SafeEvolve supplies a more explicit mechanism for deriving reversible harness updates and policy training from those trajectories."
      },
      {
        "title": "Tribal Dungeons of Global Shipping: AI Agents at Global Scale — Dmitry Buykin, Maersk",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=dQ-_i1tZiws",
        "feed7_url": "https://feed7.dev/p/tribal-dungeons-of-global-shipping-ai-agents-at-global-scale-dmitry-buyk-0kcigeh",
        "reason": "Maersk provides large-scale operating evidence for Navan’s emphasis on bounded tools, replayable trajectories, and continuously maintained procedures, while exposing the expert labor such a stack can still require."
      },
      {
        "title": "The Era of Compound Engineering — Kieran Klaassen, Every/Cora",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=_ehJyfHg1Vk",
        "feed7_url": "https://feed7.dev/p/the-era-of-compound-engineering-kieran-klaassen-every-cora-053chml",
        "reason": "Both treat reviewed experience as reusable infrastructure: Navan captures trajectories and composes testable skills, while compound engineering stresses that corrections and judgments must be curated into context for later runs."
      },
      {
        "title": "Don't Build Agents You Can't Answer For — Addy Osmani",
        "source_name": "YouTube",
        "source_url": "https://www.youtube.com/watch?v=n97BCfyFIvw",
        "feed7_url": "https://feed7.dev/p/don-t-build-agents-you-can-t-answer-for-addy-osmani-1y9nwej",
        "reason": "Navan’s capture of goals, calls, inferred answers, and trajectories supplies the evidence base needed for the candidate’s requirement that agent work remain explainable, testable, and owned before shipping."
      }
    ]
  },
  "lifecycle": "Current",
  "published_at": "2026-08-29T16:30:28.000Z",
  "modified_at": "2026-08-29T16:30:28.000Z",
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/agents-are-where-microservices-were-in-2015-roberto-milev-uday-kanagala-1pk4hle",
    "json": "https://feed7.dev/p/agents-are-where-microservices-were-in-2015-roberto-milev-uday-kanagala-1pk4hle.json",
    "markdown": "https://feed7.dev/p/agents-are-where-microservices-were-in-2015-roberto-milev-uday-kanagala-1pk4hle.md"
  }
}