opsvibe.systems

OpsVibe

TechLudditeProjects / Upstream

Projects

Frozen as of 2026-10-18T10:01:16.778449+00:00

Public repositories owned by the TechLuddite account, excluding forks. Choose a repository to inspect its description, ownership and source links. Archived projects remain visible.

Account ownership and non-fork status do not establish original authorship or exclusive ownership of code. Credit and license terms remain with the respective authors and projects.

Frozen as-of snapshot. Source links and states reflect the captured evidence, not live activity.

GitHub search can lag and is capped at 1000. No claim of all historical contributions. Metadata homepage links do not establish uptime. Prior snapshot featured a subset, so coverage growth does not establish new contributions.

Upstream

As of 2026-11-06T17:39:31.796502+00:00

All discovered public authored pull requests to other owners in this frozen snapshot. Every entry was checked on its source repository. Proposal state and acceptance are kept separate.

Upstream is refreshed at generation time. Projects and all other content remain frozen.

Static capture refreshed for this generation, not runtime live activity. GitHub search may lag or change during capture and is capped at 1,000 results. No claim of all historical contributions. Open PRs are proposals, not shipped work.

Merged

btsouth/coderev

btsouth/toolport

nixfred/infomarchy

omacom/gliff

perminder-klair/omarchy-controller-control

Open proposals

Closed-unmerged

Operator-directed content baseline, frozen as of the source snapshot. Biography and acknowledgments are retained from the original homepage, with Twitch and scope corrections. They are not independently reverified portfolio-wide claims.

About

I'm a technical services director at a managed service provider. Nearly thirty years of that career has been hardware, networks, servers, and eventually the security decisions. Programming was the one thing I deliberately left to other people.

The AI shift made that position impractical. My assumption is that you can't make sound security and service decisions about tooling you've never used hands-on, and the use cases, supply chains, and data flows underneath managed services are all changing at once. These projects are how I'm closing that gap: built in public, and honest about what went wrong along the way.

Several of these apps started as one-shot generations in an AI studio and were then audited line by line. Most shipped with a postmortem in the repo, because the bugs weren't random. They fell into recurring shapes, and the worst of them were apps reporting results they hadn't actually measured. The house rules here came directly from those postmortems.

None of this is an endorsement of how AI is currently being deployed. It's an attempt to understand it properly, which I believe is the only responsible position for someone making these calls.

Support

If one of these tools saved you an afternoon, here are the practical support options. Check each repository for its license and terms:

Bug reports and pull requests are practical ways to help. Check each repository for its issue settings and contribution guidance.