I'm not sure I agree here. In the universe representation I think only actual information should be stored, not calculated fields. The engine can 'cache' all this info if that is good for performance, and if needed for the client we can make a 'calculated fields' API calln to avoid reimplementing things in javascript, but I think we should really restrict the API definitions (of which the universe representation is the most important) to actual unique data.

What I think we should do is simply fill it as we develop. What I envision is this: whenever someone writes or updates a module, always also write/update the *unit* tests (which is a minimal test of all different corner cases, exceptions, etc, of that particular module), and update the *integration test*, which should cover all representation issues (ie use all fields, with multiple instances if needed for e.g. immunities vs hab ranges) and which is meant to ensure consistency between modules.