minn adminAbout

How Minn gets made

Human direction.
Agent execution.

Minn Admin is built by Austin Ginder with a team of coding agents. Austin owns the product, sets its direction and decides what ships. The agents turn that direction into researched, tested and documented releases.

Development process

One human sets the direction. The agents build it.

Ideas come from real sites, customers, contributors and the work itself. Austin decides which problems belong in Minn, shapes the outcome and keeps final responsibility for every release.

CustomersShare real-world needs
Ideas
Austin Ginder
Architect & release decision maker

Chooses what gets added, shapes how it should work and decides what ships.

ContributorsBring ideas and insight
Ideas
Research
Agent workstream
Build
Agent workstream
Review
Agent workstream
Verify
Agent workstream
Execution layer
CodingDesignDevelopmentAuditsTestingDocumentationTranslations

Agents handle production work from the first investigation through the final test and documentation pass. The roster can change as the tools improve. The responsibility does not.

m
Minn Admin releaseAustin reviews the result, owns the product and makes the final call to ship.
What stays human

Judgment, taste and accountability.

Product direction

Features start with a real problem. The question is not whether an agent can build something, but whether it belongs in the product.

Release judgment

Tests provide evidence. A human still decides whether the experience is clear, useful and ready for someone else's site.

Responsibility

There is no anonymous machine behind Minn. Austin owns the choices, the maintenance and the response when something goes wrong.

Open development

Inspect the work, not just the story.

The source, release history, roadmap and security policy are all public.

View on GitHubRead the roadmap