Scan artifacts

TraceMap writes evidence you can inspect.

The scanner emits machine-readable facts, a queryable SQLite index, a manifest that records coverage and commit state, a human report, and logs for analyzer diagnostics.

Required scan output

Five files define the scan packet.

Each artifact is listed explicitly so reviewers can verify which evidence was produced.

scan-manifest.jsonRepository identity, commit SHA, scanner version, analysis level, build status, and coverage.

facts.ndjsonOne deterministic fact per line, including rule IDs, tiers, spans, and extractor metadata.

index.sqliteQueryable facts plus tables for symbols, relationships, edges, surfaces, aliases, and flows when available.

report.mdHuman-readable summary of coverage, gaps, facts, surfaces, and limitations.

logs/analyzer.logAnalyzer diagnostics and project-load details for failed or partial analysis.

Example

Scan a sample repository.

Restore is explicit. Failed project load is not treated as clean analysis.

dotnet run --project src/dotnet/TraceMap.Cli -- scan \
  --repo samples/modern-sample \
  --out .tracemap

SQL scans can add a bounded operator handoff packet.

When supported SQL evidence exists, sql-runbook.md and sql-runbook.json project categorical context, prerequisites, protected steps, validation expectations, gaps, and limitations without reproducing executable SQL. Read the manager-facing SQL handoff story, then inspect the synthetic public proof packet.

Database evidence can be composed into a design-review packet.

database-design-review.md and database-design-review.json group compatible PostgreSQL design, EF mapping, application operation, query, route, provenance, cap, and gap evidence. Read the manager-facing database design review, then inspect the synthetic public proof packet.