Public atlas
Approved nations appear on a public map and directory for visitors to browse.
Development roadmap
Building the atlas before the social layer.
MicroAtlas is currently focused on becoming a serious, moderated map and directory for micronations, self-declared states, and experimental civic projects. This roadmap explains what is in scope, what may come later, and what is intentionally excluded from v1.0.
Now: MVP v1.0
The beta proves the registry model first.
v1.0 is about whether MicroAtlas can collect, review, and publish useful atlas entries without exposing private information or encouraging low-quality submissions.
Nation profiles
Each approved entry can show a short description, flag, public links, and mapped claim context.
Mapped submissions
Beta users can prepare a draft nation and add one primary claim for review.
Moderated publication
Submissions are reviewed before they become visible in the public atlas.
Next: Near-term improvements
Improvements after the first beta feedback.
These are likely directions, not launch promises. The order will depend on tester feedback, moderation needs, and the stability of the core submission workflow.
Clearer submission flow
Improve field guidance, validation, and review feedback so serious submissions are easier to complete.
Search and filters
Help visitors find entries by name, region, claim type, status, or other simple discovery signals.
Richer public profiles
Add careful space for more context, public links, dates, institutions, and community information.
Moderation polish
Improve reporting, review notes, status visibility, and the admin tools needed for a small beta.
Later: Possible future features
Possible only after the foundation is stable.
Later features should support discovery and public records without turning MicroAtlas into a general social network, roleplay game, or conflict simulator.
Optional contact routes
Explore ways to contact listed projects without exposing private account email addresses.
Update history
Let approved entries communicate significant profile changes or corrections over time.
External community directory
Make official websites, forums, wikis, Discord servers, archives, and social pages easier to find.
Carefully limited community features
Consider lightweight follow or watch tools only after the registry and moderation model are reliable.
Not planned for v1.0
Some features are deliberately outside the first release.
These exclusions are product decisions, not permanent judgments. The closed beta needs to prove privacy, moderation, mapping, and publication before adding features that create heavier social or political dynamics.
Public Chat
Direct messages
Wars or conflicts
Public Rankings
Leaderboards
Recognition mechanics
Internal Alliance Systems
Public Comments
Roadmap principle
Useful, moderated, and honest about limits.
MicroAtlas should become a reliable public record before it becomes anything more complex. The roadmap may change as beta testers find real friction in the product.
Items listed as later possibilities are not promises. They are directions under consideration once the core atlas, moderation, and privacy model are stable.
Closed beta
Help test the core atlas workflow.
Beta feedback will shape the submission process, map drawing, moderation rules, public profiles, and discovery tools.