1. Run the demo
Clone the public repository and run the checked-in demo script from a clean checkout.
Proof: scripts/demo-public.sh.
Demo walkthrough
Start with a static evidence packet, not a promise.
This guided path shows how to run the checked-in public demo, inspect public-safe summaries, follow one static evidence trail, and read the limitations before turning evidence into a review conversation.
Public claim level: demo. The walkthrough describes reproducible checked-in samples and public-safe generated summaries. It does not claim runtime behavior, production traffic, release safety, or AI impact analysis.
2. Open the summary
Start with the public-safe Markdown or JSON summary before opening local-only artifacts.
Look for: coverage labels, artifact names, deferred work, and the current result guide.
3. Follow one path
Pick an endpoint or surface and inspect the static evidence links that explain what TraceMap found.
Look for: rule IDs, evidence tiers, file paths, line spans, and limitations.
4. Check capabilities
Use the capability matrix to understand whether a workflow is main, demo, dev, or future-facing.
Proof: capability status.
5. Read limitations
Separate static repo evidence from runtime facts, monitoring data, deployment state, and approval decisions.
Proof: public limitations.
6. Share the packet
Use summaries and reports for review. Keep SQLite, fact streams, logs, and private repo details local.
Boundary: no raw snippets, secrets, local absolute paths, or private remotes.
Run it
The first run should be boring.
Run the public demo against checked-in samples. The output should give you a repeatable static evidence packet, not an incident answer or runtime diagnosis.
git clone https://github.com/joefeser/tracemap.git
cd tracemap
./scripts/demo-public.sh
# Optional: write output to a chosen folder.
./scripts/demo-public.sh .tracemap-demoWhat to inspect
Start with summaries, then open local artifacts when needed.
Public-safe summaryUse generated summary Markdown or JSON to see what ran, what was produced, and where coverage is reduced.
Report filesUse generated Markdown reports to inspect paths, surfaces, gaps, and limitations from public samples.
Facts and SQLiteUse local fact streams and SQLite indexes for deeper inspection, but keep private-repo artifacts local-only.
Analyzer logsUse logs for troubleshooting extraction, not for public copy or product claims.
Evidence packetUse the packet guide when sharing the result with a manager, reviewer, architect, or teammate.
Pressure-test wording
Use TraceMap beside runtime tools, not instead of them.
- Safe: "This endpoint has a static evidence trail through these code and data surfaces."
- Safe: "This review packet shows rule-backed findings and coverage gaps from the repository."
- Not safe: "TraceMap proves why production is down."
- Not safe: "TraceMap proves this endpoint is slow, unused, deployed, or safe to release."
Next links