Swift API-client walkthrough

Read Swift API-client evidence as static candidates, not live calls.

TraceMap can surface supported Swift URLSession, URLRequest, Alamofire, and Moya-style API-client evidence as rule-backed static candidates. The useful part is the attached proof boundary: rule ID, evidence tier, coverage label, source location, limitation, and non-claim.

Public claim level: demo. Proof path: Swift surface discovery, real-world smoke proof, and validation guide. This walkthrough explains how to read the evidence; it is not raw scanner output.

How to use it

The walkthrough gives reviewers a reading order.

Start with the selectorFind the normalized static path key and HTTP method attached to the client evidence.

Check the rule IDUse swift.http.urlsession.v1 or swift.http.client-library.v1 to know which extractor rule produced the row.

Read the tierSwift API-client rows are syntax/textual or structural candidates, not compiler semantic proof.

Keep the limit attachedEvery row needs coverage and non-claim wording before it appears in a public story or review packet.

Evidence shapes

Supported Swift API-client rows share the same proof contract.

Demo-level reading guide for Swift API-client static evidence. These rows describe evidence shape, not runtime network behavior.
Evidence shape	Rule ID	Evidence tier	Coverage label	What reviewers may say	Required limitation
URLSession literal request	`swift.http.urlsession.v1`	`Tier3SyntaxOrTextual`	`CoverageRelative` or `ReducedCoverage`	A Swift source location contains static URLSession-adjacent HTTP evidence with a normalized method/path candidate.	Does not prove request execution, endpoint reachability, response handling, auth flow, backend compatibility, production traffic, or runtime behavior.
URLRequest method and URL literal	`swift.http.urlsession.v1`	`Tier3SyntaxOrTextual`	`CoverageRelative` or `ReducedCoverage`	A URLRequest literal, method assignment, and recognized URLSession use form a static HTTP candidate.	Does not prove method mutation at runtime, request success, credentials, retry behavior, backend compatibility, or live network traffic.
Alamofire request literal	`swift.http.client-library.v1`	`Tier3SyntaxOrTextual`	`CoverageRelative` or `ReducedCoverage`	A supported Alamofire call shape exposes a static client-library surface with method/path metadata where literals are present.	Does not prove Alamofire runtime configuration, interceptors, auth headers, request success, network reachability, or production use.
Moya TargetType-style path	`swift.http.client-library.v1`	`Tier3SyntaxOrTextual`	`CoverageRelative` or `ReducedCoverage`	A supported TargetType-style path/method shape can become static client-library surface evidence.	Does not prove baseURL composition, runtime target selection, plugin behavior, auth flow, backend compatibility, or request execution.

Report reading

A safe review packet repeats the evidence fields, not the source text.

The public walkthrough should point to sanitized summaries and checked-in validation docs. Raw generated artifacts stay local; public copy should use labels, rule IDs, evidence tiers, coverage labels, normalized path keys, line spans, commit SHA, and limitations.

Rule: swift.http.client-library.v1
Tier: Tier3SyntaxOrTextual
Coverage: ReducedCoverage or CoverageRelative
Claim: static Swift API-client candidate
Non-claim: not runtime endpoint reachability

Non-claims

Do not turn API-client evidence into backend proof.

Do not claim endpoint reachability, backend compatibility, request success, auth flow, production traffic, runtime behavior, deployment state, release safety, or API correctness.
Do not claim SwiftPM restore proof, Xcode build proof, simulator/device execution, package compatibility, app navigation, rendered UI, stored values, query execution, live schema, or complete Swift semantic analysis.
Do not publish raw generated artifacts, raw source snippets, raw SQL, secrets, credentials, local absolute paths, raw remotes, hostnames, config values, runtime observations, private scan artifacts, or hidden validation details.
TraceMap core scanning and reduction do not use AI impact analysis, LLM analysis, prompt-based classification, embeddings, or vector database analysis.

Proof path

Use these pages before repeating a Swift API-client claim.

Swift evidence lane Why Swift evidence matters Swift surface discovery Swift real-world smoke proof Swift evidence safety Swift claim language checklist Validation Limitations Reduced coverage Site claim guardrails Validation guide section