How luiscaballero01/modeloparcialeva-obj1-1c2026 works
This is a small domain simulation of NERV’s EVA units, pilots, and the headquarters that manages them. The principal workflow is that an operator asks headquarters to attempt a synchronization; headquarters checks the EVA and pilot conditions, then synchronization changes training and, where applicable, EVA energy. Headquarters also registers both domain types and reports base-wide statistics and pilot-specific usability and satisfaction. The graph follows the README’s documented responsibilities; no source excerpts were provided, so it does not assert implementation details beyond those relationships.
Main entry points: nerv.wlk Headquarters · pilotos.wlk Asuka · evas.wlk EVA-01 Proto
Components 8
NERV Base
- Headquarters
nerv.wlk
EVA Units
- EVA-01 Proto
evas.wlk - EVA-02 Modes
evas.wlk - EVA-00 Prototype
evas.wlk
Other components
- Operator
Connections 10
- Operator → Headquarters: requests operations
README.md - Headquarters → EVA-01 Proto: attempts synchronization
README.md - Headquarters → EVA-02 Modes: attempts synchronization
README.md - Headquarters → EVA-00 Prototype: attempts synchronization
README.md - Headquarters → Asuka: checks conditions
README.md - Headquarters → Shinji: checks conditions
README.md - Headquarters → Rei: checks conditions
README.md - Headquarters → Asuka: reports satisfaction
README.md - Headquarters → Shinji: reports satisfaction
README.md - Headquarters → Rei: reports satisfaction
README.md