Swift story
Swift storage and data surfaces need careful wording.
TraceMap can name supported CoreData metadata, UserDefaults keys, Keychain access patterns, SQLite SQL text/shape evidence, and Realm model/property surfaces without exposing private values.
Public claim level: demo. Shipped capability anchor: PR #425. Storage/data evidence is not stored-value proof.
Use
Data-adjacent evidence helps route questions without publishing secrets.
Local persistenceCoreData and Realm-style metadata can orient reviewers to model/property surfaces where static evidence supports the row.
Key/value patternsUserDefaults keys and Keychain access patterns can be surfaced as static evidence without claiming values exist.
SQL shapeSQLite SQL text/shape evidence can be summarized without publishing raw SQL or claiming query execution.
Boundary
Storage surfaces are not live persistence proof.
- Swift storage/data surfaces do not prove stored values, query execution, live schema, runtime persistence, Keychain item existence, UserDefaults values, credentials, data impact, production usage, build success, deployment state, or release safety.
- 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