📚 Complete documentation reorganization: 🗂️ Structure: - docs/global/ → Complete project documentation (all original files) - docs/engines/ → 10 engine-specific docs with focused responsibilities - docs/serveur/ → Server coordinator and inter-engine communication - docs/client/ → Smart Client interface and user experience 🔧 Engine Documentation: - Designer: Vehicle design with AI assistance (1-2 designs/tick) - Economy: Market simulation and dynamic pricing - Event: Breakthrough system and global events - Factory: Factorio-like production with belts/assemblers - Intelligence: Metrics collection (3.1GB adaptive) + reconnaissance - Logistic: Supply chains and convoy management - MacroEntity: Companies, diplomacy, administration (1000 pts/day) - Map: Procedural generation (218+ elements) + chunk streaming - Operation: Military strategy and adaptive AI generals - War: Multi-chunk combat and persistent frontlines 📋 Each engine doc includes: - Core responsibilities and system overview - Key mechanics from relevant design documents - Communication patterns with other engines - Implementation notes and architecture details 🎯 Navigation optimized for: - Engine developers (focused system details) - System architects (coordination patterns) - Game designers (mechanics integration) 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| README.md | ||
Designer-Engine Documentation
Engine Overview
Designer-Engine handles autonomous vehicle conception for AI companies and provides design assistance for players.
Key Responsibilities:
- Vehicle design generation (1-2 designs globally per tick)
- Component grid placement and validation
- Blueprint management and evolution
- AI-driven design optimization
Core Systems
Vehicle Design System
From systeme-militaire.md:
- Grid-based Component Placement: Irregular chassis shapes with precise component positioning
- Interface Mechanics: Pick/place with A/E rotation, R for snap toggle
- Template Support: Save/load vehicle blueprints
- Validation: Ensure design constraints (weight, power, armor coverage)
Design Evolution
From arbre-technologique.md:
- Progressive Evolution: T-72 → T-80 → T-90 design lineage
- Technology Integration: New components unlock through research
- Doctrine Adaptation: Designs adapt to military doctrine preferences
Performance Requirements
From architecture-technique.md:
- Design Rate: 1-2 vehicle designs globally per tick maximum
- Autonomous Operation: AI companies generate designs independently
- Player Assistance: Provide design suggestions and optimization
Engine Architecture
Core Classes
class DesignerEngine {
// Design management (1-2 designs globally per tick)
std::unique_ptr<VehicleDesign> createDesign(const std::string& type);
void validateDesign(const VehicleDesign& design);
void saveBlueprint(const VehicleDesign& design, const std::string& name);
// Blueprint evolution
void evolveBlueprintsFromExisting(); // T-72 → T-80 → T-90
// Performance monitoring
double getDesignRate() const;
size_t getPendingDesigns() const;
};
Communication with Other Engines
- War-Engine: Receives combat effectiveness feedback for design optimization
- Economy-Engine: Gets cost constraints and production capabilities
- Intelligence-Engine: Receives reconnaissance data on enemy designs
- MacroEntity-Engine: Gets company design preferences and doctrine
- Event-Engine: Processes breakthrough events for new technologies
Key Design Documents
systeme-militaire.md- Vehicle design system detailsarbre-technologique.md- Technology progression and design evolutionarchitecture-technique.md- Performance specificationsmecaniques-jeu.md- Research integration
Implementation Notes
- Focus on autonomous AI design generation
- Player assistance tools for design optimization
- Blueprint persistence and sharing system
- Technology integration from research breakthroughs