One engine. Every door in.

Run a Kshana PNT-resilience scenario from a TOML definition and return its figures of merit. Returns the human-readable summary followed by the full result JSON (FoMs, curves). Kshana validates SGP4/SDP4, IAU reference frames, Allan deviations, GNSS availability/DOP, ARAIM protection levels, GNSS/INS fusion, and quantum-sensor models against published references. Every kind runs through this one tool, including spectrum (radio-frequency spectrum and waterfall), solar-system, constellation-design and body-pnt (constellations around any body), campaign (chained phases, parameter sweeps, Monte Carlo ensembles and composed scenarios) and the low-Earth-orbit navigation kinds leo-signal, leo-pass, leo-navmsg, leo-pvt, leo-ppp, ntn-positioning and leo-pnt-chain. Call list_scenario_kinds first to discover scenario types and their fields, and list_example_scenarios / get_example_scenario for a complete runnable scenario of a kind.

List every built-in Kshana scenario kind with its description and required/optional TOML fields, as a JSON array. Use this to discover what scenarios can be run and how to construct a valid scenario TOML for run_scenario.

Pre-flight check of a Kshana scenario TOML: verify it parses as TOML and detect its scenario kind, without running it. Returns the detected kind, or a descriptive error for malformed TOML. (run_scenario performs the full validation by executing the scenario.)

List the bundled reference scenarios as JSON: count, and scenarios, an array of name, kind and about (the first sentence of the file's own header comment). Every one is a complete scenario that runs as it stands, so this is the quickest way to a valid TOML for a kind: pick a name, fetch it with get_example_scenario, edit it, run it. Pass kind to list only the examples of one kind (for example spectrum, solar-system, constellation-design, campaign, leo-signal, leo-pass, leo-navmsg, leo-pvt).

Return the TOML text of one bundled reference scenario, byte for byte the file the repository ships under scenarios/. Pass the text (edited or not) to run_scenario, report_scenario, animate_scenario or an export tool. Names come from list_example_scenarios. A scenario that exists in the repository but is not bundled is refused with the reason.

Run a Kshana scenario and return its report: an executive summary, the inputs, every result figure with its unit and its VALIDATED or MODELLED label, the events, the capability rows the run exercised, and a reproducibility record (engine version, scenario and result SHA-256 digests, seed, the command that reproduces it). format is json (default; the machine-readable report.json) or html (the printable, self-contained report.html with the chart embedded). A campaign's report also carries its sweep table or Monte Carlo distribution. The report is a pure function of the scenario: no clock is read.

Run a Kshana scenario and return its time series as an animation. format is svg (default: one animated SVG, no script), html (one self-contained player page) or frames (numbered static SVG frames plus manifest.json, at most 120 frames in a reply). Optional fps (1 to 60, default 12), duration_s (0.5 to 600, default 8) and width (480 to 3840 pixels, default 960). The first content item is a JSON summary of what was drawn: the time range and unit, the chart titles, the number of phases and events, whether a spectrum waterfall is present, the result paths the traces were read from, any series left out, and the file names. The files follow, one content item each, in the order the summary's files lists them. A kind whose result has no sampled time axis is refused with a message that says so. The animation is MODELLED presentation of the run's own numbers; the same scenario and options give byte-identical files.

Report which interoperability export formats apply to a Kshana scenario, without running it: a JSON array with one entry per format (czml, kml, geojson, stk, sigmf) giving applies, the reason when it does not, and spec_url, the published specification the writer follows. CZML (Cesium Language), KML (Keyhole Markup Language), GeoJSON and the STK (Systems Tool Kit) ephemeris .e describe the scenario's geometry; SigMF (Signal Metadata Format) records the samples a spectrum scenario with an [iq] block synthesises. Call this before export_interop.

Export a Kshana scenario in one interoperability format: czml (Cesium Language, for CesiumJS), kml (Keyhole Markup Language, for Google Earth and geographic information system tools), geojson (RFC 7946), stk (Systems Tool Kit ephemeris .e, one file per satellite) or sigmf (Signal Metadata Format recording of a spectrum scenario's synthesised samples). The first content item is a JSON index: format, spec_url and files, each with its suffix (what the command line appends to the output name, for example .czml or .G01.e), bytes, sha256 and encoding. The files follow, one content item each, in index order: utf-8 files as their text, the binary SigMF sample file as base64. A campaign exports each member scenario the format applies to. A format that does not apply is refused with the reason; list_export_formats reports all five at once. Times are Coordinated Universal Time (UTC); the same scenario gives byte-identical files.

Write a GeoJSON route into a Kshana scenario that flies a waypoint track, and return the new scenario TOML (run it with run_scenario). The route is a LineString (or a Feature / FeatureCollection holding one) of longitude, latitude positions; it replaces the scenario's start_lat_deg, start_lon_deg, step_lat_deg, step_lon_deg and waypoints. The kinds that take a route are terrain-nav, terrain-slam, gravity-map and combined-altpnt; any other kind is refused with the reason. Give the two ends of the track, or evenly spaced positions along a straight line: the track kinds fly start + i*step, so any other shape is refused.

Export an orbit scenario's propagated constellation as SP3-c precise-ephemeris text (the standard GNSS post-processing format). Errors if the scenario is not an orbit kind.

Export an orbit scenario's mean elements as a CCSDS 502.0-B-2 OMM (Orbit Mean-Elements Message) catalogue — one OMM per satellite. Errors if the scenario is not an orbit kind.

Export an orbit scenario's propagated constellation as CCSDS OEM 2.0 ephemeris text — the inertial (TEME) state time series carrying position AND velocity, which flight-dynamics tools (GMAT / Orekit / STK) read. This is the velocity-carrying complement of the position-only export_sp3. Errors if the scenario is not an orbit kind.

Run a Kshana scenario and return its reproducibility table as CSV text — the byte-stable table the CLI writes as <scenario>.table.csv and the papers cite. Only these kinds emit one: realtime-frame-eop, lunar-time-budget, lunar-jamming, telecom-timing, leo-navmsg when its encode-decode analysis runs on a kepler16 or kepler-rac message model (the broadcast ephemeris table), and moonlight-service-volume when both export_site_lat_deg and export_site_lon_deg are set. Errors for any other kind (or an invalid scenario); use run_scenario for the figures of merit.