Skip to main content
WORKS / PROJECT RECORD / macOS app

Rockpile

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

vibe-codingmacOSordinary-builder
Publication
Reviewed & published
Build stage
Complete
Format
Software
Creator
Artin
Updated
Evidence at review · 1 checked evidence items

Human review

DecisionApproved
Review scope
Public repository metadata and consistency with the published HACC build case. This review does not certify code safety or current installability.
Rationale
Approved for publication because the public repository and build case are inspectable; the signed artifact remains a clearly labeled creator claim.
Reviewer
HACC Editorial
Review date

Confirmed brief

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 HACC case study that records the creator's release claim.

Explicit unknowns

  • Does not block publication

    The current availability of a downloadable signed build has not been independently rechecked.

  • Does not block publication

    No structured external usability result is recorded yet.

Claims

Creator claimUnverified

The macOS artifact completed signing and notarization.

Evidence record

RepositoryChecked

Public repository

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

Build log

  1. Day 0

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

  2. Day 2

    Produced the first runnable Swift build before visual polish.

  3. Day 5

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

  4. Day 7

    Opened the repository and published the build postmortem.

Failure record

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.

Next verification

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

Falsifier

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

Next ask

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

Help needed
FeedbackCode reviewDistribution