| Call graph traversal | The call graph is traversed from the affected service outward. Every upstream caller and downstream dependency is mapped before a single log is read. |
| Contract validation | Logged requests are validated against API and schema contracts defined in code. A changed response shape or a silently diverged API surfaces as a contract violation with the affected path. |
| Historical baseline | The current repository state is compared with earlier states to identify structural changes and dependency regressions from the last stable version. |
| Log analysis | Provide a log snippet or file. Trace cross-references it against the knowledge graph and constrains the relevant entries to the call paths and services already in scope. |