hoogvliets/mike

hoogvliets is bringing a private downstream Mike build back into the open, one reviewable slice at a time.

Active disclosure work through mid-May 2026, with the fork sitting level with upstream as the slices are prepared for review.

View on GitHub →

This fork is the public face of a downstream Mike build that hoogvliets has been running privately and is now disclosing back to the upstream project. Rather than dropping everything at once, the work is being carved into slices a reviewer can actually read - backend, database, frontend, and the test harness that wraps around them.

The through-line is AGPL disclosure done thoughtfully. There's a sprawling all-in-one PR that puts every downstream change in front of the upstream author, and alongside it a set of narrower disclosures that isolate each layer of the stack on its own terms.

If you're curious what a production Mike fork actually looks like under the hood - hardened backend, real migrations, a test net underneath it all - this is one of the more honest looks you'll get. Click through to GitHub for the depth.

What's in it

Full-fork disclosure A single sweeping PR puts the entire downstream build - data, backend, frontend, tests - in front of upstream all at once.
Frontend and workflow slice The app and project-workflow changes carved out as their own reviewable disclosure.
Hardened backend slice A standalone disclosure of what a production-shaped Mike backend looks like, isolated for focused review.
Database and Supabase slice The data layer pulled out on its own so reviewers can inspect migrations and configuration without wading through the rest.
Test harness first Backend tests and CI land ahead of the source changes they cover, giving the disclosure a safety net before the substance lands.

Direction

infrastructurecomplianceworkflow

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.

🟢 #127 Disclose downstream AGPL changes +25,156 -12,156 12d ago by hoogvliets ↗ analysis ↗ GitHub

This PR discloses the complete downstream source changes made to this AGPL-3.0 project. It is intentionally broad so the original maintainer can inspect the full modified codebase in one place. Smaller topic PRs are also…

🟢 #131 Disclose backend hardening and route changes +9,750 -5,851 12d ago by hoogvliets ↗ analysis ↗ GitHub

Part of the downstream AGPL disclosure. This PR isolates backend hardening and route changes for easier review.

🟢 #129 Disclose backend test coverage and CI workflow +11,471 -143 12d ago by hoogvliets ↗ analysis ↗ GitHub

Part of the downstream AGPL disclosure. This PR isolates backend test coverage and CI additions for easier review.

🟢 #130 Disclose database migrations and Supabase config +4,937 -517 12d ago by hoogvliets ↗ analysis ↗ GitHub

Part of the downstream AGPL disclosure. This PR isolates database migration and Supabase configuration changes for easier review.

🟢 #128 Disclose frontend app and project workflow updates +4,295 -6,166 12d ago by hoogvliets ↗ analysis ↗ GitHub

Part of the downstream AGPL disclosure. This PR isolates the frontend app and project workflow changes for easier review.

📝 hoogvliets opens the kimono on a full Mike fork rebuild 0 commits — infrastructuresecurity draft

A single sprawling disclosure PR puts every downstream change - database, backend, frontend, tests - in front of the upstream author at once.

📝 hoogvliets opens the books on a downstream fork 0 commits — chat-uiworkflow draft

A sprawling private build comes back into the open, sliced into pieces a reviewer can actually read.

📝 hoogvliets ships a hardened backend for upstream review 0 commits — infrastructuresecurity draft

A sweeping backend disclosure that quietly reveals what a production Mike fork actually looks like under the hood.

📝 hoogvliets makes the data layer reviewable on its own terms 0 commits — multi-tenantinfrastructure draft

A downstream fork's database work gets carved out into a standalone slice so AGPL reviewers can actually inspect it.

📝 hoogvliets puts a test harness around the disclosure 0 commits — infrastructurecompliance draft

A downstream fork lands the safety net first - backend tests and CI before the source changes they cover.

Threads of work (detailed view)

5 threads have been distilled into posts.

Pull requests (detailed view)

5 PRs touch this fork — inbound (filed against it) or outbound (filed from it). State icons match the editorial dashboard.