Roadmap: toward an AI-governed Go admin framework

[lwnmengjing]

The next stage of mss-boot is not about generating more CRUD screens. The direction is to make the project more production-maintainable and easier for both humans and AI agents to understand.

Current roadmap focus:

• Agent-readable project context: repository memory, module boundaries, API contracts, test commands, and release rules.
• Governance-first admin workflows: RBAC, menu/API permissions, configuration, audit logs, and explainable policy behavior.
• Release discipline: compatibility matrix, safer beta/prod separation, CI stability, changelog, image/version traceability, and rollback notes.
• Contributor experience: better good first issues, faster reviews, clearer local setup, and documentation that turns real issues into reusable knowledge.
• Community operations: use GitHub Discussions for Q&A/RFC/roadmap, and keep external promotion tied back to GitHub.

One important scope note: the virtual model feature is downgraded and on the deprecation path. We may still accept small safety fixes for existing installations, but we do not plan to expand it as a main product direction.

Feedback wanted:

• What should be easier to understand when adopting mss-boot?
• Which workflows should have better docs or examples first?
• What would make you comfortable contributing a first PR?
• Which production signals matter most to you: RBAC, audit, deployment, observability, release traceability, or something else?