Swift reviewer checklist

Repeat Swift claims only when the evidence label travels with them.

Swift v0 is shipped as static evidence discovery. This checklist keeps public copy tied to proof paths, rule-backed evidence, coverage labels, limitations, and non-claims before a reviewer repeats it.

Public claim level: shipped. Proof: PR #425. The checklist supports public wording review; it does not upgrade static evidence into runtime API correctness or complete Swift semantic analysis.

Checklist

A Swift claim is repeatable only after these checks pass.

Reviewer checks for public Swift wording. Each row is a gate before stronger wording appears on the site, in a post, or in a handoff.
Check	Required evidence	Allowed wording	Block or downgrade when
Public claim level	`shipped`, `demo`, `concept`, or `hidden` is attached.	Use shipped only for Swift v0 behavior landed on `main`; use demo for checked-in public-safe generated summaries.	The capability is dev-only, private-only, future-facing, or lacks a public proof path.
Proof path	A public route or repository document backs the sentence before publication.	Link to the Swift evidence lane, real-world smoke proof, or validation.	The only support is private local output, raw generated artifacts, unpublished branch state, or memory from a review.
Evidence tier	Rule ID, evidence tier, line span or supporting ID, and commit SHA are available in the source evidence packet.	Say static, syntax, structural, textual, reduced coverage, or unknown when those labels match the packet.	The sentence implies compiler semantics, runtime dispatch, endpoint reachability, live storage, or release safety without reducer-backed proof.
Coverage label	Coverage label and limitation are repeated next to the claim.	Use reduced coverage for macro, generated-code, unavailable-module, Objective-C bridge, storyboard/nib, conditional-compilation, protocol-dispatch, or unsupported-surface gaps.	The wording hides uncertainty or turns a candidate into a guarantee.
Non-claim boundary	Runtime, API correctness, build, simulator/device, production, storage, and AI-analysis boundaries stay explicit.	Say TraceMap inventories and reports static Swift evidence where rules support it.	The sentence says or implies runtime behavior, API correctness, production usage, stored values, query execution, live schema, complete Swift semantic analysis, or AI impact analysis.

Approved shape

Use claim language that names the boundary in the same breath.

Safe shippedSwift v0 is available for deterministic static evidence discovery over supported Swift repository surfaces.

Safe demoThe real-world smoke page shows pinned public Swift API-client samples and public-safe generated summaries for static artifact generation.

Safe gapReduced coverage is expected when SwiftSyntax, project context, generated code, macros, bridges, or unavailable modules limit what TraceMap can prove.

Future semantic depthFuture Swift semantic-depth work stays concept-level until the implementation lands, public-safe proof exists, and the claim level is upgraded.

Blocked wording

Do not let stronger product language sneak in through Swift copy.

Do not claim runtime behavior, runtime API correctness, endpoint reachability, backend compatibility, app navigation, rendered UI, user action, production usage, deployment state, release safety, stored values, query execution, live schema, or complete Swift semantic analysis.
Do not claim Xcode build proof, SwiftPM restore proof, simulator/device execution proof, package compatibility, dependency freshness, dependency license status, vulnerability status, or operational safety.
Do not describe TraceMap scanner or reducer work as AI impact analysis, LLM analysis, prompt-based classification, embedding-backed search, or vector database analysis.
Do not publish raw generated artifacts, raw source snippets, raw SQL, secrets, credentials, local absolute paths, raw remotes, stored values, private scan artifacts, analyzer logs, or hidden validation details.

Proof path

Use these before publishing Swift wording.

Swift evidence lane Why Swift evidence matters Swift real-world smoke proof Swift API-client evidence walkthrough Swift static inventory Swift symbols and calls Swift surface discovery Swift storage and data surfaces Swift evidence safety Site claim guardrails Review claim checklist Proof source catalog Limitations Reduced coverage Validation Swift v0 PR #425