Future concept

Open the evidence trail as a vault.

A future optional export could turn the same rule-backed TraceMap evidence packet into linked Markdown notes for managers, reviewers, architects, and engineers who want to inspect the map visually.

This is not a prettier claim.

It would be the same evidence packet made browsable. The source of truth would remain the facts, SQLite index, reports, logs, rule catalog, commit metadata, coverage labels, supporting IDs, and limitations emitted by TraceMap.

Why a vault

Some reviews need a map people can click through.

ManagersStart from `Start Here.md` and see which evidence shaped the review without reading SQLite directly.

ReviewersMove from endpoint to route to symbol to dependency surface while keeping rule IDs and tiers visible.

ArchitectsInspect cross-service and cross-language paths as linked notes instead of a prose-only summary.

EngineersJump from a path or finding back to the source file span and supporting fact IDs that justify it.

Possible workflow

A future demo could make the evidence trail browsable.

1 Run the public demo.

Generate the existing static evidence packet from checked-in sample repositories.

2 Generate a vault export.

Convert selected facts, paths, surfaces, gaps, and summaries into linked Markdown notes.

3 Open `Start Here.md`.

Begin with the manifest, coverage state, source labels, and safe entry points for review.

Exploration path

The notes would keep evidence attached to every hop.

A reviewer could click from frontend endpoint to backend route to service or code path to SQL, package, or config surface. Each note and edge would carry its rule ID, evidence tier, commit SHA, coverage label, supporting IDs, and documented limitations.

Start Here.md
sources/sample-client.md
endpoints/GET-api-admin-runner-id.md
routes/sample-server-runner-controller.md
symbols/RunnerService.getById.md
surfaces/sql-query-8f4d3a.md
paths/frontend-to-sql.md

Source of truth

The vault would not replace TraceMap artifacts.

facts.ndjsonRule-backed facts remain the evidence rows.

index.sqliteThe queryable index remains the machine-readable graph and surface store.

report.mdThe human report remains the summary of coverage, gaps, and limitations.

rule-catalog.ymlRule documentation remains the place to inspect rule intent and limitations.

Boundaries

The export layer would stay inside TraceMap's evidence rules.

It would not prove runtime behavior, production traffic, deployment state, or release approval.
It would not be AI impact analysis and would not add prompt-based classification to the scanner or reducer.
It would not require Obsidian. Any Markdown viewer that follows links should be able to inspect the notes.
It would not export raw source snippets, raw SQL, config values, secrets, local absolute paths, or raw repo remotes.