1049 lines
52 KiB
Markdown
1049 lines
52 KiB
Markdown
# Runtime Trace: 20260407-175948-92e685261a86
|
||
|
||
- active_rag_session_id: 965a992e-8be3-45cf-8a31-92e685261a86
|
||
|
||
## request
|
||
```json
|
||
{
|
||
"request_id": "req_36c125fd77054be599054b080ea92d49",
|
||
"session_id": "as_21b7fe278b9548938d3a066eb02d5ed3",
|
||
"active_rag_session_id": "965a992e-8be3-45cf-8a31-92e685261a86",
|
||
"process_version": "v2",
|
||
"created_at": "2026-04-07T17:59:48.924496+00:00",
|
||
"message": "В какой файле документация на эндпоинт health?"
|
||
}
|
||
```
|
||
|
||
## process.v2
|
||
```json
|
||
{
|
||
"event": "intent_routed",
|
||
"routing_domain": "DOCS",
|
||
"intent": "DOC_EXPLAIN",
|
||
"subintent": "FIND_FILES",
|
||
"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": [
|
||
"FIND_FILES"
|
||
]
|
||
},
|
||
"confidence": 0.8500000000000001,
|
||
"routing_mode": "llm_default",
|
||
"llm_router_used": true,
|
||
"reason_short": "Запрос явно ищет файл с документацией.",
|
||
"rag_session_id": "965a992e-8be3-45cf-8a31-92e685261a86"
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "router_resolved",
|
||
"domain": "DOCS",
|
||
"intent": "DOC_EXPLAIN",
|
||
"subintent": "FIND_FILES",
|
||
"confidence": 0.8500000000000001
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "anchors_extracted",
|
||
"signal_types": [
|
||
"FIND_FILES"
|
||
],
|
||
"endpoint_paths": [],
|
||
"target_doc_hints": [],
|
||
"matched_aliases": [],
|
||
"target_terms": [
|
||
"эндпоинт",
|
||
"health"
|
||
]
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "alias_resolution",
|
||
"resolved_aliases": [],
|
||
"target_doc_hints": []
|
||
}
|
||
```
|
||
|
||
## process.v2.retrieval_policy
|
||
```json
|
||
{
|
||
"event": "retrieval_plan_resolved",
|
||
"profile": "file_lookup",
|
||
"layers": [
|
||
"D1_DOCUMENT_CATALOG",
|
||
"D3_ENTITY_CATALOG"
|
||
],
|
||
"limit": 12,
|
||
"filters": {
|
||
"target_doc_hints": [],
|
||
"path_prefixes": [
|
||
"docs/"
|
||
],
|
||
"prefer_path_prefixes": [
|
||
"docs/"
|
||
],
|
||
"prefer_like_patterns": []
|
||
}
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "retrieval_profile_selected",
|
||
"profile": "file_lookup",
|
||
"layers": [
|
||
"D1_DOCUMENT_CATALOG",
|
||
"D3_ENTITY_CATALOG"
|
||
],
|
||
"filters": {
|
||
"target_doc_hints": [],
|
||
"path_prefixes": [
|
||
"docs/"
|
||
],
|
||
"prefer_path_prefixes": [
|
||
"docs/"
|
||
],
|
||
"prefer_like_patterns": []
|
||
}
|
||
}
|
||
```
|
||
|
||
## process.v2.rag_retrieval
|
||
```json
|
||
{
|
||
"event": "rag_rows_fetched",
|
||
"profile": "file_lookup",
|
||
"row_count": 3,
|
||
"rows": [
|
||
{
|
||
"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": "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": "D3_ENTITY_CATALOG",
|
||
"path": "docs/architecture/telegram-notify-app-overview.md",
|
||
"title": "TelegramNotifyModule",
|
||
"document_id": "architecture.telegram_notify_app",
|
||
"entity_name": "TelegramNotifyModule",
|
||
"summary_text": "",
|
||
"section_path": "",
|
||
"content_preview": "TelegramNotifyModule"
|
||
}
|
||
]
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "candidate_generation",
|
||
"query": "В какой файле документация на эндпоинт health?",
|
||
"profile": "file_lookup",
|
||
"details": {
|
||
"target_doc_hints": [],
|
||
"candidates_before_ranking": [
|
||
"docs/README.md",
|
||
"docs/architecture/telegram-notify-app-overview.md",
|
||
"docs/architecture/telegram-notify-app-overview.md"
|
||
]
|
||
},
|
||
"resolved_aliases": [],
|
||
"target_doc_hints": [],
|
||
"candidate_docs_before_ranking": [
|
||
{
|
||
"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": "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": "D3_ENTITY_CATALOG",
|
||
"path": "docs/architecture/telegram-notify-app-overview.md",
|
||
"title": "TelegramNotifyModule",
|
||
"document_id": "architecture.telegram_notify_app",
|
||
"entity_name": "TelegramNotifyModule",
|
||
"summary_text": "",
|
||
"section_path": "",
|
||
"content_preview": "TelegramNotifyModule"
|
||
}
|
||
],
|
||
"sources": {
|
||
"seeded": [],
|
||
"metadata_lookup": [],
|
||
"semantic": [
|
||
{
|
||
"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": "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": "D3_ENTITY_CATALOG",
|
||
"path": "docs/architecture/telegram-notify-app-overview.md",
|
||
"title": "TelegramNotifyModule",
|
||
"document_id": "architecture.telegram_notify_app",
|
||
"entity_name": "TelegramNotifyModule",
|
||
"summary_text": "",
|
||
"section_path": "",
|
||
"content_preview": "TelegramNotifyModule"
|
||
}
|
||
]
|
||
}
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "retrieval_executed",
|
||
"query": "В какой файле документация на эндпоинт health?",
|
||
"profile": "file_lookup",
|
||
"row_count": 3,
|
||
"target_doc_hints": [],
|
||
"top_results": [
|
||
{
|
||
"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": "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": "D3_ENTITY_CATALOG",
|
||
"path": "docs/architecture/telegram-notify-app-overview.md",
|
||
"title": "TelegramNotifyModule",
|
||
"document_id": "architecture.telegram_notify_app",
|
||
"entity_name": "TelegramNotifyModule",
|
||
"summary_text": "",
|
||
"section_path": "",
|
||
"content_preview": "TelegramNotifyModule"
|
||
}
|
||
]
|
||
}
|
||
```
|
||
|
||
## process.v2.evidence
|
||
```json
|
||
{
|
||
"event": "evidence_assembled",
|
||
"mode": "find_files",
|
||
"file_count": 2,
|
||
"files": [
|
||
"docs/README.md",
|
||
"docs/architecture/telegram-notify-app-overview.md"
|
||
]
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "evidence_assembled",
|
||
"mode": "find_files",
|
||
"primary_file": "docs/README.md",
|
||
"file_count": 2
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "ranking_explained",
|
||
"doc": "docs/README.md",
|
||
"score_breakdown": {
|
||
"semantic": 10,
|
||
"path_match": 0,
|
||
"filename_match": 0,
|
||
"alias_match": 0,
|
||
"anchor_boost": 120,
|
||
"target_doc_boost": 0,
|
||
"generic_penalty": 0
|
||
},
|
||
"score": 130,
|
||
"match_reason": "semantic_match"
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "ranking_explained",
|
||
"doc": "docs/architecture/telegram-notify-app-overview.md",
|
||
"score_breakdown": {
|
||
"semantic": 10,
|
||
"path_match": 0,
|
||
"filename_match": 0,
|
||
"alias_match": 0,
|
||
"anchor_boost": 120,
|
||
"target_doc_boost": 0,
|
||
"generic_penalty": 0
|
||
},
|
||
"score": 130,
|
||
"match_reason": "semantic_match"
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "ranking_explained",
|
||
"top_docs_after_ranking": [
|
||
{
|
||
"doc": "docs/README.md",
|
||
"score": 130,
|
||
"match_reason": "semantic_match"
|
||
},
|
||
{
|
||
"doc": "docs/architecture/telegram-notify-app-overview.md",
|
||
"score": 130,
|
||
"match_reason": "semantic_match"
|
||
}
|
||
],
|
||
"ranking_score_breakdown": [
|
||
{
|
||
"doc": "docs/README.md",
|
||
"score_breakdown": {
|
||
"semantic": 10,
|
||
"path_match": 0,
|
||
"filename_match": 0,
|
||
"alias_match": 0,
|
||
"anchor_boost": 120,
|
||
"target_doc_boost": 0,
|
||
"generic_penalty": 0
|
||
}
|
||
},
|
||
{
|
||
"doc": "docs/architecture/telegram-notify-app-overview.md",
|
||
"score_breakdown": {
|
||
"semantic": 10,
|
||
"path_match": 0,
|
||
"filename_match": 0,
|
||
"alias_match": 0,
|
||
"anchor_boost": 120,
|
||
"target_doc_boost": 0,
|
||
"generic_penalty": 0
|
||
}
|
||
}
|
||
]
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "evidence_gate_checked",
|
||
"passed": false,
|
||
"reason": "low_confidence_shortlist",
|
||
"answer_mode": "deterministic"
|
||
}
|
||
```
|
||
|
||
## workflow.v2.find_files
|
||
```json
|
||
{
|
||
"event": "workflow_started",
|
||
"workflow_id": "v2.docs_explain.find_files"
|
||
}
|
||
```
|
||
|
||
## workflow.v2.find_files
|
||
```json
|
||
{
|
||
"event": "workflow_trace_flushed",
|
||
"workflow_id": "v2.docs_explain.find_files",
|
||
"steps": [
|
||
{
|
||
"step_id": "finalize_find_files_answer",
|
||
"title": "Сборка списка файлов",
|
||
"input": {},
|
||
"output": {
|
||
"answer_length": 64
|
||
}
|
||
}
|
||
]
|
||
}
|
||
```
|
||
|
||
## workflow.v2.find_files
|
||
```json
|
||
{
|
||
"event": "workflow_completed",
|
||
"workflow_id": "v2.docs_explain.find_files"
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "answer_generated",
|
||
"answer_mode": "deterministic",
|
||
"answer_length": 64
|
||
}
|
||
```
|
||
|
||
## result
|
||
```json
|
||
{
|
||
"status": "done",
|
||
"answer": "docs/README.md\ndocs/architecture/telegram-notify-app-overview.md",
|
||
"completed_at": "2026-04-07T17:59:50.263763+00:00"
|
||
}
|
||
```
|
||
|
||
## request
|
||
```json
|
||
{
|
||
"request_id": "req_8345d97e397b482d9243764513180c4c",
|
||
"session_id": "as_21b7fe278b9548938d3a066eb02d5ed3",
|
||
"active_rag_session_id": "965a992e-8be3-45cf-8a31-92e685261a86",
|
||
"process_version": "v2",
|
||
"created_at": "2026-04-07T18:00:20.485493+00:00",
|
||
"message": "Как работает send_message_endpoint?"
|
||
}
|
||
```
|
||
|
||
## process.v2
|
||
```json
|
||
{
|
||
"event": "intent_routed",
|
||
"routing_domain": "DOCS",
|
||
"intent": "DOC_EXPLAIN",
|
||
"subintent": "SUMMARY",
|
||
"normalized_query": "Как работает send_message_endpoint?",
|
||
"target_terms": [
|
||
"send_message_endpoint"
|
||
],
|
||
"anchors": {
|
||
"entity_names": [],
|
||
"file_names": [],
|
||
"endpoint_paths": [],
|
||
"target_doc_hints": [],
|
||
"matched_aliases": [],
|
||
"process_domain": null,
|
||
"process_subdomain": null,
|
||
"signal_types": []
|
||
},
|
||
"confidence": 0.7500000000000001,
|
||
"routing_mode": "llm_default",
|
||
"llm_router_used": true,
|
||
"reason_short": "Запрос явно касается работы конкретного endpoint'а.",
|
||
"rag_session_id": "965a992e-8be3-45cf-8a31-92e685261a86"
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "router_resolved",
|
||
"domain": "DOCS",
|
||
"intent": "DOC_EXPLAIN",
|
||
"subintent": "SUMMARY",
|
||
"confidence": 0.7500000000000001
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "anchors_extracted",
|
||
"signal_types": [],
|
||
"endpoint_paths": [],
|
||
"target_doc_hints": [],
|
||
"matched_aliases": [],
|
||
"target_terms": [
|
||
"send_message_endpoint"
|
||
]
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "alias_resolution",
|
||
"resolved_aliases": [],
|
||
"target_doc_hints": []
|
||
}
|
||
```
|
||
|
||
## process.v2.retrieval_policy
|
||
```json
|
||
{
|
||
"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
|
||
```json
|
||
{
|
||
"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
|
||
```json
|
||
{
|
||
"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": "- [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/architecture/telegram-notify-app-overview.md",
|
||
"title": "architecture.telegram_notify_app:Telegram Bot API",
|
||
"document_id": "architecture.telegram_notify_app",
|
||
"entity_name": "",
|
||
"summary_text": "",
|
||
"section_path": "Архитектура Telegram Notify App > Details > Интеграции > Telegram Bot API",
|
||
"content_preview": "- target: ext.telegram_bot_api\n- target_type: external_system\n- direction: outbound\n- interaction: calls\n- via: HTTPS `POST /bot{token}/sendMessage`\n- purpose: доставка как плановых, так и ручных уведомлений\n- details:\n - producers:\n - logic.telegram_notification_loop\n - api.send_message_endpoint\n - timeout_seconds: 30"
|
||
},
|
||
{
|
||
"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/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": "- `src/telegram_notify_app/main.py` - загрузка YAML, регистрация runtime и сигналов shutdown.\n- `src/telegram_notify_app/module.py` - регистрация worker и send service в runtime.\n- `src/telegram_notify_app/control_api.py` - HTTP control plane и endpoint `/send`.\n- `src/telegram_notify_app/worker.py` - фоновый workflow отправки и расчет health.\n- `src/telegram_notify_app/send_service.py` - разовая "
|
||
},
|
||
{
|
||
"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
|
||
```json
|
||
{
|
||
"event": "candidate_generation",
|
||
"query": "Как работает send_message_endpoint?",
|
||
"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/architecture/telegram-notify-app-overview.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": "- [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/architecture/telegram-notify-app-overview.md",
|
||
"title": "architecture.telegram_notify_app:Telegram Bot API",
|
||
"document_id": "architecture.telegram_notify_app",
|
||
"entity_name": "",
|
||
"summary_text": "",
|
||
"section_path": "Архитектура Telegram Notify App > Details > Интеграции > Telegram Bot API",
|
||
"content_preview": "- target: ext.telegram_bot_api\n- target_type: external_system\n- direction: outbound\n- interaction: calls\n- via: HTTPS `POST /bot{token}/sendMessage`\n- purpose: доставка как плановых, так и ручных уведомлений\n- details:\n - producers:\n - logic.telegram_notification_loop\n - api.send_message_endpoint\n - timeout_seconds: 30"
|
||
},
|
||
{
|
||
"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/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": "- `src/telegram_notify_app/main.py` - загрузка YAML, регистрация runtime и сигналов shutdown.\n- `src/telegram_notify_app/module.py` - регистрация worker и send service в runtime.\n- `src/telegram_notify_app/control_api.py` - HTTP control plane и endpoint `/send`.\n- `src/telegram_notify_app/worker.py` - фоновый workflow отправки и расчет health.\n- `src/telegram_notify_app/send_service.py` - разовая "
|
||
},
|
||
{
|
||
"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": "- [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/architecture/telegram-notify-app-overview.md",
|
||
"title": "architecture.telegram_notify_app:Telegram Bot API",
|
||
"document_id": "architecture.telegram_notify_app",
|
||
"entity_name": "",
|
||
"summary_text": "",
|
||
"section_path": "Архитектура Telegram Notify App > Details > Интеграции > Telegram Bot API",
|
||
"content_preview": "- target: ext.telegram_bot_api\n- target_type: external_system\n- direction: outbound\n- interaction: calls\n- via: HTTPS `POST /bot{token}/sendMessage`\n- purpose: доставка как плановых, так и ручных уведомлений\n- details:\n - producers:\n - logic.telegram_notification_loop\n - api.send_message_endpoint\n - timeout_seconds: 30"
|
||
},
|
||
{
|
||
"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
|
||
```json
|
||
{
|
||
"event": "retrieval_executed",
|
||
"query": "Как работает send_message_endpoint?",
|
||
"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": "- [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/architecture/telegram-notify-app-overview.md",
|
||
"title": "architecture.telegram_notify_app:Telegram Bot API",
|
||
"document_id": "architecture.telegram_notify_app",
|
||
"entity_name": "",
|
||
"summary_text": "",
|
||
"section_path": "Архитектура Telegram Notify App > Details > Интеграции > Telegram Bot API",
|
||
"content_preview": "- target: ext.telegram_bot_api\n- target_type: external_system\n- direction: outbound\n- interaction: calls\n- via: HTTPS `POST /bot{token}/sendMessage`\n- purpose: доставка как плановых, так и ручных уведомлений\n- details:\n - producers:\n - logic.telegram_notification_loop\n - api.send_message_endpoint\n - timeout_seconds: 30"
|
||
},
|
||
{
|
||
"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
|
||
```json
|
||
{
|
||
"event": "evidence_assembled",
|
||
"mode": "summary",
|
||
"document_count": 1,
|
||
"documents": [
|
||
"docs/architecture/telegram-notify-app-overview.md"
|
||
]
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "evidence_assembled",
|
||
"mode": "summary",
|
||
"primary_doc": "docs/architecture/telegram-notify-app-overview.md",
|
||
"document_count": 1
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "ranking_explained",
|
||
"doc": "docs/architecture/telegram-notify-app-overview.md",
|
||
"score_breakdown": {
|
||
"semantic": 60,
|
||
"path_match": 0,
|
||
"filename_match": 0,
|
||
"alias_match": 0,
|
||
"anchor_boost": 0,
|
||
"target_doc_boost": 0,
|
||
"generic_penalty": 0
|
||
},
|
||
"score": 60,
|
||
"match_reason": "semantic_match"
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "ranking_explained",
|
||
"top_docs_after_ranking": [
|
||
{
|
||
"doc": "docs/architecture/telegram-notify-app-overview.md",
|
||
"score": 60,
|
||
"match_reason": "semantic_match"
|
||
}
|
||
],
|
||
"ranking_score_breakdown": [
|
||
{
|
||
"doc": "docs/architecture/telegram-notify-app-overview.md",
|
||
"score_breakdown": {
|
||
"semantic": 60,
|
||
"path_match": 0,
|
||
"filename_match": 0,
|
||
"alias_match": 0,
|
||
"anchor_boost": 0,
|
||
"target_doc_boost": 0,
|
||
"generic_penalty": 0
|
||
}
|
||
}
|
||
]
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "evidence_gate_checked",
|
||
"passed": true,
|
||
"reason": "target_doc_found",
|
||
"answer_mode": "grounded_summary"
|
||
}
|
||
```
|
||
|
||
## workflow.v2.summary
|
||
```json
|
||
{
|
||
"event": "workflow_started",
|
||
"workflow_id": "v2.docs_explain.summary"
|
||
}
|
||
```
|
||
|
||
## workflow.v2.summary.llm
|
||
```json
|
||
{
|
||
"event": "request",
|
||
"prompt_name": "v2_docs_explain.summary_answer",
|
||
"system_prompt": "Ты объясняешь документацию только на основе найденных SUMMARY-блоков.\nИспользуй только факты из входного контекста.\nЕсли информации мало, прямо скажи об этом и не додумывай детали.\nВ конце перечисли файлы, на которые ты опирался.",
|
||
"user_prompt": "Запрос пользователя:\nКак работает send_message_endpoint?\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/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_8345d97e397b482d9243764513180c4c"
|
||
}
|
||
```
|
||
|
||
## workflow.v2.summary.llm
|
||
```json
|
||
{
|
||
"event": "response",
|
||
"text": "На основе представленного SUMMARY-блока, подробной информации о том, как именно работает endpoint `send_message_endpoint`, нет. Документ лишь указывает, что этот endpoint существует и ссылается на файл \"../api/send-message-endpoint.md\", который предположительно содержит более подробную информацию.\n\nФайлы, на которые я опирался:\n- docs/architecture/telegram-notify-app-overview.md"
|
||
}
|
||
```
|
||
|
||
## workflow.v2.summary
|
||
```json
|
||
{
|
||
"event": "workflow_trace_flushed",
|
||
"workflow_id": "v2.docs_explain.summary",
|
||
"steps": [
|
||
{
|
||
"step_id": "generate_summary_answer",
|
||
"title": "Сборка ответа по summary",
|
||
"input": {},
|
||
"output": {
|
||
"answer_length": 381
|
||
}
|
||
}
|
||
]
|
||
}
|
||
```
|
||
|
||
## workflow.v2.summary
|
||
```json
|
||
{
|
||
"event": "workflow_completed",
|
||
"workflow_id": "v2.docs_explain.summary"
|
||
}
|
||
```
|
||
|
||
## process.v2.pipeline
|
||
```json
|
||
{
|
||
"event": "answer_generated",
|
||
"answer_mode": "grounded_summary",
|
||
"answer_length": 381
|
||
}
|
||
```
|
||
|
||
## result
|
||
```json
|
||
{
|
||
"status": "done",
|
||
"answer": "На основе представленного SUMMARY-блока, подробной информации о том, как именно работает endpoint `send_message_endpoint`, нет. Документ лишь указывает, что этот endpoint существует и ссылается на файл \"../api/send-message-endpoint.md\", который предположительно содержит более подробную информацию.\n\nФайлы, на которые я опирался:\n- docs/architecture/telegram-notify-app-overview.md",
|
||
"completed_at": "2026-04-07T18:00:23.497821+00:00"
|
||
}
|
||
```
|