toolchains
Status: available. Evidence tier: Tier2Structural. Counts required local tools before analysis runs.
Demo result
The public demo already produces a readable first evidence packet.
The current public demo scans checked-in .NET and TypeScript samples, writes local scan artifacts, and produces public-safe summary files that show available sections, upgraded proof rows, evidence tiers, rule IDs, coverage labels, counts, and reasons.
Public claim level: demo. This page describes the current first-slice demo result. It does not claim runtime behavior, production traffic, deployment state, endpoint performance, release safety, or AI impact analysis.
Run
Generate the result from a clean checkout.
Use an ignored output directory when running inside the repository. The summary files are designed for public-safe inspection; raw scan artifacts stay local.
git clone https://github.com/joefeser/tracemap.git
cd tracemap
./scripts/demo-public.sh .tracemap-demo
sed -n '1,160p' .tracemap-demo/demo-summary.mdWhat runs today
The first demo slice demonstrates the scan packet shape across checked-in samples.
Toolchain checksStatus: available. The script checks `git`, `.NET`, `node`, and `npm` before writing the summary.
BuildStatus: available. The demo builds the .NET CLI and TypeScript adapter used by the sample scans.
.NET modern sampleStatus: available. Produces the required scan artifacts under the generated output root.
.NET endpoint server sampleStatus: available. Produces static endpoint and scan evidence from checked-in sample code.
TypeScript modern sampleStatus: available. Produces reducer-compatible TypeScript scan artifacts.
TypeScript endpoint client sampleStatus: available. Produces static client-side endpoint evidence from checked-in sample code.
Summary files
The public-safe result is a status ledger, not a raw artifact dump.
demo-summary.mdHuman-readable table with section name, status, evidence tier, rule IDs, coverage, counts, and reasons.demo-summary.jsonMachine-readable section rows with a hashed output-root label instead of an absolute local path.public.demo.summary.v1Rule ID used for demo summary rows so each public conclusion remains rule-backed.Tier2StructuralEvidence tier for available demo sections such as toolchain checks, build, and sample scans.Tier4UnknownEvidence tier for deferred, unavailable, or failed sections where the demo cannot make a stronger claim.Representative section rows
The exact counts can vary with toolchain coverage, but the statuses are explicit.
python
Status: not_requested by default. Python scanning is opt-in for this demo slice and must use an isolated environment when requested.
jvm
Status: unavailable when Java 21 is absent, or deferred when Java 21 exists but JVM demo assertions are still follow-up work.
build
Status: available. The demo builds the .NET and TypeScript tooling needed for the checked-in sample scans.
sample-scans
Status: available. Four checked-in samples produce manifests, facts, SQLite indexes, reports, and analyzer logs.
proof upgrades
Status: upgraded. Combined report, paths/reverse, portfolio, diff, impact, and release-review rows now have demo evidence in the proof-upgrades ledger.
Proof upgrades
The formerly deferred rows are now visible demo evidence.
combine-and-dependency-reportAvailable as demo evidence with generated dependency reports for endpoint-stack and mixed-stack samples.
paths-and-reverseAvailable as demo evidence with generated path and reverse lookup reports.
portfolioAvailable as demo evidence with a generated portfolio manifest and portfolio report.
diffAvailable as demo evidence from checked-in public before/after fixtures.
impactAvailable as demo evidence derived from the public demo diff output.
release-reviewAvailable as demo evidence with a generated static review checklist.
Messy legacy validation is a separate proof lane.
The legacy validation concept explains how future validation can test old .NET projects, failed builds, UI event wiring, and large repositories without turning local sample details into public claims.
Artifact safety
Share summaries; keep raw generated internals local.
demo-summary.*Public-shareable after the generated-output sentinel scan passes.reports/**/*.mdPublic-shareable only when generated from public samples and scrubbed by sentinel checks.scans/**/scan-manifest.jsonLocal-only generated artifact; may contain temporary execution details.scans/**/facts.ndjsonLocal-only fact stream for deeper inspection and reducer input.scans/**/index.sqliteLocal-only queryable index; do not publish private-repo SQLite artifacts raw.scans/**/logs/analyzer.logLocal-only diagnostic log for extraction and coverage troubleshooting.Claim boundary
What this demo result supports right now.
- Safe: the demo can generate scan packets and public-safe summary rows from checked-in .NET and TypeScript samples.
- Safe: the current result makes upgraded and bounded sections visible instead of hiding gaps.
- Safe: the summaries can orient a review conversation around static evidence, rule IDs, evidence tiers, coverage labels, and gaps.
- Not safe: claiming the demo proves full impact, runtime behavior, production traffic, production dependency understanding, endpoint performance, or release safety.
Deciding what can be shared?
Use the public demo runbook to check public-safe summaries, local-only artifact boundaries, proof paths, validation, and limitations before repeating a row status.
See the upgraded demo rows.
The demo proof upgrades page shows the combined reports, paths, reverse, portfolio, diff, impact, and release-review rows that now have reproducible public-demo evidence, plus the limits that still apply.
Need a scannable visual layer?
The demo proof assets page shows public-safe report-style cards that orient readers before they inspect generated summaries and reports.
Source material