Apple Runtime Performance Proof

Turn performance reports into reproducible, bounded claims. Code inspection creates hypotheses; it does not prove runtime behavior.

Evidence contract

Bind every claim through this chain:

source revision → built/installed artifact → executable UUID/hash → live PID and helpers → scenario → measurement window

If a link is missing, stop at that boundary. A successful build does not prove which app was measured.

Record source; build/SDK/architecture/version; installed executable and symbols; process tree; device/OS/sandbox; representative data; tool, trace, and window.

Read references/evidence-binding.md for the provenance record, child/provider attribution, and source, artifact, runtime, sandbox, provider, configuration, and harness boundaries.

Workflow