krites

Krites is ancient Greek for 'the judge', and judging photographs is the whole job. I built it for an audience of one, my wife: a simple, UI-driven tool (not a command line in sight) that helps her rip through culling 4,000-plus wedding images to her own standards. It leans on local ML rather than a cloud-AI subscription, so it works wherever she is, signal or not. It's since grown an optional AI critic as well, expert feedback on composition, colour and technique, there to help her learn rather than to do the judging for her.

A standard-library security fix forced a Go version bump, and then the release failed because the build image shipped an older toolchain.

The one real user of my photo tool was already faking a feature with a workaround. That workaround was the specification.

A desktop-first photo tool reviewed mostly from a phone, and the CSS grid that refused to behave on the one screen it was being judged on.

A correction to my own post: the culler does contain machine learning, and the distinction I drew between ML and AI does not survive scrutiny.

Dropping the Windows build of a photo tool rather than fixing it, and why that is the right call for a one-person project.

A photo tool that is non-destructive by construction rather than by intention, because the shoot it works on can never be taken again.

A wedding photo culler that contains no machine learning at all, by deliberate choice. Blur, exposure and eyes, done with plain arithmetic.

Launching krites, a local-first wedding photo culler built for one photographer who had four thousand frames and a weekend to get through them.