Notarization
Both distribution artifacts of ORIX Monitor 1.0.0 (build 1) were submitted to Apple's notary service on 2026-11-21 with
xcrun notarytool, using a keychain profile that already existed on the release Mac. The service's verdicts below are
copied from its JSON answers, kept locally in build/notary/ (not committed).
| Artifact | Submission ID | Status | Stapled | stapler validate |
|---|---|---|---|---|
ORIX Monitor.app (uploaded as a zip) |
4f0026aa-6755-471b-9392-b06671e90083 |
Accepted | Yes | The validate action worked |
ORIX-Monitor-1.0.0.dmg |
13bf43c8-e0e8-4c84-acfc-8e74bc3f6f23 |
Accepted | Yes | The validate action worked |
The notary log of the app submission reports status "Accepted", summary "Ready for distribution", and no issue.
Four earlier submissions of previous builds of the same version were also accepted (apps 9611e866-7c3c-4c67-8291-adcc533003c0
and 9ed75733-9ac3-486f-986c-5930ecbe0569, disk images f4d9cee3-e915-4a37-893a-5ecf39a31cf0 and
6a308fc2-49dd-47b2-ba84-c44318d8e4a8). Those builds were replaced before any distribution: the first after the
accessibility audit led to darker light-mode text colours, the second after the overhead benchmark led to live charts
being redrawn without animation. Their artifacts were deleted; only the build named in the table exists.
Procedure
Scripts/notarize.sh "dist/ORIX Monitor.app" app # zip, submit, wait, fetch log, staple, validate
Scripts/package.sh zip # zip of the *stapled* app
Scripts/package.sh dmg # disk image of the stapled app, signed
Scripts/notarize.sh dist/ORIX-Monitor-1.0.0.dmg dmg # submit, wait, staple, validateScripts/notarize.sh:
- uses the profile named by
NOTARY_PROFILE(defaultMacLustr-Notarize), created beforehand withxcrun notarytool store-credentials; it never creates, prints or changes credentials; - waits for Apple's answer and prints "notarized" only when the status is
Accepted; - downloads the notary log to
build/notary/<name>-log.jsonwhatever the verdict; - on rejection, exits non-zero and names the log to read. The fix-rebuild-resign-resubmit loop is then manual.
The ZIP cannot carry a stapled ticket itself; it contains the stapled app.
Gatekeeper validation
Run on the release Mac after stapling:
$ spctl --assess --type execute --verbose=2 "dist/ORIX Monitor.app"
dist/ORIX Monitor.app: accepted
source=Notarized Developer ID
$ spctl --assess --type open --context context:primary-signature --verbose=2 dist/ORIX-Monitor-1.0.0.dmg
dist/ORIX-Monitor-1.0.0.dmg: accepted
source=Notarized Developer IDInstallation test on other Macs
The final disk image was copied to two other Macs, given a com.apple.quarantine attribute as a browser download would
have, assessed, mounted, and the app copied out and run for 45 seconds with an isolated data directory. The database it
wrote was then read back.
| Mac | macOS | Checksum matches | DMG assessment | App assessment | Ran 45 s | Metrics stored |
|---|---|---|---|---|---|---|
Mac mini, M2 (Mac14,3) |
26.5.1 | Yes | accepted, Notarized Developer ID | accepted, Notarized Developer ID | Yes | 24 metrics, 28–29 samples each |
Mac mini, M4 Pro (Mac16,11) |
26.5.1 | Yes | accepted, Notarized Developer ID | accepted, Notarized Developer ID | Yes | 24 metrics, 29–30 samples each |
Neither Mac has a battery: the three battery metrics were correctly absent from their databases, and thermal state, GPU
utilization (best effort), memory, disk, network and process metrics were present. An earlier build had passed the same test on an M4 Mac mini (Mac16,10, macOS 26.7).
Limits of this test. The app was started from a shell over SSH inside the logged-in user's session, not by
double-clicking in Finder, so the first-launch Gatekeeper dialog itself was not seen; spctl is the same policy engine but
not the same path. Nobody looked at the window on those Macs. None of the three runs macOS 15, the minimum the app
declares.