TraceMap

Capabilities

TraceMap maps static evidence across scans, indexes, and review packets.

This demo/evidence matrix maps what TraceMap can show from public samples, repository docs, validation commands, and source-backed workflows. It is not a product-completeness promise.

Public claim level: demo. Rows use main, demo, dev, or future status language and should not be upgraded to shipped until the relevant evidence is true on main.

Scan

Index repositories into manifests, facts, SQLite, reports, and analyzer logs.

tracemap scan

Status: demo. Proof: scripts/demo-public.sh, samples/.

Reduce

Reduce contract deltas against indexed facts with evidence rows and coverage-aware outcomes.

tracemap reduce

Status: main. Proof: README.md, src/dotnet/TraceMap.Cli/Program.cs.

Combine

Merge indexes while preserving source labels, commit metadata, coverage, and provenance.

tracemap combine

Status: main. Proof: docs/VALIDATION.md, scripts/smoke-combined-paths.sh.

Report

Generate combined dependency reports for endpoints, surfaces, edges, gaps, and limitations.

tracemap report

Status: main. Proof: README.md, docs/VALIDATION.md.

Paths and reverse

Walk bounded static evidence from roots to surfaces, or from surfaces back to roots.

tracemap paths tracemap reverse

Status: main. Proof: scripts/smoke-combined-paths.sh.

Diff and impact

Compare static snapshots and turn changed evidence into coverage-relative review reports.

tracemap diff tracemap snapshot-diff tracemap impact

Status: main. Proof: README.md, docs/VALIDATION.md.

Release review

Compose available diff, impact, contract, path, reverse, gap, and checklist evidence.

tracemap release-review

Status: main. Proof: README.md, docs/VALIDATION.md.

Portfolio and endpoints

Summarize many indexes and align client-called endpoints with server-declared endpoint evidence.

tracemap portfolio tracemap endpoints

Status: main. Proof: README.md, implementation-state notes.

Inspect and export

Inspect flows, relationships, and exportable index views without publishing raw private artifacts.

tracemap flow tracemap relate tracemap export

Status: main. Proof: README.md, src/dotnet/TraceMap.Cli/Program.cs.

Adapter maturity

Language support is real, but not identical across adapters.

.NET/C#Status: main. Strongest adapter: Roslyn semantic extraction, syntax fallback, API/DTO, SQL, config, package, call, and value-origin evidence. Proof: README.md, docs/VALIDATION.md.
Swift v0Status: shipped on main. Static inventory, SwiftSyntax-backed symbols/calls, surface discovery, storage/data surfaces, reduced-coverage gaps, and pinned real-world API-client smoke validation. Proof: Swift evidence lane, real-world smoke proof, PR #425.
TypeScript MVPStatus: main/demo. Compiler-backed facts with syntax fallback, endpoint/client, package, config, SQL-adjacent integration facts, and reducer-compatible SQLite output. Proof: README.md, public demo samples.
JVM MVPStatus: main with maturity caveats. Java compiler-backed facts plus Java/Kotlin syntax fallback, Maven/Gradle metadata, integration facts, and reduced-coverage labels. Kotlin is not full semantic parity. Proof: .kiro/specs/jvm-indexer/implementation-state.md.
Python MVPStatus: main with maturity caveats. AST/package/config/SQL/FastAPI/Flask/Pydantic/SQLAlchemy/httpx/requests evidence. The scanner does not import or execute user code. Proof: .kiro/specs/python-indexer/implementation-state.md.

Demo-safe surface

Show summaries and reports, keep raw analysis artifacts local.

demo-summary.mdPublic-shareable summary from checked-in sample projects.
demo-summary.jsonMachine-readable public summary with labels instead of private paths.
reports/**/*.mdSafe when generated from public samples and scrubbed of raw values.
index.sqliteKeep private-repo SQLite indexes local-only.
facts.ndjsonKeep private-repo fact streams local-only.
logs/analyzer.logKeep analyzer logs local-only because they may contain execution details.

Web Forms and VB.NET claim ladder

Four public surfaces carry four bounded jobs.

The lane is intentionally mixed: one workflow is shipped, two public synthetic review surfaces are demo-level, and one privacy projection remains concept-level. Those labels do not promote broad Web Forms support.

Shipped · guided terminal setup

The guided setup covers explicit website/project selection, form scoping, persisted pause and resume, build consent, external Windows publication handoff, and stop conditions on main.

Concept · source + compiled projection

The source-plus-compiled proof illustrates candidate getter, constructor, provider-DLL, and database-terminal hops with unresolved values and explicit gaps. It is not independently projected extractor output.

Demo · reproducible local corpus

The local demo and artifact map documents five operator layouts, bounded query views, fail-closed outcomes, and an exact-tree Windows receipt for checked-in synthetic fixtures.

Demo · review-workbench walkthrough

The seven-step walkthrough demonstrates how to inspect one synthetic route, an unresolved category, a coverage gap, and owner questions without becoming a live workbench.

Still futureAutomatic solution-wide discovery, backend microservice onboarding, cross-service click-to-database tracing, and source-server/PDB acquisition.
Still excludedDev-only repairs that are not ancestors of the current main baseline are not part of the shipped claim.
Still boundedWindows-only build/publication validation, candidate bridges, unresolved values, partial coverage, and explicit gaps remain attached to the exact proof surface.

Legacy validation is still a concept-level proof lane.

The legacy validation concept describes the planned safe validation pass for old and unusually large .NET codebases. It should not be read as a shipped support claim until redacted validation summaries exist.

Incident review orientation is a concept use case.

The incident review orientation page connects existing demo and main-backed evidence surfaces into a review workflow. It is not a shipped incident-response capability and does not claim runtime proof.

SQL project refactor intent is a bounded checked-in evidence surface.

The SQL project refactor-intent proof page shows supported table renames, column renames, and table schema moves with rule IDs, tiers, relative spans, coverage, gaps, and limitations. It does not build a project, inspect a DACPAC, deploy a change, or establish database state.

Non-claims

Capabilities stay bounded by static evidence.

Source material

Every capability should point back to inspectable evidence.

Repository README Validation guide Acceptance plan Rule catalog Evidence packet guide Manager packet Database design review Database design proof packet MSBuild binlog evidence proof packet SQL project refactor-intent proof Database rename evidence article Incident review orientation Public roadmap Swift evidence lane Swift real-world smoke proof Docs map Public demo Current demo result Proof path index Proof source catalog Claim ledger Legacy validation concept Examples Limitations