Proof

“No networking code” is the kind of claim anyone can make and nobody can check. These are the two things that would catch it if it were false.

1. The tests fail if a door is added back

The promise this app makes is a negative, and negatives rot quietly — nobody notices the day someone adds a share sheet “just for this one thing”. So the test suite scans the source for the symbols that would make it possible, and fails if any of them appear. A release does not go out with a failing test.

It covers networking (URLSession, Network, CloudKit, WKWebView and the rest), every export route (UIActivityViewController, UIPasteboard, PHPhotoLibrary, AirDrop, save-to-Photos), and some less obvious ones — AirPlay, picture-in-picture, and the system context menu, which lifts a rendered copy of your thumbnail into a layer that screenshots can capture.

The one deliberate exception

Media can leave, by exactly one route: the encrypted Transfer archive. Removing that symbol from the forbidden list would have thrown the guarantee away, so instead the rule narrowed. Two tests now hold it:

2. The check runs against the binary, not the source

Source can be read selectively. This inspects the app that actually ships: its linked frameworks, the symbols it references, and its Info.plist. Run against a Release build, verbatim, no editing:

$ ./tools/verify-offline.sh SockDrawer.app

== linked frameworks ==
CFNetwork                                            absent
Network                                              absent
NetworkExtension                                     absent
CloudKit                                             absent
MultipeerConnectivity                                absent
WebKit                                               absent
SafariServices                                       absent
SystemConfiguration                                  absent
MessageUI                                            absent

== networking symbols referenced by the binary ==
NSURLSession                                         absent
NSURLConnection                                      absent
CFReadStream                                         absent
CFSocket                                             absent
nw_connection_create                                 absent
nw_path_monitor_create                               absent
getaddrinfo_async                                    absent
SCNetworkReachability                                absent
WKWebView                                            absent
UIDocumentInteractionController                      absent
UIPrintInteractionController                         absent
MFMailComposeViewController                          absent
MFMessageComposeViewController                       absent

== debug-only scaffolding ==
LockSeed                                             absent
MJ_SEED_PIN                                          absent
MJ_SEED_DECOY_PIN                                    absent
MJ_CAPTURE_SELFTEST                                  absent

== Info.plist posture ==
UIFileSharingEnabled                                 false
LSSupportsOpeningDocumentsInPlace                    false
NSAppTransportSecurity:NSAllowsArbitraryLoads        false
ITSAppUsesNonExemptEncryption                        false

PASS — nothing in this binary can reach a network.

What this does NOT say: media can leave, by two deliberate routes.
Settings > Transfer writes the vault to one file, encrypted under a passphrase
you choose, without decrypting anything. And Export — off until the owner turns
it on in Settings, and behind Face ID or the PIN every time — saves unencrypted
copies to Photos (add-only access) or the share sheet. UIActivityViewController
is therefore expected in this binary; OfflinePostureTests holds it, and every
photo-library API, to MediaExport.swift.

Generated from a real run on 19 November 2026. The last section is there because a check that overstates what it proved is worse than no check.

Why this instead of open source

Open source would be the stronger answer and this is not it. Being straightforward about that: Sock Drawer is closed source, and no amount of published test output is the same thing as letting you read the code.

What these checks do give you is something most closed-source apps cannot: a claim that is falsifiable without trusting anyone. Put a proxy in front of the app and watch it make no connections. Run the script against the binary yourself. The claim either survives that or it does not.