<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:news="http://www.google.com/schemas/sitemap-news/0.9">
  <url>
    <loc>https://samtaelabs.com/blog/ai-agent-code-execution-isolation-boundary-requirements</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-10-13T03:00:28.235Z</news:publication_date>
      <news:title>AI 에이전트에게 코드 실행 권한을 줄 때, 격리 수준을 요구사항으로 적어야 하는 이유</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://samtaelabs.com/blog/geo-ontology-first-before-content-production</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-10-12T22:30:03.670Z</news:publication_date>
      <news:title>GEO 프로젝트, 콘텐츠 캘린더보다 온톨로지 설계가 먼저여야 하는 이유</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://samtaelabs.com/blog/multi-agent-message-channel-design-requirements</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-10-12T12:30:36.351Z</news:publication_date>
      <news:title>다중 에이전트 시스템 도입 실패의 숨겨진 원인: 메시지 채널 설계를 요구사항 단계에서 분리해야 하는 이유</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://samtaelabs.com/blog/coding-agent-evaluation-framework-before-vendor-selection</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-10-12T03:00:28.228Z</news:publication_date>
      <news:title>코딩 에이전트 도입이 멈추는 이유는 모델 성능이 아니다: 벤더 선정 전에 먼저 정해야 할 것들</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://samtaelabs.com/blog/llm-adoption-decision-vs-alternatives</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-10-11T22:30:03.349Z</news:publication_date>
      <news:title>LLM이 꼭 필요한 기술처럼 느껴질 때, 그 느낌을 검증하는 방법</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://samtaelabs.com/blog/ai-agent-token-budget-orchestration-requirements-phase</loc>
    <news:news>
      <news:publication>
        <news:name>삼태연구소</news:name>
        <news:language>ko</news:language>
      </news:publication>
      <news:publication_date>2026-10-11T12:30:36.461Z</news:publication_date>
      <news:title>AI 에이전트 대규모 투입 전, 요구사항 단계에서 정의하지 않으면 반드시 터지는 세 가지 비용 구조</news:title>
    </news:news>
  </url>
</urlset>