FLIGHT MANUAL / 04 · SYSTEMS
Module catalog
KMS behaves as one suite, but each mission domain has a clear responsibility and can be diagnosed independently.
Core
Shared runtime services, compatibility patches, performance controls, configuration health, operator commands, and cross-mod integration. Core is required by KMS-authored systems.
Communications
RemoteTech-based RF routing, signal margin, antenna channels, packet throughput, onboard routing capacity, store-and-forward buffers, optical mesh links, access cells, ground gateways, and telemetry adapters.
Science
SCANsat survey state, Tarsier observations, experiment readiness, science storage, return planning, contract quality controls, and a unified checklist surfaced to Mission Control.
Parts
Near Future, Far Future, MOLE, OctoSat, Mk-X, Tarsier, antennas, and KMS-authored mission/network payloads. KMS patches their tech nodes, entry costs, categories, power systems, communications, and science behavior into one career progression.
Visuals
Spectra, Environmental Visual Enhancements, Scatterer, and profile-specific configuration. Full-quality visuals remain optional because they dominate GPU and memory requirements.
Utilities
VesselMover, HyperEdit for explicit testing, editor/flight quality-of-life tools, diagnostics, and repeatable test fixtures. Utility capabilities never silently alter a career state.
Dependency policy
Every component is classified as KMS-owned, redistributable, official-download-only, or local-archive-only. The release catalog records source, version, license expression, module, and acquisition method.
Optional modules declare hard and soft dependencies. A missing soft integration disables that bridge and reports it; a missing hard dependency blocks the affected profile before launch.
Installation profiles
Core establishes the shared runtime. Mission Operations adds communications, navigation, science, and the local console. Advanced Spaceflight adds part families and propulsion. Full Visuals adds the reference Spectra/EVE/Scatterer configuration.
Profiles are operator choices, not separate products. All selected modules still share one versioned compatibility layer and diagnostic vocabulary.