How deontologician/evofighters works
Main Components
a) Simulation Core:
• Arena System (manages encounters between creatures)
• Creature Management System
• DNA Processing Pipeline
• Evolution Engine
b) DNA Processing Pipeline (Key Subsystem):
• Parser
• Compiler
• AST Evaluator
• Mutation Engine
Component Relationships
Top Level:
[Simulation Controller] → [Arena] → [Encounter Manager]
• ↓
[Population Manager] ← → [DNA Processing Pipeline]
• ↓
[Save/Load System] ← → [Statistics/Evaluation]
DNA Processing Pipeline (Detail View):
[Raw DNA] → [Parser] → [AST Builder] → [Compiler] → [Evaluator] → [Action Decision]
• ↑ ↓
• [Grammar Rules] ← - - - - - - - - - - [Mutation Engine]
Specific Implementation Details
• Rectangles: Core processing components
• Hexagons: Decision points
• Diamonds: Evaluation steps
• Blue: Core simulation components
• Green: DNA processing components
• Yellow: Data storage/persistence
• Red: Critical decision points
Key Processes to Highlight
a) Creature Lifecycle:
[Creation] → [DNA Parsing] → [Compilation] → [Evaluation] → [Action Execution]
b) Evolution Cycle:
[Population] → [Selection] → [Mating] → [Mutation] → [New Generation]
Important Elements
• Both Python and Rust implementations as parallel systems
• Grammar.bnf file's role in DNA parsing
• Save/load functionality
• Encounter system's flow
• Demonstrate the mutation and breeding mechanics
Technical Details to Note
• Error handling paths
• Where parallelization is possible
• System boundaries
Implementation-Specific Notes
For the Rust implementation, highlight:
• AST optimization paths
• Pre-compilation optimizations
• Memory management boundaries
For the Python implementation, show:
• PyPy optimization points
• Interpretation paths