Swift story
Swift static inventory gives review a starting map.
TraceMap Swift v0 can name package/project inventory, source file selection, module-ish metadata, and reduced-coverage labels before a reviewer asks a runtime or build system question.
Public claim level: shipped. Proof: PR #425. Static inventory is shipped evidence, not Xcode build proof, SwiftPM restore proof, simulator execution, device execution, or complete module understanding.
Use
Inventory is the place to begin, not the place to conclude.
What it can nameSupported Swift project/package shapes, selected source files, module-ish metadata, and reduced-coverage labels.
What it gives reviewersA repository snapshot vocabulary for asking better follow-up questions about Swift code ownership and coverage.
What stays visibleToolchain, generated-code, macro, conditional-compilation, unavailable module, and unsupported-surface gaps remain limitations.
Boundary
Keep inventory separate from build and runtime claims.
- Inventory does not prove runtime behavior, app navigation, rendered UI, production usage, deployment state, release safety, build success, or endpoint performance.
- TraceMap core scanning and reduction do not use AI impact analysis, LLM analysis, prompt-based classification, embeddings, or vector database analysis.
- Public pages must not publish raw source snippets, raw SQL, secrets, local absolute paths, raw remotes, credentials, stored values, private scan artifacts, or hidden validation details.
Proof path