jthacker48/mike

A Rule26-hosted instance of Mike, being wired into an existing AI infrastructure stack as a sibling service.

Five commits in, last pushed a week before MikeWatch first noticed it - early-stage but recently active, with all energy on plumbing.

This fork of Mike belongs to jthacker48 - Jeremy Thacker - who is setting Mike up to run alongside other AI services inside Rule26's environment. The work so far is deployment-focused: making Mike fit cleanly into a server room that already hosts other tools.

There are no product changes here yet. If you tried this fork today, you'd essentially be trying Mike - the interest is in where it's being plugged in, not what it does differently. Rule26 appears to be the operator betting on Mike as part of a broader AI lineup.

If you're curious how a small shop is hosting Mike for real-world use, this is one to watch. The direction is operational rather than experimental - getting Mike into production next to its siblings.

What's in it

Rule26 deployment Mike is being set up as a sibling service inside Rule26's existing AI infrastructure rather than run as a standalone experiment.

Direction

infrastructureintegration

Activity

Themed changes and pull requests touching this fork, newest first. Themed changes that haven't been turned into a public post yet still appear — they're real work even without a published writeup.

📝 jthacker48 wires Mike into the Rule26 server room 5 commits 14d ago infrastructure draft

Jeremy Thacker is plugging the Mike fork in as a sibling service on Rule26's AI infrastructure - pure plumbing, no product changes.

Threads of work (detailed view)

1 thread have been distilled into posts.

jthacker48 wires Mike into the Rule26 server room

Jeremy Thacker is plugging the Mike fork in as a sibling service on Rule26's AI infrastructure - pure plumbing, no product changes.

infrastructure

5 commits · latest 14d ago