Swift v0

Swift v0 is a shipped static evidence lane.

TraceMap can now inspect supported Swift repository surfaces and emit deterministic evidence for inventory, symbols, calls, relationships, client/UI/package/storage surfaces, and reduced-coverage gaps.

Public claim level: shipped for Swift v0 capability copy. Proof: PR #425, merge commit e8813daaf763e277e7c5d88a2c0b2ad0b570f25a. This page describes static evidence only.

What landed

Swift joins the same evidence contract as the other adapters.

Static inventorySwift packages/projects, source files, module-ish metadata, and reduced-coverage labels.

Symbols and callsSwiftSyntax-backed declarations, call candidates, construction candidates, and direct relationships where syntax supports them.

Surface discoverySupported HTTP/API client surfaces, SwiftUI/UIKit-ish surfaces, and package/dependency surfaces.

Storage and data surfacesCoreData metadata, UserDefaults keys, Keychain access patterns, SQLite text/shape evidence, and Realm model/property surfaces.

Evidence safetyRule IDs, evidence tiers, coverage labels, hashed sensitive identifiers, and explicit analysis gaps.

Evidence matrix

Each Swift story keeps its claim level and limitation attached.

Swift v0 public story slices. Shipped means the capability is on main; demo means a future page may add public-safe generated output without changing the static boundary.
Story	Public claim level	Evidence shape	Proof anchor	Limitation
Swift v0 evidence lane	`shipped`	Deterministic static Swift discovery with rule IDs, evidence tiers, file paths, line spans, commit SHA, coverage labels, and documented limitations.	PR #425 on `main`.	Does not prove Swift runtime behavior, app navigation, production usage, build success, deployment state, release safety, or AI impact analysis.
Swift static inventory	`shipped`	Swift package/project inventory, source file selection, module-ish metadata, and reduced-coverage labels when project or toolchain context is limited.	PR #425 and repository validation docs.	Inventory is not Xcode build proof, SwiftPM restore proof, simulator/device execution, or complete module understanding.
Swift symbols and calls	`shipped`	SwiftSyntax-backed declarations, call candidates, construction candidates, inheritance/conformance-style relationship evidence, and syntax-tier usage rows.	PR #425 and acceptance criteria.	Syntax-backed candidates are not compiler semantic resolution, runtime dispatch, protocol witness proof, dependency injection proof, or SwiftUI runtime reachability.
Swift surface discovery	`demo`	Supported static HTTP/API client, SwiftUI/UIKit-ish, package, and dependency surface evidence, with dynamic composition gaps visible.	PR #425 and the real-world smoke proof for pinned public API-client samples.	HTTP/API surfaces are not runtime network reachability; UI surfaces are not rendered UI, complete navigation, or user action proof; dependency surfaces are not vulnerability, license, freshness, or build compatibility analysis.
Swift API-client evidence walkthrough	`demo`	Reader-friendly guide for URLSession, URLRequest, Alamofire, and Moya-style static API-client evidence fields.	The real-world smoke proof, surface discovery, and validation guide.	Does not prove endpoint reachability, backend compatibility, request success, auth flow, production traffic, runtime behavior, or API correctness.
Swift storage and data surfaces	`demo`	CoreData metadata, UserDefaults keys, Keychain access patterns, SQLite SQL text/shape evidence, and Realm model/property surfaces where statically supported.	PR #425; demo rows need public-safe generated summaries.	Does not prove stored values, query execution, live schema, runtime persistence, Keychain item existence, UserDefaults values, credentials, or data impact.
Swift evidence safety	`shipped`	Rule IDs, evidence tiers, coverage labels, reduced-coverage gaps, and hashed sensitive identifiers where supported.	PR #425, site claim guardrails, and limitations.	Public pages still must not publish raw source snippets, raw SQL, secrets, local absolute paths, raw remotes, credentials, stored values, private scan artifacts, or hidden validation details.

How to read it

Swift evidence is useful because it names both proof and gaps.

Tier2StructuralUseful for project/package structure, metadata files, and framework patterns when the rule documents the limitation.

Tier3SyntaxOrTextualExpected for many SwiftSyntax and literal text candidates; it is evidence, not runtime certainty.

Tier4UnknownUse for unsupported, unavailable, hidden, or unproven Swift behavior instead of filling gaps with stronger language.

ReducedCoverageVisible when toolchain, macro, generated-code, Objective-C bridge, storyboard/nib, conditional-compilation, protocol-dispatch, or missing-module limits apply.

Boundaries

Do not upgrade static Swift evidence into operational proof.

TraceMap does not run Swift apps, simulators, devices, Xcode builds, SwiftPM restores, production traffic, or runtime persistence.
TraceMap does not prove rendered UI, user action, complete navigation, live network reachability, stored values, credentials, query execution, or live schema behavior.
TraceMap does not perform AI impact analysis, LLM analysis, prompt-based classification, embeddings, or vector database analysis in the scanner or reducer.
TraceMap should not use impact wording for a Swift surface unless reducer-backed public-safe evidence supports that wording.

Swift v0 is a shipped static evidence lane.

Swift joins the same evidence contract as the other adapters.

Each Swift story keeps its claim level and limitation attached.

Swift evidence is useful because it names both proof and gaps.

Do not upgrade static Swift evidence into operational proof.

Follow the public proof path before repeating the claim.