Workflows

Static evidence for contract and dependency review.

TraceMap workflows turn repository snapshots into evidence packets. They help reviewers find what needs review without pretending to observe runtime execution.

Scan

Index a repository into deterministic facts and a SQLite database.

Reduce

Compare contract deltas against indexed facts with coverage-aware classifications.

Combine

Merge indexes while preserving source labels, commit SHAs, and original fact IDs.

Paths

Find bounded static evidence paths from endpoints or symbols to dependency surfaces.

Reverse

Start from dependency surfaces and walk back to static roots such as endpoints or symbols.

Diff

Compare combined snapshots by stable static evidence keys.

Impact

Project static diff evidence into change-impact review items.

Portfolio

Summarize dependency surfaces and coverage across many indexes.

Release review

Assemble a release-oriented evidence packet with explicit unavailable sections.

Coverage controls the conclusion.

A no-evidence result under full known coverage means something different than no evidence under reduced coverage. TraceMap keeps those outcomes separate.

Future exploration

Vault export would be a review layer, not a new source of truth.

ConceptA future optional export could turn paths, sources, symbols, endpoints, packages, SQL, and config surfaces into linked Markdown notes.
BoundaryThe facts, SQLite index, reports, and rule catalog would remain the evidence source.
FramingOpen the evidence trail as a vault explains the idea without claiming it is shipped.