All public works
HAACC PUBLIC WORK / macOS app

Rockpile

An AI-built personal macOS project documented through a public repository and an explicitly unverified release claim.

Publication
Reviewed & published
Build stage
Complete
Updated
2026-07-16
Problem

A non-coder wanted a small focus tool but had no reliable path from AI-generated code to an installable macOS app.

Primary user

People who can think and prompt but do not hand-write production code, and want a shipped artifact rather than a sandbox demo.

Current artifact

A public Swift repository plus a HAACC case study that records the creator's release claim.

Source factSupported

The project has a public Swift repository.

Creator claimUnverified

The macOS artifact completed signing and notarization.

RepositoryChecked

Public repository

The repository URL, source tree, commit history, and README are publicly inspectable.

  • Does not block publicationThe current availability of a downloadable signed build has not been independently rechecked.
  • Does not block publicationNo structured external usability result is recorded yet.
Day 0

Selected one concrete problem: a small focus app, not a platform.

Day 2

Produced the first runnable Swift build before visual polish.

Day 5

Separated device testing, code signing, and notarization into an explicit verification gate.

Day 7

Opened the repository and published the build postmortem.

Where it broke

Code signing and notarization blocked the first release attempt.

Why

A green local build was mistaken for a distributable artifact.

What changed

Signing became an independent checklist and verification step.

If an independent user cannot install or inspect the artifact from the published evidence, the shipping claim is incomplete.

Publish a current signed build and ask an independent macOS user to install it while preserving the verification evidence.

Find real-user UX feedback and a second review of the Swift code and release path.

Help needed
FeedbackCode reviewDistribution
Review scope
Public repository metadata and consistency with the published HAACC build case. This review does not certify code safety or current installability.
Decision
Approved
Rationale
Approved for publication because the public repository and build case are inspectable; the signed artifact remains a clearly labeled creator claim.
Reviewer
HAACC Editorial / 2026-07-16
HAACC lens

AI coding stops being a toy when an ordinary builder owns the verification loop end to end.