campaign-jam-spoof-holdover-integrityOne chained run: nominal, jamming, spoofing, holdover, an integrity alarm and recovery.Your mission. Its failure. A scenario that shows it.
Pick a sector: defence, Earth orbit, the Moon and deep space, the air, the sea, the road, the railway, critical infrastructure, telecom, or the lab. Each names the question it answers and the threat, and lays out the real bundled scenario files that demonstrate it. Every card opens that exact run in Kshana Studio. PNT means positioning, navigation and timing; GNSS means the Global Navigation Satellite Systems (GPS, Galileo, BeiDou and GLONASS).
- Free core every scenario and chart on this page
- Pro the Pareto front of a design space, uncertainty and sensitivity, and a one-command mission dossier
- Custom study models calibrated to your hardware, done for you
The matrix is drawn from the scenario cards below when the page script loads.
Select a cell to open that sector.
Ten sectors. One engine.
Each sector: its question, the threat, the files that answer it and a chart from a real run. Cards with a dashed edge carry their figures on the card: each is read from a recorded run of the engine, and opens in Kshana Studio on the view that reproduces it, beside the engine's own report, the scenario file and the command.
How long do our own navigation and timing stay trustworthy under jamming and spoofing, and which layers keep us in spec?
Every satellite's C/N₀ under a jammer
jamming-demo.toml · seed 1Open in Kshana StudioReportjamming-demoA ground jammer near a receiver: every satellite's signal-to-noise and lock state as it comes on.Recorded runOpen in Kshana Studiospoof-detectspoof-detectA fused spoof detector: consistency across satellites, receiver gain and signal shape, and which monitor fires.Recorded runOpen in Kshana Studiospoofspoof-attackAn active time-spoofing attack: does each clock's integrity monitor catch the push?Recorded runOpen in Kshana Studiospoofspoof-meaconingA delayed rebroadcast of real signals drags the time solution; the detector has its own bound.Recorded runOpen in Kshana Studioconflict-resilienceconflict-resilienceLayered navigation under rising threat intensity: the chance of losing every layer at once.Recorded runOpen in Kshana Studiocombined-altpntcombined-altpntGravity, magnetic and terrain matching fused into one navigator that needs no satellites.Recorded runOpen in Kshana Studiogravity-mapgps-denied-gravity-navAn hour without satellites, navigating on a gravity map with a quantum sensor.Recorded runOpen in Kshana Studioterrain-navterrain-navTerrain-referenced navigation: measured heights matched to a map while satellites are denied.Recorded runOpen in Kshana Studiol-band-waterfall-jammingThe L-band spectrum as a waterfall under several jammers, band by band.campaign-sweep-jammer-powerThe same receiver while the jammer's power is swept: where tracking gives out.leo-resilience-gnss-jammed-leo-carriesGNSS is jammed and a low-orbit layer carries the user, with integrity maintained.leo-resilience-spoof-monitorsLow-orbit signals under spoofing: which monitor sees which spoofer.Figures of merit
- Effective C/N₀ (carrier-to-noise density) and lock state per satellite under a jammer
- Spoof verdict and which detection layer fired
- Total-loss probability against threat intensity for layered PNT
- Bounded alternative-PNT position error through the outage
Run every scenario file in this sector in Kshana Studio or from any install, read the ledger and export reports.
Custom: export-controlled resilience work under the appropriate clearance and NDA (non-disclosure agreement).
Request a studyDefensive use only: protecting your own navigation and timing, resilience assessment and holdover planning. Kshana does not model targeting, interception or guidance, and it is not an RF signal simulator or a receiver.
Does my spacecraft see enough navigation satellites, how long does its clock hold time between fixes, and what would a low-orbit navigation layer add?
GNSS availability for a spacecraft inside the shell
orbit-gnss-challenged.toml · seed 7Open in Kshana StudioReportorbit-gnss-challengedNavigation-satellite availability for a spacecraft inside the constellation shell, from real geometry.Recorded runOpen in Kshana Studioorbitorbit-molniyaThe same question for a highly eccentric orbit that climbs above the constellation.Recorded runOpen in Kshana Studioorbitorbit-sgp4-gpsAvailability from the real GPS constellation, propagated from two-line element sets.Recorded runOpen in Kshana Studioorbitorbit-multignssGPS and Galileo together: how much a second constellation adds overhead.Recorded runOpen in Kshana Studioslot-timingslot-timing-ocxo-leoHow long an oven-controlled crystal clock on a small low-orbit satellite stays inside its routing slot.Recorded runOpen in Kshana StudioephemerisephemerisWhere the satellite is right now, and the ground track it draws.Recorded runOpen in Kshana StudiopassespassesGround-station pass prediction for the operations team.Recorded runOpen in Kshana Studiolink-budgetlink-budgetA one-way link budget, from transmitter power to receiver margin.Recorded runOpen in Kshana Studiospace-weatherspace-weatherThe space-weather environment a mission flies through.Recorded runOpen in Kshana Studioconstellation-multi-gnss-coverageAll four global systems together, scored over the whole Earth for a sidereal day.leo-pnt-mega-shellA low-orbit navigation mega-constellation in four shells, scored as a coverage and geometry map.leo-pass-vs-gnss-cn0One low-orbit navigation pass beside the Galileo satellites in view: signal strength through the pass.leo-doppler-positioningA position fix from the Doppler shift of low-orbit satellites alone.meo-leo-fused-pvtGPS and Galileo fused with a low-orbit navigation layer: what the extra layer does to the fix.leo-ppp-convergencePrecise point positioning: how much sooner it converges once low-orbit satellites are added.leo-pnt-end-to-endOne low-orbit navigation system end to end: signal design, pass link budget, navigation message and the fix.A low-orbit navigation layer, scored before it flies.
LEO-PNT (low Earth orbit positioning, navigation and timing): thousands of satellites a few hundred kilometres up, close enough to be heard indoors and moving fast enough to fix a position from Doppler. The engine designs and scores the constellation (the leo-pnt-mega-shell run, in the orbit console below) and follows the signal from its design to the fix, for any system: the cards around this one are recorded runs of those kinds.
- The kinds behind it
leo-signalsignal designleo-passpass link budgetleo-navmsgnavigation messageleo-pvtposition and timeleo-pppprecise positioningntn-positioning5G from orbitleo-pnt-chainend to end
Figures of merit
- GNSS availability and dilution of precision from real geometry
- Clock time error through each gap in coverage
- Satellites in view and PDOP (position dilution of precision) over the whole Earth, for any constellation you design
A geostationary user: set the user orbit in an orbit-kind scenario, the way orbit-molniya sets a highly eccentric one.
Run every scenario file in this sector in Kshana Studio or from any install, read the ledger and export reports.
Pro: architecture trade studies ranked on a figure of merit. Pro: clock digital twins calibrated to your device's published Allan budget.
Request a Pro evaluationWill a lander, a rover or an orbiter at the Moon, at Mars or further out get a trustworthy position and time, and what does the local time scale add to the error budget?
Lunar south-pole integrity, from a real run
lunanet-araim.toml · deterministic, no seedOpen in Kshana StudioReportmoonlight-service-volumeCoverage and protection levels of a lunar navigation service across its service volume.Recorded runOpen in Kshana Studiolunar-integritylunanet-araimIntegrity for a landed receiver in the lunar south-pole region.Recorded runOpen in Kshana Studioearth-gnss-lunarearth-gnss-lunarHow much of Earth's navigation signal still reaches a receiver at the Moon.Recorded runOpen in Kshana Studiolunar-jamminglunar-jammingJamming a lunar surface user, satellite by satellite.Recorded runOpen in Kshana Studiolunar-time-offsetlunar-time-offsetThe relativistic rate between Earth and Moon clocks, against the published band.Recorded runOpen in Kshana Studiolunar-time-budgetlunar-time-budgetThe end-to-end time-error budget for coordinated lunar time, clock class by clock class.Recorded runOpen in Kshana Studiolunar-vlbilunar-vlbiTwo Earth radio telescopes observing a beacon on the lunar near side.Recorded runOpen in Kshana Studiocislunar-observabilitycislunar-observabilityCan a small constellation near the Moon be tracked, and over how long an arc?Recorded runOpen in Kshana Studiolunar-attack-surfacelunar-attack-surfaceThe signal-security attack surface for navigation on the lunar surface.Recorded runOpen in Kshana Studiolunar-beaconlunar-beaconSurface beacons that augment a lunar orbital navigation service.Recorded runOpen in Kshana Studiomars-pntmars-pnt-lmoA low Mars orbiter navigating against a relay constellation.Recorded runOpen in Kshana Studiomars-pntmars-pnt-surfaceA lander on the rotating surface of Mars.Recorded runOpen in Kshana Studiomars-pntmars-pnt-transferA spacecraft arriving at Mars on a high, eccentric arc.Recorded runOpen in Kshana Studiolunar-relay-constellationRelays in frozen elliptical orbits that linger over the lunar south pole, scored over the whole Moon.mars-orbit-pntA low Mars orbiter with a relay constellation and a deep-space range from Earth.europa-surface-pntA lander on Europa, with relays and an Earth link that rises and sets once a Europan day.solar-system-tourEvery body the engine knows at one epoch, from the Sun to Titan.Figures of merit
- Lunar service-volume coverage and protection levels
- Earth-GNSS reception at lunar distance
- Lunar time rate against the published band, and the end-to-end time-error budget
- Relay-navigation error in Mars orbit, on the surface and in transfer
Run every scenario file in this sector in Kshana Studio or from any install, read the ledger and export reports.
Pro: clock digital twins calibrated to your device's published Allan budget. Pro: architecture trade studies ranked on a figure of merit.
Request a Pro evaluationAfter a jammer takes GNSS away, how long does my UAS (uncrewed aircraft system) stay inside its position budget, and is integrity available on my route?
Dual-constellation integrity, from a real run
araim-gps-galileo.toml · deterministic, no seedOpen in Kshana StudioReportsmall-uas-jammed-navA small drone loses satellites to a jammer: how long each inertial unit keeps it in budget.Recorded runOpen in Kshana Studiojammingjamming-demoA ground jammer near a receiver: every satellite's signal-to-noise and lock state as it comes on.Recorded runOpen in Kshana Studiognss-insgnss-insSatellite navigation blended with a strapdown inertial navigator, then coasting through an outage.Recorded runOpen in Kshana Studioins-trn-coastins-trn-coastInertial coasting with terrain fixes: position error against coast time.Recorded runOpen in Kshana Studiointegrityintegrity-raimReceiver integrity-monitoring availability over a GPS-like constellation.Recorded runOpen in Kshana Studiointegrityaraim-gps-galileoAdvanced integrity monitoring with GPS and Galileo together.Recorded runOpen in Kshana Studioaraim-reference-checkaraim-reference-checkThe engine's protection levels against the working group's own worked examples.Recorded runOpen in Kshana Studiognss-simgnss-sim-raimPseudoranges simulated with ionosphere and troposphere, then checked for integrity.Recorded runOpen in Kshana Studiocampaign-sweep-jammer-powerThe same receiver while the jammer's power is swept: where tracking gives out.Figures of merit
- Seconds inside the position budget, flight-controller MEMS (micro-electromechanical systems) against a tactical-grade IMU (inertial measurement unit)
- Horizontal and vertical protection levels against the alert limits
- Coast error against coast duration
Run every scenario file in this sector in Kshana Studio or from any install, read the ledger and export reports.
How far across the water does a jammer take GNSS away, would a position push be caught, and how long can a ship coast into port?
Free-inertial coast by IMU grade
Drawn from the recorded run of maritime-port-approach-coast.toml when the page script loads.
maritime-port-approach-coast.toml · deterministic, no seedOpen in Kshana StudioReportmaritime-strait-jammingA shore or ship jammer across a strait: jammer-to-signal ratio and satellites kept.Recorded runOpen in Kshana Studiospoof-detectNewmaritime-spoof-position-pushA spoofer drags a ship's reported position; which detectors catch it, and when.Recorded runOpen in Kshana Studioins-trn-coastNewmaritime-port-approach-coastSatellites jammed on the port approach: how long each inertial grade can coast.Recorded runOpen in Kshana Studiospoof-detectspoof-detectA fused spoof detector: consistency across satellites, receiver gain and signal shape, and which monitor fires.Recorded runOpen in Kshana Studioinertialimu-deadreckoningDead reckoning through an outage: a cold-atom accelerometer against a navigation-grade unit.Recorded runOpen in Kshana Studioclockclock-holdoverThe reference case: a clock synchronised to satellites, then free-running when they are denied.Recorded runOpen in Kshana Studiocampaign-shared-jammer-sea-roadOne jammer, a ship and a car: the same transmitter, two very different outcomes.leo-vertical-rail-maritimeThe bundled rail and maritime cases again, with a low-orbit layer added.One jammer, a ship and a car.
A campaign binds one jammer, its power and its position, into two ordinary jamming runs: a ship in a strait and a car on a coast road. Same transmitter, two very different outcomes, in one reproducible run.
Figures of merit
- Mean J/S (jammer-to-signal ratio) and satellites tracked under a shore jammer
- Spoof verdict and which detection layers fired for a position push
- Seconds of free-inertial coast before the harbour position budgets
The jamming footprint under What a run shows maps maritime-strait-jamming over a grid of ship positions, one engine run per cell.
Run every scenario file in this sector in Kshana Studio or from any install, read the ledger and export reports.
How far does a car drift under an overpass or past a roadside jammer, and does it stay inside its lane-level budget?
Through the urban canyon, from a real run
automotive-urban-canyon.toml · seed 7Open in Kshana StudioReportautomotive-urban-canyonA car through an urban canyon, an underpass and a roadside jammer, against a lane budget.Recorded runOpen in Kshana Studiognss-insgnss-insSatellite navigation blended with a strapdown inertial navigator, then coasting through an outage.Recorded runOpen in Kshana Studioins-trn-coastins-trn-coastInertial coasting with terrain fixes: position error against coast time.Recorded runOpen in Kshana Studiointegrityintegrity-raimReceiver integrity-monitoring availability over a GPS-like constellation.Recorded runOpen in Kshana Studiojammingjamming-demoA ground jammer near a receiver: every satellite's signal-to-noise and lock state as it comes on.Recorded runOpen in Kshana Studiocampaign-shared-jammer-sea-roadOne jammer, a ship and a car: the same transmitter, two very different outcomes.leo-vertical-autonomous-vehicleAn autonomous vehicle through an urban canyon, with a low-orbit layer added.One jammer, a ship and a car.
A campaign binds one jammer, its power and its position, into two ordinary jamming runs: a ship in a strait and a car on a coast road. Same transmitter, two very different outcomes, in one reproducible run.
Figures of merit
- Position error through the underpass and the jammer, automotive MEMS against a tactical-grade IMU, against a lane-level budget
- Protection level against an alert limit you set
- Lock state under the jammer
Run every scenario file in this sector in Kshana Studio or from any install, read the ledger and export reports. Commercial licence of the open core: closed or proprietary integration without AGPL obligations.
How many seconds into a tunnel can a train still tell which track it is on?
Seconds into a tunnel, by IMU grade
Drawn from the recorded run of rail-tunnel-coast.toml when the page script loads.
rail-tunnel-coast.toml · deterministic, no seedOpen in Kshana StudioReportrail-tunnel-coastA train in a tunnel: seconds of inertial coast before it can no longer tell its track.Recorded runOpen in Kshana Studioins-trn-coastins-trn-coastInertial coasting with terrain fixes: position error against coast time.Recorded runOpen in Kshana Studioterrain-slamterrain-slamRecursive terrain-referenced navigation that keeps bounding the inertial drift.Recorded runOpen in Kshana Studiognss-insgnss-insSatellite navigation blended with a strapdown inertial navigator, then coasting through an outage.Recorded runOpen in Kshana Studiointegrityintegrity-raimReceiver integrity-monitoring availability over a GPS-like constellation.Recorded runOpen in Kshana Studioleo-vertical-rail-maritimeThe bundled rail and maritime cases again, with a low-orbit layer added.Figures of merit
- Seconds of free-inertial coast before the track-discrimination budget and a wider one
- The error term that dominates at each crossing
- How a terrain or map fix bounds the coast
Run every scenario file in this sector in Kshana Studio or from any install, read the ledger and export reports.
If GNSS time is lost or spoofed, how long do a power grid, a trading venue or a data centre keep traceable time, and which clock carries them?
A Monte Carlo clock ensemble, from a real run
clock-ensemble.toml · seed 42Open in Kshana StudioReportclock-holdoverThe reference case: a clock synchronised to satellites, then free-running when they are denied.Recorded runOpen in Kshana Studioclockclock-holdover-labsrA laboratory strontium optical clock against a chip-scale atomic clock.Recorded runOpen in Kshana Studioclockclock-ensembleA Monte Carlo ensemble of holdover runs: the spread, not one lucky draw.Recorded runOpen in Kshana Studiosweepsweep-clock-stabilityHow holdover scales with clock stability, as a trade study.Recorded runOpen in Kshana Studiospoofspoof-attackAn active time-spoofing attack: does each clock's integrity monitor catch the push?Recorded runOpen in Kshana Studiospoofspoof-meaconingA delayed rebroadcast of real signals drags the time solution; the detector has its own bound.Recorded runOpen in Kshana StudiotimetransfertimetransferOptical time transfer between satellites against classical two-way radio transfer.Recorded runOpen in Kshana Studiocampaign-monte-carlo-clock-holdoverA seeded Monte Carlo ensemble of a free-running clock, against its closed form.campaign-spectrum-holdover-integrityJamming read from the spectrum, clock holdover, then integrity on Galileo alone.leo-timing-utcTime transfer to Coordinated Universal Time from low-orbit satellites, against signal strength and the receiver's oscillator.leo-vertical-critical-infrastructure-timingCritical-infrastructure timing through holdover, with low-orbit time as the second source.Figures of merit
- Clock time error through holdover against the guard you set
- Holdover time by oscillator class, from chip-scale to optical
- Monte Carlo ensemble spread
- Time-spoof detection by the clock's integrity monitor
Power grid and finance: your sector's time-accuracy limit goes in as threshold_ns.
Run every scenario file in this sector in Kshana Studio or from any install, read the ledger and export reports.
Pro: clock digital twins calibrated to your device's published Allan budget. Pro: audit-grade, reproducible evidence packs for a review.
Request a Pro evaluationIf the GNSS time reference is lost, does my network clock stay inside the ITU-T masks, and for how long?
Time error against the ITU-T masks
telecom-prtc-holdover-24h.toml · seed 20260925Open in Kshana StudioReporttelecom-prtc-holdover-24hA rubidium timing reference loses satellites for a day: time error against the telecom masks.Recorded runOpen in Kshana Studiotelecom-timingtelecom-tie-ingestBring your own time-error series and score it against the telecom masks.Recorded runOpen in Kshana Studioclockclock-holdoverThe reference case: a clock synchronised to satellites, then free-running when they are denied.Recorded runOpen in Kshana Studioclockclock-ensembleA Monte Carlo ensemble of holdover runs: the spread, not one lucky draw.Recorded runOpen in Kshana Studioquantum-time-transferquantum-time-transferA trusted quantum timing chain: transfer, secure dissemination and anomaly detection.Recorded runOpen in Kshana StudiotimetransfertimetransferOptical time transfer between satellites against classical two-way radio transfer.Recorded runOpen in Kshana Studiospoofspoof-attackAn active time-spoofing attack: does each clock's integrity monitor catch the push?Recorded runOpen in Kshana Studiontn-5g-positioningPositioning from a 5G non-terrestrial network downlink in the mobile-satellite S band.leo-vertical-5g-network-timingBase-station timing for a mobile network: holdover, and time from low orbit.Figures of merit
- MTIE (maximum time interval error) and TDEV (time deviation) against ITU-T masks, with a pass, a fail and a margin per mask
- Timing error 95th percentile, holdover time and availability
- Time-spoof detection by the clock's integrity monitor
Run every scenario file in this sector in Kshana Studio or from any install, read the ledger and export reports.
Pro: clock digital twins calibrated to your device's published Allan budget. Pro: audit-grade, reproducible evidence packs for a review.
Request a Pro evaluationThe engine carries ITU-T G.8272, G.8272.1, G.8273.2 and G.8271.1 limits, including PRTC-A, PRTC-B and ePRTC (primary reference time clock, classes A and B, and enhanced).
Can I reproduce, extend and cite a PNT result, down to the seed?
Holdover against clock stability, a trade study
sweep-clock-stability.toml · seed 42Open in Kshana StudioReportsweep-clock-stabilityHow holdover scales with clock stability, as a trade study.Recorded runOpen in Kshana Studioquantum-tradequantum-tradeQuantum against classical navigation, with measured clock-stability data ingested.Recorded runOpen in Kshana Studiohybridhybrid-pntAn all-quantum navigation suite against an all-classical one, with satellites denied.Recorded runOpen in Kshana Studiopvtpvt-abmfSingle-point positioning from real measurements logged at a surveyed ground station.Recorded runOpen in Kshana Studiocislunar-observabilitycislunar-observabilityCan a small constellation near the Moon be tracked, and over how long an arc?Recorded runOpen in Kshana Studiolunar-vlbilunar-vlbiTwo Earth radio telescopes observing a beacon on the lunar near side.Recorded runOpen in Kshana Studioimpairment-evalimpairment-evalA testbed that scores radio-impairment detectors on labelled cases.Recorded runOpen in Kshana Studiosweep-ndsweep-nd-inertialA many-axis parameter sweep over an inertial scenario.Recorded runOpen in Kshana Studioleo-navmsg-fit-interval-tradeA low-orbit navigation message: range error against how long one message is fitted for.leo-band-tradeA band trade for low-orbit navigation signals, from ultra-high frequency to a wide C band.Figures of merit
- Every figure with its unit and provenance
- Deterministic from scenario, seed and engine version
- A citable DOI (Digital Object Identifier) for every release
Run every scenario file in this sector in Kshana Studio or from any install, read the ledger and export reports. Commercial licence of the open core: closed or proprietary integration without AGPL obligations.
Custom study: training and consulting on quantum and classical PNT performance analysis.
Request a studyAny constellation, around any body.
Design a constellation around the Earth, the Moon or Mars and read what a receiver gets from it. Each view replays a real engine run: the orbits are the run's own, re-propagated here and checked against every sample the engine wrote; the receiver response is the engine's output, unchanged.
Engine v0.29.1, build 6ec0e34 · constellation-multi-gnss-coverage.toml · deterministic, no seedOpen in Kshana StudioReportJSONTOML
Orbits: re-propagated from the run's own elements and checked against the engine's ground tracks. Planets: NASA imagery.
With Pro: the design optimiser runs a whole constellation design space around the Earth, the Moon or Mars through this engine and returns its Pareto front, each front design written out as a plain scenario file. See a real front
Six ways GNSS fails, and who it hits.
Each card is one way satellite navigation breaks, replayed from a recorded engine run. The chips name the sectors above that face it; open any card in Kshana Studio to run it yourself and get the same chart.
Jamming
A broadband jammer takes every visible satellite below the tracking threshold, so the receiver cannot hold a fix.
jamming-demo.toml · seed 1Open in Kshana StudioReportMeaconing
A delayed rebroadcast of real signals drags the time solution. The detector's bound says when the offset can no longer hide.
spoof-meaconing.toml · deterministic, no seedOpen in Kshana StudioReportClock holdover
GNSS goes away and each clock free-runs. A chip-scale atomic clock leaves the 20 ns guard long before an optical clock does.
clock-holdover.toml · seed 42Open in Kshana StudioReportGeometry and visibility
SGP4 propagation of a real two-line element set: the passes a ground station can see decide when a fix is even possible.
ephemeris.toml · deterministic, no seedOpen in Kshana StudioReportProtection levels
RAIM (receiver autonomous integrity monitoring) bounds the error. When a protection level crosses the alert limit, the position cannot be trusted.
integrity-raim.toml · seed 7Open in Kshana StudioReportCoasting without GNSS
A small uncrewed aircraft loses GNSS mid-route and flies on its inertial navigation system. Error grows through the outage.
small-uas-jammed-nav.toml · seed 7Open in Kshana StudioReportFour pictures every sector asks for.
How far a jammer reaches, how fast a spoof drags you off, how long each class of clock holds time, and how wide the inertial cone grows. Each one is drawn from engine output, and each opens the run behind it.
How far across the water a jammer reaches
The maritime strait scenario puts a broadband jammer on a mast near a ship. Here the ship's position is moved over a grid around the jammer and every cell is its own engine run of maritime-strait-jamming.toml (npm kshana, the engine Kshana Studio runs). Colour is the mean J/S (jammer-to-signal ratio); outlined cells lost every satellite. Select a cell to open that exact run in Kshana Studio.
The footprint map is drawn when the page script loads.
Hover or tap a cell for its run.
maritime-strait-jamming.toml · seed 1 · receiver moved per cellOpen in Kshana StudioReportModelled: free-space propagation, as the scenario states (no horizon, terrain or sea-surface multipath). Coastlines: Natural Earth.
A time spoof walks the clock off, and who notices
A linear-ramp spoof drags the time solution. Each clock's integrity monitor has its own detection bound; the replay marks when each one fires, against the spec.
Drawn from the recorded run when the page script loads.
Engine v0.29.1 · spoof-attack.toml · deterministic, no seedOpen in Kshana StudioReport
Time error after a day of holdover, by oscillator class
The lunar time budget carries one row per clock class, from an optical master clock down to a miniature rubidium clock, each reproducing its published one-day specification.
Drawn from the recorded run when the page script loads.
Engine v0.29.1 · lunar-time-budget.toml · deterministic, no seedOpen in Kshana StudioReport
The cone an inertial system flies inside
From the moment GNSS is lost, position error opens a cone around the true track. The flight-controller IMU leaves the position budget after 28.1 s; the tactical-grade IMU stays inside for the whole outage.
Drawn from the recorded run when the page script loads.
Engine v0.29.1 · small-uas-jammed-nav.toml · seed 7Open in Kshana StudioReport
A way in for every role.
Eight kinds of user, each with the entry point, the command they would reach for first, and what Pro or custom work adds for them.
Mission and systems engineer
Size a PNT architecture and see where it breaks.
kshana scenarios/hybrid-pnt.tomlPNT or GNSS specialist
Open the TOML, change the physics, check it against the ledger.
kshana --validate scenarios/integrity-raim.tomlTest and evaluation lead
Pin scenarios as regression tests and run a whole suite into one stamped study.
kshana --study scenarios/quantum-pnt-demonstrator.suite.tomlProcurement or programme reviewer
Use the validation ledger as due-diligence evidence: every capability names its oracle and its test.
https://github.com/ashfordeOU/kshanaOpenResearcher or student
Reproduce a result to the seed, extend it and cite the exact engine version.
pip install kshanaTiming and network engineer
Check holdover against ITU-T masks before the GNSS antenna fails.
kshana scenarios/telecom-prtc-holdover-24h.tomlAI-assistant user
Let your assistant run the validated engine instead of guessing the maths.
cargo install kshana-mcpEmbedded or product developer
Call the engine from Rust, Python or JavaScript inside your own product.
cargo add kshanaKshana is not an RF signal simulator and not a GNSS receiver. It is a study and trade-off instrument: it simulates what jamming, spoofing and signal loss do to a navigation and timing solution, and tells you which of its answers are validated. Not a flight product.