What problem does it solve? Investigating 1C:Enterprise incidents requires manually correlating registration journal (ЖР) events, technological log (ТЖ) fragments, SQL traces, and source code, which is slow and error-prone when timestamps, sessions, and transactions span multiple files. ## Core Features & Use Cases - Evidence classification and timeline building: Classifies ЖР events, ТЖ events, platform exceptions, DBMS/SQL artifacts, deadlocks, long calls, background jobs, and HTTP service requests, then builds a timeline with explicit clock sources and timezones. - Log-to-code mapping: Links log entries back to source modules and metadata objects using the unica MCP tools (code search, metadata info, project map, standards search). - Root-cause separation: Distinguishes the originating exception, lock, or timeout from downstream rollback noise, preserving lock holder/waiter, SQL text, transaction boundaries, and session identifiers. - Use Case: A user pastes a technological log fragment showing a DBMSSQL deadlock and asks for the cause; the Skill extracts the lock holder and waiter, maps the query to the responsible procedure, and produces a root-cause hypothesis with evidence lines. ## Quick Start Analyze this technological log fragment and registration journal export to find the root cause of the deadlock and map it to the responsible 1C code.
