Classification Integration Strategy
Cross-Project Classification System
Current Projects Involved
- Planet-U
- Carts & CargoShape
- AI HM
- DMP & ASA → Web lattice integration
Implementation Philosophy
“I don’t think I will implement exactly classification - quite written universe and the linked build. It’s one generation based on the discovery users made in the web version.”
Key Decision: Classification data from Star Sailors feeds other projects rather than being reimplemented in each game.
Data Flow Architecture
Classification Sources
- All classification data comes from:
- Star Sailors classifications
- Galaxy projects database
- Mars-specific databases
Value Proposition Questions
- What does social classification make?
- How does build onwards provide value?
User Experience Strategy
Standalone vs. Integrated Experience
Standalone Capability:
- Users get simplified preparation/environment sharing
- More information available outside main web build
- Allows users to play games without web authentication
- Maintains biodiversity maps of Mars/Jupiter ecosystems
Integration Benefits:
- Graphical preparation of compilation game with player chapters
- Allows other projects to be integrated via missions
- Classification projects can be reintroduced
- More engagement across the ecosystem
Technical Architecture
Current Encoding System
- Yellow (wild) → Provincial copy
- Replicating/media → Comparisons
- Playable → Specialized homebox game
- Coordinating → Cross-project coordination
Future Vision
Star Sailors ecosystem connects:
- Simulation in 3D
- Multiple games
- Classification databases
- User progression across projects
Value Proposition
Core Challenge: Find the value proportion this system provides
Benefits:
- Unified user experience across projects
- Leveraged citizen science contributions
- Reduced development overhead (single classification system)
- Enhanced engagement through ecosystem approach
Related: