Examples

See the evidence packet before you run it.

Start here when you are showing TraceMap to a teammate. These pages show representative scan packets, fact rows, Markdown summaries, contract deltas, and impact findings before anyone has to install or build the tool.

Tour path

Four pages cover the first conversation.

What does the public demo produce?Use the demo result page to show available sections, deferred sections, and generated summary rows.

What does a scan emit?Use the scan packet page to show the artifact bundle and coverage labels.

How does impact review work?Use the contract-impact page to show classification, evidence, and gaps together.

Where does this help us?Use the use-cases page to connect outputs to review and release workflows.

Database design review proof packet Schema, mapping, operation, query, route, and gap evidence together.

A synthetic public-safe comparison of the shipped single-index and combined-index packet boundaries.

SQL runbook proof packet Categorical operator handoff with protected values omitted.

A synthetic public-safe packet with context transitions, permission statuses, milestones, gaps, and evidence provenance.

Demo result Available sections, deferred sections, and summary rows.

What the checked-in public demo currently produces.

Scan packet Manifest, facts, SQLite, report, and logs.

What a repository scan emits and how coverage stays visible.

Contract impact Delta input, reducer rows, evidence, and gaps.

How changed contract elements map to rule-backed findings.

Use cases Where static evidence helps review work.

Contract changes, releases, cross-repo maps, and legacy systems.

These examples are orientation, not marketing claims.

They show file paths, line spans, rule IDs, evidence tiers, hashes, and coverage labels. They do not show raw source snippets, secrets, raw SQL, connection strings, or proof of runtime behavior.