Endpoint to route
Show which static route, handler, controller, service method, or adapter surface produced the evidence row.
Incident call use case
When the call is live, start with what static evidence can prove.
TraceMap can orient a production incident or P1 call by showing the static dependencies and proof paths around an endpoint, route, package, configuration surface, or code path.
Public claim level: concept. No public conclusion without evidence. This page describes static dependency evidence, not runtime observability, production traffic, endpoint performance, outage cause, release safety, operational safety, or an APM replacement.
The call question
What static dependencies surround this surface?
Name the surfaceStart with the endpoint, handler, DTO, package, config key family, or SQL-facing surface the team is discussing.
Follow evidenceTrace from that name into rule-backed public-safe summaries with rule IDs, evidence tiers, coverage labels, and limitations.
Separate proofUse TraceMap for static repository evidence while telemetry, logs, traces, tests, and owners prove runtime behavior.
Keep gaps visibleReduced coverage and analysis gaps stay in the packet so a partial map does not become a clean bill of health.
Fast orientation
The useful output is a narrow list of places to inspect next.
Route to code path
Link the public-safe summary to file paths, line spans, supporting IDs, commit SHA, extractor version, and coverage label.
Code path to nearby surfaces
Keep related DTOs, packages, SQL-facing surfaces, config/project metadata, and cross-app references visible when demo evidence supports them.
Finding to limitation
Attach analysis gaps and reduced-coverage labels before anyone turns static evidence into a runtime conclusion.
Proof path shape
A call note should point back to evidence, not memory.
rule idWhich deterministic rule produced the visible fact or path?evidence tierWas it compiler-resolved, structural, syntax/textual, or an unknown gap?coverage labelIs the analysis complete for this scope, reduced, partial, or explicitly unavailable?supporting idsWhich public-safe summary rows, artifact references, and file spans support the statement?limitationWhat should the incident team avoid concluding from this static evidence?Boundary
This is not the system of record for production behavior.
- TraceMap does not prove runtime behavior, production traffic, endpoint performance, outage cause, release safety, or operational safety.
- TraceMap does not replace Dynatrace, APM tooling, logs, traces, metrics, tests, incident command, or service ownership.
- TraceMap should not use impact language for a dependency unless reducer-backed public-safe evidence supports that wording.
- TraceMap concept pages are orientation, not operational approval or a production dependency guarantee.
Public-safe packet
Publish the orientation layer, keep private internals local.
Safe to shareRule IDs, evidence tiers, coverage labels, limitations, public-demo file spans, commit SHA, extractor versions, counts, and generated report families.
Keep privateRaw fact streams, SQLite indexes, analyzer logs, source excerpts, SQL text, config values, secrets, local paths, repository remotes, scan directories, and private sample identities.
Review firstPrivate repository evidence should stay private until a human has reviewed and redacted the summary for public use.
P1-call orientation and incident review are related, not identical.
Use this page when the team needs a quick static map around a named endpoint or surface during a live call. Use incident review orientation for broader follow-up after the event, when the question is how static evidence can support review notes, ownership conversations, and future code inspection. Use the static triage checklist when engineers need handoff questions for a named static code surface during the call.
Evidence trail