Swift story
Swift evidence safety keeps proof usable without leaking private material.
Swift public copy should carry rule IDs, evidence tiers, coverage labels, reduced-coverage gaps, and hashed sensitive identifiers where supported, while keeping raw private evidence out of the site.
Public claim level: shipped. Proof: PR #425. Public pages must not publish raw source snippets.
Use
Safety is part of the evidence contract, not an afterthought.
Attach the ruleEvery public Swift claim should route back to a rule ID, evidence tier, proof path, and limitation.
Keep gaps visibleReduced coverage is a useful label because it stops weak evidence from becoming stronger public copy.
Keep private material outUse public-safe summaries and hashed sensitive identifiers where supported instead of raw values or local evidence.
Boundary
Safety language prevents accidental claim upgrades.
- Swift evidence safety does not prove runtime behavior, app navigation, rendered UI, production usage, endpoint performance, build success, deployment state, release safety, stored values, query execution, or live schema.
- 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, analyzer logs, facts.ndjson, index.sqlite, or hidden validation details.
Proof path