TraceMap

Public demo

Generate a local evidence packet from checked-in samples.

The public demo scans sample repositories, writes generated artifacts, and produces public-shareable summaries that avoid local absolute paths.

Run it

The demo is one script from a clean checkout.

The output is static-analysis evidence. It is not deployment evidence, production traffic evidence, or release approval. 

git clone https://github.com/joefeser/tracemap.git
cd tracemap
./scripts/demo-public.sh
./scripts/demo-public.sh .tracemap-demo

Before you run it

Know what the demo is meant to show.

Repeatable artifactsThe same checked-in samples should produce the same kind of scan packet and summaries.
Inspectable claimsThe demo points to rules, coverage, files, and gaps instead of asking reviewers to trust a paragraph.
Bounded scopeThe output is static evidence. It does not claim production usage, runtime reachability, or release approval.

Expected result

The demo writes summaries and generated artifacts.

ScansChecked-in sample repositories produce scan artifacts.
Summary MarkdownA human-readable demo summary describes what ran, what was upgraded, and which optional rows still have limits.
Summary JSONMachine-readable status rows make the demo result inspectable.
Sentinel checksPublic-shareable output avoids raw local paths and raw sensitive values.

Need the operator checklist?

The public demo runbook connects the walkthrough, result guide, evidence trail, proof paths, validation, and limitations into one sharing checklist.

Showing the demo to a manager or teammate?

The manager demo script gives a bounded route order, answer shapes, stop conditions, and follow-up handoff for a short public-site walkthrough.

Want to know what the current first slice produces?

The demo result guide shows which sections are available today, which rows have been upgraded, and how to read the generated summary rows without overstating the evidence.

Want the upgraded proof rows?

The demo proof upgrades page shows combined reports, paths, reverse lookup, portfolio, diff, impact, and release-review evidence generated from checked-in public samples.

Want to follow one public-safe evidence trail?

The demo evidence trail walks one static question through changed surfaces, endpoint findings, path evidence, downstream gaps, coverage labels, and limitations.

Want a visual orientation first?

The demo proof assets page shows public-safe report-card examples for summary rows, paths, diff and impact rows, and release-review checklists without publishing raw local artifacts.

Want the runway behind the demo?

The public roadmap shows how demo rows can become stronger public claims only after checked-in proof, generated public-safe summaries, and visible limitations land.

Need the guided path first?

Use the demo walkthrough to run the sample, inspect the public-safe summaries, follow one static evidence path, and read the limitations before making claims.

Sharing the result?

The evidence packet guide explains what a demo-safe packet can support, what should stay local, and which runtime or production claims are still out of bounds.

Future concept: open the evidence trail as a vault.

A future optional export could make the same demo evidence browsable as linked Markdown notes for managers, reviewers, architects, and engineers. This is a concept, not a shipped demo output: read the vault export framing.