Systems
- #systems
Every system built here, on one page. Each card says three things and stops there: what it is, whether it has reached real use, and where to get it.
Product means a whole system built for the people whose work it does. Open source means the source is public and the repository’s README is its manual. The badge on each card says which one you are looking at.
A card carrying a month reached real use in that month, and the month comes from version control rather than memory. A card without one is still being built, and says so instead of implying otherwise.
driftless
Portfolio, program and project management where a dishonest status cannot be typed
keycut
Lossless multi-range video cutting that snaps to keyframes instead of lying about it
agent-audit
Audit the skills, instruction files and workflows your AI agents actually read
claude-batch-runner
Declarative parallel agent campaigns with schema-verified results and a cost table
pycube-lut
Read and apply Adobe .cube 3D LUTs, HALD CLUTs and 1D tone curves to NumPy images
redactcam
Face and licence-plate redaction for video, with a second pass that proves the blur landed
sun-track
Solar elevation, a golden-hour band defined over it, and where a GPX track was at a given instant
rigscore
Configuration hygiene checker for AI development environments
Quiet Corners
Census-driven scoring of rural US counties for stability, remoteness and sprawl risk
GrantBridge
Grant consulting as one lifecycle and one system of record, serving both sides of the table
GrantPath
Grant discovery, ranked matches and a gated application pipeline for the people doing the applying
This grid is rendered from data/systems.json — the roster itself, not the list of pages
that happen to exist on this site. A system with no page of its own still appears here.
Where a system has a manual, an installer or release notes, they sit with that system —
on its own page here, or in its repository — rather than in a separate section of the
site.