sber/agent

Fork 0

Files

T

alex 8fb76bb331 фиксирую состояние

2026-04-07 21:41:27 +03:00

36 KiB

Raw Blame History

Runtime Trace: 20260407-182058-3f56c69c7290

active_rag_session_id: c8b893cc-cb13-4493-a6d1-3f56c69c7290

request

{
  "request_id": "req_bab9c8812ac94847bb102cba68516f10",
  "session_id": "as_4fdccc9c55c549faad8f3ef379371129",
  "active_rag_session_id": "c8b893cc-cb13-4493-a6d1-3f56c69c7290",
  "process_version": "v2",
  "created_at": "2026-04-07T18:20:58.679614+00:00",
  "message": "Как работает метод health?"
}

process.v2

{
  "event": "intent_routed",
  "routing_domain": "DOCS",
  "intent": "DOC_EXPLAIN",
  "subintent": "SUMMARY",
  "normalized_query": "Как работает метод health?",
  "target_terms": [
    "метод",
    "health"
  ],
  "anchors": {
    "entity_names": [],
    "file_names": [],
    "endpoint_paths": [],
    "target_doc_hints": [],
    "matched_aliases": [],
    "process_domain": null,
    "process_subdomain": null,
    "signal_types": []
  },
  "confidence": 0.75,
  "routing_mode": "llm_default",
  "llm_router_used": true,
  "reason_short": "Запрос на понимание работы конкретного метода \"health\".",
  "rag_session_id": "c8b893cc-cb13-4493-a6d1-3f56c69c7290"
}

process.v2.pipeline

{
  "event": "router_resolved",
  "domain": "DOCS",
  "intent": "DOC_EXPLAIN",
  "subintent": "SUMMARY",
  "confidence": 0.75
}

process.v2.pipeline

{
  "event": "anchors_extracted",
  "signal_types": [],
  "endpoint_paths": [],
  "target_doc_hints": [],
  "matched_aliases": [],
  "target_terms": [
    "метод",
    "health"
  ]
}

process.v2.pipeline

{
  "event": "alias_resolution",
  "resolved_aliases": [],
  "target_doc_hints": []
}

process.v2.retrieval_policy

{
  "event": "retrieval_plan_resolved",
  "profile": "docs_summary_generic",
  "layers": [
    "D1_DOCUMENT_CATALOG",
    "D0_DOC_CHUNKS"
  ],
  "limit": 8,
  "filters": {
    "target_doc_hints": [],
    "prefer_path_prefixes": [
      "docs/"
    ],
    "prefer_like_patterns": []
  }
}

process.v2.pipeline

{
  "event": "retrieval_profile_selected",
  "profile": "docs_summary_generic",
  "layers": [
    "D1_DOCUMENT_CATALOG",
    "D0_DOC_CHUNKS"
  ],
  "filters": {
    "target_doc_hints": [],
    "prefer_path_prefixes": [
      "docs/"
    ],
    "prefer_like_patterns": []
  }
}

process.v2.rag_retrieval

{
  "event": "rag_rows_fetched",
  "profile": "docs_summary_generic",
  "row_count": 8,
  "rows": [
    {
      "layer": "D1_DOCUMENT_CATALOG",
      "path": "docs/architecture/telegram-notify-app-overview.md",
      "title": "Архитектура Telegram Notify App",
      "document_id": "architecture.telegram_notify_app",
      "entity_name": "",
      "summary_text": "- Purpose: сервис поднимает HTTP control plane и фоновый worker для отправки уведомлений в Telegram.\n- Entry point: `src/telegram_notify_app/main.py`.\n- Main components: `RuntimeManager`, `TelegramControlChannel`, `TelegramNotifyModule`, `TelegramNotifyWorker`, `TelegramSendService`.\n- Configuration: `config/config.yaml` или путь из `CONFIG_PATH`.\n- Related API: [`/health`](../api/health-endpoint.",
      "section_path": "",
      "content_preview": "- Purpose: сервис поднимает HTTP control plane и фоновый worker для отправки уведомлений в Telegram.\n- Entry point: `src/telegram_notify_app/main.py`.\n- Main components: `RuntimeManager`, `TelegramControlChannel`, `TelegramNotifyModule`, `TelegramNotifyWorker`, `TelegramSendService`.\n- Configuration: `config/config.yaml` или путь из `CONFIG_PATH`.\n- Related API: [`/health`](../api/health-endpoint."
    },
    {
      "layer": "D1_DOCUMENT_CATALOG",
      "path": "docs/README.md",
      "title": "Индекс технической документации test_echo_app",
      "document_id": "index.test_echo_app_docs",
      "entity_name": "",
      "summary_text": "- Purpose: точка входа в техническую документацию сервиса `test_echo_app`.\n- Scope: архитектура, HTTP API control plane, цикл отправки уведомлений, health-модель и каталог ошибок.\n- Canonical structure: `docs/architecture`, `docs/api`, `docs/logic`, `docs/domains`, `docs/errors`.\n- Primary parent doc: [Архитектура Telegram Notify App](./architecture/telegram-notify-app-overview.md).\n- Navigation: ",
      "section_path": "",
      "content_preview": "- Purpose: точка входа в техническую документацию сервиса `test_echo_app`.\n- Scope: архитектура, HTTP API control plane, цикл отправки уведомлений, health-модель и каталог ошибок.\n- Canonical structure: `docs/architecture`, `docs/api`, `docs/logic`, `docs/domains`, `docs/errors`.\n- Primary parent doc: [Архитектура Telegram Notify App](./architecture/telegram-notify-app-overview.md).\n- Navigation: "
    },
    {
      "layer": "D0_DOC_CHUNKS",
      "path": "docs/architecture/telegram-notify-app-overview.md",
      "title": "architecture.telegram_notify_app:Операторские и мониторинговые клиенты",
      "document_id": "architecture.telegram_notify_app",
      "entity_name": "",
      "summary_text": "",
      "section_path": "Архитектура Telegram Notify App > Details > Интеграции > Операторские и мониторинговые клиенты",
      "content_preview": "- target: ext.operator_and_probes\n- target_type: external_system\n- direction: inbound\n- interaction: calls\n- via: HTTP `/health`, `/actions/{action}`, `/send`\n- purpose: диагностика, lifecycle-управление и ручная отправка сообщений\n- details:\n  - transport: FastAPI + UvicornThreadRunner\n  - status_mapping: non-ok health -> HTTP 503"
    },
    {
      "layer": "D0_DOC_CHUNKS",
      "path": "docs/architecture/telegram-notify-app-overview.md",
      "title": "architecture.telegram_notify_app:Связанные документы",
      "document_id": "architecture.telegram_notify_app",
      "entity_name": "",
      "summary_text": "",
      "section_path": "Архитектура Telegram Notify App > Details > Связанные документы",
      "content_preview": "- [API /health](../api/health-endpoint.md)\n- [API /actions/{action}](../api/control-actions-endpoint.md)\n- [API /send](../api/send-message-endpoint.md)\n- [Логика цикла отправки уведомлений](../logic/telegram-notification-loop.md)\n- [Доменная модель runtime health](../domains/runtime-health-entity.md)"
    },
    {
      "layer": "D0_DOC_CHUNKS",
      "path": "docs/README.md",
      "title": "index.test_echo_app_docs:Навигация",
      "document_id": "index.test_echo_app_docs",
      "entity_name": "",
      "summary_text": "",
      "section_path": "Индекс технической документации test_echo_app > Details > Навигация",
      "content_preview": "- [Архитектура Telegram Notify App](./architecture/telegram-notify-app-overview.md)\n- [API /health](./api/health-endpoint.md)\n- [API /actions/{action}](./api/control-actions-endpoint.md)\n- [API /send](./api/send-message-endpoint.md)\n- [Логика цикла отправки уведомлений](./logic/telegram-notification-loop.md)\n- [Доменная модель runtime health](./domains/runtime-health-entity.md)\n- [Каталог ошибок]("
    },
    {
      "layer": "D0_DOC_CHUNKS",
      "path": "docs/architecture/telegram-notify-app-overview.md",
      "title": "architecture.telegram_notify_app:Summary",
      "document_id": "architecture.telegram_notify_app",
      "entity_name": "",
      "summary_text": "",
      "section_path": "Архитектура Telegram Notify App > Summary",
      "content_preview": "- Purpose: сервис поднимает HTTP control plane и фоновый worker для отправки уведомлений в Telegram.\n- Entry point: `src/telegram_notify_app/main.py`.\n- Main components: `RuntimeManager`, `TelegramControlChannel`, `TelegramNotifyModule`, `TelegramNotifyWorker`, `TelegramSendService`.\n- Configuration: `config/config.yaml` или путь из `CONFIG_PATH`.\n- Related API: [`/health`](../api/health-endpoint."
    },
    {
      "layer": "D0_DOC_CHUNKS",
      "path": "docs/README.md",
      "title": "index.test_echo_app_docs:Summary",
      "document_id": "index.test_echo_app_docs",
      "entity_name": "",
      "summary_text": "",
      "section_path": "Индекс технической документации test_echo_app > Summary",
      "content_preview": "- Purpose: точка входа в техническую документацию сервиса `test_echo_app`.\n- Scope: архитектура, HTTP API control plane, цикл отправки уведомлений, health-модель и каталог ошибок.\n- Canonical structure: `docs/architecture`, `docs/api`, `docs/logic`, `docs/domains`, `docs/errors`.\n- Primary parent doc: [Архитектура Telegram Notify App](./architecture/telegram-notify-app-overview.md).\n- Navigation: "
    },
    {
      "layer": "D0_DOC_CHUNKS",
      "path": "docs/architecture/telegram-notify-app-overview.md",
      "title": "architecture.telegram_notify_app:Интеграционные сценарии",
      "document_id": "architecture.telegram_notify_app",
      "entity_name": "",
      "summary_text": "",
      "section_path": "Архитектура Telegram Notify App > Details > Интеграционные сценарии",
      "content_preview": "1. При старте `main()` загружает YAML-конфиг, извлекает host, port и интервал отправки, затем собирает runtime.\n2. `RuntimeManager` регистрирует `TelegramControlChannel` для HTTP control plane.\n3. `TelegramNotifyModule` добавляет `TelegramNotifyWorker` и `TelegramSendService` в runtime.\n4. Внешний клиент вызывает endpoint'ы control plane для health-check, lifecycle-операций или ручной отправки.\n5."
    }
  ]
}

process.v2.pipeline

{
  "event": "candidate_generation",
  "query": "Как работает метод health?",
  "profile": "docs_summary_generic",
  "details": {
    "target_doc_hints": [],
    "candidates_before_ranking": [
      "docs/architecture/telegram-notify-app-overview.md",
      "docs/README.md",
      "docs/architecture/telegram-notify-app-overview.md",
      "docs/architecture/telegram-notify-app-overview.md",
      "docs/README.md",
      "docs/architecture/telegram-notify-app-overview.md",
      "docs/README.md",
      "docs/architecture/telegram-notify-app-overview.md"
    ]
  },
  "resolved_aliases": [],
  "target_doc_hints": [],
  "candidate_docs_before_ranking": [
    {
      "layer": "D1_DOCUMENT_CATALOG",
      "path": "docs/architecture/telegram-notify-app-overview.md",
      "title": "Архитектура Telegram Notify App",
      "document_id": "architecture.telegram_notify_app",
      "entity_name": "",
      "summary_text": "- Purpose: сервис поднимает HTTP control plane и фоновый worker для отправки уведомлений в Telegram.\n- Entry point: `src/telegram_notify_app/main.py`.\n- Main components: `RuntimeManager`, `TelegramControlChannel`, `TelegramNotifyModule`, `TelegramNotifyWorker`, `TelegramSendService`.\n- Configuration: `config/config.yaml` или путь из `CONFIG_PATH`.\n- Related API: [`/health`](../api/health-endpoint.",
      "section_path": "",
      "content_preview": "- Purpose: сервис поднимает HTTP control plane и фоновый worker для отправки уведомлений в Telegram.\n- Entry point: `src/telegram_notify_app/main.py`.\n- Main components: `RuntimeManager`, `TelegramControlChannel`, `TelegramNotifyModule`, `TelegramNotifyWorker`, `TelegramSendService`.\n- Configuration: `config/config.yaml` или путь из `CONFIG_PATH`.\n- Related API: [`/health`](../api/health-endpoint."
    },
    {
      "layer": "D1_DOCUMENT_CATALOG",
      "path": "docs/README.md",
      "title": "Индекс технической документации test_echo_app",
      "document_id": "index.test_echo_app_docs",
      "entity_name": "",
      "summary_text": "- Purpose: точка входа в техническую документацию сервиса `test_echo_app`.\n- Scope: архитектура, HTTP API control plane, цикл отправки уведомлений, health-модель и каталог ошибок.\n- Canonical structure: `docs/architecture`, `docs/api`, `docs/logic`, `docs/domains`, `docs/errors`.\n- Primary parent doc: [Архитектура Telegram Notify App](./architecture/telegram-notify-app-overview.md).\n- Navigation: ",
      "section_path": "",
      "content_preview": "- Purpose: точка входа в техническую документацию сервиса `test_echo_app`.\n- Scope: архитектура, HTTP API control plane, цикл отправки уведомлений, health-модель и каталог ошибок.\n- Canonical structure: `docs/architecture`, `docs/api`, `docs/logic`, `docs/domains`, `docs/errors`.\n- Primary parent doc: [Архитектура Telegram Notify App](./architecture/telegram-notify-app-overview.md).\n- Navigation: "
    },
    {
      "layer": "D0_DOC_CHUNKS",
      "path": "docs/architecture/telegram-notify-app-overview.md",
      "title": "architecture.telegram_notify_app:Операторские и мониторинговые клиенты",
      "document_id": "architecture.telegram_notify_app",
      "entity_name": "",
      "summary_text": "",
      "section_path": "Архитектура Telegram Notify App > Details > Интеграции > Операторские и мониторинговые клиенты",
      "content_preview": "- target: ext.operator_and_probes\n- target_type: external_system\n- direction: inbound\n- interaction: calls\n- via: HTTP `/health`, `/actions/{action}`, `/send`\n- purpose: диагностика, lifecycle-управление и ручная отправка сообщений\n- details:\n  - transport: FastAPI + UvicornThreadRunner\n  - status_mapping: non-ok health -> HTTP 503"
    },
    {
      "layer": "D0_DOC_CHUNKS",
      "path": "docs/architecture/telegram-notify-app-overview.md",
      "title": "architecture.telegram_notify_app:Связанные документы",
      "document_id": "architecture.telegram_notify_app",
      "entity_name": "",
      "summary_text": "",
      "section_path": "Архитектура Telegram Notify App > Details > Связанные документы",
      "content_preview": "- [API /health](../api/health-endpoint.md)\n- [API /actions/{action}](../api/control-actions-endpoint.md)\n- [API /send](../api/send-message-endpoint.md)\n- [Логика цикла отправки уведомлений](../logic/telegram-notification-loop.md)\n- [Доменная модель runtime health](../domains/runtime-health-entity.md)"
    },
    {
      "layer": "D0_DOC_CHUNKS",
      "path": "docs/README.md",
      "title": "index.test_echo_app_docs:Навигация",
      "document_id": "index.test_echo_app_docs",
      "entity_name": "",
      "summary_text": "",
      "section_path": "Индекс технической документации test_echo_app > Details > Навигация",
      "content_preview": "- [Архитектура Telegram Notify App](./architecture/telegram-notify-app-overview.md)\n- [API /health](./api/health-endpoint.md)\n- [API /actions/{action}](./api/control-actions-endpoint.md)\n- [API /send](./api/send-message-endpoint.md)\n- [Логика цикла отправки уведомлений](./logic/telegram-notification-loop.md)\n- [Доменная модель runtime health](./domains/runtime-health-entity.md)\n- [Каталог ошибок]("
    },
    {
      "layer": "D0_DOC_CHUNKS",
      "path": "docs/architecture/telegram-notify-app-overview.md",
      "title": "architecture.telegram_notify_app:Summary",
      "document_id": "architecture.telegram_notify_app",
      "entity_name": "",
      "summary_text": "",
      "section_path": "Архитектура Telegram Notify App > Summary",
      "content_preview": "- Purpose: сервис поднимает HTTP control plane и фоновый worker для отправки уведомлений в Telegram.\n- Entry point: `src/telegram_notify_app/main.py`.\n- Main components: `RuntimeManager`, `TelegramControlChannel`, `TelegramNotifyModule`, `TelegramNotifyWorker`, `TelegramSendService`.\n- Configuration: `config/config.yaml` или путь из `CONFIG_PATH`.\n- Related API: [`/health`](../api/health-endpoint."
    },
    {
      "layer": "D0_DOC_CHUNKS",
      "path": "docs/README.md",
      "title": "index.test_echo_app_docs:Summary",
      "document_id": "index.test_echo_app_docs",
      "entity_name": "",
      "summary_text": "",
      "section_path": "Индекс технической документации test_echo_app > Summary",
      "content_preview": "- Purpose: точка входа в техническую документацию сервиса `test_echo_app`.\n- Scope: архитектура, HTTP API control plane, цикл отправки уведомлений, health-модель и каталог ошибок.\n- Canonical structure: `docs/architecture`, `docs/api`, `docs/logic`, `docs/domains`, `docs/errors`.\n- Primary parent doc: [Архитектура Telegram Notify App](./architecture/telegram-notify-app-overview.md).\n- Navigation: "
    },
    {
      "layer": "D0_DOC_CHUNKS",
      "path": "docs/architecture/telegram-notify-app-overview.md",
      "title": "architecture.telegram_notify_app:Интеграционные сценарии",
      "document_id": "architecture.telegram_notify_app",
      "entity_name": "",
      "summary_text": "",
      "section_path": "Архитектура Telegram Notify App > Details > Интеграционные сценарии",
      "content_preview": "1. При старте `main()` загружает YAML-конфиг, извлекает host, port и интервал отправки, затем собирает runtime.\n2. `RuntimeManager` регистрирует `TelegramControlChannel` для HTTP control plane.\n3. `TelegramNotifyModule` добавляет `TelegramNotifyWorker` и `TelegramSendService` в runtime.\n4. Внешний клиент вызывает endpoint'ы control plane для health-check, lifecycle-операций или ручной отправки.\n5."
    }
  ],
  "sources": {
    "seeded": [],
    "metadata_lookup": [],
    "semantic": [
      {
        "layer": "D1_DOCUMENT_CATALOG",
        "path": "docs/architecture/telegram-notify-app-overview.md",
        "title": "Архитектура Telegram Notify App",
        "document_id": "architecture.telegram_notify_app",
        "entity_name": "",
        "summary_text": "- Purpose: сервис поднимает HTTP control plane и фоновый worker для отправки уведомлений в Telegram.\n- Entry point: `src/telegram_notify_app/main.py`.\n- Main components: `RuntimeManager`, `TelegramControlChannel`, `TelegramNotifyModule`, `TelegramNotifyWorker`, `TelegramSendService`.\n- Configuration: `config/config.yaml` или путь из `CONFIG_PATH`.\n- Related API: [`/health`](../api/health-endpoint.",
        "section_path": "",
        "content_preview": "- Purpose: сервис поднимает HTTP control plane и фоновый worker для отправки уведомлений в Telegram.\n- Entry point: `src/telegram_notify_app/main.py`.\n- Main components: `RuntimeManager`, `TelegramControlChannel`, `TelegramNotifyModule`, `TelegramNotifyWorker`, `TelegramSendService`.\n- Configuration: `config/config.yaml` или путь из `CONFIG_PATH`.\n- Related API: [`/health`](../api/health-endpoint."
      },
      {
        "layer": "D1_DOCUMENT_CATALOG",
        "path": "docs/README.md",
        "title": "Индекс технической документации test_echo_app",
        "document_id": "index.test_echo_app_docs",
        "entity_name": "",
        "summary_text": "- Purpose: точка входа в техническую документацию сервиса `test_echo_app`.\n- Scope: архитектура, HTTP API control plane, цикл отправки уведомлений, health-модель и каталог ошибок.\n- Canonical structure: `docs/architecture`, `docs/api`, `docs/logic`, `docs/domains`, `docs/errors`.\n- Primary parent doc: [Архитектура Telegram Notify App](./architecture/telegram-notify-app-overview.md).\n- Navigation: ",
        "section_path": "",
        "content_preview": "- Purpose: точка входа в техническую документацию сервиса `test_echo_app`.\n- Scope: архитектура, HTTP API control plane, цикл отправки уведомлений, health-модель и каталог ошибок.\n- Canonical structure: `docs/architecture`, `docs/api`, `docs/logic`, `docs/domains`, `docs/errors`.\n- Primary parent doc: [Архитектура Telegram Notify App](./architecture/telegram-notify-app-overview.md).\n- Navigation: "
      },
      {
        "layer": "D0_DOC_CHUNKS",
        "path": "docs/architecture/telegram-notify-app-overview.md",
        "title": "architecture.telegram_notify_app:Операторские и мониторинговые клиенты",
        "document_id": "architecture.telegram_notify_app",
        "entity_name": "",
        "summary_text": "",
        "section_path": "Архитектура Telegram Notify App > Details > Интеграции > Операторские и мониторинговые клиенты",
        "content_preview": "- target: ext.operator_and_probes\n- target_type: external_system\n- direction: inbound\n- interaction: calls\n- via: HTTP `/health`, `/actions/{action}`, `/send`\n- purpose: диагностика, lifecycle-управление и ручная отправка сообщений\n- details:\n  - transport: FastAPI + UvicornThreadRunner\n  - status_mapping: non-ok health -> HTTP 503"
      },
      {
        "layer": "D0_DOC_CHUNKS",
        "path": "docs/architecture/telegram-notify-app-overview.md",
        "title": "architecture.telegram_notify_app:Связанные документы",
        "document_id": "architecture.telegram_notify_app",
        "entity_name": "",
        "summary_text": "",
        "section_path": "Архитектура Telegram Notify App > Details > Связанные документы",
        "content_preview": "- [API /health](../api/health-endpoint.md)\n- [API /actions/{action}](../api/control-actions-endpoint.md)\n- [API /send](../api/send-message-endpoint.md)\n- [Логика цикла отправки уведомлений](../logic/telegram-notification-loop.md)\n- [Доменная модель runtime health](../domains/runtime-health-entity.md)"
      },
      {
        "layer": "D0_DOC_CHUNKS",
        "path": "docs/README.md",
        "title": "index.test_echo_app_docs:Навигация",
        "document_id": "index.test_echo_app_docs",
        "entity_name": "",
        "summary_text": "",
        "section_path": "Индекс технической документации test_echo_app > Details > Навигация",
        "content_preview": "- [Архитектура Telegram Notify App](./architecture/telegram-notify-app-overview.md)\n- [API /health](./api/health-endpoint.md)\n- [API /actions/{action}](./api/control-actions-endpoint.md)\n- [API /send](./api/send-message-endpoint.md)\n- [Логика цикла отправки уведомлений](./logic/telegram-notification-loop.md)\n- [Доменная модель runtime health](./domains/runtime-health-entity.md)\n- [Каталог ошибок]("
      }
    ]
  }
}

process.v2.pipeline

{
  "event": "retrieval_executed",
  "query": "Как работает метод health?",
  "profile": "docs_summary_generic",
  "row_count": 8,
  "target_doc_hints": [],
  "top_results": [
    {
      "layer": "D1_DOCUMENT_CATALOG",
      "path": "docs/architecture/telegram-notify-app-overview.md",
      "title": "Архитектура Telegram Notify App",
      "document_id": "architecture.telegram_notify_app",
      "entity_name": "",
      "summary_text": "- Purpose: сервис поднимает HTTP control plane и фоновый worker для отправки уведомлений в Telegram.\n- Entry point: `src/telegram_notify_app/main.py`.\n- Main components: `RuntimeManager`, `TelegramControlChannel`, `TelegramNotifyModule`, `TelegramNotifyWorker`, `TelegramSendService`.\n- Configuration: `config/config.yaml` или путь из `CONFIG_PATH`.\n- Related API: [`/health`](../api/health-endpoint.",
      "section_path": "",
      "content_preview": "- Purpose: сервис поднимает HTTP control plane и фоновый worker для отправки уведомлений в Telegram.\n- Entry point: `src/telegram_notify_app/main.py`.\n- Main components: `RuntimeManager`, `TelegramControlChannel`, `TelegramNotifyModule`, `TelegramNotifyWorker`, `TelegramSendService`.\n- Configuration: `config/config.yaml` или путь из `CONFIG_PATH`.\n- Related API: [`/health`](../api/health-endpoint."
    },
    {
      "layer": "D1_DOCUMENT_CATALOG",
      "path": "docs/README.md",
      "title": "Индекс технической документации test_echo_app",
      "document_id": "index.test_echo_app_docs",
      "entity_name": "",
      "summary_text": "- Purpose: точка входа в техническую документацию сервиса `test_echo_app`.\n- Scope: архитектура, HTTP API control plane, цикл отправки уведомлений, health-модель и каталог ошибок.\n- Canonical structure: `docs/architecture`, `docs/api`, `docs/logic`, `docs/domains`, `docs/errors`.\n- Primary parent doc: [Архитектура Telegram Notify App](./architecture/telegram-notify-app-overview.md).\n- Navigation: ",
      "section_path": "",
      "content_preview": "- Purpose: точка входа в техническую документацию сервиса `test_echo_app`.\n- Scope: архитектура, HTTP API control plane, цикл отправки уведомлений, health-модель и каталог ошибок.\n- Canonical structure: `docs/architecture`, `docs/api`, `docs/logic`, `docs/domains`, `docs/errors`.\n- Primary parent doc: [Архитектура Telegram Notify App](./architecture/telegram-notify-app-overview.md).\n- Navigation: "
    },
    {
      "layer": "D0_DOC_CHUNKS",
      "path": "docs/architecture/telegram-notify-app-overview.md",
      "title": "architecture.telegram_notify_app:Операторские и мониторинговые клиенты",
      "document_id": "architecture.telegram_notify_app",
      "entity_name": "",
      "summary_text": "",
      "section_path": "Архитектура Telegram Notify App > Details > Интеграции > Операторские и мониторинговые клиенты",
      "content_preview": "- target: ext.operator_and_probes\n- target_type: external_system\n- direction: inbound\n- interaction: calls\n- via: HTTP `/health`, `/actions/{action}`, `/send`\n- purpose: диагностика, lifecycle-управление и ручная отправка сообщений\n- details:\n  - transport: FastAPI + UvicornThreadRunner\n  - status_mapping: non-ok health -> HTTP 503"
    },
    {
      "layer": "D0_DOC_CHUNKS",
      "path": "docs/architecture/telegram-notify-app-overview.md",
      "title": "architecture.telegram_notify_app:Связанные документы",
      "document_id": "architecture.telegram_notify_app",
      "entity_name": "",
      "summary_text": "",
      "section_path": "Архитектура Telegram Notify App > Details > Связанные документы",
      "content_preview": "- [API /health](../api/health-endpoint.md)\n- [API /actions/{action}](../api/control-actions-endpoint.md)\n- [API /send](../api/send-message-endpoint.md)\n- [Логика цикла отправки уведомлений](../logic/telegram-notification-loop.md)\n- [Доменная модель runtime health](../domains/runtime-health-entity.md)"
    },
    {
      "layer": "D0_DOC_CHUNKS",
      "path": "docs/README.md",
      "title": "index.test_echo_app_docs:Навигация",
      "document_id": "index.test_echo_app_docs",
      "entity_name": "",
      "summary_text": "",
      "section_path": "Индекс технической документации test_echo_app > Details > Навигация",
      "content_preview": "- [Архитектура Telegram Notify App](./architecture/telegram-notify-app-overview.md)\n- [API /health](./api/health-endpoint.md)\n- [API /actions/{action}](./api/control-actions-endpoint.md)\n- [API /send](./api/send-message-endpoint.md)\n- [Логика цикла отправки уведомлений](./logic/telegram-notification-loop.md)\n- [Доменная модель runtime health](./domains/runtime-health-entity.md)\n- [Каталог ошибок]("
    }
  ]
}

process.v2.evidence

{
  "event": "evidence_assembled",
  "mode": "summary",
  "document_count": 2,
  "documents": [
    "docs/README.md",
    "docs/architecture/telegram-notify-app-overview.md"
  ]
}

process.v2.pipeline

{
  "event": "evidence_assembled",
  "mode": "summary",
  "primary_doc": "docs/README.md",
  "document_count": 2
}

process.v2.pipeline

{
  "event": "ranking_explained",
  "doc": "docs/README.md",
  "score_breakdown": {
    "semantic": 20,
    "path_match": 0,
    "filename_match": 0,
    "alias_match": 0,
    "anchor_boost": 0,
    "target_doc_boost": 0,
    "generic_penalty": 0
  },
  "score": 20,
  "match_reason": "semantic_match"
}

process.v2.pipeline

{
  "event": "ranking_explained",
  "doc": "docs/architecture/telegram-notify-app-overview.md",
  "score_breakdown": {
    "semantic": 20,
    "path_match": 0,
    "filename_match": 0,
    "alias_match": 0,
    "anchor_boost": 0,
    "target_doc_boost": 0,
    "generic_penalty": 0
  },
  "score": 20,
  "match_reason": "semantic_match"
}

process.v2.pipeline

{
  "event": "ranking_explained",
  "top_docs_after_ranking": [
    {
      "doc": "docs/README.md",
      "score": 20,
      "match_reason": "semantic_match"
    },
    {
      "doc": "docs/architecture/telegram-notify-app-overview.md",
      "score": 20,
      "match_reason": "semantic_match"
    }
  ],
  "ranking_score_breakdown": [
    {
      "doc": "docs/README.md",
      "score_breakdown": {
        "semantic": 20,
        "path_match": 0,
        "filename_match": 0,
        "alias_match": 0,
        "anchor_boost": 0,
        "target_doc_boost": 0,
        "generic_penalty": 0
      }
    },
    {
      "doc": "docs/architecture/telegram-notify-app-overview.md",
      "score_breakdown": {
        "semantic": 20,
        "path_match": 0,
        "filename_match": 0,
        "alias_match": 0,
        "anchor_boost": 0,
        "target_doc_boost": 0,
        "generic_penalty": 0
      }
    }
  ]
}

process.v2.pipeline

{
  "event": "evidence_gate_checked",
  "passed": true,
  "reason": "target_doc_found",
  "answer_mode": "grounded_summary"
}

workflow.v2.summary

{
  "event": "workflow_started",
  "workflow_id": "v2.docs_explain.summary"
}

workflow.v2.summary.llm

{
  "event": "request",
  "prompt_name": "v2_docs_explain.summary_answer",
  "system_prompt": "Ты объясняешь документацию только на основе найденных SUMMARY-блоков.\nИспользуй только факты из входного контекста.\nЕсли информации мало, прямо скажи об этом и не додумывай детали.\nВ конце перечисли файлы, на которые ты опирался.",
  "user_prompt": "Запрос пользователя:\nКак работает метод health?\n\nСигналы запроса:\n{\n  \"entity_names\": [],\n  \"file_names\": [],\n  \"endpoint_paths\": [],\n  \"target_doc_hints\": [],\n  \"matched_aliases\": [],\n  \"process_domain\": null,\n  \"process_subdomain\": null,\n  \"signal_types\": []\n}\n\nНайденные SUMMARY-блоки:\n\n1. path: docs/README.md\ntitle: Индекс технической документации test_echo_app\nmatch_reason: semantic_match\nsummary: - Purpose: точка входа в техническую документацию сервиса `test_echo_app`.\n- Scope: архитектура, HTTP API control plane, цикл отправки уведомлений, health-модель и каталог ошибок.\n- Canonical structure: `docs/architecture`, `docs/api`, `docs/logic`, `docs/domains`, `docs/errors`.\n- Primary parent doc: [Архитектура Telegram Notify App](./architecture/telegram-notify-app-overview.md).\n- Navigation: документы связаны через `related_docs`, `parent`/`children` и markdown-ссылки без дублирования деталей.\n\n2. path: docs/architecture/telegram-notify-app-overview.md\ntitle: Архитектура Telegram Notify App\nmatch_reason: semantic_match\nsummary: - Purpose: сервис поднимает HTTP control plane и фоновый worker для отправки уведомлений в Telegram.\n- Entry point: `src/telegram_notify_app/main.py`.\n- Main components: `RuntimeManager`, `TelegramControlChannel`, `TelegramNotifyModule`, `TelegramNotifyWorker`, `TelegramSendService`.\n- Configuration: `config/config.yaml` или путь из `CONFIG_PATH`.\n- Related API: [`/health`](../api/health-endpoint.md), [`/actions/{action}`](../api/control-actions-endpoint.md), [`/send`](../api/send-message-endpoint.md).\n- Related logic: [цикл отправки уведомлений](../logic/telegram-notification-loop.md).\n- Related domain: [runtime health](../domains/runtime-health-entity.md).",
  "log_context": "agent:req_bab9c8812ac94847bb102cba68516f10"
}

workflow.v2.summary.llm

{
  "event": "response",
  "text": "На основе представленного контекста невозможно предоставить подробное объяснение работы метода health. \n\nФайлы, на которые я опирался:\n1. docs/README.md\n2. docs/architecture/telegram-notify-app-overview.md"
}

workflow.v2.summary

{
  "event": "workflow_trace_flushed",
  "workflow_id": "v2.docs_explain.summary",
  "steps": [
    {
      "step_id": "generate_summary_answer",
      "title": "Сборка ответа по summary",
      "input": {},
      "output": {
        "answer_length": 205
      }
    }
  ]
}

workflow.v2.summary

{
  "event": "workflow_completed",
  "workflow_id": "v2.docs_explain.summary"
}

process.v2.pipeline

{
  "event": "answer_generated",
  "answer_mode": "grounded_summary",
  "answer_length": 205
}

result

{
  "status": "done",
  "answer": "На основе представленного контекста невозможно предоставить подробное объяснение работы метода health. \n\nФайлы, на которые я опирался:\n1. docs/README.md\n2. docs/architecture/telegram-notify-app-overview.md",
  "completed_at": "2026-04-07T18:21:01.793612+00:00"
}

36 KiB Raw Blame History

Runtime Trace: 20260407-182058-3f56c69c7290

request

process.v2

process.v2.pipeline

process.v2.pipeline

process.v2.pipeline

process.v2.retrieval_policy

process.v2.pipeline

process.v2.rag_retrieval

process.v2.pipeline

process.v2.pipeline

process.v2.evidence

process.v2.pipeline

process.v2.pipeline

process.v2.pipeline

process.v2.pipeline

process.v2.pipeline

workflow.v2.summary

workflow.v2.summary.llm

workflow.v2.summary.llm

workflow.v2.summary

workflow.v2.summary

process.v2.pipeline

result

36 KiB

Raw Blame History