KNOWLEDGE · DATABASE
The Database
The Database is this Captain's persistent reference layer: what you have actually learned, encountered, reconstructed, or confirmed about the universe. It helps answer what something is, what it connects to, what you currently know about it, and what useful actions are available next.
The Database is not omniscient.Entries can be public, known, partial, or unknown. New evidence updates only the subjects it actually supports, while encountered resources, equipment, hulls, activities, locations, organizations, and schematics accumulate into your personal reference over time.
USE IT AS A MAP
The Database helps you follow systems outward from what you already know.
Inspect a resource to follow its processing and production relationships. Inspect a schematic to see its output, required materials, current-station availability, and runs you can make. Inspect an exact physical item to see its realized stats, condition, support, comparison context, provenance, and Science layers. Inspect a location or organization to follow only the relationships your Captain has actually learned.
Known subject→Facts & relationships→Requirements / current support→Useful next action
SCHEMATICS
Important production knowledge can stay visible while you gather the inputs.
Encountered schematics live in their own Database section with Known or reconstruction status. You can pin a schematic to the top of the Database, then use its Info view to see the resources required at your current station and how many complete runs your stored materials support.
NEW EVIDENCE
The Database can change because the world taught you something.
Newly supported entries can be marked NEW until reviewed. That makes the Database useful not only as a static reference, but as a place to notice when combat, exploration, sites, organizations, or other evidence have changed what your Captain knows.