Validation and evidenceEdit on GitHubSource: docs/MODELLED-RATIONALE.md

Modelled capabilities — rationale

These capabilities are implemented from published or first-principles physics with tests, but are honestly labelled MODELLED — not checked against an independent external oracle to a stated tolerance. The matrix invariant tests enforce that only ExternalDataset-backed rows may be VALIDATED, so nothing here can be silently promoted. Each row states why it stays Modelled.

Requirement Capability Oracle kind Why it stays Modelled Module Tests
Solar limb-darkened SRP shadow (opt-in) SRP lit fraction as the un-occulted fraction of the limb-darkened solar flux (Eddington-approximation law I(mu)/I(1) = 2/5 + 3/5 mu, Gauss-Legendre quadrature) over a spherical or WGS-84 Earth (srp_shadow::limb_darkened_shadow, the ShadowModel variant OblateEarthLimbDarkened) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — None external: Orekit 12.2 has no limb-darkened lighting ratio. Checked against closed forms of the same law only srp_shadow srp_shadow::tests (the annular closed form, the uniform law reproducing the conical shadow, full sun and umbra limits)
DE440 Sun and Moon in the Cowell force model (opt-in) Opt-in ephemeris tier for the third-body and SRP terms of the numerical Cowell ForceModel: the geocentric Sun and Moon from any EphemerisProvider (a DE440 SPK kernel through KernelEphemeris) at TDB = TT + (TDB - TT), refusing a provider that cannot serve the epoch and counting any fallback to the analytic series; default off ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — Orekit 12.2 (Apache-2.0) NumericalPropagator/DormandPrince853 with ThirdBodyAttraction and SolarRadiationPressure on Orekit's own DE440 reader (orekit-data lnxp1990.440), run as a separate program; kshana reads a bit-for-bit, SPICE-checked cut of NAIF de440s.bsp. Bars pre-registered in xval/propagator-de440-orekit/PREREGISTRATION.md (6386b3a2). The orbit bar (0.5 m) and the sensitivity control are met, but the Sun/Moon position bar (3 m / 0.2 m) missed at 6.39 m / 0.244 m. SPICE reading the same kernel at its exact TDB misses Orekit by the same amount (6.25 m / 0.240 m), so the gap lies between NAIF's de440s path and Orekit's DE440 reader or time scale; cause not isolated. Recorded and pinned, so the row stays MODELLED propagator (ForceModel::with_ephemeris, ForceEphemeris), ephem_provider tests/propagator_de440_orekit_oracle.rs (5 cases x 25 hourly states over 24 h, LEO, GEO and HEO, third body and third body + SRP: worst |dr| 0.0170 m, |dv| 1.84e-5 m/s; analytic-series control misses by 9.96 m; Sun 6.39 m and Moon 0.244 m from Orekit's DE440 positions, a recorded miss); propagator unit tests (provider refusal, fallback counting shared across clones)
S1 atmospheric tide (opt-in) The diurnal S1 air-pressure tide as a geopotential perturbation: Biancale and Bode (2006) model N1, degrees 2 to 6, through the IERS 2010 Eq. 6.21 load formula (tides::atmospheric_tide_s1, s1_air_tide_acceleration), opt-in on the Cowell and precise force models (air_tide_s1, default off) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — None external for the geopotential effect. The 24 coefficients are transcribed from GFZ STR06/01 Table 1 model N1 and were re-checked row by row against the report (SHA-256 890865ae); degrees 0, 1, 7 and 8 are not used. Ray and Ponte (2003) print no spherical-harmonic table, so no second source was compared tides, propagator, precise_od tides::tests (the S1 term is diurnal, turns 90 deg in a quarter day, and has the load-factor amplitude of each row; physical magnitude at LEO); propagator::tests::the_s1_air_tide_flag_adds_exactly_the_s1_acceleration
High-degree spherical-harmonic gravity (EGM2008 to 2190) Underflow-safe, pole-safe evaluation of a fully-normalized field to degree 2190 (SphericalHarmonicField::acceleration_hf / potential_hf, Holmes-Featherstone 2002 modified forward column with the gradient free of 1/cos phi), a streaming ICGEM .gfc loader (from_gfc_file / from_gfc_reader; the full EGM2008 is fetched at run time, not bundled), and the Holmes-Featherstone evaluator selectable on the opt-in Cowell Geopotential ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — Orekit 12.2 (Apache-2.0) HolmesFeatherstoneAttractionModel and pyshtools 4.14.1 (BSD-3-Clause) MakeGravGridPoint, run as separate programs; bars pre-registered in xval/high-degree-gravity/PREREGISTRATION.md (73b2c75d) and xval/cowell-tesseral-200-orekit/PREREGISTRATION.md (876be39d). Orekit agrees everywhere it is defined, but pyshtools misses its pre-registered bar at the two near-pole points (up to 7.3e-10 m/s^2; a 50-digit mpmath check puts the error in pyshtools), there is no oracle value exactly on the polar axis, and the 24 h orbit's pre-registered degree-70 sensitivity control missed (0.726 m against > 1 m). Each miss is recorded, not tuned away, so the row stays MODELLED gravity_sh, propagator (FieldEvaluator) tests/gravity_sh_high_degree.rs (Orekit at 8 off-axis points: max |da| 2.2e-17 m/s^2 at N = 70, always run; 3.5e-17, 3.9e-17 and 7.3e-17 m/s^2 at N = 200, 360, 2190, data-gated on KSHANA_EGM2008_GFC); tests/cowell_tesseral_200_orekit_oracle.rs (24 h 200x200 orbit, data-gated: worst |dr| 0.1317 m, |dv| 1.45e-4 m/s; degree-70 control 0.726 m); gravity_sh unit tests (agreement with the classic evaluator to 1e-13 at degree 70, finite difference and pole continuity on a degree-2190 field, an underflowing degree-2190 term against an extended-exponent calculation)
Range-rate and az/el batch orbit determination with station masking Recover an epoch state from mixed range, range-rate and azimuth/elevation tracking above an elevation mask by Gauss-Newton on H = (dh/dx(t)) Phi(t, t0): analytic measurement partials and a variational state-transition matrix with analytic two-body + J2 partials (RK4-integrated, not a closed-form STM) ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — Orekit 12.2 (Apache-2.0) BatchLSEstimator with custom instantaneous geometric RangeRate and AzEl measurements (cross-checked against Orekit's TopocentricFrame), run as a separate program on identical masked, seeded observations. Bars pre-registered in xval/od-measurements-orekit/PREREGISTRATION.md (acfd14c). Every bar met except B4, the noiseless state agreement of 1 cm, missed on 2 of 4 scenarios (1.46, 1.74 cm): Orekit's own noiseless estimate sits that far from its simulated truth (cause on the Orekit side not isolated). Recorded and pinned, so the row stays MODELLED. Not modelled: light time, aberration, refraction, Earth rotation, a sequential filter for these measurement types orbit_determination (determine_orbit_batch_tracking, propagate_with_stm, is_visible), batch_ls (gauss_newton_analytic) tests/od_tracking_measurements_reference.rs (8 scenarios: range-rate, az/el and mixed, LEO and MEO, noiseless and seeded sigma 5 m / 5 mm/s / 1e-4 rad, 5 and 10 deg masks, against Orekit 12.2: visible sets identical; measurement values within 5.84e-8 m, 6.30e-10 m/s, 1.44e-13 rad; STM within 1.2e-14 relative; noisy states within 1.74 cm and 1.14e-5 m/s; per-type post-fit RMS within 2.7e-4 relative; noiseless kshana against truth 1.06e-8 m; noiseless kshana against Orekit 1.464 and 1.740 cm on two scenarios, a recorded miss of the 1 cm bar); orbit_determination and batch_ls unit tests
SP3 accuracy-code observation weighting Map SP3 accuracy codes (header ++ exponents in 2^n mm, the %f base, per-record base^n mm standard deviations) to per-observation position sigmas for the precise orbit-determination engine (sp3::parse_sp3_accuracy, Sp3Accuracy::position_sigma_m) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — None external: the weights are a modelling choice (the SP3 format defines the code only as the producer's accuracy indicator; it is read here as a per-axis one-sigma). The existing recorded agency runs are unchanged sp3, precise_od src/sp3.rs unit tests; tests/agency_galileo.rs::galileo_e11_sp3_accuracy_weighted_fit (committed 8 h ESOC fixture, sigma 0.032 m from header exponent 5: Tier-1 3D RMS 0.132 m unchanged, Tier-2 0.035 m against 0.070 m at sigma 1 m, the change coming from the re-balanced empirical a-priori constraint); tests/agency_swarm.rs (the Swarm product carries no accuracy codes and falls back, pinned)
Attach a published gravity field to a body with_gravity_field (on Body, in src/gravity_pds.rs): attach any loaded spherical-harmonic field (for example GMM-3 or GL0660B) to a Body so the propagator evaluates it body-fixed; opt-in, default bodies unchanged InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency only. Each published field is defined in its producer's body-fixed frame (GMM-3 in the Konopliv et al. 2006 Mars frame, GL0660B in the DE421 lunar principal-axis frame), while the field is evaluated in the IAU frame; the offset is not modelled gravity_pds, body, propagator, mars_frame tests/planetary_gravity_pds.rs::a_shadr_field_attached_to_a_body_drives_the_propagator; gravity_pds::tests::with_gravity_field_is_opt_in
Navigation-message encoders beyond GPS LNAV (GPS CNAV, Galileo I/NAV and F/NAV) GPS CNAV message types 10/11/30, Galileo I/NAV word types 1-5 in nominal even/odd pages and Galileo F/NAV page types 1-4: ICD field packing and quantisation, CRC-24Q, rate-1/2 K=7 convolutional coding (G2 inverted for Galileo), block interleaving and sync patterns, with matching test decoders InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal round trip and ICD known answers; no third-party decoder has been run (the RTKLIB/GNSS-SDR harness reading KSHANA_NAVMSG_ORACLE_JSON is data-gated). MODELLED gnss_navmsg (gps_cnav, gal_inav, gal_fnav, fec) gnss_navmsg::tests (CRC-24Q check value 0xCDE703; convolutional impulse response; Viterbi corrects injected errors; layout widths); tests/gnss_navmsg_roundtrip.rs (field start bits equal the ICD bit numbers; encode -> FEC -> interleave -> Viterbi -> decode round trips within half an LSB); tests/gnss_navmsg_galileo_brdc_grid.rs (IGS BRDC 2018-133 Galileo records on the LSB grid, worst 3.6e-3 LSB; pre-registered satellite-count bar missed, 15 of 20, FINDING)
Hatch carrier smoothing of code on real RINEX observations Divergence-free Hatch filter (ionosphere-free code carried by the ionosphere-free carrier, window N epochs, restart on loss of lock, geometry-free jump or gap) in the precise single-point positioning assembly InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — FINDING against the published ITRF2020 WTZR coordinate: the pre-registered bars (smoothed median and p95 at most 0.6 x raw; tests/fixtures/gnss_wettzell_2025055/PREREGISTRATION_HATCH.md) were missed, ratios 0.718 and 0.923; the residual metre-level error is bias-like (C1C code bias, antenna, tide, long-period multipath), not the white noise smoothing removes. MODELLED: the filter's statistics are checked internally hatch (HatchFilter), pvt (assemble_epoch_precise_smoothed, CarrierSmoother) hatch::tests (noise-free pass-through; white-noise variance 1/(2N-1); restarts); tests/hatch_wettzell_oracle.rs::hatch_finding_is_pinned (WTZR 2025-02-24 01-06 h, 600 epochs, N = 100: median 3-D error 1.553 -> 1.116 m, p95 3.473 -> 3.207 m)
RINEX 4 observation file reading RINEX 4.0x observation headers (DOI, LICENSE OF USE, STATION INFORMATION, MERGED FILE; labels matched in columns 61-80 for version 4 and later) and epoch records InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Format conformance on a real published RINEX 4.00 file (values read back equal the file's printed literals) and a specification-derived header; no independent reader was run, so MODELLED rinex_obs (parse_obs) tests/rinex4_obs_mao0.rs (first 4 epochs of the IGS MGEX RINEX 4.00 file MAO000USA_R_20231980000_01D_30S_MO, 58 satellites, 7 systems: header records and first-epoch values equal the published literals); rinex_obs::tests::parses_a_rinex_4_header_with_its_new_records (synthetic 4.02 header from the specification)
BeiDou GEO broadcast satellite position BDS-SIS-ICD-B1I v3.0 §5.2.4.12 geostationary-satellite position from a broadcast ephemeris (inertial-like frame, then Rz(Ω̇e·tk)·Rx(−5°)), opt-in through the include_beidou_geo field of NavParseOptions, so the default reader still skips GEOs InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Pre-registered (589b7c9, 3446949) against an IGS MGEX precise orbit with the GEOs; no such product was reachable from the session that built it, so the comparison is pending and the row is MODELLED (checked against the published nominal GEO slots only) rinex (RinexEphemeris::sv_position_ecef_bds_geo, NavParseOptions) tests/bds_geo_broadcast_oracle.rs (real C01-C04 records: geostationary radius, longitudes 140.02/80.04/110.55/159.99 deg at the published slots, |latitude| 2.13 deg with the tilt vs 6.65 without; the pre-registered broadcast-vs-precise SP3 comparison is data-gated on KSHANA_BDS_GEO_SP3 and has not been run); rinex::tests
Carrier-phase tightly coupled GNSS/INS with float ambiguities Error-state EKF over 15 INS states, a two-state receiver clock and one float carrier ambiguity per tracked satellite; pseudorange, carrier phase and optional range rate from an SGP4 Walker constellation (light-time and Sagnac), Klobuchar and Saastamoinen/Niell corrections applied in the loop at the filter's own position; time-differenced-carrier slip detection with a per-satellite threshold widened by the velocity uncertainty; ambiguity re-initialisation on slips and re-acquisition InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency: the measurements are synthesised from the models the filter uses (χ² NEES/NIS over seeds, a noise-free convergence, slip injection). MODELLED; no real receiver data or third-party filter is compared fusion::carrier_tc (run_carrier_tc, CarrierTcCfg), fusion::trajectory (truth_epochs) tests/fusion_carrier_tc.rs (figure-8 drive: steady 3-D RMS 0.025 m carrier vs 0.470 m code on identical measurements; 12 seeds mean NIS/dof 1.00 and steady NEES/dof 0.92; a 1-cycle slip detected at its epoch with no false alarms and the solution intact; switching the broadcast corrections off raises the code error from 0.51 m to 19.6 m (iono) and 8.0 m (tropo); noise-free run converges to 0.3 mm)
GNSS/INS maritime, rail and aviation packs with a tight-coupling option Three gnss-ins scenarios on the trajectory library (a vessel weaving at 8 m/s with a five-minute outage; a train through a two-satellite cutting and a tunnel; an aircraft whose outage covers a 25-degree banked turn) and the pack's optional [tight] table: pseudoranges from an SGP4 Walker constellation fused by the closed-loop navigator, every satellite above the mask when nominal and the highest few when degraded InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal: each pack's figures of merit against its own truth and a loose/tight comparison on identical inputs. MODELLED; the audit's NaveGo comparison has not been run fusion::pack (TightCfg, [tight]), scenarios gnss-ins-maritime / gnss-ins-rail / gnss-ins-aviation tests/gnss_ins_packs.rs (each pack: fused below free INS over the outage for both sensors; rail: tight 5.3 m vs loose 12.9 m navigation-grade and 15.6 m vs 18.8 m tactical over the outage, availability 0.97 vs 0.95; tight table validated); tests/gnss_ins_legacy_trajectory_pin.rs (the loosely-coupled default bit-identical)
Coupled pseudorange PNT filter with bias state and 3-D extension in the fusion pack One stacked Kalman filter over position, velocity, clock phase and frequency fed pseudoranges that couple position and clock (Joseph-form updates carrying the cross-covariance); a 1-DOF variant augmented with a constant accelerometer-bias state that the fusion pack runs under [coupled]; and the 3-D 8-state version with line-of-sight rows InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency: truth simulated from the filters' own models (χ² NEES over Monte Carlo seeds, the decoupled pack on identical sensors). MODELLED fusion::coupled (CoupledPntFilter, CoupledPntBiasFilter, CoupledPnt3d), fusion (run_coupled_suite), hybrid (CoupledCfg) tests/fusion_coupled_filters.rs (3-D filter over 60 seeds: second-half mean NEES 8.12 for 8 states, last-epoch χ² sum inside its 95 % band; a 0.1 ns clock fix cuts the 3-D position sigma from 5.58 m to 3.07 m; bias filter over 60 seeds: χ²(5) sum in band, bias within 3 sigma in 59 of 60; fusion-pnt-coupled with biased accelerometers: position p95 18.7 m / 90.0 m and integrity 1.00 / 0.97 coupled vs 430 m / 4060 m and 0.006 / 0.000 decoupled); fusion::coupled::tests; tests/fusion_coupled_pack.rs (fusion and hybrid without [coupled] bit-identical)
GNSS/INS trajectory library and CSV truth import Selectable motion profiles for the gnss-ins pack (straight, figure-8, urban stop-and-go, aircraft climb and coordinated turn, survey drone), defined by Euler-rate and along-track-acceleration commands closed on the truth state with the kinematic IMU (centripetal, gravity and Coriolis terms), and imported CSV truth turned into the IMU that reproduces it; the historical drive unchanged when no profile is given InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal: rigid-body kinematics identities, the CSV round trip and the filter's own covariance. MODELLED (no real drive log is compared) fusion::trajectory (TrajectoryCfg, Trajectory, kinematic_imu, parse_truth_csv), fusion::pack ([trajectory]) fusion::trajectory::tests (coordinated turn has no side force and load factor 1/cos φ; CSV import reproduces a flown profile to 1e-3 m/s and 1 m); tests/gnss_ins_trajectory_library.rs (every profile runs and fusion beats free INS over the outage; each flies its named motion; heading observability: yaw sigma after 240 s 1.27 deg cruising straight vs 0.039 deg figure-8 and 0.062 deg stop-and-go); tests/gnss_ins_legacy_trajectory_pin.rs (legacy result and truth hashes bit-identical)
Earth-Moon CR3BP 9:2 NRHO against the orbit CAPSTONE flew The circular-restricted 9:2 L2 southern near-rectilinear halo orbit that cr3bp::differential_correct_halo corrects (the Gateway and CAPSTONE orbit family), compared for its mean geometry (period, perilune radius, apolune radius) with the orbit CAPSTONE actually flew. A measurement of how well the CR3BP member describes the real orbit; a CR3BP orbit is not an ephemeris-model orbit and is not compared epoch by epoch ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — Measured against the JPL Horizons reconstructed CAPSTONE ephemeris (NAIF -1176, CAPSTONE_merged, Moon-centred ICRF, 2023-03-01..31 at 10 min), committed byte for byte (tests/fixtures/capstone_horizons/, NOTICE.md), pre-registered dab3215c before it was fetched, as a measurement with bars on the mean geometry. Not a validation: the CR3BP omits the Sun, the Moon's eccentricity and the station keeping CAPSTONE performed, so the bars describe how representative the model orbit is, not an accuracy. Results: docs/design/evidence/cap29d-capstone-nrho/RESULTS.md cr3bp (differential_correct_halo, PeriodicOrbit) tests/capstone_nrho_horizons.rs::cr3bp_nrho_matches_capstone_mean_geometry (CAPSTONE March 2023, 4 perilunes and 5 apolunes: period 6.5004 d vs 6.5699 d (1.07 %, bar 3 %), apolune 71 182 vs 71 215 km (0.05 %, bar 5 %), perilune 3 385 vs 3 245 km (4.1 %, bar 20 %)); cr3bp::tests::reproduces_l2_southern_nrho_92_regime
Position error from geometry: RMS error = sigma_UERE x DOP for the engine's least-squares fix dop_error_mc::run_geometry and check: a seeded Monte Carlo (N = 20,000 epochs per geometry, sigma = 1.5 m, ChaCha8 seed 36 + i) of the engine's own iterated least-squares fix (pvt::solve_spp, unit weights, solved from the true position) on the 8 geometries of tests/fixtures/dop/dop_reference.csv, comparing the east, north, up and clock error variances, the H/V/P RMS, the east-north correlation, the mean errors and the fraction inside the 95 % horizontal ellipse with sigma^2 Q, where Q is the covariance factor of the orbit::dop kernel (orbit::dop_cofactor, the same arithmetic) on the same geometry InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency against a closed form: under the linear Gaussian model the least-squares covariance is sigma^2 (H^T H)^-1 (Kaplan and Hegarty (eds.), Understanding GPS: Principles and Applications, 2nd ed., Artech House, 2006, ch. 7). Method and tolerances of the 0.36 geometry design note, section 5.2, fixed in a pre-registration commit before the first run: each variance within 5 % (5 standard errors of a sample variance at N = 20,000), each RMS within 2.5 %, the east-north correlation within 0.035 (5/sqrt(N)), each mean within 5 standard errors, the 95 % ellipse fraction within 0.95 +/- 0.0077 (5 binomial standard errors); negative controls (PDOP doubled; errors growing as 1/sin(elevation) against the unweighted Q) must fail. HOW IT COMPOSES: Q is the covariance factor of the orbit::dop kernel, VALIDATED against gnss_lib_py 1.0.4 on these same 8 geometries in tests/dop_reference.rs (row 'GNSS geometry / dilution of precision'); this row adds the step from those factors to metres through the engine's solver and does not borrow that row's status. WHY MODELLED: no external dataset is involved; agreement shows the estimator and noise realise sigma x DOP under the textbook model, not that any receiver's error equals UERE x DOP, and sigma_UERE is an input dop_error_mc (run_geometry, check, TOLERANCES); dop_error_ci (run, GEOMETRIES); pvt (solve_spp); orbit (dop, dop_cofactor) tests/uere_dop_monte_carlo.rs (position_error_is_sigma_times_dop_on_the_gnss_lib_py_geometries: all 104 checks pass on the first run after pre-registration f97bf4c1, worst variance 3.2 %, RMS 1.6 %, correlation 0.012, mean 2.2 standard errors, ellipse fraction 0.0039; negative_control_a_doubled_pdop_fails_every_geometry; negative_control_elevation_dependent_errors_fail_the_low_elevation_geometries: both controls fail as required; position_error_is_sigma_times_dop_on_masked_skies: the design note's two masked-skyline geometries, the 10sat-mixed sky under the city-street (4 satellites, PDOP 16.6) and container-terminal (9 satellites, PDOP 2.5) presets, all 26 checks pass on the first run after pre-registration ad4d02cb, tests/fixtures/dop/PREREGISTRATION-MASKED.md); tests/position_error_dop_ci.rs (a first, separate check on four hand-chosen skies (open, clustered, canyon, half-sky; sigma 1 m, seed 0x0D0B5EED) with chi-square confidence intervals at 1e-6 total over 20 checks: ratios 0.987 to 1.009, the solver's own PDOP/GDOP equal to the kernel's to 2.5e-12, and negative controls for a 10 % DOP error and 1/sin(elevation) errors; run before the pre-registration, so it is reported, not pre-registered); dop_error_mc::tests; dop_error_ci::tests
Geometry-aware trust classification: satellite geometry beside the receiver-trust score and a class on every deduction receiver_trust::geometry: per-epoch satellite geometry (good, degraded with reasons few-satellites/high-pdop/high-hdop/sky-blocked, or unknown when the log gives no GSV, NAV-SAT or GSA) derived from the reported elevations and azimuths through orbit::dop or taken from GSA, with a label always reported and never scored (good, fair, poor, unknown) and the HDOP, PDOP, VDOP, satellite count and signal loss in words; a vessel-score geometry monitor that deducts nothing unless the geometry is poor (ratio max(hdop/4, pdop/6, 5/n_used) above 1), then ramps to a cap of 15 points at 1.5 that geometry alone cannot take below the degraded band (cap, ramp end and floor in [geometry]; no alarm); a class on every deduction (geometry, environment, inconsistency) with loss-of-lock to satellites below 15 deg classed geometry, satellites in view but not tracked classed environment, and a poor-geometry deduction whose stated HDOP is beyond max(1.0, 25 % of the derived HDOP) from the stated sky classed inconsistency InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency: the classification is checked against the rules it states and against hand-derived ratios on synthetic edits of the committed demo log, and the no-change pins hold the 0.35.0 outputs: no score changes unless the geometry is poor; the label is always reported. WHY MODELLED: the thresholds are chosen, not fitted (provenance in each run's geometry_model; the IEC 61108-1 and GPS SPS figures as cited, to be checked against the standards' text), and there is no external labelled dataset of natural geometry degradation against attacks to validate the classification against. The derived DOP reuses the orbit::dop kernel, VALIDATED against gnss_lib_py, whose status this row does not borrow. A class of geometry is a statement about the sky, not a finding that no attack occurred receiver_trust (geometry: GeometryTracker, geometry_ratio, sky_ratio, geometry_points, GeometryLabel; score: DeductionClass, score_with; monitors; live); telemetry (sample, prometheus, syslog, otlp) tests/natural_degradation_trust.rs (a_stated_skyline_reads_the_fjord_as_geometry: on the synthetic fjord passage of scenarios/training/fjord-natural-degradation.toml the same 624 epochs are deducted with and without the stated [skyline]; with it sky-blocked is reported on 680 epochs (0 without: the azimuth-gap fallback sees nothing in a two-sided fjord), open_fraction is 0.758, and the environment-class epochs fall from 78 to 33, the rest being losses of satellites the stated skyline leaves in the open; outside the event the skyline changes no score); receiver_trust::geometry::tests (hand-derived ratios at the thresholds, the threshold edges, the ramp and cap, the floor, the label edges, [geometry] overrides, the DOP on the validated kernel, held and expired skies, unknown not guessed, signal loss, the poor-geometry tolerance, no-fix sentinels); tests/geometry_trust.rs (a fair masked sky labelled and not scored, a poor masked sky, a low-elevation loss, a power drop, a forged HDOP, total signal loss, a drag-off during poor geometry, unknown geometry, session overrides, the live schema); tests/geometry_trust_no_change.rs (both example sessions byte-identical to 0.35.0 once the appended keys are removed); tests/geometry_corpus_identity.rs (every committed vessel NMEA corpus, also as GPS-only open sky, and the crew-training scenarios: byte-identical to 0.35.0 except poor epochs, which differ by the geometry deduction alone)
Street-canyon, sector and terrain reductions to a table skyline: the street canyon in closed form (cut atan((h - a) / d) with d = (w/2) / abs(sin(az - s)), open ends for a finite length), sharp-edged sectors clockwise with wrap, and terrain points reduced to a table with the curvature drop d^2/(2 * 4/3 R); the skyline is their pointwise maximum with any table InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal: the closed forms are checked against hand-computed values (wall-top elevations of a stated street, the open-end condition, the curvature drop of a stated point). No external oracle: the design note scopes these reductions as MODELLED, and Orekit's ElevationMask takes a table, so the comparison of row 'Azimuth-dependent skyline mask: visible set, azimuth and elevation, and DOP under the mask' reads their 360-point tables as inputs and does not check them skyline (Canyon::cut_deg, Sector::contains, TerrainPoint::elevation_deg, reduce_terrain, SkylineCfg::build) skyline::tests (canyon_matches_hand_computed_wall_elevations; terrain_takes_the_curvature_drop; sectors_have_sharp_edges_and_wrap; a_preset_is_overridden_or_added_to_field_by_field; malformed_sections_are_refused)
Skyline presets (city street, harbour approach, fjord, container terminal) skyline::PRESETS: four REPRESENTATIVE geometries with the design note's stated dimensions and a provenance line each: city-street (a canyon, street 0 deg, 20 m between 30 m walls, antenna 1.5 m), harbour-approach (sectors: open to seaward over 180 deg, quay buildings 8 deg over 90 deg, the breakwater 3 deg), fjord (terrain: walls 600 m above the antenna at 1.5 km either side of a north-south channel, curvature drop applied), container-terminal (sectors: stacks 12 deg over the landward half, crane booms 35 deg and 25 deg over two narrow sectors); overridable field by field InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — None: chosen and stated dimensions, not a survey of any street, port, fjord or terminal (the aspect ratio of the street is inside the 0.5-2 band of Oke (1988); the fjord is of the order of the west-Norwegian fjords; the stacks use the ISO 668 high-cube height). The test checks the presets against their own stated dimensions, a transcription check, which the validation rule does not count skyline (PRESETS, preset, preset_list) skyline::tests (presets_carry_the_note_dimensions_and_provenance)
Sky geometry functions: visibility, DOP, covariance, error ellipse, Monte Carlo cloud geometry (sky_geometry, sky_monte_carlo, skyline_presets, skyline_profile, skyplot_svg; CLI kshana sky and kshana skyline, Python and WASM functions of the same names, MCP sky_geometry): from a site, a time and constellation presets (or satellites as azimuth/elevation or ECEF), the satellites visible and masked under a skyline, GDOP/PDOP/HDOP/VDOP/TDOP, the unit-variance cofactor (H^T H)^-1 and the covariance in east-north-up with one receiver clock per system or one in common, the horizontal error ellipse (semi-axes k sigma sqrt(lambda), k = sqrt(-2 ln(1 - p)), orientation 0.5 atan2(2 Q_EN, Q_NN - Q_EE) from north), and n seeded least-squares errors under independent Gaussian range errors with their empirical covariance, RMS and 95 % containment. The cofactor is orbit::cofactor_from_los, the one kernel behind orbit::dop and orbit::dop_cov (dop is dop_cov's reduction): no second DOP implementation ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — The single-clock DOP factors rest on the kernel validated against gnss_lib_py 1.0.4 (row 'GNSS geometry / dilution of precision (DOP)'); this row's own checks are internal: sky_geometry reproduces orbit::dop and dop_cov on the same geometry, the ellipse reproduces an analytic 2x2 eigen-decomposition, ECEF and azimuth/elevation inputs agree, and the seeded cloud's RMS and 95 % containment agree with the geometry. The ENU covariance with one clock per system and the ellipse are VALIDATED in row 'Horizontal error ellipse and per-system cofactor from the geometry covariance' (numpy, P2); what stays MODELLED here is the composition: the preset propagation to a representative sky, the Monte Carlo cloud (checked against the geometry it samples, a self-consistency check) and the surfaces. The constellation presets give a representative sky, not a dated one; the Gaussian error model and the UERE are stated inputs, not a measured accuracy or an integrity bound geometry; orbit (cofactor_from_los, dop_cov, dop); surface (sky_geometry, sky_monte_carlo, skyline_presets, skyline_profile, skyplot_svg) geometry::tests (ellipse_of_an_analytic_two_by_two_case; sky_geometry_equals_orbit_dop_on_the_same_visible_set; ecef_input_matches_azimuth_elevation_input; one_clock_per_system_adds_a_state_and_costs_geometry; monte_carlo_is_seeded_and_agrees_with_the_geometry; presets_propagate_and_are_seen_from_a_site); tests/dop_reference.rs (the single-clock kernel against gnss_lib_py)
GNSS-denied clock holdover Closed-form coast-error growth + holdover-to-threshold; quantum-clock classes ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — Multi-step clock_state covariance recursion (same-codebase cross-check); the underlying coast-variance & holdover-inversion kernel is externally validated vs scipy (see 'Clock-holdover coast-variance & threshold inversion'). The per-class red-noise-floor holdover figures stay MODELLED holdover holdover::tests (vs multi-step Kalman covariance recursion; white-FM exact; round-trip); coast-variance kernel externally validated in tests/gnss_denied_clock_holdover_reference.rs (vs scipy Van-Loan/brentq)
Measured clock device cards (held-out prediction) clock_library: a device card (white phase, white, flicker and random-walk FM plus a linear frequency drift) fitted to one third of a named measured clock record after a logged conditioning pass (gaps, phase outliers, phase steps, bursts removed; frequency steps logged), weighted by the lag-1-identified noise-type degrees of freedom, and its predicted Allan deviation scored on the held-out two thirds; readers for RINEX and IGS clock files, BIPM per-laboratory files and Circular T Section 1; conversion of a card to the slot-timing noise model, the extended Kalman clock model and the spoofing monitor's noise levels ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — Measured records, held out: IGS final combined 30 s clocks of the 11 GPS Block IIF satellites over 2026-03-01 to 14 (a window no test had opened; IGS, open with attribution) and the JammerTest 2024 u-blox ZED-F9P receiver in its non-scored stationary sessions (GPL-3.0-or-later). D9 external comparison (pre-registered 14169982, every card's predicted / measured Allan deviation within [1/1.5, 1.5] at its fitted averaging times), a finding (stays MODELLED): 10 of 11 GPS IIF cards are within the bar; G27 is optimistic at the two-hour scale (0.662 at 7680 s, worst factor 1.510), the periodic hour-scale error a power-law card does not carry. The receiver TCXO card is blocked: outside the logged transmissions the dataset's other sessions leave 167 epochs against the 3600 required. Reported, not blind (records opened by earlier rows): the 5071A caesium card is within the bar (worst 1.070 up to 4096 s), the OCXO card is conservative and outside it (2.348 at 128 s; its noise floor changes during the record), and the Norcia strontium card fitted on the three shortest published points is within it at the two scored points (1.291, 1.405). Galileo passive hydrogen masers (no login-free source of final Galileo clocks reachable) and the Deep Space Atomic Clock (one open in-space value) are blocked. D9 round 2, the ZED-F9P receiver TCXO as a model class on 14 days of 12 static Wroclaw stations (Zenodo 6488497, CC BY 4.0; pre-registered 698f3842), a finding: with the registered pipeline 11 of 12 stations were not evaluable (RAIM rejected most ionosphere-free epochs) and BX14 failed; a disclosed re-run with a corrected pipeline (pre-registered cdfde420) passes 1 of 11 blind stations (BX12, 1.412; BX07 1.532 and BX13 1.542 just outside), because single-point receiver clocks from intermittent 30 s files are not a clean oscillator record clock_library (card, condition, series), realdata::clk, allan (lag1_noise_id) tests/clock_library_device_cards_oracle.rs (gps_iif_cards_reproduce_the_recorded_finding; receiver_training_is_blocked_by_the_epoch_minimum; non_blind_cards_are_reported; pre-registered 14169982); clock_library::card::tests; clock_library::condition::tests; clock_library::series::tests; realdata::clk::tests; tests/clock_library_f9p_cards_oracle.rs (f9p_first_pipeline_reproduces_the_recorded_finding; f9p_corrected_pipeline_reproduces_the_recorded_finding; data-gated)
Measured GPS Block IIF clock cards with per-revolution terms (held-out prediction) clock_library::card::DeviceCard::fit_phase_periodic: a device card that carries the once- to four-per-revolution phase terms (period T/k, T = 43 082.05 s), fitted jointly with the quadratic by least squares on one third of a measured satellite clock record, with each term's closed-form Allan contribution 4 A^2 sin^4(pi tau / P) / tau^2 in the predicted Allan deviation ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — Measured records, held out: IGS final combined 30 s clocks of the 11 GPS Block IIF satellites over 2026-04-01 to 14 (a window no test had opened; IGS, open with attribution). D9 external comparison (pre-registered 698f3842, predicted / measured Allan deviation within [1/1.5, 1.5] at every fitted averaging time on every satellite), a finding (stays MODELLED): 9 of 11 cards are within the bar; G03 (1.947) and G25 (1.581) are optimistic between 60 s and 2000 s because their held-out records are noisier than their fit thirds (G25's held-out part carries 16 gaps and 29 phase outliers), a change of the clock rather than a missing periodic term. Dropping the periodic terms from the prediction fails all 11 cards (1.77 to 4.96), so the terms carry the prediction clock_library (card) tests/clock_library_periodic_cards_oracle.rs (periodic_cards_reproduce_the_recorded_finding; pre-registered 698f3842); clock_library::card::tests (a_periodic_card_carries_the_sinusoid_a_power_law_card_cannot)
Onboard clock state estimation 3-state (phase/freq/drift) van-Loan Kalman clock, Joseph-stabilised ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — filterpy 1.4.5 KalmanFilter (R. Labbe, MIT), with F via scipy.linalg.expm and Q via the Van-Loan 1978 block-matrix — an independent reference implementation reproducing kshana's full filter trajectory. Cross-implementation consistency: the clock physics / Allan calibration are not externally validated, so this stays MODELLED. 0.30 external comparison, a finding (stays MODELLED): on IGS final 30 s clocks of 11 GPS Block IIF satellites (2025-08-17 to 30), with Q fitted to the first-half ADEV and the filter scored on the held-out second half, the filter is consistent one step ahead (0.906 to 0.971 of epochs inside its 95 % band, bar 90 %) but over-confident at one hour on 9 of 11 clocks (0.486 to 0.829) and its innovation sums fall outside [2.4, 3.6] on 5. The fitted white-phase noise is zero on every satellite, and the hour-scale error (periodic terms, flicker FM) is not in the 3-state model. 0.30 round 2, an extended filter (flicker FM and once- and twice-per-revolution states) on fresh held-out IGS clocks of 2025-09-01 to 14 (pre-registered d8d18573), a finding (stays MODELLED): the one-step and one-hour consistency criteria hold on all 11 satellites (0.948 to 0.988 and 0.907 to 0.996), but the innovation-sum criterion fails on G24 (0.964) and G30 (1.929) against [2.4, 3.6]. D9 round 3, the round-2 extended filter, tuning and criteria unchanged after the frozen clock_library conditioning detector, on fresh IGS clocks of 2026-04-01 to 14 (pre-registered 698f3842), a finding (stays MODELLED): (a) one-step 0.941 to 0.968 and (c) triple-NIS mean 2.641 to 3.549 hold on all 11 satellites; (b) one hour fails on G09 (0.894) and G26 (0.876) against 0.90 clock_state clock_state::tests (analytic van-Loan Q; NEES; PSD positivity); tests/clock_state_reference.rs (full predict+update trajectory — state x and 3×3 covariance P over 1925 steps / 4 parameter sets vs filterpy 1.4.5; worst |relΔ| 2.8e-14); tests/clock_state_igs_holdout_oracle.rs::three_state_filter_on_held_out_igs_clocks_finding (pins the finding); tests/clock_state_ext_igs_fresh_oracle.rs::extended_filter_on_fresh_igs_clocks_finding; tests/clock_state_ext_igs_conditioned_oracle.rs::conditioned_extended_filter_finding (D9 round 3)
Time-transfer error budgeting Two-way/TWSTFT (Sagnac), GNSS common-view, PPP; link-jitter→range ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — Sagnac magnitude checked against an authoritative PUBLISHED VALUE — N. Ashby, 'Relativity in the GPS', Living Reviews in Relativity 6:1 (2003), Eq. 1.29: an eastward equatorial circumnavigation accrues 207.4 ns (2ωA_E/c²); kshana reproduces 207.386 ns. Independently corroborated by RTKLIB 2.4.3 geodist() (Takasu, BSD-2-Clause), which carries the same 2Aω/c² geometry. The composite BIPM TWSTFT transponder/common-view/PPP budget has no external oracle, so the capability stays Modelled timetransfer, timetransfer_adv timetransfer::tests (reciprocal cancellation; two-form Sagnac identity); tests/time_transfer_error_budgeting_reference.rs (equatorial-circumnavigation Sagnac = 207.386 ns vs the published Ashby 207.4 ns to <0.05 ns; plus Sagnac/geodist geometry cross-checked against RTKLIB 2.4.3 geodist() compiled from C source)
Nav-signal modulation & code-tracking analysis BPSK-R/BOC PSD, spectral-separation κ, Gabor bandwidth, DLL jitter, multipath ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — GPS C/A Gold cross/auto-correlation matched EXACTLY (integer ±65/−1/63) against independent IS-GPS-200 code generation; BPSK-R(1)/BOC(1,1) PSD shape vs an independent scipy periodogram. The modulation/SSC/DLL closed forms (Betz 2001 / Kaplan & Hegarty) remain analytic, so the row stays MODELLED — but the code-correlation sub-claim is externally matched. 0.30 round 2, against the printed values of Betz 2001 and Hein et al. 2006 (pre-registered 1181ce1d, half a printed unit), a finding (stays MODELLED): all 45 Table 1 spectral cells, the 1 GHz correlation values, the MBOC interference figures and 2 of 3 Fig. 17 offsets agree; the 24 MHz first side lobes, the BOC(8,4) Fig. 17 offset and every Figs. 18-21 worst-case multipath bias (11 to 15 % low) do not. Kshana and an independent NumPy evaluation of the pre-registered reading agree, so the gap lies in that reading or in an unstated detail of the paper; cause unresolved navsignal navsignal::tests (BPSK self-SSC = 2/3R_c; unit-area PSD; DLL); tests/nav_signal_modulation_code_tracking_reference.rs (GPS C/A Gold cross/auto-correlation exact-integer match vs independent IS-GPS-200 code generation; BPSK-R(1)/sine-BOC(1,1) PSD vs an independent scipy periodogram); tests/nav_signal_betz_hein_published_oracle.rs (betz_text_correlation_values_over_1_ghz; hein_mboc_interference_improvements; finding_betz_side_lobes_and_multipath, pinned)
Quantum inertial sensor performance Cold-atom interferometer accelerometer from first principles (k_eff·T², QPN) ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — Published CAI primary-paper numeric vectors (Cheinet 2008 transfer function; Peters/Freier sensitivity): k_eff·T² matched exactly, shot-noise ASD a one-sided floor within ~2× of each published instrument (real devices carry technical noise above the quantum floor). A bracket, not parity. 0.30 round 2 (pre-registered e7de532a), a finding (stays MODELLED): the QPN-only rotation noise against the measured Gauguet et al. 2009 Fig. 14 points gives ratios 0.695 to 0.788 at the three admitted points (0.751 at the operating point), missing the pre-registered 30 % bar by 0.5 points; the QPN floor sits 21 to 31 % below the measured noise, as expected of a model without laser and detection noise. The gradiometer composition matches the Janvier et al. 2022 QPN model line (ratio 1.013 to 1.017, Reference). The measured test cannot discriminate a sqrt(2) composition error; only the unequal-contrast Janvier line can inertial::quantum_imu quantum_imu::tests (k_eff; Mach-Zehnder T²; Freier-2016 floor bracket); tests/quantum_inertial_sensor_reference.rs (transfer function |H(ω)|, k_eff·T² and shot-noise ASD vs published Cheinet 2008 / Peters / Freier numeric vectors); tests/quantum_inertial_measured_qpn.rs (gauguet_finding_qpn_floor_sits_below_the_measured_noise, pinned; gradiometer_qpn_line_matches_janvier_model)
Quantum inertial sensor fringe-ambiguity / dynamic range Mach–Zehnder fringe-ambiguity dynamic range: the 2π-periodic fringe readout sets a maximum unambiguous specific force a_max=π/(k_eff·T²), and the unambiguous range in resolution cells a_max/σ_a=π/σ_Φ is independent of the optical scale factor — the T² sensitivity gain costs unambiguous range in exact lockstep (interrogation time trades resolution for range, leaving the cell count fixed by the readout phase noise) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Self-consistency of the interferometer fringe model: the half-fringe edge, the 2π-periodic aliasing structure, and the scale-factor cancellation in the range/resolution ratio are closed-form algebraic identities checked against the engine's own Mach–Zehnder phase and sensitivity functions — internal-consistency checks, NOT an external dataset, so the row stays InternalConsistency. MODELLED ideal three-pulse fringe-ambiguity; no wavefront-aberration or contrast-loss bounds on the unambiguous range inertial::quantum_imu quantum_imu::tests (a_max sits at the ±π half-fringe edge with the 1/T² range scaling; wrapped-phase recovery is exact inside [−a_max,a_max] and aliases by exactly 2·a_max outside it; the unambiguous dynamic range a_max/σ_a=π/σ_Φ is identical across two very different wavelength/T scale factors; the CaiAccelerometer methods match the free functions)
Quantum inertial dead-reckoning resilience Composed bias + scale-factor + VRW + stability-decay position budget over holdover ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — Independent numpy Monte-Carlo SDE integration of double-integrated white-acceleration noise (validates the analytic VRW variance by a genuinely independent algorithm) + a Groves 2013 published-value anchor for the bias/scale-factor terms; the CAI device numbers quantify partner hardware and stay MODELLED inertial::quantum_imu (QuantumNavBudget) budget_tests (bias vs AccelModel integrator; VRW vs analytic integral); tests/quantum_inertial_dead_reckoning_reference.rs (VRW vs an independent numpy Monte-Carlo double-integration of white-acceleration noise, worst dev 0.42% within ±3% over 6 coast times; bias/scale-factor vs a Groves 2013 closed-form value; holdover round-trips)
GNSS-denied jamming resilience Geometry J/S link budget, anti-jam C/N₀, per-satellite loss-of-lock InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Anti-jam C/N₀ link-budget equation cross-checked against an independent numpy re-derivation (shares the same closed form → InternalConsistency) plus a real-JammerTest-2024 C/N₀ degradation characterisation. 0.30 round 2, blocked (stays MODELLED): the measured JammerTest 2024 C/N0 drop against a link-budget prediction (pre-registered 6b2f6240, within 3 dB) was not run because the F8.1 antenna position and pointing at Bleik and the L1 share of the multi-band 1.6.4 ramp power are not documented in the test catalogue or the official log jamming jamming::tests (broadband_q_equals_the_spectral_separation_closed_form and cw_q_equals_the_spectral_separation_closed_form: the Q table, CW and narrowband 1, broadband and swept 2, pinned to the navsignal closed forms; a_cw_jammer_is_more_damaging_than_broadband_noise_at_equal_js); tests/gnss_denied_jamming_resilience_reference.rs (FSPL/J-S/effective-C-N₀ vs an independent numpy re-derivation of the Kaplan & Hegarty §9.4 link budget; real JammerTest C/N₀ falls monotonically through the 25 dB-Hz threshold); tests/jamming_jammertest_cn0_oracle.rs (pre-registered, blocked, not run)
Spoofing detection Clock-aided χ², RAIM, AGC, SQM fused per-epoch security FoM ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — TEXBAT scenario parameters (Humphreys 2012) — characterisation, not pinned vectors. 0.30 external comparison, a finding (stays MODELLED): on JammerTest 2024 (Bleik; GPL-3.0 data) the observable-level monitors (clock-aided chi-square, RAIM, solve failure) raised no alarm within 10 s of any of the 8 evaluable published spoofing onsets (where the pre-onset window was clean, the first alarm came 10.2 to 39 s after the published slot start), and three pre-onset windows carried false alarms from the clock monitor (81, 64 and 173 epochs). The first observable effect was a loss of dual-frequency GPS tracking, not a RAIM inconsistency. The published onsets are minute-resolution schedule slot starts; that they precede the RF capture is an interpretation, not a measurement. 0.30 round 2, against the organisers official JammerTest 2024 log (second resolution; pre-registered 6b2f6240 with a Hadamard-calibrated three-state clock monitor without latching), a finding (stays MODELLED): the monitor alarms within 10 s at 4 of 10 logged onsets; at the other six it is 18 to 211 s late or raises pre-onset clock false alarms (1 at 2.1.4, 85 at 2.3.15). D9 round 3 (a receiver card from the JammerTest unit's other sessions, pre-registered 14169982) blocked: 167 training epochs against 3600. D9 rounds 4 and 4b (noise levels from a u-blox ZED-F9P model-class card, Wroclaw 2021, pre-registered 698f3842; 4b a disclosed re-run with a corrected extraction, cdfde420), a finding (stays MODELLED): zero pre-onset false alarms at all 10 logged onsets and 6 of 10 within 10 s; 2.1.1, 2.3.5, 2.3.10 and 2.6.1 stay late (+211, +23, +18, +51 s), unchanged by the clock noise level spoof, spoof_detect, spoof_monitors tests/spoof_texbat_validation.rs (TEXBAT parameter characterisation); tests/spoof_detection_jammertest_oracle.rs::monitors_against_the_published_onsets_reproduce_the_recorded_disagreement (pins the finding); tests/spoof_detection_jammertest_log_oracle.rs::engine_monitors_against_the_logged_onsets_reproduce_the_recorded_disagreement; tests/clock_library_tcxo_card_jammertest_oracle.rs (round_3_is_blocked_by_the_training_minimum; round_4_reproduces_the_recorded_finding; round_4b_reproduces_the_recorded_finding; D9)
Timing Protection Level under spoofing Closed-form bound on worst-case undetected time error = monitor floor + oscillator coast-σ over CUSUM detection latency, reported as a red-noise-floor band InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Composes Validated primitives (allan/holdover van-Loan, security floor); calibrated on JammerTest 2024 scenario 2.1.1 (~1.01 ms real served-time pull vs ≤51 ns claimed). Bridge over Validated parts — not itself an external validation. 0.30 external comparison, a finding (stays MODELLED): on the JammerTest 2024 spoofing scenarios the measured undetected served-time error exceeds the nominal TPL at 3 of 8 detected onsets: 184.3 vs 34.6 ns (2.1.4), 295.7 vs 159.3 ns (2.3.5) and 143.0 vs 69.0 ns (2.3.11); three of the five inside are trivial (a latched pre-onset false alarm). Likely cause: the coast term from a 60 s calibration with zero drift noise does not cover the receiver TCXO's frequency wander over 15 to 39 s. The measured error is Kshana's own single-point clock estimate against a line fitted to its own pre-onset estimates, so even agreement would not have been fully independent. 0.30 round 2, against the official JammerTest 2024 log onsets and the measured receiver time error (pre-registered 6b2f6240), a finding (stays MODELLED): at 4 of 10 logged onsets the undetected error exceeds the drift-state TPL (634.7 against 458.5 ns at 2.1.1, 232.6 against 16.2 ns at 2.3.5, 41.3 against 6.0 ns at 2.3.10, 218.6 against 47.4 ns at 2.6.3) tpl tpl::tests (closed-form oracles + CUSUM); examples/tpl_jammertest.rs (JammerTest 2024 real-spoof calibration); tests/tpl_jammertest_coverage_oracle.rs::tpl_against_measured_time_error_reproduces_the_recorded_disagreement (pins the finding); tests/tpl_jammertest_log_oracle.rs::drift_state_tpl_against_the_logged_onsets_reproduces_the_recorded_disagreement
Alternative / complementary PNT Gravity-map matching, terrain-referenced (TERCOM/SITAN), magnetic anomaly InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — IGRF-14 coefficients; first-principles matched-filter CRLB. The real-field gravity benchmark's field is externally checked (row 'Gravity-anomaly synthesis from a spherical-harmonic model'), but its navigation outcome has no external oracle altpnt, mapmatch, gravimeter, igrf tests/alternative_complementary_pnt_reference.rs (map-matching CRLB; IGRF-14 field); mapmatch::tests; gravimeter::tests; igrf::tests; tests/gravity_map_real_field.rs (the 60-min GPS-denied benchmark on the real EGM2008 degree-70 field, pre-registered in xval/icgem-egm2008/: matched 3106 m, so the < 500 m bar is NOT MET and asserted as missed, and the tenfold cut on the 70.6 km drift is MET; plus the seeded map-error Monte Carlo); altpnt::terrain::tests::emag2_format_grid_reproduces_the_synthetic_magnetic_channel and tests/emag2_real_grid.rs (data-gated EMAG2v3 reader on a real crop; no navigation outcome claimed on it); tests/terrain_slam_rbpf.rs (joint map estimation, a FastSLAM-style RBPF, against known-map SITAN on a 15 m correlated map error over 20 seeds, pre-registered in xval/terrain-slam-rbpf/: 1.5% mean gain and better in 10 of 20, so the 10% and 12-of-20 bars are NOT MET and asserted as missed; no harm on a perfect map, MET)
Reproducibility & software assurance Deterministic, scenario-hashed, SBOM + cross-platform golden gates ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — SBOM conformance to the official CycloneDX 1.5 JSON Schema (+ valid SPDX identifiers) — an external published standard, zero validation errors over the full dependency graph; the FoM-determinism / byte-reproducibility part remains a pinned self-consistency check, so the row stays MODELLED report, scenario; CI (golden/determinism/SBOM) tests/golden.rs, tests/determinism.rs, tests/cross_platform_golden.rs; tests/reproducibility_software_assurance_reference.rs (the generated SBOM validates with zero errors against the official CycloneDX 1.5 JSON Schema over the full 66-component shipped graph: default + python + wasm features, dev-dependencies excluded)
Machine-learning RF-impairment detection evaluation (13494) Labelled synthetic impairment corpus + detector-agnostic ROC/AUC/confusion/Pfa-Pmd harness; leakage guard, stratified split, distribution-shift (in- vs out-of-regime) optimism report. Runnable from the CLI/bindings as the impairment-eval scenario kind (scenarios/impairment-eval.toml) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed-form AUC bounds (Mann–Whitney) + a perfect-oracle detector; corpus is SYNTHETIC (parameter-grounded, not field/IQ) impairment_eval impairment_eval::tests (AUC perfect=1/identical=0.5/tie=0.125, ROC monotone, fused>0.8, per-class layer separation, leakage guard, reproducible corpus, distribution-shift flags optimism); dominance_demonstrators (reachable + reproducible + MODELLED-not-VALIDATED + optimism-gap self-consistent)
Machine-learning RF-impairment optimism-gap study & ID-only gap predictor Controlled synthetic study of the in-distribution→out-of-distribution AUC optimism gap across published-method and learned (logistic-regression / one-hidden-layer MLP) detectors: per-class scaling-law trends (Spearman ρ + slope on 1−severity) and an ID-only ridge predictor that estimates the gap from in-distribution diagnostics alone, scored leave-one-detector-out and leave-one-class-out. Reproducible via cargo run --release --example optimism_study InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Hand-derived statistics vs closed forms (binormal AUC Φ(d'/√2), DeLong variance, tied-rank Spearman, exact OLS recovery) + leave-one-out CV against the predict-the-mean baseline. Corpus is SYNTHETIC (parameter-grounded, never field/IQ) and the optimism gap is a synthetic→synthetic severity shift, NOT a sim-to-field result impairment_study, impairment_ml, eval_stats impairment_study::tests (per-class oracle AUC≈1, learned optimism gap>0, grid shape + bootstrap CI brackets the mean + positive scaling trend, ID features finite, gap predictor beats predict-the-mean under BOTH leave-one-detector-out and leave-one-class-out CV + deterministic); impairment_ml::tests (logreg separates + deterministic + loss↓, MLP solves XOR a linear model cannot + seeded); eval_stats::tests (bootstrap/DeLong/Spearman/ridge vs closed forms)
Quantum-vs-classical PNT trade & GNSS-denied resilience (13503) Measured-ADEV ingestion (NNLS), trade table (timing/inertial holdover + benefit), resilience-vs-time envelope; floor caveat carried on the artifact. Runnable from the CLI/bindings as the quantum-trade scenario kind (scenarios/quantum-trade.toml) ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — The measured-ADEV→PSD fit (NNLS) kernel is matched to scipy.optimize.nnls (tests/scipy_reference.rs / tests/quantum_vs_classical_pnt_trade_reference.rs) — an independent external kernel; but the trade NUMBERS quantify (never validate) a partner clock/CAI, so the trade itself stays MODELLED, no validation halo quantum_trade quantum_trade::tests (ADEV round-trip recovery, NNLS non-negativity, floor-caveat present/absent, benefit>1, monotone envelope + alt-PNT bound); dominance_demonstrators (measured-ADEV is data-driven not floor-assumed, assumed-class flags floor + caveat, malformed curve rejected, MODELLED-not-VALIDATED)
Space-weather environment & activity-driven thermospheric density Solar/geomagnetic indices (definitional Kp↔ap table), the Jacchia-1971 exospheric temperature, and the Jacchia 1971 thermospheric density (SAO Special Report 332: static diffusion profiles reproducing its Table 7, with the diurnal, geomagnetic, semiannual, seasonal-latitudinal and helium variations) against the static USSA76 atmosphere. Runnable from the CLI/bindings as the space-weather scenario kind (scenarios/space-weather.toml) ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — Definitional Kp↔ap table + Jacchia-1971 exospheric-temperature closed form (matched to <1 K vs the published anchors, tests/space_weather_reference.rs); the density is characterised against pymsis NRLMSISE-00 (an independent NRL model): the 800 km solar-cycle swing is 10.4x against NRLMSISE-00 13.6x. 0.30 revision: the calibrated first-order activity factor was replaced by Jacchia 1971 (default scenario density at 400 km 4.176e-12 -> 6.929e-12 kg/m3; reference_exospheric_temperature_k removed, mean_exospheric_temperature_k added). 0.30 round 2, measured TOLEOS CHAMP/GRACE/GRACE-FO accelerometer densities (ESA Swarm DISC; pre-registered bb8756e3), a finding (stays MODELLED): orbit averages at 400 to 500 km are within a factor 2 at solar maximum outside storms (CHAMP 2001 521/521, GRACE-A 2002 120/120, GRACE-FO 2024 526/547), but Jacchia 1971 is about 1.7x too dense in the 2008 solar minimum (GRACE-A 412/544 within a factor 2), so the density is not validated space_weather space_weather::tests (Kp↔ap exact at grid points + round-trip + monotone, daily-Ap mean, exospheric-T vs published solar-min/mean/max + storm increment anchors, density unity-at-reference, solar-cycle swing in the observed 5–10× band, scenario reproducible + MODELLED-not-VALIDATED + out-of-range rejection); dominance_demonstrators (reachable + reproducible + physical T + MODELLED-not-VALIDATED); tests/space_weather_density_accelerometer_oracle.rs::jacchia71_finding_is_pinned
Launch-window & ascent geometry (mission analysis) Two-body launch azimuth(s) (sin Az = cos i / cos lat), minimum reachable inclination, circular velocity, Earth-rotation eastward bonus, dogleg plane-change Δv and daily opportunities, and, given an epoch and IERS finals2000A rows, the site speed about the true pole (launch::site_rotation_speed_at). Runnable from the CLI/bindings as the launch-window scenario kind (scenarios/launch-window.toml) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed-form spherical-trig launch geometry vs published worked-example anchors (Vallado, Fundamentals of Astrodynamics 4th ed., Algorithm 37 launch-azimuth + Ch.6 plane-change; tests/launch_window_ascent_geometry_reference.rs). These re-use the same closed form kshana implements (a published-value parity / transcription check, InternalConsistency); MODELLED two-body, no rotating-Earth velocity-triangle / ascent / drag-loss model. 0.30 external comparison against Orekit 12.2 (Apache-2.0), a finding (stays MODELLED): the geometry agrees to rounding (inclination read back from the burnout azimuth over 158 cases, worst 2.6e-15 rad; minimum inclination, circular velocity and dogleg delta-v to 3e-16), but the Earth-rotation site speed misses the pre-registered 1e-6 relative at 62.9 deg latitude (1.12e-6). The gap grows as tan(lat), consistent with a polar-motion pole offset of about 5.8e-7 rad in Orekit's Earth frame that the spherical ω·R·cos(lat) omits. The claim was not narrowed before the run, so the row cannot promote on this comparison. 0.30 round 2 (pre-registered 60d7f773): with an epoch and IERS rows, the true-pole site speed (scenario field site_rotation_speed_true_pole_m_s) agrees with Orekit within 1e-6 at 24 sites over four longitudes (worst 4.9e-8), but the nominal no-epoch speed the scenario emits by default as the Earth-rotation bonus still misses by 1.12e-6, so the row stays MODELLED pending a decision on the default output launch launch::tests (due-east launch reaches i=latitude, KSC→ISS = textbook 45°, polar = N/S, i<lat unreachable, 465 m/s equatorial bonus, plane-change 10° ≈ 1.34 km/s + 180° = 2v, daily-opportunity counts, scenario reproducible/MODELLED + dogleg path); dominance_demonstrators (reachable + reproducible + KSC→ISS 45° + MODELLED-not-VALIDATED); tests/launch_geometry_orekit_oracle.rs::burnout_azimuth_reproduces_the_target_inclination_in_orekit; tests/launch_geometry_orekit_oracle.rs::earth_rotation_speed_gap_is_recorded_as_a_finding; tests/launch_geometry_orekit_oracle.rs::true_pole_site_speed_matches_orekit_at_a_fresh_epoch_and_longitudes
Ballistic re-entry corridor (Allen–Eggers) Peak deceleration (ballistic-coefficient-independent), velocity + altitude at peak-g, and peak-heating velocity for an exponential-atmosphere ballistic entry. Runnable from the CLI/bindings as the reentry scenario kind (scenarios/reentry.toml) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed-form Allen–Eggers analytic entry, additionally cross-checked vs a scipy 1.18 solve_ivp (DOP853) numerical integration of the SAME drag-only entry ODE (tests/ballistic_re_entry_corridor_reference.rs, 36 cases, worst a_max rel 2.9e-9) — a numeric-integral-vs-own-analytic-form check, so still InternalConsistency, NOT an external validation. MODELLED ballistic (no lift), no aerothermal/TPS — heating output is a velocity, not a heat-flux. 0.30 external comparison, a finding (stays MODELLED): against the Stardust SRC entry reconstruction (Desai and Qualls, NASA NTRS 20080008567), the Allen–Eggers peak deceleration for the printed inertial entry state (12.9 km/s, -8.2 deg, H 7200 m) is 61.8 g against the best-estimated-trajectory 32.89 g, +88 % against a 15 % tolerance: the constant-flight-path-angle, no-gravity solution roughly doubles the peak of a shallow, faster-than-escape entry. Stardust carried no accelerometer, so the reconstruction is a trajectory estimate. 0.30 round 2, blocked (stays MODELLED): an integrated planar point-mass solution (reentry::simulate_planar_entry, US76, inverse-square gravity, curvature) agrees with the Stardust and Genesis best-estimated trajectories within 15 % (+11.3 %, +5.6 %), but those maxima are agency simulation outputs, not measurements, so this is a cross-check only. The accelerometer comparison (pre-registered 18863477) is blocked on a readable copy of the Hayabusa2 REMM analysis (doi 10.57350/jesa.16) reentry reentry::tests (peak-g independent of ballistic coefficient + physical g-band, grows with steeper γ / faster entry, peak-g velocity = V_e·e^(−1/2) and peak-heating = V_e·e^(−1/6) faster, peak-g altitude physical + deeper for higher B, scenario reproducible/MODELLED + degenerate-geometry rejected); dominance_demonstrators (reachable + reproducible + V_e·e^(−1/2) fraction + MODELLED-not-VALIDATED); tests/reentry_reconstruction_oracle.rs::reentry_overprediction_is_recorded_as_a_finding; tests/reentry_point_mass_reconstruction_oracle.rs::point_mass_peak_deceleration_matches_reconstructed_entries (cross-check only); tests/reentry_point_mass_accelerometer_oracle.rs (blocked, not run)
DVB-S2 adaptive coding and modulation along a LEO downlink pass Downlink Es/N0 along each pass of one satellite over one station (EIRP, free-space loss, cosecant-law atmospheric loss, other losses, G/T, Boltzmann's constant, symbol rate), the most efficient DVB-S2 MODCOD that clears its ETSI EN 302 307-1 V1.4.1 Table 13 quasi-error-free threshold plus an implementation margin at each step, the pass's ACM data volume, and the constant-coding baseline that closes at the mask and the longest range. Runnable as the acm-link scenario kind. Illustrative inputs; MODELLED. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency: the spectral efficiency computed in closed form from Table 5a K_bch and the frame lengths agrees with the efficiencies Table 13 prints (a transcription check on the threshold table); the link-budget pieces agree with their closed forms; the selection is monotone in Es/N0 and honours the margin; ACM moves at least the constant-coding volume. The pass geometry comes from the separately VALIDATED apparent pass predictor. WHAT IS NOT: no external tool or measured link has been compared; the thresholds are the standard's ideal AWGN values, not a modem's; rain fade, pointing loss along the pass and pilots are not modelled. contact_schedule (es_n0_db, select_modcod, fspl_db, atmospheric_loss_db, ccm_modcod, pass_capacity, AcmLinkScenario); passes::predict_passes_apparent contact_schedule::tests::modcod_efficiency_closed_form_matches_the_printed_table; contact_schedule::tests::modcod_selection_is_monotone_and_honours_the_margin; contact_schedule::tests::link_budget_pieces_have_closed_forms; contact_schedule::tests::acm_link_defaults_run_and_acm_beats_ccm
Multi-satellite, multi-station ground-contact scheduling with conflict resolution Candidate contacts from every satellite-station pass with its ACM data volume; conflicts where one antenna would serve two satellites inside its turnaround or one satellite would downlink to two stations at once; a priority-weighted delivery objective capped at each satellite's backlog; a lazy marginal-value greedy plan, a first-come baseline and an exact branch and bound on up to 26 candidates, with the greedy's optimality gap reported. Runnable as the contact-schedule scenario kind. Illustrative inputs; MODELLED. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency: the exact branch and bound agrees with brute-force enumeration on small random sets, every plan is checked feasible against the conflict rules, and the greedy never beats the exact optimum. WHAT IS NOT: no external scheduler or operational plan has been compared; contacts are taken whole (no splitting), the backlog is fixed at the window start, slew time beyond the fixed turnaround and onboard storage are not modelled. contact_schedule (conflicts, objective, delivered, schedule_chronological, schedule_greedy, schedule_optimal, ContactScheduleScenario) contact_schedule::tests::conflicts_cover_turnaround_and_one_station_per_satellite; contact_schedule::tests::greedy_is_feasible_and_the_exact_solver_beats_or_ties_it; contact_schedule::tests::exact_solver_matches_brute_force_and_plans_are_feasible; contact_schedule::tests::exact_solver_declines_above_the_limit; contact_schedule::tests::contact_schedule_defaults_run_reproducibly; contact_schedule::tests::scenarios_reject_bad_inputs
Frugal cost-per-coverage / ROI framing Cost-per-percent-coverage + coverage-per-euro ROI over the constellation sizing engine; per-satellite cost is a caller-sourced low/nominal/high bracket (no fabricated prices) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed-form cost arithmetic vs hand-derived values; an economic FRAMING of a modelled coverage figure, not a quote or validated cost model frugal (over walker) frugal::tests (hand-derived cost-per-coverage 48/96=0.5, ROI ratio 2.667, bracket-ordering + zero-coverage guards)
Detection-miss integrity impact (context-aware HPL/VPL vs alert limit) Maps an undetected spoof/jam bias to effective error → Stanford region (available/unavailable/MI/HMI) against context-specific HAL/VAL (open-sky vs urban) ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — Composes the externally-validated RAIM Stanford classification (raim::classify_stanford); the detection-miss→AL mapping itself is modelled, not a certified integrity allocation integrity_impact (over raim) integrity_impact::tests (same miss flips Available→MI→HMI as the context tightens; conservative-PL→Unavailable; per-axis HMI; input guards)
CAI cited error-model parameter sheet (13503) Bracketed (best/nominal/conservative) cold-atom-interferometer performance — bias instability, velocity/angle random walk, scale-factor stability, interrogation-limited sample rate, fringe-ambiguity dynamic range — each citation-traceable; feeds QuantumNavBudget without modelling hardware InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency: the cited VRW bracket cross-checked against CaiAccelerometer::accel_asd physics + raw dynamic range computed from the fringe-ambiguity limit; numbers are MODELLED literature-survey brackets (needs_source_confirmation), no device validated, no validation halo inertial::cai_params (over inertial::quantum_imu) inertial::cai_params::tests (physics VRW lands inside the cited VRW bracket at all 3 levels; raw fringe-ambiguity range computed from k_eff·T²; conservative budget drifts more than best; every bracket sourced + confirmation-flagged; bracket-ordering guards)
Timing-integrity conformance benchmark — Stanford integrity-diagram epoch classifier TIB Stanford integrity-diagram epoch classification (nominal / unavailable / MI / HMI) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Independent numpy re-implementation of the four-region rule (scripts/gen_tib_scorer_reference.py) on the identical sample set; method Cited from the Stanford–ESA integrity diagram (Tossaint et al., ION GNSS 2007) and RTCA DO-229 WAAS MOPS. NOT an ExternalDataset accuracy oracle — the benchmark is honesty-immune. src/benchmark/stanford.rs src/benchmark/stanford.rs::tests (four regions + inclusive boundaries + |error| + PL>AL unavailability); tests/tib_scorer_reference.rs (classification counts vs independent numpy on a fixed synthetic set)
Timing-integrity conformance benchmark — integrity-coverage scorer TIB integrity-coverage scoring (HMI/MI/availability rates + overbound-coverage verdict) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Independent numpy region re-count in tests/fixtures/tib/reference.json; scorer machinery cross-check only, no accuracy claim. src/benchmark/coverage.rs src/benchmark/coverage.rs::tests (clean/under-bounded/all-unavailable/empty); tests/tib_scorer_reference.rs (counts + rates + coverage_ok vs numpy to 1e-12)
Timing-integrity conformance benchmark — fault catalog (parametric generators) TIB fault menu (domain-divergence, clock-slam, holdover-coast, static/incremental/symmetric/asymmetric delay, replay-within-freshness, path-selective, k-of-N quorum) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Representative parametric fault generators (Modelled); the undetectable set (symmetric delay, replay-within-freshness) is Cited from Mizrahi RFC 7384 and Narula & Humphreys (IEEE JSTSP 2018). No external oracle — a fault catalog makes no measured claim. src/benchmark/faults.rs src/benchmark/faults.rs::tests (offset profiles, monotone coast, undetectable-set flagging, max_offset consistency, exactly two undetectable classes)
Timing-integrity conformance benchmark — undetectable-absorption verdict TIB undetectable-absorption verdict (symmetric/replay must be absorbed by the PL, never reported detected) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Property check that the Verdict enum structurally cannot report an undetectable fault as detected (Mizrahi RFC 7384); absorbed ⟺ PL ≥ offset. No accuracy oracle. src/benchmark/scorecard.rs src/benchmark/scorecard.rs::tests (reference PL absorbs; broken PL unabsorbed-never-detected; detectable coverage verdict; the honesty property that no coverage/detection verdict is reachable for an undetectable scenario)
Hybrid optical/RF report self-description The hybrid-optical-rf report states the link configuration it actually ran at (carrier wavelength, transmit and receive aperture, range, pulse width, integration time, efficiencies and losses, defaults resolved) and carries a units block giving the unit and provenance class of every quantity a paper is likely to quote, including the handoff covariance traces in square metres InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — No external oracle, and none is possible: this is self-description, not a measurement. It is recorded because the absence of it was a defect -- P5 had to quote the carrier wavelength and transmit aperture from source defaults, and to infer that a bare variance was in square metres from an internal consistency check. The inference was correct, which is precisely why it mattered: nothing would have caught it being wrong hybrid_integrity hybrid_integrity::tests (the resolved configuration is echoed for defaults and for overrides, without round-tripping the wavelength through metres; every units entry carries both a unit and a provenance class; every field the units block names is actually emitted, so it cannot document a ghost)
Hybrid optical/RF link availability on the RF side The hybrid-optical-rf report states an RF link availability, composed from quantities the engine already computes rather than from an imported climatology, and states the composition as a named rule: A_rf = I_closure * I_track, where I_closure is the closure verdict of the one-way CCSDS-401 / DSN-810-005 link budget (linkbudget::link_budget, Eb/N0 margin >= 0) at the scenario's own range and I_track is the tracking-loop verdict (jamming::lock_status) on the C/N0 that SAME budget returned. Each factor carries its input's provenance class through to the output, and the factors deliberately NOT in the product -- geometric visibility, interference denial, and an RF outage climatology -- are named with the reason rather than silently set to 1. The resolved RF leg is echoed as its own rf_link_configuration block, and the continuous figures beside the indicator (link margin, C/N0 margin, the closed-form closure and tracking ranges, and the range utilisation) are the range inversions of the same budget. The report states in full, on the block and in the units entry a reader lands on, that this figure is MARGIN/GEOMETRY-LIMITED and DETERMINISTIC while optical availability is WEATHER/CLIMATOLOGY-LIMITED and probabilistic, so the two can never be quoted as a comparable pair of percentages InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — No external oracle, and ExternalDataset is declined. The two inputs are an Eb/N0 margin and a C/N0 threshold crossing, both functions of a MODELLED EIRP, figure of merit and lumped loss allocation; there is no measured availability record for an Earth-Moon optical/RF hybrid service to check the composed figure against. The checks that exist are internal and are stated as such: the composition is recomputed from the report's own published margins rather than from the emitter's internals, and the closure range is verified by re-running the link equation AT it and requiring the margin to vanish -- an inversion round trip, not an independent implementation. The honest limit of the figure is recorded on the report itself: it is a deterministic 0/1 indicator, not a probability, because nothing in this engine measures an RF link-outage distribution at this band and geometry. That missing input is named in rf_availability.factors_not_included rather than invented, and supplying it is what a probabilistic RF availability would need hybrid_integrity, linkbudget, jamming hybrid_integrity::tests (the availability equals the product of the two indicators recomputed from the report's own margins, and those margins are themselves reassembled from the report's own EIRP, free-space loss, lumped loss, figure of merit, Boltzmann term, data rate and requirement to 1e-9 dB; the value is measured to be 0 or 1 while the optical availability at the same run is measured to be strictly between them; each factor row carries a provenance class from the closed field_schema vocabulary; the reported closure range re-run through the link budget returns a margin of 0 to 1e-9 dB and is measured to be independent of the range the run sat at across four decades, while the range utilisation moves by exactly the range ratio; a -40 dBW link reports availability 0, LOST, and a utilisation above 1 rather than a fraction; the superseded 'no RF-availability counterpart is computed by this engine' note is asserted gone and the replacement is asserted to name the new field; a malformed RF input is refused rather than clamped)
Like-for-like optical-versus-RF ranging comparison The hybrid-optical-rf report emits the optical-versus-RF ranging ratio with the ONE configuration both legs were evaluated at carried in the same object: the same one-way path, the same range, and the same accumulation time. The optical leg is the engine's photon-limited ToA CRLB on the one-way photon count; the RF leg is the engine's DLL early-late thermal code-tracking jitter at the C/N0 the engine's own link budget returns for that same one-way range. The loop noise bandwidth is derived, not chosen: B_L = 1/(2*integration_s) puts the RF leg at exactly the optical accumulation time, and if a caller overrides it so the two averaging times disagree the ratio is REFUSED -- null, with the mismatch and both times named -- rather than quoted at two operating points. No ratio is formed against the scenario's CHOSEN parametric rf_position_sigma_m, and the refusal says why: that input carries no configuration at all. The released two-way optical headline and the exact factor bridging it to the one-way comparison leg are emitted beside the ratio, so the report cannot be read as carrying two disagreeing optical sigmas InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — No external oracle for the RATIO, and ExternalDataset is declined deliberately. The underlying RF chain does have one -- tests/validate_p5_rf_ranging_precision.rs checks linkbudget::link_budget and navsignal::dll_code_jitter_chips against an independent Python/NumPy fixture and against the hardcoded Kaplan & Hegarty worked value (2.814e-3 chip / 0.825 m at 45 dB-Hz) -- and the optical CRLB has its own closed-form row. Claiming either anchor for this row would be borrowed validation, which the matrix invariants exist to prevent: the quantity here is a RATIO at a configuration with a MODELLED EIRP, figure of merit, transmit power and aperture, and no measured optical-versus-RF ranging comparison at a common operating point exists to check it against. What is checked internally is the thing the ratio can actually get wrong: that the two legs sit at one operating point. That is measured by scaling the common accumulation time and requiring both legs to move by the same square-root law and the ratio to stay put, and it is enforced by refusing the ratio outright when the averaging times disagree. Both legs are thermal/shot-noise bounds and both exclude media delay, clock error and ambiguity, so the exclusion is identical on each side; the report says so rather than leaving it inferred hybrid_integrity, optical_linkbudget, linkbudget, navsignal hybrid_integrity::tests (the ratio equals the two emitted legs divided, to 1e-15 relative, and its reciprocal and decibel forms agree; each leg's range and time sigma are related by exactly c; the emitted common configuration is asserted equal to the scenario's own range and integration time and the RF leg's range is asserted equal to the optical leg's; the RF leg's C/N0 is bit-for-bit the availability block's, from one link budget, not a re-derivation; the LIKE-FOR-LIKE property is MEASURED rather than asserted -- quadrupling the common accumulation time halves the optical leg to 1e-12 and the RF leg to 1e-7 and leaves the ratio unmoved to 3.19e-9 relative, which a leg secretly averaging over something else could not do; an rf_dll_bandwidth_hz override that breaks the common averaging time makes the ratio null with a reason naming both times, while both legs are still emitted; a one-way run makes the comparison leg bit-for-bit the released headline with a penalty factor of exactly 1, and a two-way run reproduces the penalty 0.5/sqrt(return-path geometric loss) recomputed from the report's own geometric_loss_db to 1e-12)
Link-budget report self-description The link-budget report states every absolute constant its own margin was computed from -- the carrier frequency the free-space loss used, the EIRP, the figure of merit, the lumped loss and the Boltzmann term -- plus the required G/T at which the margin is zero, the link constant (EIRP - losses - required Eb/N0) that is the only combination a published rate/gain table can ever fix, and, when a caller states a system noise temperature, the receive antenna gain that figure of merit implies InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — No external oracle: this is self-description over an equation already validated against a published design-control table (see the one-way link budget row). It is recorded because the absence of it was a measured defect -- reproducing the released d1_rate_gain_beamwidth.csv required back-solving one effective constant to 0.0034 dB from all thirty rows, and the engine now both names that combination and proves, by test, that no released table could ever have separated its three components linkbudget linkbudget::tests (across three bands, four decades of range and both closure verdicts, the margin and the free-space loss under it are recomputed from the report alone to better than 1e-9 dB; the required G/T assembled from the equation terms agrees with the same quantity reached as G/T minus margin, and re-running at it zeroes the margin; three budgets with wildly different EIRP, loss and threshold but an equal link constant give an identical requirement, while 1 dB on the constant moves it exactly 1 dB; the gain split is absent unless a noise temperature is stated and a non-positive one is refused; every field the units block names is actually emitted)
Per-clock-class lunar time crossover table One lunar-time-budget run emits a clock-vs-frame crossover row per clock class against a single shared frame term, so the clock is the only variable in the comparison; each row carries the crossover reached two ways -- bisected from the general power-law time-error curve and inverted algebraically from the row's dominant noise type -- with the relative difference between them InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Two different in-codebase computations of the same quantity, not one restated: bisection on the IEEE-1139 power-law curve knows nothing about noise type, while the closed form inverts the dominant type algebraically, so a misclassified noise type or a bad bracket shows as a non-tiny relative difference. The four values also reproduce the paper's published table to half its last printed digit -- but that table was itself reconstructed from the same closed form, so it is a reproducibility check and not an external oracle, and the frame term it is measured against is a Modelled allocation lunar_time_budget lunar_time_budget::tests and lunar_time_budget_scenario::tests (all four classes present in one run and in a requested subset order; every row agrees with its own closed form to better than 1e-12 relative; scaling the frame error by k scales the crossover by k for a flicker-FM clock and by k^2 for a white-FM one, checked at k=2 and k=3, which separates the two noise classes; each row reproduces the single-clock crossover the budget already reported; every row recovers the one shared frame term; an unknown clock name is rejected)
Capture footprint against altitude and beamwidth Two-axis sweep of the pattern-weighted, altitude-limited surface capture footprint over transmitter altitude and dish diameter, emitted one row per operating point with the half-power beamwidth each diameter implies, and limb capture reported as a THRESHOLD -- per row the limb J/S, its margin and the transmit power that would close it; per grid the located crossings, or an explicit statement that the limb is not reached anywhere on the grid, with the shortfall InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Set inclusion: the jammer-to-signal ratio enters as a uniform decibel offset, so the captured set at a higher transmit power contains the set at a lower one and the fraction can only rise -- a property the Airy pattern does NOT give in beamwidth or altitude, where the captured region breaks into rings and the fraction is genuinely non-monotone. No published table gives the captured disk fraction of a lunar orbital transmitter against altitude and beamwidth, so there is nothing external to check these cells against; the pattern underneath is separately Validated against published Bessel values and keeps its own row antenna antenna::tests and attack_surface::tests (the grid is complete and every captured fraction lies in [0,1]; captured fraction is non-decreasing in transmit power at every node; it is NOT monotone in beamwidth or altitude, which is pinned by its own test so the sweep cannot later be smoothed; the baseline node reproduces the existing captured fraction bit-for-bit; the limb-only evaluation is bit-identical to the full sweep's last point; a located crossing sits on the threshold to 1e-9 dB and is straddled)
Lunar time-error budget reproducibility The lunar-time-budget scenario publishes its array-valued outputs as a long-form (grid index, averaging time, term) table alongside the report, so the seven per-term x(tau) curves and the root-sum-square total are engine output rather than something a reader rebuilds from the method section InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Self-consistency only: the published total is checked against the root-sum-square of the terms in the same file, and the emitted curve reproduces the released p3_time_budget_curve.csv over all 57 points. Both checks share this engine's own term definitions, so neither is independent. The clock term rests on published clock specifications, but the link, frame, relativistic and ephemeris floor MAGNITUDES are documented budget allocations with no external oracle lunar_time_budget_scenario lunar_time_budget_scenario::tests (all 57 averaging times x 8 terms present, the grid index runs 0..=56 and carries 8 rows each; the total row equals the root-sum-square of the seven terms beside it at every tau; the table follows a requested grid rather than a hard-coded one; emitting it leaves the report JSON byte-identical)
Lunar station time laboratory: miniRAFS holdover against LTC The optional [time_lab] block of the lunar-time-budget scenario models a lunar reference station clock (default the miniRAFS class, or any named class, or a device card fitted to stated stability points) steered to Coordinated Lunar Time and then free-running or re-steered every N seconds: the time-error curve x(t) as the root-sum-square of the clock power-law term, a constant steer residual (ILLUSTRATIVE), a constant LTC realisation residual and an opt-in station-height rate term; the time after a steer to 1, 10 and 100 ns (or stated thresholds) by bisection beside the closed-form inverse for the dominant noise type, and the dominant term at each stated horizon, all with units InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency only: the bisected time to threshold is checked against the closed-form inverse of the clock's dominant noise type, and the free-running clock term against the budget's own clock term. The clock classes rest on published one-day specifications (their own rows); the LTC rate is not re-derived here and keeps its own VALIDATED row (Lunar coordinate time); the steer residual is ILLUSTRATIVE, the realisation residual is a budget allocation and no thermal model is included. The nanosecond-level target described in the ICG WG-B Lunar PNT material of June 2024 is quoted as a source statement, not adopted as a claim; nothing here is a statement about any real station clock lunar_time_lab (over clock_specs, lunar_time_budget, lunar_time) lunar_time_lab::tests (free_run_clock_term_is_the_budget_clock_term: with steering off the clock term equals the budget's clock term to the bit for all four classes; bisection_matches_the_closed_form within 1e-9 relative for both noise classes; threshold_below_the_floor_is_flagged; steering_holds_and_resets; height_term_is_opt_in_and_linear; device_card_reproduces_a_named_class; bad_inputs_are_refused); tests/lunar_station_time_lab.rs (the_block_is_additive: the default document, table and summary are unchanged and the block adds only its own object and units; time_to_threshold_matches_the_closed_form_through_the_scenario; clocks_are_ordered_over_the_span_where_the_model_orders_them: optical < PHM < RAFS < miniRAFS from 1 s to 7e5 s, with the PHM and RAFS curves crossing between 7e5 and 8e5 s pinned as a disclosed property of the single-noise-type clock models; every_time_lab_field_has_a_unit; unknown_time_lab_fields_and_clocks_are_refused)
Lunar geodetic VLBI Near-field VLBI delay for an Earth baseline observing a lunar beacon + partials ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — Plane-wave delta_dor (same-codebase) in the far-field limit; finite-difference partials. 0.30 external comparison, a finding (stays MODELLED): against ANISE 0.10 converged light times through DE440 (75 delays on 2024-01-01 over three DSN baselines, generated by xval/anise-lunar-od without Kshana code), no delay is within the 1 ps tolerance. The largest gap is 24 µs, from the analytic Moon centre (about 200 km from DE440), the single instantaneous geometry with no light-time iteration (3.6 µs) and the dropped polar motion; beacon partials differ by up to 2.9e-3 relative against 1e-6. The module-doc claim that the frame approximations are below the model fidelity does not hold at this level. 0.30 round 2: the kernel path (lunar_vlbi::KernelGeometry) is validated against NAIF SPICE light times in its own row, Lunar geodetic VLBI, kernel path; the ANISE comparison of that path (75/75 within 1 ps, worst 0.12 ps, tests/lunar_vlbi_anise_oracle.rs::kernel_delay_matches_the_anise_light_time_difference) is a kernel-evaluation cross-check only, because the light-time solve in that harness is this project own. This row (the analytic default path) stays MODELLED with the finding above lunar_vlbi lunar_vlbi::tests (far-field limit matches delta_dor; near-field correction; FD partials); tests/lunar_vlbi_anise_oracle.rs::near_field_delay_disagrees_with_the_anise_light_time_difference
Earth-GNSS at lunar distance Earth-GNSS reception at lunar distance: the weak-signal layer P7 Table 1 names and the engine had no model for. Per satellite and per epoch it computes the off-boresight angle against the transmitter nadir, whether the Earth occults the straight path, the slant range and its free-space loss, the transmit gain at that angle, the received power and the carrier-to-noise density; it then aggregates only the links clearing a tracking threshold, and sweeps a full constellation revolution so the answer is a DISTRIBUTION rather than one snapshot. Three facts drive the result and the report states each: the Earth subtends 13.90 deg from the constellation radius so the beam PEAK is geometrically unavailable to any lunar-bound ray; what remains is the main-lobe edge and the sidelobes, the regime LuGRE operated in at the Moon in 2025; and the L1 path loss is about 208 dB, some 25 dB more than a terrestrial user pays. MEASURED on the bundled 24-satellite GPS-class geometry over 64 epochs of one orbital period: SIGNAL availability 0.375 with a best link of 30.93 dB-Hz, and FIX availability 0.000 - at most two simultaneous trackable links, never the four a position needs. The separation of those two availabilities is the point, and the report refuses to let them be confused: Earth-GNSS at lunar distance is a TIMING-grade layer, not a position-grade one, and a layered-resilience prior must take the fix availability. The conditioning is emitted for the same reason - every visible satellite lies inside a cone a couple of degrees wide as seen from the Moon, so the lines of sight are near-parallel by construction. Runnable as the earth-gnss-lunar kind Restated per D7: the claim at lunar distance is the RELATIVE carrier-to-noise density between satellites at one epoch, from measured two-dimensional transmit patterns (NAVCEN Block IIR/IIR-M), plus geometric visibility; absolute C/N0 is not claimed (Parker et al. report a common 7 to 12 dB loss). InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed-form identities and internal consistency; NO external oracle is claimed. The limb half angle is checked against asin(R_earth/r_orbit) and the geometry against it; the free-space loss, the DOP kernel and the SGP4 propagation this composes are each externally validated in their own rows and this row does not borrow their status. WHY MODELLED, and it is the transmit pattern: the gain at angle is a uniformly illuminated circular aperture, the Airy pattern, while a real GPS L1 antenna is a twelve-element helical array with a shaped main lobe peaked off-boresight to even out power across the Earth disc and sidelobes that are not Airy. Published measured patterns exist and are not vendored here, so orderings and orders of magnitude carry, while the dB of any single satellite does not. A FIRST IMPLEMENTATION OF THIS ROW WAS WRONG IN A WAY WORTH RECORDING: the Airy expression is valid only in the forward hemisphere, its argument goes as sin(theta), and at theta near 180 deg it wraps around and returns FULL BORESIGHT GAIN behind the aperture - so the two strongest links in the first report were satellites pointing their antennas away from the Moon, and they were the only two that cleared the threshold. Behind the aperture the model now applies a flat back-lobe floor, stated as a bound rather than a fabricated pattern shape. Deliberately absent, each making the budget OPTIMISTIC: no ionospheric or tropospheric loss on the limb-grazing rays, no polarisation, pointing or implementation loss, and a spherical Earth with no refractive extension. The Moon position is an INPUT, not an ephemeris lookup, because the quantity under test is the link and the beam geometry. Upgrading this row to Validated needs a measured transmit pattern and LuGRE normal points to check against; neither is in the repository and neither is invented here. 0.30 round 2, a finding (stays MODELLED): a measured-input link path (real SP3 positions, per-block transmit power, tabulated transmit and receive patterns, acquisition and tracking hysteresis) was checked against Montenbruck et al. 2023 Table 3 for GENESIS at 6000 km (pre-registered 758df4eb): zenith-antenna means agree on 5 of 6 within one dB of the paper sensitivity; nadir-antenna means are 1.0 to 2.4 satellites higher than printed, plausibly because the paper used azimuth-dependent GPS side-lobe patterns that are not published. The lunar-distance figures of this row still use the Airy stand-in. 0.30+ D7, a finding (stays MODELLED): the restated quantity, the C/N0 DIFFERENCE between Block IIR/IIR-M satellites tracked at one epoch, predicted with the NAVCEN per-SVN measured L1 patterns (two-dimensional, yaw-steering frame) against the LuGRE flight C/N0 (pre-registered 7425dc34: 99 % visible, pair RMS <= 3.0 dB, median <= 2.0 dB, at least 50 records and 30 pairs) has too little data: the 26 qualifying transit and lunar-orbit epochs hold 15 tracked IIR/IIR-M records (mostly IIF and III are tracked) and one pair. All 15 are predicted visible and the single pair's residual is -0.06 dB; nothing is claimed earth_gnss_lunar earth_gnss_lunar::tests (11 lib tests: the Earth-limb half angle against its closed form asin(R/r) with a further assertion that EVERY un-occulted link lies outside that cone, so the occultation test and the limb angle cannot disagree; the occultation predicate checked on the near side, the far side and the case where the body lies BEHIND the transmitter; path loss bounded to the plausible lunar-range band on every link; the trackable set shown to be a subset of the geometrically visible set and disjoint from the occulted one; monotonicity in both directions - more receiving gain never reduces the count, a stricter threshold never raises it; no link credited with more than boresight gain; a receiver inside the Earth refused; the sweep asserted to actually VARY with epoch; and signal-vs-fix availability asserted distinct, correctly ordered, and consistent with the per-epoch rows); tests/earth_gnss_measured_montenbruck_oracle.rs::finding_genesis_nadir_counts_exceed_the_paper (pinned); tests/lugre_relative_cn0_visibility.rs::too_few_iir_records_at_lunar_distance_for_the_relative_cn0_bar (pinned finding)
Lunar orbit determination: Earth-GNSS against ground radiometric Orbit determination in a near-rectilinear halo orbit (or an elliptical frozen orbit) from two independent data types: Earth-GNSS pseudoranges received on board (the link rule of the Earth-GNSS-at-lunar-distance row, plus Moon occultation) and ground two-way range and range-rate from three Deep Space Network stations. Each is a one-step batch least squares about the reference orbit with its formal covariance; a seeded Monte Carlo of the difference between the two estimates tests whether the two covariances explain it (q = d' (P_G + P_R)^-1 d, chi-square with six degrees of freedom when the models match) and what an unmodelled acceleration does to the statistic. ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — An independent scipy/numpy program integrates the same variational equations (bar O1). Nothing is compared with a measurement of a lunar orbit. The oracle checks the numerics of stated formulas, not the physics, so the row stays MODELLED. Restricted three-body model: no Sun, no lunar harmonics, the Earth rotation axis along the orbit normal, ILLUSTRATIVE receiver and station inputs. lunar_infra::{orbit, gnss, od} tests/lunar_infra_od_consistency.rs (bar O1: the state-transition matrix chained over three days and over one period equals scipy DOP853 to a relative 1e-6; bar C1: mean q and the in-95 % fraction; bar C2: sample over formal trace of each estimator; bar C3, NOT MET and pinned: with 3e-10 m/s2 of unmodelled acceleration the in-95 % exceedance is 0.0525, not at least 0.5 - the on-board estimate is known only to hundreds of metres, so about ten metres of displacement hides inside its covariance); lunar_infra::orbit::tests, lunar_infra::gnss::tests, lunar_infra::od::tests, lunar_infra::la::tests
Lunar carrier-phase ambiguity resolution: surface and orbiter Between-receiver single-differenced Earth-GNSS carrier phase and code at a lunar surface station and an orbiter, with the per-epoch clock difference profiled out, one ambiguity per continuous pass and the longest pass as the gauge. The float ambiguity covariance is a Schur complement; LAMBDA resolves the integers, the bootstrapped rate is reported beside a seeded Monte Carlo integer-least-squares success rate and the float and fixed position sigmas. Reported as found: at the registered 12 dBi the double-difference problem is not formable (amendment 1 moved the default to 25 dBi after availability counts only were seen), and at 25 dBi integer fixing is NOT achieved - out of reach (a few percent at most) although the float solution improves with the arc. ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — An independent numpy solve of the same normal equations from the exported rows (Q3) and a brute-force integer enumeration (Q4). No GNSS or lunar carrier-phase measurement is compared with. MODELLED. lunar_infra::phase; lambda tests/lunar_infra_carrier_phase.rs (bar Q1: Monte Carlo success at least the bootstrap bound minus three standard errors; Q2: no fall with arc length beyond three standard errors; Q4: LAMBDA equals brute-force enumeration for 200 draws of dimension up to five; Q3: the float design equals an independent numpy solve to 1e-9 for the ambiguity and position covariances, and the bootstrapped rate is NOT MET at 1e-9, pinned: it differs by a relative 1.7e-6 because LAMBDA's normal CDF is an Abramowitz and Stegun approximation)
Lunar frame co-estimation: surface stations and orbiters Fisher information of the seven-parameter lunar frame datum from Earth-station laser ranging to the five reflectors alone and with orbiter-to-surface-station ranges added: the information matrix, rank, Cramer-Rao sigmas, the degeneracy metric of the lunar identifiability module and seeded random station sets. The orbit is held known in the lunar axes (its error is carried by the orbiter range sigma). ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — An independent numpy finite difference of the forward model (F2). Nothing is compared with real lunar frame solutions. The factor is conditional on the assumed known orbit and the 1 m range sigma. MODELLED. lunar_infra::frame; lunar_datum; lunar_identifiability; lunar_llr_geometry tests/lunar_infra_studies_3_5.rs (bar F1: the CRLB trace does not rise and the smallest eigenvalue does not fall with orbiter links, in the example and in 20 seeded random sets; bar F2: the range partials equal an independent numpy longdouble finite difference of the Rodrigues forward model on 50 geometries; bar F3: the smallest eigenvalue rises by at least 2.0x, found about 111x)
Space-tie frame-tie precision: co-located GNSS, VLBI and laser ranging Cramer-Rao precision of the inter-technique translation, scale and rotation offsets between GNSS, VLBI and laser-ranging frames when one spacecraft carries all three, with the spacecraft position eliminated at every epoch and nine local-tie nuisance parameters carrying a prior, swept over the local-tie accuracy. Covariances by the square-root route (normal equations lose the digits when the techniques are near perfect). ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — An independent numpy stacked system with the position unknowns eliminated by explicit Schur complements (T3). No GRASP, Genesis or other mission data are compared with. MODELLED. lunar_infra::tie; fim::crlb_srif tests/lunar_infra_studies_3_5.rs (bar T1: translation sigmas do not fall as the local tie loosens; T2: with technique sigmas scaled by 1e-6 each pair's translation sigma is within 1 % of sqrt(2) times the local-tie sigma, found within 3e-7; T3: the information matrix equals an independent numpy stacked assembly to 1e-9). The first T2 run with normal-equation inversion missed (1.3 % at a 0.1 m tie, values below the floor at 1 m); the cause was numerical and the covariance moved to the square-root route before the bar was rescored.
Lunar Love-number and libration sensitivity Fisher information of h2, k2, l2 and the physical libration amplitudes from laser ranging (radial and horizontal tidal displacement, reflector rotation), orbiter tracking (the degree-2 k2 acceleration integrated along the line of sight, trend removed), a surface gravimeter (gravimetric factor 1 + h2 - 1.5 k2) and a surface clock (fractional rate (1 + k2 - h2) W2/c2, tied to the lunar-time constants). h2 and l2 nominal values are linearisation points; the study says what is sensitive to what, not what the numbers are. ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — An independent numpy finite-difference assembly (G2) and closed-form evaluation (G4). The k2 sensitivity of the orbiter family is an upper-end figure (the orbit state absorbs only a constant and a trend here). No lunar tide or libration measurement is compared with; k2 is quoted from Lemoine et al. 2014 as a nominal. MODELLED. lunar_infra::geodesy; lunar_od::degree2_tide_accel; lunar_time tests/lunar_infra_studies_3_5.rs (bar G1: analytic partials equal a central finite difference of each forward model to 1e-8; G2: the 5x5 information equals an independent numpy assembly to 1e-6; G4: the clock tide amplitude and its k2 and h2 sensitivities equal an independent evaluation to 1e-9; bar G3 NOT MET in its trace half, pinned: adding a family never lowers the smallest eigenvalue (28 of 28) but the pseudo-inverse trace rose in 12 of 28 additions because the added family raised the rank)
Lunar surface-beacon DOP augmentation Beacon-augmented dilution of precision for a lunar surface user: the visible-satellite line-of-sight rows and the visible-surface-beacon ranging rows are concatenated into one design matrix and evaluated through the shared DOP kernel, and the resulting DOP is mapped to a realised 1-sigma accuracy IN METRES through a per-beacon user-equivalent ranging error assembled as the root-sum-square of clock-synchronisation, multipath and survey terms. Beacon visibility is the airless-Moon two-height geometric horizon, which has no refractive extension and is therefore exact rather than approximate. Runnable as the lunar-beacon scenario kind, which reports satellites alone, satellites plus beacons, and a larger constellation as the competing route to the same geometry. MEASURED on the bundled golden geometry (user at -80 deg, three surveyed beacons, six-satellite illustrative LCNS at t=0, 5 deg mask): 5 visible satellites give PDOP 9.6941 and a 3-D 1-sigma of 11.222 m; adding the beacons that actually clear the horizon gives PDOP 4.1160 and 4.765 m, a factor of 2.355; the 24-satellite service instead gives PDOP 2.4226 and 2.804 m, a factor of 4.002. The report prints the VISIBLE beacon count rather than the configured one, and on this geometry only ONE of the three beacons clears the horizon: the two flanking sites lie about 333 km from the user against an 86 km horizon for a 2 m antenna, so a reader is never left to assume all three contributed ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — The DOP arithmetic is the crate::orbit::dop kernel, separately externally validated against gnss_lib_py in tests/dop_reference.rs; this row does not re-borrow that row's status. The beacon-visibility horizon is the L01 closed form, and sigma = DOP x sigma_URE is the standard GNSS relation (Kaplan and Hegarty, Understanding GPS/GNSS, section 7). Within this row the augmentation itself is checked against an independent in-repo DOP path and pinned to a committed golden. WHY MODELLED: the constellation design, the beacon placement, the antenna heights and all three error-budget magnitudes are illustrative inputs rather than a fielded survey or a measured link, so the reported metres are a property of a chosen scenario and not of any deployed service. NOTE ON PROVENANCE: this capability was advertised in the README and exercised by two validation tests, yet carried NO matrix row and no scenario kind, so it could not be reached from a run at all. It was claimed in prose, absent from the ledger, and unreachable in the engine at the same time. The row and the kind were added together. 0.30 round 2 (pre-registered be137249), blocked (stays MODELLED): ANISE 0.10.6 visibility and a numpy DOP on the row geometry agree (visible sets exact including 72 near-horizon and 48 near-mask cases; DOP within 7.2e-13), but the reported metres are DOP times an illustrative 1.158 m root-sum-square ranging error with no oracle; the scoping that would exclude them awaits an owner decision lunar_beacon lunar_beacon::tests (horizon visibility against the L01 closed form; the beacon-augmented DOP against the bare one; the error-budget root-sum-square; the DOP-to-metres relation); tests/validate_p2_beacon_before_after_table.rs (the whole before/after table pinned to a committed golden at 1e-9 relative); tests/validate_p2_beacon_before_after_independent_dop.rs (the same geometry through an INDEPENDENT DOP path, so the augmentation is not checked against the kernel that produced it); tests/validate_lunar_beacon_anise_visibility_dop.rs::beacon_visibility_and_augmented_dop_match_anise_and_numpy
Common-mode protection level and total integrity envelope cmpl_horizontal bounds the k-sigma horizontal position error contributed by the blind common-mode class, by forming blind_position_covariance = SCovS^T and projecting it into ENU; integrity_envelope reports hpl_total = hpl_araim + cmpl. The distinction the pair exists to make: the RAIM/ARAIM RESIDUAL test is provably blind to range(G) errors, but the ARAIM PROTECTION LEVEL is not - its fault-free term already bounds them up to a provider URA plus nominal bias. The CMPL is therefore only the cross-provider EXCESS that a single provider per-provider URA/ISM does not overbound, and the sum is a conservative triangle-inequality bound rather than an RSS, valid only where that excess is not already inside URA. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Analytic projector algebra checked against itself: a covariance confined to range(G) must give a positive CMPL, a covariance confined to parity space must give approximately zero, and the envelope must sum two measurement-space-orthogonal contributions. The common-mode covariance, the constellation geometry and k are representative Modelled inputs, NOT a certified budget, and no claim is made that the triangle bound is tight. NOTE ON PROVENANCE: cmpl_horizontal, blind_position_covariance and integrity_envelope are public and shipped, and their unit tests were already cited by the common-mode blindness row, but the ENVELOPE CLAIM itself carried no row - so the one caveat that keeps it honest, that the sum is a triangle bound and not an RSS, was stated nowhere in the ledger. The row registers the claim and the caveat together. lunar_common_mode lunar_common_mode::tests (common_mode_covariance_gives_positive_cmpl, parity_only_covariance_gives_near_zero_cmpl, envelope_sums_the_two_classes, state_map_matches_split)
Lunar absolute-station observability (datum defect) Fisher-information observability of the joint lunar solve: without Earth baselines the absolute-frame datum lies in the null space of HᵀWH (station position unobservable); ≥3 baselines restore full rank and bound the station Cramér–Rao error, which the estimator attains InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Analytic datum-defect structure — the unobservable absolute-frame mode lies in the null space of the Fisher information (closed-form), the rank threshold matches the published 3-station design rationale, and the estimator attains the resulting CRLB in Monte-Carlo. The lunar geometry itself is a representative network (not a flown ephemeris), so the row stays MODELLED; the underlying FIM/CRLB engine is checked against the Kay (1993) closed forms separately. 0.30 round 2 (pre-registered e4134aa7), blocked (stays MODELLED): NumPy/SciPy recompute the rank and defect at the stated 1e-9 threshold, the station axes share of the null space (within 8.4e-10) and the station CRLB (within 1.2e-10) on 17 committed Kshana-generated configurations (P2). Not promoted: the claim that the estimator attains the bound (Monte Carlo efficiency about 0.98) has no oracle, and the scoping that would leave it MODELLED awaits an owner decision lunar_combination (lunar_observability) + fim lunar_combination::tests (rank-deficient without Earth baselines; three baselines restore full rank — the 3-station threshold from the information rank, not solve error; station CRLB attained by the estimator at efficiency 0.98; CRLB tightens monotonically with baselines); tests/lunar_observability_numpy_oracle.rs::lunar_observability_matches_numpy_on_the_committed_jacobians
LunaNet AFS spreading-code generation (LSIS V1.0) The Augmented Forward Signal codes of LSIS V1.0 (29 January 2025): the AFS-Q 10230-chip primary generated from the IS-GPS-800 L1C pilot construction with the IS-GPS-800J indices (the same 210 assignments LSIS Appendix D prints), the AFS-I 2046-chip Gold codes generated from g1 = x^11 + x^2 + 1 and g2 = x^11 + x^8 + x^5 + x^2 + 1 with each PRN's G2 delay recovered from the standard's Annex 3 file, the four secondary codes, the 1500-chip tertiary codes, the interim Table 11 node assignment and the tiered pilot code. LSIS content is read at run time from a SHA-256-verified local cache filled from the NASA-hosted PDF, never redistributed ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — Reference: the values LSIS V1.0 prints for validation (Tables C-1 to C-5, D-1 to D-6, E-1 to E-6) and its Annex 3 electronic code files, under a zero-mismatch criterion fixed before the comparison. The criterion is missed by one printed cell that is internally inconsistent with the standard's own Annex 3 file, so the row stays MODELLED; an erratum note is drafted. The same chips also equal LANS-AFS-SIM's (row 'LunaNet AFS baseband rendering against an independent generator, given its channel state') lunar_afs::codes, lunar_afs::lsis, lunar_afs::params (IS-GPS-800J indices) lunar_afs::codes::tests (maximal-length registers, Legendre balance, G2 delay round trip, tier composition); tests/lunar_afs_codes_lsis_reference.rs::afs_codes_finding_one_misprinted_table_cell (without the LSIS cache: four cited numbers pin the finding; with it: 2 937 232 chips and bits vs the LSIS Annex 3 files, printed first/last 24 chips, Legendre Tables D-1 and E-1 and G2 initialisations give exactly one differing item, the Table E-5 PRN 147 'last 24 chips' cell, which duplicates PRN 151's while the Annex 3 file agrees with the generator); the strict pre-registered test afs_codes_match_lsis_v1_tables_and_annex3_bit_exact is ignored with that gap
LunaNet AFS closed-loop decodability by an independent receiver (LSIS V1.0) A Kshana AFS recording acquired, tracked and decoded by an independent software receiver and compared with the recording's own truth labels. This proves conformance to the standard and label consistency only; it is not a statement about channel physics, propagation, received power or link budgets, whose values in the recording are chosen inputs ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — Library: PocketSDR-AFS (T. Ebinuma after T. Takasu's PocketSDR 0.13, BSD-2-Clause, commit 5b23809f30d68518b7fad7a564fd0fac57cc497d, S-band build, print-only log-level copy), under criteria fixed before each run. The third pre-registered comparison meets its decoding and tracking bars C1 and C2 in full but not its guard G0 as written (two runs of the unmodified receiver differ in the same four acquisition records), and the second missed by 5 violations, so the row stays MODELLED. LANS-AFS-SIM and PocketSDR-AFS share an author and count as one independent implementation; the frame-coding row's printed-vector checks guard against a shared misreading lunar_afs::waveform (recording and truth labels), xval/lunar-afs/run_pocketsdr.sh tests/lunar_afs_decodability_pocketsdr_v3_oracle.rs::third_run_finding_c1_c2_hold_g0_is_receiver_nondeterminism (third pre-registration: 2 nodes, 4 channels tracked, worst Doppler error 0.57 Hz, worst code offset error 0.008 chip, all 6 frames decoded with the right TOI across the 99 -> 0 wrap and matching subframe 2; G0 not met as written, the receiver's own run-to-run variation in its acquisition records); tests/lunar_afs_decodability_pocketsdr_4bit_oracle.rs::decodability_finding_five_violations (second: 5 violations); tests/lunar_afs_decodability_pocketsdr_oracle.rs::first_run_finding_no_acquisition_outside_the_receivers_4_bit_range (first: void); the strict tests of the three files are ignored with their gaps
GPS L1 C/A cross-generator conformance GPS L1 C/A spreading codes (sdr::CaCode) and LNAV subframes 1-3 (gps_lnav: IS-GPS-200 field quantisation with the specification's pi, two's complement packing, TLM and HOW words, Table 20-XIV parity with D29*/D30* inversion, the parity-solving bits of words 2 and 10) compared bit for bit with gps-sdr-sim on its bundled brdc0010.22n (32 satellites) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — gps-sdr-sim (MIT, commit 28ca29a6, run as a separate program through a committed harness), pre-registered 45ba9543 with a bit-exact bar on (A) C/A chips, (B) every computed LNAV field, (C) every parity bit. FINDING: (A) 0 of 32 736 chips differ, (C) the parity of 0 of 1 920 words differs, (B) 230 of 1 152 computed fields differ by one unit: gps-sdr-sim's eph2sbf truncates toward zero with C casts where the broadcast integer needs rounding (every differing value lies within 0.01 of a unit of Kshana's rounded integer). Stays MODELLED: the registered bar was the conjunction gps_lnav, sdr tests/gps_l1ca_gpssdrsim_cross_generator.rs::gps_sdr_sim_truncates_where_the_broadcast_integer_needs_rounding (pinned finding); tests/gps_l1ca_gpssdrsim_cross_generator.rs::ca_codes_lnav_fields_and_parity_match_gps_sdr_sim_bit_exactly (strict, ignored with the gap); gps_lnav::tests
GNSS IQ acquisition on independently generated I/Q samples iq::acq::acquire (FFT parallel code-phase search with the square-law Marcum-Q threshold) with the GpsL1Ca replica, on 20 ms of gps-sdr-sim's own 8-bit I/Q output decoded by the iq::io sample decoder (ci8, 2.6 MHz, 11 satellites, no noise): every PRN 1 to 32 searched in two 10 ms windows, the result compared with the code phase and Doppler gps-sdr-sim modulated ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — gps-sdr-sim (MIT, commit 28ca29a6) I/Q samples and its own channel state, pre-registered d9ea217d: (B1) every simulated PRN acquired, (B2) no other PRN acquired, (B3) code phase within 0.5 chip, (B4) Doppler within 125 Hz. FINDING: B1, B3 and B4 hold in both windows (worst 0.195 chip, 72 Hz), but B2 fails: all 21 PRNs gps-sdr-sim did not simulate also cross the threshold (statistic 151 to 206 against 79.5; simulated PRNs 1 300 and up). The threshold is set for Gaussian noise of the measured sample power; gps-sdr-sim adds no noise, so the cells of an absent PRN hold the other satellites' cross-correlation. Stays MODELLED: the registered bar was the conjunction iq::acq (acquire, AcqConfig); iq::io (decode_samples); iq::scene (GpsL1Ca) tests/iq_gpssdrsim_cross_generator.rs::acquisition_threshold_is_crossed_on_gps_sdr_sim_noise_free_samples (pinned finding); tests/iq_gpssdrsim_cross_generator.rs::acquisition_finds_gps_sdr_sim_satellites_in_its_samples (strict, ignored with the gap)
IQ monitors scored in lab-replay campaigns: detection, misses, false alarms and closed-form false-alarm figures iq::campaign::detect and the campaign runner: an optional [monitors] table runs the IQ monitors on every cell in the runner's single pass. The power and spectral monitors see the samples after each front-end chain; the C/N0, SQM and lock monitors see each tracked channel's loop updates. Each alarm is scored against the stated events: detected or missed per (event, alarm kind, channel), time to detect, and false alarms outside the events over their exposure. Each test's closed-form false-alarm figure is stated: power per block (exact Gamma tail), spectral excess per block (approximation), kurtosis (one-sided Gaussian), pulses (binomial ceiling), SQM per averaged update (2Q(k) = Q(1/2, k^2/2), new), and the C/N0 CUSUM's ARL0 (Siegmund). Without the table, cells, keys and digests are unchanged. No interference waveform is synthesised InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — The monitors' own closed forms on Kshana's own GPS L1 C/A scenes (noise and legitimate signals; attenuation events of the satellites' own signals), against bars pre-registered in docs/design/MONITORS-IN-CAMPAIGN.md (56322c99). FINDING: M1, M2 and M4 met. M3 met on detection (18 of 18 attenuations, P_md 0) and NOT MET on its timing clause: the median time to detect is 1.001 s against 2 x ARL1 samples = 0.433 s. The CUSUM sees one estimate per 1 s window, so the sample-count bound is below one sample. RE-RUN 0.41 (D8b row 8, docs/design/evidence/d8b-iq-timing-campaign-rerun/, 3dcbaace9): with the campaign's automatic C/N0 stride set to one NWPR window (0.020 s), M3 stays NOT MET on its timing clause, as stated before the run: 18 of 18 detected on seen and fresh seeds, median time to detect 0.221 s and 0.201 s against 0.0068 s and 0.0064 s; M1, M2 and M4 unchanged. The miss is structural (the 1 s sliding estimator's delay); a further attempt needs a new pre-registration. v2 (D8b row 8 v2, PREREGISTRATION-v2.md, c46e1479e): with the bound per detected event D_est + 2 x ARL1 x stride, D_est the first stride at which the noise-free drop CUSUM fed the noise-free sliding M2M4 estimate exceeds h, M3 v2 is NOT MET on its timing clause on all three seed sets: 18 of 18 detected on each; median time to detect 0.2208 s, 0.2008 s and 0.2207 s against median bounds 0.0868 s, 0.0864 s and 0.0660 s (seeds 200-205, 100200-100205, 200200-200205; largest bound 0.0916 s, so informative); the independent recomputation of D_est and the bound agrees (worst difference 0 s, bar 1e-9 s); M4 holds (0 false alarms). The cause of the gap between the noise-free and the real estimate is not established. Internal consistency only: no real receiver or recorded interference is checked iq::campaign (detect, runner, spec); iq::monitor (stats::gaussian_two_sided_pfa, sqm) tests/iq_campaign_monitors.rs: m1_power_test_false_alarm_rate_matches_the_closed_form (73 of 5900 blocks against the 99 % binomial interval [40, 80] of P_fa 0.01), m2_sqm_false_alarm_fraction_is_within_a_factor_of_2_of_2q_k (delta 0.0160, ratio 0.0131 against 0.01), m4_cn0_false_alarms_stay_within_the_poisson_bound_of_arl0 (0 against 0), the_monitors_table_parses_and_validates; m3_every_attenuation_is_detected_within_twice_the_arl1 (strict, ignored with the gap); iq::campaign::detect tests; iq::monitor::stats tests (gaussian_two_sided_tail_matches_known_values); tests/iq_campaign.rs (the pinned digests are unchanged without the table); tests/iq_campaign_cn0_bound_v2.rs (m3_v2_m4_recorded_numbers: the recorded v2 numbers, the miss included; the strict test is ignored with them)
Detection ROC of the IQ monitors from a scored lab-replay campaign iq::campaign::detect (windows, roc) and iq::campaign::report::rocs: each cell of a campaign with monitors keeps, per alarm kind and channel, the maximum of the monitor's own test statistic over each stated event window (positive) and over tiled roc_window_s windows outside the events (negative). The statistics are the block-power departure, the PSD excess, the kurtosis z, the SQM |z| of the averaged metric, and the C/N0 CUSUM. The report pools them by kind into an empirical window-level ROC with its AUC and the operating point at the configured threshold, written as roc.json (kshana.campaign-roc/1) and a Detection ROC section of report.html. A campaign without monitors writes neither InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Synthetic campaigns from Kshana's own GPS L1 C/A scenes (attenuations of the satellites' own signals), against bars pre-registered in docs/design/DETECTION-ROC.md (04981059). FINDING: R2 met (chance level with nothing to detect). R1 NOT MET: cn0_drop AUC 0.7855 against 0.95, because every negative window after an event inherits the CUSUM's decay from the detection (all 18 post-event negatives reach 81 or more; all 18 pre-event ones stay at 0). RE-RUN 0.41 (D8b row 9, f09660907): R1 MET on re-run with the CUSUM restarted at each scored window's start ([monitors] roc_restart, default on): AUC 1.0000 on seen seeds 300-305 and on fresh seeds 100300-100305; R2 still at chance; the control (restart off) reproduces 0.7855. The seen-seed outcome was largely known in advance (disclosed). Internal consistency only: no real receiver or recorded interference is checked iq::campaign (detect, report, runner); iq::monitor::spectral (kurtosis_reference) tests/iq_campaign_roc.rs: r2_with_nothing_to_detect_the_roc_sits_at_chance (AUC cn0_drop 0.500, sqm_delta 0.566, power_drop 0.639 on stated events that attenuate nothing); r1_the_cn0_drop_roc_separates_6_db_attenuations (strict, ignored with the gap); iq::campaign::detect tests (the_roc_of_separated_and_of_identical_samples, windows_tile_the_time_outside_the_events)
Calibration of the open receiver's C/N0 and lock models to IQ campaign results, with stated prediction error iq::labfit (campaign, cn0, iqfit, iqreport) and [input] campaign on kshana iq labfit, Python kshana.iq_labfit and the MCP labfit tool (campaign folders inside its work directory only): reads a kshana iq campaign output folder by its DIGEST and groups the scored cells into fit units (signal x loop design x front-end chain x jammer type, never pooled). Per unit, it fits measured C/N0 against stated J/S with the spectral-separation form. Q_eff is not identifiable from C/N0 data without an independent measurement of the jammer and signal powers, so Q is stated, never fitted (the type table, the event's q, or for an unknown type the most damaging stated value, cw Q = 1). The fitted parameter is the identifiable offset delta_eff = delta - 10 log10 Q, with the correlation guard reporting the degeneracy. C/N0 bins locked under 90 % are censored and listed. The threshold J/S is given directly and by the closed form; the tracking-loop and empirical lock models are coupled through the C/N0 model, with drop and re-lock dwells. A seeded cluster bootstrap over recordings (1000 replicates) gives percentile intervals; 90 % prediction intervals come from residual draws; leave-one-recording-out hold-outs are split into interpolation and extrapolation; a pre-registered [validation] table is hashed and each bar judged PASS/FAIL. Report kshana.labfit-iq/1 as JSON, CSV and generated Markdown, with a units block. Synthetic only (no third-party recording, no jammer waveform). The receiver-log labfit path is unchanged InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Synthetic parameter recovery on Kshana's own GPS L1 C/A scenes with a known C/N0 profile imposed from the section 3.1 formula, tracked and scored by kshana iq campaign, against bars pre-registered in docs/design/LABFIT-FROM-IQ.md (section 5.1, amended 2026-10-12 in 4ca3ef3, section 13). The campaigns' C/N0 estimator (M2M4) was fixed in fa388b82, pushed before the first bar evaluation (committed together with the fit code, not alone), after one disclosed diagnostic tracking run. FINDING on the 18-event bar campaign: (c) PASS; (a') NOT MET, delta_eff error -1.097 dB against 0.5 dB (still -0.89 dB on bins at 38 dB-Hz and above); (b') NOT MET, 0 of 50 campaigns cover the truth (error -1.189 +/- 0.093 dB, interval about 0.3 dB); (d) NOT MET, closed form 2.20 dB below the direct J/S at loss, about the fitted drop dwell times the ramp rate (2.09 dB); the original Q clauses of (a) and (b) are NOT MET because Q is not identifiable. FOLLOW-UP (bars pre-registered in 99e7c599, docs/design/evidence/labfit-followup/RESULTS.md): on a stepped-J/S campaign delta_eff is recovered within +0.185 dB (S1 MET: the ramp error is estimator lag); (d) as written on it is met by the tracking-loop model (0.45 dB) but not the empirical one (6.42 dB), so S2 is NOT MET; on a fresh ramp campaign (d) with the fitted drop dwell times each event's ramp rate added is within 1 dB for both models (R1 MET), and (a') and (d) as written miss again (-1.25 dB; 2.32 and 9.47 dB). RE-RUN 0.41 (D8a row 6, 61b389998, docs/design/evidence/d8a-iq-tracking-cn0-rerun/): with the fit modelling each bin 0.5 s earlier along the profile ([campaign_fit] cn0_lag_s), still NOT MET: (a') +0.5015 dB seen (bar 0.5) and +0.399 dB fresh; (b') 0 of 50 on seen and fresh seeds, now +0.45 to +0.47 dB with every interval above the truth (the 0.5 s lag overshoots); (c) met on seen seeds, missed on fresh (time-to-loss coverage 1.000 against a bar of at most 0.98); (d) 2.19 dB seen, 0.32 dB fresh. The controls (lag 0) reproduced before scoring (disclosed). A different lag would need a new pre-registration. RE-RUN v2 (PREREGISTRATION-v2.md, scored once, 7892f3a24; determinism re-check of batch 17 on a second machine byte-identical before scoring): the fit models the estimator's own response, with no free parameter; still NOT MET: (a') met on all three sets (+0.165, +0.098, +0.099 dB); (b') 36, 32 and 27 of 50 against a bar of 45 (errors +0.083 to +0.099 dB against intervals about 0.23 dB wide); (c) time-to-loss coverage 1.000 on the v1-fresh set (bar at most 0.98), met on the other two; (d) 2.195 dB on the v1-registered set (bar 1 dB), 0.324 and 0.193 dB on the fresh sets. The method is checked, not any receiver: it cannot be VALIDATED from synthetic data iq::labfit (campaign, cn0, iqfit, iqreport, schema, mod); iq::cli::labfit tests/iq_labfit_campaign.rs: bar_c_holdout_prediction_intervals_cover_between_80_and_98_percent (PI90 coverage 0.891 over 558 bins, 0.900 over 10 time-to-loss events under each lock model), the_report_carries_its_inputs_censoring_validation_and_labels (inputs, censoring, [validation] hash and verdicts, units block audit), the_cluster_bootstrap_reproduces_from_the_campaign_and_seed, a_validation_mode_fit_refuses_to_start_without_its_table; bar_a_prime_delta_eff_is_recovered_and_q_is_stated_not_fitted, bar_d_closed_form_threshold_matches_the_direct_estimate_within_1_db and bar_b_prime_ci_subset (strict, ignored with the gap); bar_b_prime_full_set_of_50_campaigns (ignored, run before release); iq::labfit::cn0 tests (exact Q-delta degeneracy, delta recovery at the stated Q, closed-form threshold inverse); iq::labfit::iqfit tests (the lock-model conditions reproduce the C/N0 model exactly); tests/iq_labfit_followup.rs (the follow-up registered in 99e7c599: s1_delta_eff_on_the_stepped_campaign MET, s2_d_as_written_on_the_stepped_campaign asserting the recorded NOT MET, r1_dwell_corrected_d_on_the_fresh_ramp_campaign MET, in release)
GPS LNAV encoding decoded by an independent receiver library Kshana's LNAV subframes 1-3 (gps_lnav::encode_subframes) for the 32 brdc0010.22n ephemerides fed to RTKLIB's decode_word and decode_frame: parity of every word, subframe decoding with consistent issue of data, and every decoded parameter against Kshana's integer and against the input value InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — RTKLIB v2.4.2-p13 (BSD-2-Clause, commit 71db0ffa) decode_word/decode_frame as a separate program, pre-registered c26e2b28: R1 parity and decoding, R2 decoded value equal to Kshana's integer times the IS-GPS-200 scale within 2^-52 relative, R3 within half a quantum of the input. FINDING: R1 960 of 960 words and 96 of 96 subframes; R3 every parameter, week and reference times exact; R2 fails on 41 values (af1, delta-n, IDOT) by 1 to 4 units in the last place because RTKLIB's P2_43 is the decimal 1.136868377216160E-13, 2.6e-16 relative from 2^-43; dividing by RTKLIB's constant returns Kshana's integer in every case. Stays MODELLED: the registered R2 bar was too tight for the oracle's own constant gps_lnav tests/gps_lnav_rtklib_decode_oracle.rs::rtklib_recovers_every_integer_and_differs_only_by_its_decimal_two_to_the_minus_43 (pinned finding); tests/gps_lnav_rtklib_decode_oracle.rs::kshana_lnav_subframes_decode_in_rtklib_to_the_broadcast_parameters (strict, ignored with the gap)
GPS LNAV navigation-message encoding IS-GPS-200 LNAV subframes 1-3 (gps_lnav::encode_subframes: round-to-nearest quantisation of every clock and orbit parameter at the specification's scale factors and value of pi, two's complement packing, TLM and HOW words, Table 20-XIV parity with D29*/D30* inversion, the parity-solving bits of words 2 and 10), the message a GPS L1 C/A signal generator transmits ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — RTKLIB v2.4.2-p13 (BSD-2-Clause, commit 71db0ffa) readrnx parsing the IGS daily broadcast file BRDC00IGS_R_20250610000_01D_MN.rnx and decode_word/decode_frame decoding Kshana's words, run as a separate program; pre-registered a48d5b91 before the file was fetched, exact-integer bar. Mutation: truncating instead of rounding gives 235 failures. Earlier comparisons of the same encoder are recorded as findings: against gps-sdr-sim, which truncates (230 fields), and against RTKLIB's scaled values, whose decimal 2^-43 constant missed a one-ulp bar (41 values). Integrator post-verification (stays MODELLED): the comparison agrees and a parity-set mutation also turns it red, but the pre-registration a48d5b91 reached the public branch at 20:02:29 UTC, two seconds after the result commit 25638e9e (20:02:27 UTC) that already holds RTKLIB's output for the file, so the order 'registered before the file was fetched' cannot be shown; a fresh registration pushed before an unseen broadcast file is fetched would settle it gps_lnav tests/gps_lnav_rtklib_integer_oracle.rs::kshana_lnav_integers_decode_in_rtklib_from_an_unseen_broadcast_file (32 satellites of the IGS broadcast file of 2 March 2025: 960 of 960 words pass RTKLIB parity, 96 of 96 subframes decode, 608 of 608 decoded broadcast integers equal Kshana's, every input within half a quantum, week and times exact); gps_lnav::tests
Acquisition and C/N0 estimation on real lunar IQ Parallel code-phase search (acquisition::pcps_acquire: portable FFT, coherent folding, non-coherent accumulation, chi-square threshold for a search-wide false-alarm probability), refinement, open-loop prompt correlation with code Doppler and the M2M4 C/N0 estimator, run on the LuGRE L1 4-bit IQ batches read through realdata::ion_sdr InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — GNSS-SDR 0.0.19 (GPL-3.0, separate program, pinned configuration) on the nine non-surface L1 batches and the flight receiver's RAW C/N0 (LuGRE Mission Data, Zenodo 16411687, CC BY 4.0), pre-registered 7425dc34. FINDING: Kshana's reader decodes all 288 compared spans identically to an independent converter; GNSS-SDR declares 266 of 288 searches positive and Kshana agrees on all 266 decisions, but only 250 are located on GNSS-SDR's cell (A2 fails); the C/N0 leg is vacuous, no flight RAW epoch lying within 30 s of any batch (nearest 141 s). Most positives are artefacts: the bare two's-complement levels carry a -0.5 mean on I and Q, a zero-frequency line 32 dB above the noise in a 1 kHz bin, which both receivers acquire. Two batches (OP5, OP12) were excluded in error: a digit-stripped reading of their metadata was taken for a contradiction with their headers; the real cause was that the reader could not read a sample wider than a word (since fixed). Stays MODELLED acquisition, portable_math, realdata::ion_sdr, realdata::lugre tests/lugre_acquisition_gnss_sdr_oracle.rs::finding_dc_artefacts_and_no_contemporaneous_flight_cn0 (pinned finding, data-gated); tests/lugre_acquisition_gnss_sdr_oracle.rs::acquisition_and_relative_cn0_on_lugre_iq_match_gnss_sdr_and_the_flight_receiver (strict, ignored with the gap); acquisition::tests; realdata::ion_sdr::tests; realdata::lugre::tests
Acquisition on real lunar IQ against orbit-predicted Doppler (sample-power decision) acquisition::pcps_acquire with its sample-power decision on the nine non-surface LuGRE L1 batches with mid-rise levels; Doppler differences between acquired satellites compared with differences predicted from ESA final orbits and the Firefly-reconstructed Blue Ghost trajectory InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Predicted Doppler from ESA/ESOC final orbits and the NAIF CLPS reconstructed trajectory (xval/lugre-predicted-doppler/predict.py, independent of Kshana), pre-registered c9868b3e. FINDING: all 288 searches cross the threshold on noise (sample-power statistics about 430 to 520 against 346.3), so P1 holds trivially and P3 holds (274 of 288 predicted visible) while P2 fails on 4033 of 4036 pairs. The band-limited front end raises every cell's noise about 1.46 times (pinned: noise floor 292 against the white-noise 200 on OP2 PRN 1), which the sample-power statistic does not see. Stays MODELLED acquisition, realdata::ion_sdr tests/lugre_acquisition_predicted_doppler_oracle.rs::noise_alone_crosses_the_sample_power_threshold_on_lugre_iq (pinned finding, data-gated); tests/lugre_acquisition_predicted_doppler_oracle.rs::acquired_doppler_differences_on_lugre_iq_match_the_orbit_prediction (strict, ignored with the gap)
Acquisition on real lunar IQ scored by orbit-predicted Doppler acquisition::pcps_acquire with the cell-averaging decision (peak over the grid's mean cell, robust to band-limited noise) on the nine non-surface LuGRE L1 batches with mid-rise levels; Doppler differences between acquired satellites compared with differences predicted from ESA final orbits and the Firefly-reconstructed Blue Ghost trajectory InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Predicted Doppler from ESA/ESOC final orbits and the NAIF CLPS reconstructed trajectory (xval/lugre-predicted-doppler/predict.py, independent of Kshana), pre-registered 470b0fc9. FINDING: P1 and P3 hold (4 batches, 12 of 12 acquisitions predicted visible) but P2 fails on 8 of 8 pairs. The two strongest pairs match the prediction in magnitude with the sign reversed (OP2 PRN 18/24: +7670.0 Hz measured, -7693.9 predicted; OP17 PRN 11/30: +11155.0, -11114.4), so the registered I-in-the-low-nibble order is the conjugate of the batches; the six detections just above threshold match neither sign. The refinement's Doppler scatter (30 to 50 Hz between two runs) was also underestimated by the registration. Stays MODELLED acquisition, realdata::ion_sdr tests/lugre_acquisition_cell_average_doppler_oracle.rs::strong_pairs_match_the_prediction_only_with_the_doppler_sign_reversed (pinned finding, data-gated); tests/lugre_acquisition_cell_average_doppler_oracle.rs::cell_average_acquisitions_on_lugre_iq_match_the_orbit_predicted_doppler (strict, ignored with the gap)
Acquisition on held-out real lunar IQ against orbit-predicted Doppler acquisition::pcps_acquire (cell-averaging decision, false-alarm probability 1e-7) with refine_doppler_coherent on the LuGRE L1 batches recorded on the lunar surface (I in the high nibble, mid-rise levels); Doppler differences between acquired satellites against differences predicted from ESA final orbits and the Firefly landing-site kernel InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Predicted Doppler from ESA/ESOC final orbits and the NAIF CLPS Firefly landing-site kernel (xval/lugre-predicted-doppler/predict_surface.py, independent of Kshana), pre-registered 73ee3e14 on batches never opened before. FINDING: non-vacuity fails; no batch holds two acquisitions. OP40 excluded (metadata names a missing file); OP38, OP73, OP77_0, OP77_1 acquire nothing and show no false alarm at 1e-7 (top statistics 325 to 356 against 385.9); OP74 and OP76 acquire PRN 31 and OP78_0 and OP78_1 PRN 12, each alone, all predicted visible. Stays MODELLED. Disclosed deviations: the registered 10 Hz Doppler bar rests on a synthetic Monte Carlo of the coherent refinement, not on the scatter of the already-seen batches the integrator asked for; OP40 was excluded before the run because its metadata names a sample file the dataset does not ship acquisition, realdata::ion_sdr, realdata::lugre tests/lugre_surface_acquisition_doppler_oracle.rs::each_surface_acquisition_is_a_single_predicted_visible_satellite (pinned finding, data-gated); tests/lugre_surface_acquisition_doppler_oracle.rs::surface_acquisitions_match_the_orbit_predicted_doppler (strict, ignored with the gap)
Lunar differential PNT NovaMoon-class differential reference station: common-mode cancellation + baseline-growing residual + DGNSS protection levels InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Differential error-cancellation identity + reuse of the DO-229E SBAS PL machinery; the single-difference + WLS solve is additionally cross-checked against RTKLIB's lsq()/matinv() (Takasu, BSD-2-Clause, compiled C) — independent solver code, but the same first-order LOS-difference algebra, so still InternalConsistency lunar_dpnt lunar_dpnt::tests (clock common-mode cancels exactly; residual grows with baseline; reuses SBAS PL; the satellite count is honoured to the builder's limit of 24, so a larger constellation cannot silently return a smaller one); tests/lunar_differential_pnt_reference.rs (single-difference residual + WLS position solve vs RTKLIB's lsq() compiled from C source)
Lunar interoperability export LunaNet/IOAG-aligned lunar frame + time + ephemeris export (CCSDS OEM + KIF) with round-trip conformance InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — kshana's lunar OEM export re-parsed by the independent third-party oem library (R. J. Anderson): frame/time tokens and per-epoch state agree to write precision (1 mm / 1e-9 km/s) and a dropped-TIME_SYSTEM export is rejected — a structural interchange round-trip; the lunar frame/time physical semantics are validated by their own rows, so this stays MODELLED. 0.30 external comparison, a finding (stays MODELLED): a second independent reader, the Orekit 12.2 CCSDS OEM parser (Apache-2.0, strict defaults), refuses both lunar files because it does not implement the LTC and TCL time systems (it decodes the crate's EME2000/UTC OEM, and decodes the lunar files once TIME_SYSTEM is replaced by TDB); oem 0.4.5 decodes them within the written precision only by falling back from the unsupported time system. Interchange of these lunar files with mainstream CCSDS readers is not established lunar_interop lunar_interop::tests (OEM carries lunar REF_FRAME/TIME_SYSTEM; time metadata round-trips; KIF envelope); tests/lunar_interoperability_export_reference.rs (kshana's emitted lunar OEM re-parsed by the independent oem Python library: REF_FRAME/TIME_SYSTEM/CENTER tokens + per-epoch state to format precision; a corrupted export is rejected); tests/lunar_interop_oem_oracle.rs::recorded_two_reader_outcome_is_for_todays_export
PNT-resilience framework-aligned scoring Per-dimension sub-scores over Kshana's own seven resilience categories (not DHS terms), RethinkPNT RDRR functions and Yang criteria, each tagged Modelled with its driver; tentative RPCF Level with a bounded-degradation gate. Simulation-derived self-assessment, never certification. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Hand-derived per-metric formulas: inverse-Simpson diversity, weighted-mean composite, bounded/unbounded timeline durations, weakest-link Level ladder resilience::arch, resilience::score, resilience::diversity, resilience::timeline resilience::score::tests (monotonicity, composite bounds, level cap, modelled-provenance); resilience::diversity::tests (inverse-Simpson, common-mode, SPOF)
Resilience-score decision-instability study Quantifies how a single composite score / RPCF Level reorders architectures under a defensible weighting simplex and a threat ensemble (top-1 flip rate, Kendall-tau dispersion, Level-flip rate, rank ranges); declared-vs-measured and diversity-collapse analyses. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed-form rank-statistics identities (tau in [-1,1] with hand-computed values; deterministic seeded Dirichlet) and constructed stable/unstable witnesses resilience::stats, resilience::study, resilience::panel resilience::stats::tests (Kendall-tau hand example, Dirichlet simplex, flip-rate); resilience::study::tests (stability control, instability witness, declared-vs-measured, diversity collapse)
Demonstration representativeness & gaps-to-flight Per-result honesty ledger qualifying a demonstration output: its external anchors, modelled assumptions, gaps-to-flight and representative TRL band, with invariants enforced (Validated requires an external anchor; Modelled requires a gap and cannot claim above TRL 4). InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed-form invariants mapping to the 'representativeness justified + gaps-to-flight identified' compliance discipline; tied to the verification status/oracle-kind boundary representativeness representativeness::tests (validated-needs-external-anchor, modelled-needs-gap, modelled-TRL-ceiling, malformed-band, JSON fields)
Quantum-vs-classical trade evidence (common shape) One reproducible TradeEvidence object (fixed frame: scenario+seed+engine; common per-FoM quantum-vs-classical values with polarity-correct benefit, optional 95% CI, validated/modelled label) carrying a representativeness record, so every quantum-PNT vertical reports the trade the same honest way. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed-form benefit/winner identities + faithful wrap of the existing quantum_trade::TradeResult; honesty tied to the representativeness ledger and verification labels qtrade qtrade::tests (benefit polarity higher/lower-is-better, wraps a real TradeResult faithfully, dishonest evidence rejected, validated-FoM needs external anchor, deterministic JSON)
Quantum device error-model library Device cards (optical/trapped-ion/mercury-ion + classical clocks reused from holdover/clock_state; cold-atom interferometer; classical + entanglement/single-photon time-transfer links) each carrying a representativeness record; the entanglement link adds a shot-limited timing-precision model (~jitter/sqrt(R*tau), dark-count penalty, systematic floor). InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Reused clock/CAI coefficients (holdover/clock_state, published values) + closed-form shot-noise/loss identities for the entanglement link quantum_devices quantum_devices::tests (clock cards honest+ordered; entanglement precision ~1/sqrt(tau); detected rate -10x/10dB; dark counts degrade; systematic floor bounds; card modelled+valid)
Trusted quantum timing (time transfer + secure dissemination + anomaly) End-to-end quantum vs classical time-transfer chain (clock coast + link precision in quadrature), a reused timing protection level, a delay/replay-attack security FoM (1-P_md) and a clock-anomaly detection probability + CUSUM latency, emitted as honest TradeEvidence with a representativeness record. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed-form quadrature budget over reused validated kernels (ADEV vs Stable32/NIST; TPL bound; detection analytic_pd/pmd); honesty tied to the representativeness ledger timetransfer_chain timetransfer_chain::tests (precision improves with integration; quantum can win AND lose; PL finite-positive; security FoM in [0,1] and grows with attack delay; anomaly Pd monotone; trade is_honest)
GNSS-free quantum navigation Quantum (cold-atom interferometer) vs classical navigation-grade INS dead-reckoning over a GNSS outage: position-error growth, holdover to a position threshold, and the quantum-vs-classical trade as honest TradeEvidence; honest observability note (bias unobservable without a fix, so error grows). InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Reused inertial budgets cross-checked against an independent Octave double-integration of the same dead-reckoning ODE (different runtime, shared model → ReferenceImpl) plus the Freier-2016 published short-term noise as a one-sided anchor; the quantum-vs-classical composite stays MODELLED quantum_nav_od quantum_nav_od::tests (quantum beats classical over a long outage; advantage is outage-dependent; trade is_honest); tests/gnss_free_quantum_navigation_reference.rs (dead-reckoning position growth vs an independent Octave double-integration + the Freier-2016 published noise anchor)
Fault/anomaly detection for quantum PNT systems Labelled quantum-fault catalog (clock frequency-jump/drift/lock-loss; sensor bias-step/dropout), a detection-statistic ROC AUC with a bootstrap CI, and a minimum-detectable fault at a fixed false-alarm rate; a quantum-clock-aided monitor detects smaller faults than a classical one, emitted as honest TradeEvidence. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed-form Gaussian AUC = Phi(mu/(sigma*sqrt2)) cross-checked against the externally-validated eval_stats::bootstrap_auc_ci (vs scikit-learn) + detection analytic thresholds quantum_faults quantum_faults::tests (analytic AUC known values; empirical bootstrap AUC brackets the closed form; quantum detects smaller faults / higher AUC; advantage vanishes for huge faults; 5-class catalog; trade is_honest)
TDOA/FDOA passive emitter geolocation Locate an emitter (jammer/spoofer, or an opportunistic source for reverse-PNT) from time-difference-of-arrival across a receiver network — the τᵢ=(Rᵢ−R₀)/c hyperboloid intersection solved by Gauss–Newton least squares — and, adding frequency-difference-of-arrival (range-rate differences) with moving receivers, jointly recover position and velocity; with the Cramér–Rao lower bound on the position covariance from the measurement geometry InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Self-consistency of the estimator and geometry: forward→inverse round trips, the Fisher/CRLB identity J·CRLB=I, GDOP monotonicity, and the estimator attaining its own Cramér–Rao bound under Monte-Carlo noise — internal-consistency checks, NOT an external dataset, so the row stays InternalConsistency. MODELLED passive geolocation — point-source line-of-sight model; no multipath / NLOS, receiver-clock-bias, or atmospheric-refraction terms. 0.30 round 2, against Ho and Chan 1993 and Ho and Xu 2004 (pre-registered 034e1d1b, 1 % of each printed value), a finding (stays MODELLED): the surface-constrained TDOA bound reproduces the 40 N geometric factors (-0.11 %, -0.02 %) and the maximum TDOA; the joint TDOA+FDOA bound reproduces Fig. 6 (+0.06 %, -0.17 %) and, at the source the authors own code names for Fig. 7 (amendment written after that result was seen, disclosed), Fig. 7 (+0.11 %, -0.02 %); it equals the authors published bound code (BSD-style, run under GNU Octave) to 3e-12; the covariance-weighted maximum-likelihood solver attains the printed bound (+0.3 to +0.4 %). The Ottawa factors the paper prints from a Monte Carlo (251, 7.1) differ by +1.3 % and +4.4 %, outside the 1 % bar geolocation geolocation::tests (noiseless TDOA forward→inverse to 1e-6 m; J·CRLB=I with a symmetric PD covariance; the CRLB position-variance trace is non-increasing when a receiver is added; joint TDOA+FDOA recovers a moving emitter's position+velocity; <4 receivers rejected); tests/geolocation_reference.rs (round trips over four geometries with a 3-D-diverse network; the Gauss–Newton estimator attains its Cramér–Rao bound — empirical error covariance tracks the analytic bound over 4000 Monte-Carlo trials); tests/geolocation_crlb_published_oracle.rs (ho_chan_1993_maximum_tdoa; ho_xu_2004_fig7_with_the_authors_corrected_source; ho_xu_2004_bound_matches_the_authors_code; finding_ho_chan_ottawa_printed_values_are_not_the_bound and finding_ho_xu_fig7_printed_source_is_not_the_plotted_one, pinned)
Stagnation-point convective entry heating (Sutton-Graves) on a 3-DoF entry Stagnation-point convective heat flux q = k sqrt(rho/R_n) V^3 with the Sutton-Graves constants for Earth air and the Mars atmosphere (NASA TR R-376, 1971), its peak and the integrated heat load along a 3-DoF entry, ballistic or lifting at constant bank, on Earth or Mars. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency: the relation and constants as printed in NASA TR R-376, a half-step convergence check, and the expected ordering of heating and deceleration peaks. WHAT IS NOT: no published heating value has been compared (the Stardust papers give a design limit and a convective-plus-radiative estimate of about 1200 W/cm2, which a convective-only relation cannot match); no radiative heating, wall-temperature or catalycity correction, or thermal-protection response. entry_eo_ascent::entry_heating (stagnation_heat_flux, simulate_entry) entry_eo_ascent::entry_heating::tests::heat_flux_relation_has_the_published_form_and_constants; entry_eo_ascent::entry_heating::tests::lift_lowers_peak_deceleration_and_heat_flux_of_a_shallow_entry; entry_eo_ascent::entry_heating::tests::mars_entry_runs_with_the_mars_constants; tests/entry_stardust_published.rs (records 746 W/cm2 for Stardust without a bar)
Electro-optical imager radiometry, MTF, relative edge response and GIQE 4 NIIRS Nadir imager signal-to-noise budget (Lambertian scene radiance, camera equation, shot, dark, read and quantisation noise), the system MTF at Nyquist as the product of unobscured-aperture diffraction, detector aperture, linear smear and Gaussian jitter, the edge response and relative edge response integrated from that MTF, Q = lambda F / p, and the GIQE version 4 NIIRS with no MTF compensation. Runnable as the eo-radiometry scenario kind. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed forms: the diffraction MTF at half cutoff, the one-pixel ramp edge of a pure detector aperture (RER 1), the normal-CDF edge of a Gaussian blur (RER = erf(0.5/(sigma sqrt 2))), shot-noise scaling, and the GIQE 4 coefficients as published (Leachtenauer et al., Applied Optics 36(32), 1997). WHAT IS NOT: no external imager, measured MTF or rated image has been compared; the GIQE is an empirical regression with its own error; no stray light, atmospheric MTF, MTF compensation or aliasing. entry_eo_ascent::eo_radiometry (Imager, snr_budget, giqe4_niirs, EoRadiometryScenario) entry_eo_ascent::eo_radiometry::tests::diffraction_mtf_has_its_closed_form_values; entry_eo_ascent::eo_radiometry::tests::a_pure_pixel_aperture_has_a_ramp_edge_and_rer_one; entry_eo_ascent::eo_radiometry::tests::a_gaussian_blur_has_the_normal_cdf_edge; entry_eo_ascent::eo_radiometry::tests::snr_budget_scales_as_shot_noise_when_signal_dominates; entry_eo_ascent::eo_radiometry::tests::giqe4_switches_coefficients_at_rer_0_9_and_falls_with_gsd
Launch ascent gravity, drag, steering and back-pressure losses Planar gravity-turn ascent of a multi-stage vehicle over a non-rotating spherical Earth through the US Standard Atmosphere 1976 (density and pressure), with a pitch kick, thrust reduced by the nozzle back-pressure, stage burnouts at exact step boundaries, and the gravity, drag, steering and back-pressure losses integrated beside the state. Runnable as the ascent-losses scenario kind. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency: the exact identity burnout speed = sum Isp g0 ln(m0/mf) minus the four integrated losses (residual below 1e-6 m/s), Tsiolkovsky's equation on a vertical vacuum burn with gravity the only loss, and the US76 sea-level and tropopause pressures. WHAT IS NOT: no published vehicle's losses have been compared; no Earth rotation, coast, throttling or guidance beyond the kick; constant C_D; not a trajectory optimiser. entry_eo_ascent::ascent (simulate_ascent, AscentScenario); reentry::us76_pressure entry_eo_ascent::ascent::tests::the_loss_identity_holds_to_integration_error; entry_eo_ascent::ascent::tests::vertical_vacuum_burn_has_only_gravity_loss_and_stays_vertical; entry_eo_ascent::ascent::tests::us76_pressure_has_the_standard_values; entry_eo_ascent::ascent::tests::a_larger_kick_lowers_burnout_flight_path_angle
TWSTFT two-way equation, uncertainty budget and link stability with flicker and diurnal non-reciprocity The TWSTFT two-way equation solved for T_A - T_B with station transmit and receive delays, the Ku-band ionospheric up/down asymmetry, the transponder delay difference and the Sagnac terms, against its exact forward model; a quadrature uncertainty budget with the link TDEV as the type A term; a two-way series with white and flicker phase noise (Kasdin-Walter), a diurnal non-reciprocity and a constant reciprocity residual; and the rate, residual RMS, TDEV and ADEV of supplied Circular T, MJD-CSV or IGS RINEX station-clock series. Runnable as the time-transfer-budget scenario kind. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency: the forward model and the solved equation agree to 1e-15 s, the Sagnac term equals the module's independent BIPM 2A omega/c^2 loop form, the ionospheric term is 40.3 TEC (1/f_up^2 - 1/f_down^2)/c, and the noise processes show their expected TDEV shapes. WHAT IS NOT: no real TWSTFT measurement or calibration report has been compared; the stated delays and uncertainties are inputs, not measured; the stabilities of supplied series are reported, not validated. twstft_budget (counter_readings, solve_offset, combined_uncertainty, flicker_phase, two_way_series, series_stability); time_transfer_budget (TimeTransferBudgetScenario, read_series) twstft_budget::tests (the two-way equation recovers the offset exactly; the Sagnac term equals the BIPM loop closed form; the ionospheric term follows the frequency split and the troposphere cancels; flicker phase has a flat TDEV; a diurnal residual lifts TDEV near half a day; a reciprocity bias shifts the offset and not the TDEV; series stability removes a rate); time_transfer_budget::tests
Optical slant-path atmosphere numerics: Rytov variance, scintillation, gamma-gamma fade probability, aperture averaging, cloud and clear-air optical depth Hufnagel-Valley Cn2 integrated along a slant path for the plane- and spherical-wave Rytov variance (uplink and downlink), the Andrews-Phillips scintillation index and gamma-gamma parameters, the gamma-gamma fade probability and fade margin, the weak-turbulence aperture-averaging factor, the cloud optical depth of a liquid-water column and the Kim-visibility plus Rayleigh clear-air optical depth, replacing the lumped atmospheric loss of the optical link budget when an atmosphere is supplied. Runnable inside the optical-atmosphere scenario kind. ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — The numerics are compared with an independent program (xval/optical-atmosphere/oracle.py, mpmath 1.4.1 at 30 digits, tanh-sinh quadrature on the original height variable and Bessel-K gamma-gamma densities) that shares no code with Kshana, under bars fixed before any implementation existed (xval/optical-atmosphere/PREREGISTRATION.md). WHY MODELLED: that oracle evaluates the same published formulas, so it checks the implementation of the stated formulas and not the atmosphere; no ITU-R validation example and no measured scintillation or slant-path extinction record is used (the ITU values are an open licence decision and are kept out of the repository). The Cn2 profile level, the visibility, the aerosol and molecular scale heights, the aperture-averaging path length and the moment-matching used to apply aperture averaging to the gamma-gamma parameters are stated inputs or conventions. A source line in the module records that one widely copied survey prints the second scintillation exponent as 7/6 where Andrews and Phillips give 5/6; the 5/6 form is implemented optical_atmosphere (rytov_variance, scintillation, gamma_gamma_cdf, fade_margin_db, aperture_averaging_factor, cloud_optical_depth, clear_air_optical_depth); optical_linkbudget (optical_link_budget_atmosphere) tests/optical_atmosphere_reference.rs (pre-registered bars A1-A3 against the independent mpmath oracle: 216 Rytov grid points worst relative error 3.4e-7 against a 1e-6 bar, scintillation worst 4.5e-16, aperture factor worst 5.7e-16, 96 gamma-gamma fade probabilities worst 1.3e-12 in log10, cloud and clear-air optical depth worst 6.6e-16); tests/optical_atmosphere_no_moved_output.rs (bar A5: the lumped-loss link budget and the existing site-availability outputs are bit-identical to the base commit over 1,000 parameter sets)
Weather-driven optical ground-site availability and distance-correlated site diversity Availability of an optical link against a stated link margin from a log-normal cloud liquid-water climate (ITU-R P.840 amount, geometric-optics extinction) and the independent gamma-gamma turbulence fade, the link margin needed for target availabilities and the ceiling no margin lifts, log-normal outage durations, enhancement-technique what-ifs, and a one-factor Gaussian-copula network availability whose pair correlation is exp(-distance/decorrelation length). Runnable as the optical-atmosphere scenario kind. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency: closed-form limits and monotonicity of the diversity model, the cloud-ceiling closed form, and the log-normal outage identities. NO external oracle is claimed and none has been compared: no measured optical-ground-station availability or cloud-free-line-of-sight record is used. WHY MODELLED: the cloud climate (probability of cloud, median and spread of the liquid-water column, outage durations), the independence of cloud and turbulence, the Gaussian-copula form, the decorrelation length and every technique gain are assumptions; the bundled scenarios state ILLUSTRATIVE climates, not a dataset. Upgrading this row needs a cited measured availability record and a bar registered before the comparison optical_weather; optical_sitediv; optical_techniques; optical_atmosphere_scenario tests/optical_atmosphere_identities.rs (bar A4: rho = 0 equals the independent union and rho = 1 the best single site to 1e-12, and zero monotonicity violations in the number of sites and in the correlation; the first run of this bar missed by 3e-9 because the normal CDF in use was the 1.5e-7 Abramowitz-Stegun form, an implementation defect replaced by the incomplete-gamma CDF with the bar unchanged); optical_weather::tests and optical_sitediv::tests (monotone margin, the cloud ceiling as a closed form, the outage-duration identities, inversion of the margin search)
Timing and ranging continuity through optical outages The outage-duration distribution of an optical site coupled to the closed-form coast variance of the clock holdover model: timing and ranging error at stated outage quantiles, the holdover to a timing threshold, the fraction of outages and of outage time inside it and the timing availability A + U E[min(D, T_h)]/E[D], for the classical and quantum clock classes. Runnable inside the optical-atmosphere scenario kind. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency with the holdover module, bit for bit; NO external oracle is claimed. The class PSDs are the synthesised long-tau floors the holdover module already carries, so the figures inherit its stated caveat that holdover to a tight threshold is governed by the assumed red-noise floor and not by the cited Allan deviation. The outage durations are a log-normal model with stated parameters, not a measured cloud-dwell record optical_outage_holdover (couple, clock_psds); holdover (coast_phase_sigma, holdover_seconds, phase_to_range_m) tests/optical_atmosphere_identities.rs (bar A6: the per-outage timing error equals holdover::coast_phase_sigma and the range error equals phase_to_range_m bit for bit over 9 clocks, 3 mean durations, 3 spreads and 4 quantiles); optical_outage_holdover::tests
Optical link margin against time: one seeded realisation of a site's weather An opt-in [timeseries] table (duration, step, seed) makes the optical-atmosphere kind also write, per site, one seeded realisation of the stated site model through time: cloud episodes (clear spells exponential, cloud outages log-normal with the stated mean and spread, the share of time in cloud set to the stated cloud probability), one log-normal liquid-water column per cloud episode, one gamma-gamma scintillation sample per step, and from them the link margin, the cloud and scintillation fades and the link-up flag, with the realised availability, cloud fraction, outage count and longest outage. Without the table the result is the 0.37 document. Draws go through the portable distribution and maths routes, so native and wasm32 give the same bytes. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency only; NO external oracle is claimed and none exists for a weather realisation. The checks compare one draw with the statistical output of the same model, so a pass says the generator samples the stated distributions (the draw's availability and cloud share sit inside pre-registered tolerances of the stated figures), not that any real site behaves so. The series is one realisation, not the climate: its availability differs from the stated one by the draw's sampling error, and scintillation samples at different steps are independent, a stated simplification of a process that decorrelates in milliseconds. The weather inputs stay the scenario's assumptions. optical_timeseries (site_series, SiteModel, SeriesSpec, Series); optical_atmosphere_scenario (TimeseriesSpec) tests/optical_atmosphere_timeseries.rs (bars T1-T6 of xval/optical-atmosphere/PREREGISTRATION-timeseries.md, fixed before the first run: same seed same bytes and another seed other bytes; no key without the table; over 8760 h at 600 s, seeds 37 and 38, the realised availability of each of the three default sites within 6 points of the stated one (worst 3.3) and the realised cloud fraction within 5 points of the stated probability (worst 2.1); the margin equals the budget minus the two fades and up equals margin not negative at every step; no non-portable maths call in the module; over-long runs and bad steps refused)
TRK-2-18 Orbit Data File reader and Mars ramped 2-way Doppler model A reader for DSN Orbit Data Files (TRK-2-18): the 36-byte record groups (file label, identifier, orbit data, per-station ramps, clock offsets, summary, end of file), and in each orbit-data record the time tag since 1950, downlink and uplink delays, observable, stations, data type, bands, validity, channel, spacecraft, the 46-bit reference frequency and the compression time; ramp start and end times, rates and start frequencies. On top of it, a ramped 2-way X-band Doppler model (integrated uplink ramps, round-trip light time with Shapiro and troposphere, DSN stations through the IAU 2006/2000A CIO chain and IERS EOP, station time) and a Mars-orbiter batch orbit determination (GMM-3 field, third bodies, SRP, drag). ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — The PDS3 label that the DSN navigation data-conditioning process produced with the file (NASA PDS Geosciences Node, MRO-M-RSS-1-MAGR-V1.0), checked against bars pre-registered in xval/mro-odf/PREREGISTRATION.md before the reader existed. MODELLED because one registered bar (the end-of-file table's rows, 121 in the file against 120 in the label) missed; the label is internally inconsistent there. Stage 2 (xval/mro-od/PREREGISTRATION.md, amendments A1 and A2 before the scored result): the Doppler predicted from the MRO navigation team's reconstruction (mro_psp5, NAIF) matches the observed ramped 2-way Doppler to 12.5 mHz on passes not used in development, bar met; the registered orbit determination failed on the scored arc (normal matrix not positive definite) and produced no orbit, so the orbit bars were not met. Run 2 (xval/mro-od/PREREGISTRATION-RUN2.md, a damped estimator, the same arc and bars, a scoring amendment R2-A1 disclosed in docs/revisions) converged: the estimated orbit is within 0.36 km RMS (0.53 km maximum) of the reconstruction, bars met, but the post-fit Doppler RMS is 48.6 mHz against the 30 mHz bar, not met, so the row stays MODELLED. WHAT IS NOT: no estimated orbit has met every registered bar; ionosphere, solar plasma and most of the antenna offset (a 1.5 m radial offset is fitted on the development pass) are not modelled. odf (parse_odf, Odf, OdfObservation, OdfRamp, seconds_1950); mars_od (DopplerModel, RampTable, compress_two_way, MarsDynamics, fit, fit_damped); naif_kernel (SPK type 1); gravity_pds (SphericalHarmonicField::from_shadr) tests/mro_odf_reader_label_oracle.rs (a real MRO ODF, 2007-304/305, against its PDS label: record count, group positions, stations, start and stop times and data types hold; the end-of-file table's row count misses by one, a label inconsistency, pinned as a finding); odf::tests (hand-built record round trip, 1950 epoch); tests/mro_odf_short_arc_od_oracle.rs (data-gated, inputs SHA-256 pinned, monthly CI with real data required: Doppler predicted from the MRO navigation reconstruction mro_psp5 on the scored DSS 63 and DSS 14 passes, 12.5 mHz RMS, bar 30 mHz, met; the registered orbit determination produced no orbit, pinned as a finding; run 2 with a damped estimator, separately registered: orbit 0.36 km RMS and 0.53 km maximum against mro_psp5, met, post-fit Doppler 48.6 mHz against 30 mHz, not met, pinned as a finding; SPK type 1 reader against CSPICE, 5e-7 m); mars_od::tests
Multiplicative EKF attitude estimation from a gyro and a star tracker The Lefferts-Markley-Shuster multiplicative EKF: body-frame attitude error and gyro bias states, propagation with the gyro rate less the bias estimate and Farrenkopf's discrete process noise (angle and rate random walk), star-tracker updates with the residual 2 vec(q^-1 q_st) in Joseph form, and the multiplicative reset; a Farrenkopf discrete gyro and star-tracker simulator. The aocs kind can close the control loop on its estimate. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency: the filter's normalised estimation error squared against truth simulated from the same sensor models over Monte Carlo seeds, and convergence of the attitude and bias estimates. WHAT IS NOT: no external estimator or flight data has been compared (Basilisk 2.9.1 has no MEKF module); the sensor models are the textbook ones, without misalignment, scale factor or star-tracker field-of-view effects. aocs_mekf (Mekf, GyroSim, attitude_error, spd_solve6); aocs_kind (estimator) aocs_mekf::tests::mekf_is_consistent_over_monte_carlo_seeds (40 seeds, mean six-degree-of-freedom NEES over the second half within 4.5 to 7.5); aocs_mekf::tests::star_tracker_updates_bound_the_attitude_error; aocs_mekf::tests::attitude_error_is_the_body_frame_small_angle; aocs_kind::tests::estimator_loop_runs_and_reports_consistency
Aperture navigation-versus-communications duty cycle One run takes a contact plan (a list of aos_s/los_s windows, each asking the aperture for navigation or communications — the same window vocabulary passes::predict_passes emits, converted by aperture_duty::windows_from_passes), an aperture count and an explicit arbitration policy, and returns the navigation duty, the communications duty, the idle duty and the per-session outage. The policy is an input with a documented default (navigation-priority; also communications-priority and non-preemptive first-come-first-served), and the report carries the resolved policy, its full definition and the duty and outage definitions, because a duty figure quoted without its arbitration rule is not reproducible. The schedule is an exact interval sweep over the window boundaries, so a window that ends exactly where the next begins never contends, and navigation, communications and idle aperture-seconds are accumulated independently in that one sweep. Runnable as the aperture-duty-cycle scenario kind InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency, from three quantities computed by different expressions in the same sweep and then required to close. Navigation aperture-seconds, communications aperture-seconds and idle aperture-seconds are accumulated separately — idle from (apertures − |served|) per elementary interval, never as a remainder — and their sum is asserted against apertures × horizon_s, which a mis-bracketed boundary, a double-counted interval or a dropped one breaks immediately; the per-session served times are separately required to add back to the two service totals. The scheduler's structural properties are measured rather than assumed: served time is asserted non-decreasing in the aperture count over 200 pseudo-random plans for all three policies (not obvious for the non-preemptive policy, where an extra aperture changes who holds what at every later boundary), and the boundary arithmetic is pinned at the touching/one-second-overlap pair where an off-by-one would otherwise hide. The pass-predictor bridge is checked against passes::predict_passes output: with one aperture and no competing service the navigation aperture-seconds equal the predictor's own summed pass durations. No external oracle is claimed and none exists: the capability supersedes hand arithmetic rather than being checked against it, the bundled contact plan is illustrative rather than flown, and no operational scheduler publishes a plan-plus-answer pair with its arbitration rule stated — a duty computed under an unstated policy is not comparable to one computed under a stated one, and the policy dependence is measured (navigation duties of 100/150 vs 50/150 on the identical plan). Slew and changeover time, data volume, buffer state, energy and link closure are excluded in the report label rather than silently modelled aperture_duty aperture_duty::tests (a window that ends exactly when the next begins does not contend, and moving it one second earlier costs exactly one second — the off-by-one guard; overlapping windows beyond the aperture count put the lower-ranked session in outage, with the contention interval pinned; the arbitration policy decides which service holds the aperture, with all three policies' numbers pinned on one plan; first-come-first-served does not preempt a session already holding an aperture; a session that loses arbitration at its start acquires an aperture when one frees; the three duties account for every available aperture-second across 3 policies × 4 aperture counts; adding an aperture never increases any session outage, measured over 200 pseudo-random plans × 3 policies × every aperture count; enough apertures for every session leave no outage at all; the reporting horizon clips the plan and sets the duty denominator; a predicted pass list becomes a contact plan without a second window type; the bundled plan duty numbers are engine outputs for one and two apertures; the report states the policy that produced the numbers; every reported figure carries a unit and a provenance class; the scenario is reproducible and declares itself MODELLED; the scenario rejects a plan it cannot schedule); api::tests::aperture_duty_cycle_kind_round_trips_through_the_dispatch
Lunar surface-navigation RF jamming (per-satellite J/S) Lunar-native jammer-to-signal ratio, effective C/N₀ and loss of lock for a selenographic surface user under a lunar surface (or raised) jammer, over the illustrative public-source Moonlight/LCNS-class constellation. Composes the open jamming chain (j_over_s_db, effective_cn0_dbhz, rx_antenna_gain_db, lock_status, q_factor, nominal_cn0_dbhz, free_space_path_loss_db) with the open lunar sky geometry (lunar_service::LunarConstellation + topocentric, lunar::selenographic_to_mcmf); no geometry or radiometry is re-derived. Unlike the Earth jamming kind the signal leg is not a fixed received power: each satellite's isotropic received power is its own link-budget EIRP − FSPL(slant range), so J/S varies satellite by satellite with lunar range and elevation. Emits ONE ROW PER VISIBLE (epoch, satellite) LINK as JSON and as a *.table.csv artifact, with both received powers the J/S is the difference of printed alongside it; aggregate figures of merit sit beside that table, never in place of it. Runnable as the lunar-jamming scenario kind ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — Composition cross-check against an independent in-repo code path: every per-link J/S is re-derived as the difference of two link budgets computed with linkbudget::received_signal_power_dbw, whose free-space loss is the single expression 20·log10(4πRf/c) rather than the three-term sum jamming::free_space_path_loss_db uses — the two agree to < 1e-9 dB on every row (measured worst case 7.11e-14 dB, i.e. float round-off). The underlying interference chain it composes is separately externally anchored in tests/gnss_denied_jamming_resilience_reference.rs (independent numpy/scipy re-derivation of J/S and effective C/N₀ pinned to Kaplan & Hegarty §9.4, plus JammerTest 2024 measured C/N₀, Zenodo 10.5281/zenodo.15910563); the lunar geometry it composes is the lunar_service/lunar geometry with its own oracles. Closed-form identities checked here: a halved jammer standoff adds exactly 20·log10(2) dB to every row; J/S is exactly invariant to the user-antenna boresight gain while C/N₀ moves by exactly that gain; an elevation mask changes no surviving row bit-for-bit. The row itself stays ReferenceImpl/Modelled: no measured lunar jamming campaign exists to validate against, and the constellation is an illustrative public-source Moonlight/LCNS-class geometry, not a flown ephemeris lunar_jamming (composing jamming, lunar_service, lunar) lunar_jamming::tests (17 lib tests: j_over_s_equals_the_difference_of_two_independent_link_budget_runs; the_report_prints_both_link_budget_legs_so_the_difference_is_checkable_from_it; the_scenario_reports_one_j_over_s_row_per_visible_satellite_and_never_a_median; a_single_median_j_over_s_would_misreport_the_outcome_that_the_table_reports; a_closer_jammer_raises_j_over_s_by_exactly_the_free_space_loss_difference; a_more_distant_satellite_is_the_weaker_signal_so_it_carries_the_higher_j_over_s; j_over_s_is_invariant_to_the_user_antenna_boresight_gain; a_narrowband_jammer_leaves_no_higher_effective_cn0_than_broadband_at_equal_js; a_selenographic_jammer_gets_its_range_from_the_shared_lunar_geometry; a_strong_enough_jammer_takes_every_lunar_link_below_the_tracking_threshold; no_jammer_is_a_clean_sky_lunar_baseline_with_an_undefined_j_over_s; raising_the_elevation_mask_can_only_remove_rows_never_change_the_ones_that_remain; every_emitted_numeric_field_has_a_unit_and_a_provenance_class; the_csv_table_carries_every_row_of_the_json_table; the_run_is_deterministic_and_the_dispatch_surface_is_populated; bad_inputs_are_rejected_rather_than_producing_a_number); api::tests::lunar_jamming_kind_round_trips_through_the_dispatch_with_a_per_satellite_table
Lunar denial contour with an uncertainty band from the measured C/N₀ spread The lunar-jamming report no longer rests its denial contour on one scalar. It emits the full measured wanted-signal C/N₀ distribution over the per-satellite table — n, min, p05, p25, median, p75, p95, max, mean, sample stdev, and the sample's own asymmetry (p95 − median) − (median − p05) — beside the per-link rows, which are unchanged. The contour is then reported at each of those order statistics under BOTH denial criteria the engine recognises, never one in place of the other: the incumbent power-ratio criterion (J/S = 30 dB, the same threshold attack_surface and tracking_loop use, and the criterion behind the released lunar link-jamming table's denial column), and the loss-of-lock criterion (the effective C/N₀ falling to tracking_threshold_dbhz), which is the criterion this report's own links[].status column is scored with. Each contour point is given on both axes of the denial plane — the jammer EIRP required at the scenario's standoff, and the denial standoff at the scenario's EIRP — so the band is an interval on the same axes a contour plot is drawn on. The band edges ARE contour(p05) and contour(p95): the same closed-form map applied to the sample's own quantiles, not a sigma fitted to the sample and not median ± k·stdev, and the report says so in a band_definition string beside the numbers. stdev is emitted for continuity and is used by nothing. A quantile whose C/N₀ is already at or below the tracking threshold has no finite denying J/S; those columns are emitted as null with a counted reason rather than as an infinity or a clamped radius InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency against the engine's own forward functions, which is all this capability can honestly claim. Every contour point is a closed-form inversion, and each inversion is checked by pushing its answer back through the FORWARD function the report's own rows were scored with: the J/S column through jamming::effective_cn0_dbhz (which must return tracking_threshold_dbhz to < 1e-9 dB-Hz), the standoff column through jamming::free_space_path_loss_db and jamming::j_over_s_db (the same J/S to < 1e-9 dB), the EIRP column through jamming::j_over_s_db at the scenario's own standoff. The contour is further checked to be the BOUNDARY of the denial set rather than a point inside it — lock_status loses lock on a strict inequality, so the verdict is measured to flip from DEGRADED to LOST across 1e-4 dB of J/S either side of the contour, which an off-by-an-epsilon contour would fail. The strongest check is per-link rather than per-quantile: applying the same map to every row's own C/N₀ reproduces the report's status column exactly — 0 disagreements on 38 of 38 rows at the documented operating point (kind = lunar-jamming, every input default except jammer.range_m = 25 000 m), where 26 rows are LOST and 12 are not. Monotonicity is measured, not assumed: 20 001 samples across [tracking_threshold + 1e-3, 80] dB-Hz, 0 violations of a strictly decreasing standoff and a strictly increasing required power, so the quantile ordering of the band is demonstrated rather than asserted. ExternalDataset is declined and Validated with it: no measured lunar jamming campaign exists to compare a denial radius against, the constellation is an illustrative public-source Moonlight/LCNS-class geometry rather than a flown ephemeris, and the contour's inputs (EIRP, jammer power, antenna gains, noise temperature) are representative magnitudes. ReferenceImpl was considered and declined too — the inverse and the forward expression are the SAME algebra read in two directions, so the round trip catches transcription and sign errors but is not an independent implementation; calling it a cross-check would be the borrowed-independence move the matrix invariants exist to prevent. What the band buys is measured and quoted rather than asserted: at that operating point the single-scalar contour is 27.402916 km and puts 25 km on the denied side for all 38 rows, while the band 21.256108 .. 29.921360 km contains the operating point and therefore reports the split the table actually shows. The two criteria are also measured to disagree — the power-ratio band (38.186527 .. 53.691675 km) does not contain 25 km at all — which is why both are printed lunar_jamming (denial_js_db, range_for_free_space_path_loss_m, Cn0Distribution, DenialContourPoint, ContourBand, DenialContour; inverting jamming::effective_cn0_dbhz, jamming::j_over_s_db and jamming::free_space_path_loss_db) lunar_jamming::tests (10 lib tests: the_contour_is_the_exact_inverse_of_the_functions_the_rows_were_scored_with; the_band_is_the_measured_quantiles_pushed_through_the_contour_not_a_sigma; the_asymmetry_the_band_carries_is_the_samples_own_shape_bent_by_the_criterion; the_contour_is_monotone_in_cn0_measured_over_a_dense_sweep_not_assumed; the_band_recovers_the_split_verdict_the_single_scalar_contour_lost; the_distribution_is_the_tables_own_order_statistics_and_keeps_the_rows; a_link_already_below_the_threshold_gets_a_null_contour_point_not_a_number; a_clean_sky_run_has_no_contour_at_all_rather_than_an_empty_one; the_denial_threshold_is_the_same_thirty_decibels_the_rest_of_the_engine_uses; the_units_block_describes_the_contour_and_names_nothing_the_report_omits)
Cross-modality integrity monitor detection power The hybrid-optical-rf report states what the cross-modality chi-square monitor can actually DETECT, not only that it passes a fault-free case: the minimum detectable bias per monitored axis (east, north, up, clock) at the scenario's stated false-alarm and missed-detection probabilities, the detection-power curve either side of it, the noise-free bias multiple at which the realised statistic first crosses the threshold, and the time-to-detect for a bias ramp at a stated rate. Faults are also injected through the real monitor and the statistic it returns is reported alongside the analytic prediction InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Two internal oracles, no external dataset. (1) Closed-form round trip: the minimum detectable bias is produced by inverting the non-central chi-square tail on the non-centrality (raim::pbias) and is verified by feeding the resulting non-centrality back through raim::noncentral_chi2_cdf at the monitor's own threshold, which must return P_md. (2) Injection vs analysis: a bias is written into the RF estimate of one axis and cross_raim::run_cross_raim is re-run, so the statistic compared against the analytic non-centrality is the one the monitor computed, not a re-derivation. A seeded Monte-Carlo of the statistic itself is carried in the tests as a third check; it is deliberately NOT in the report, because a sampled estimate would be slower and not reproducible bit-for-bit. ExternalDataset is declined: the quantity is the detection power of THIS monitor at THIS scenario's sigma allocation, and the sigma magnitudes the MDB is scaled by are Modelled representative inputs, not measurements. ReferenceImpl was also considered and declined — the Monte-Carlo samples the same statistic the analysis describes, so it catches transcription and coefficient errors but is not an independent implementation of the monitor. 0.30 round 2 (pre-registered 0913a98a), blocked (stays MODELLED): SciPy 1.18.1 chi2/ncx2/brentq reproduce the report threshold (within 5.4e-12), per-axis MDB, power curve, crossing multiple and ramp time-to-detect (within 5.3e-10) on five configurations; the injected-fault statistics have no independent oracle and the sigma magnitudes are Modelled inputs, so the scoping awaits an owner decision hybrid_integrity hybrid_integrity::tests (the detection-power curve runs from the false-alarm rate at zero fault to 1 − P_md at the minimum detectable bias; the minimum detectable bias fed back through noncentral_chi2_cdf at the threshold the monitor itself applied returns P_md to 1e-9, on every axis and through the public helper; a bias actually injected into the RF estimate shifts the monitor's own statistic by exactly the hand-computed b²/(σ_rf² + σ_opt²); a noise-free bias is caught above √(T/λ*)×MDB and missed below it, with the injected ladder straddling that crossing; detection power is monotone in fault magnitude and identical on all four axes in MDB multiples; a seeded 200,000-sample Monte-Carlo of the monitor statistic reproduces the analytic power within 4σ at four points on the curve; the timing MDB is pinned above the timing alert limit, which is a measured weakness and not a feature; the Wilson-Hilferty quantile is measured to disagree with the monitor's exact threshold by ~4%, recording why it was not used; the ramp figure is exactly MDB/rate and scales inversely with the rate, and a non-positive rate reports null rather than zero); tests/hybrid_fault_power_scipy_oracle.rs (report_detection_power_matches_scipy_chi2_and_ncx2; report_detection_power_matches_scipy_with_comparable_sigmas)
Post-handover covariance re-growth against the alert limit The hybrid-optical-rf report exposes the filter's process-noise model and states how long the post-handover solution stays inside the alert limit: for both handoff directions it carries the per-axis covariance the handover left behind, propagates it forward under a stated random-walk process noise, and reports the time at which the coverage-scaled 1σ reaches the horizontal, vertical and timing alert limits, which limit binds first, the variance doubling time constant, and a sampled coast profile that brackets the crossing. Process-noise PSDs, the coverage factor and the alert limits are all inputs with documented defaults InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — No external oracle. The crossing is a closed-form solution of the random-walk variance growth, and the tests recompute it independently from the values the report itself publishes rather than from the emitter's internals. The starting covariance is pinned bit-for-bit to the trace the existing handoff block already reported, so the coast cannot propagate a covariance nobody else saw. The process-noise PSDs are MODELLED representative inputs and the crossing times scale directly with them, which the scaling test states as a measured property rather than a claim. ExternalDataset is declined deliberately: the coast time is a direct function of two Modelled PSDs and of alert limits that are themselves representative, and there is no measured lunar optical/RF handover coast to compare against. An external oracle here would need a published post-handover covariance-growth or holdover-accuracy curve for a comparable receiver with its process-noise model stated, checked to a tolerance hybrid_integrity hybrid_integrity::tests (the coast starts from exactly the covariance trace the handoff block reports, for both directions, so the replayed diagonal cannot drift from the reported handover; the reported crossing time is recomputed from the report's own handover sigma, process-noise PSD and coverage factor, and the bound is inside the alert limit just before it and outside just after; the coast time scales exactly inversely with the process-noise PSD and shortens when the alert limit tightens; a zero-PSD coast reports null rather than a zero time, because never is not immediately; the emitted profile crosses exactly once and brackets the reported crossing; the variance doubling time and the alert-limit crossing time are pinned apart, being eight orders of magnitude different after the tight optical stage and within one order of magnitude after the loose RF stage; leaving the optical modality buys more coast time than leaving RF, by exactly the covariance difference divided by the horizontal growth rate; and random_walk_time_to_limit separates already-outside, crosses-at-t and never-crosses)
Off-boresight antenna pattern in the lunar geometry export The per-satellite geometry export carries, per (epoch, satellite), the off-boresight angle AT THE SATELLITE and the transmit gain toward the site from the real uniformly-illuminated circular-aperture (Airy) pattern, and reports the in-beam count under that pattern BESIDE the in-beam count under the symmetric gain-to-beamwidth approximation (θ_3dB[deg] = √(31000/G_lin)), with the difference emitted as an explicit correction in links, in satellites per epoch, and as the worst single epoch. Both implied aperture efficiencies of the approximation are emitted (0.641 against the 70·λ/D degrees rule it is quoted with, 0.920 against a uniform circular aperture) so the efficiency it silently assumes is stated rather than inferred. Off by default: the block appears only when an export site and an aperture are both given InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Mixed, and separated rather than pooled. The PATTERN underneath is externally validated and keeps its own row (a scipy.special.j1 fixture to < 0.05 dB in tests/validate_p1_orbital_footprint.rs, plus here the published Airy half-power abscissa x = 1.61634 located by bisection rather than assumed). The GEOMETRY is checked against closed-form triangle trigonometry written as a different expression from the dot product under test. The CONTAINMENT of the real beam by the approximate cone is derived algebra (28.019/√η vs 29.479 degrees per λ/D), so the correction can only be non-positive for η ≤ 0.9035. But the in-beam COUNTS themselves have no external oracle: no published table gives how many satellites of a Moonlight/LCNS-class shell hold a south-polar site inside a given dish's half-power beam, and the constellation is an illustrative public-source approximation, not a flown ephemeris. The measured disagreement at the documented working point — 0 links in beam under the real pattern against 28 under the approximation, −2.33 satellites per epoch, worst epoch 3, on 76 evaluated links — is therefore a MODELLED finding about the approximation, pinned as a regression literal (the nearest row sits 0.069° from either beam edge, four orders of magnitude above any last-digit disagreement), not an externally validated coverage number. Labelling the row ExternalDataset on the strength of the pattern's own external anchor would be borrowed validation, which is the move the matrix invariants exist to prevent. 0.30 round 2 (pre-registered 67d5f30c), blocked (stays MODELLED): SPICE geometry and SciPy Bessel functions reproduce the off-boresight angle (worst 3.0e-5 deg), Airy gain and in-beam flags on 6 336 rows of flown-orbiter states and the documented working point; but on flown geometry the flags split by satellite identity (the nearest link is 1.66 deg from the beam edge), the 5 deg visibility is checked as a flag, not a numeric elevation, the symmetric-approximation flag applies the 31000/G rule of thumb to a validated angle without validating the rule, and the implied efficiencies have no oracle; the scoping awaits an owner decision lunar_service, antenna antenna::tests and lunar_service::tests (the half-power crossing located by bisection on the pattern matches the published Airy x = 1.61634 and yields the exact 1.02899·λ/D width, recording that the conventional 1.02 coefficient sits at −2.955 dB not −3.010 dB; the pattern is strictly decreasing over 400 points from boresight to the first null; the implied-efficiency algebra round-trips to 1e-12 and reproduces 0.641 / 0.920; the off-boresight angle matches tan θ = R·sin γ/(r − R·cos γ) at 20 points and both limits to 1e-12; the approximate cone contains the real beam row by row; the headline counts equal the per-row flags they summarise and the correction equals their difference; every row verdict is recomputable from the emitted report alone; every emitted numeric and boolean field has a unit and a provenance class; an impossible aperture emits no block; with no antenna configured the export keeps exactly its six pre-existing keys, 0 leaves changed and 0 removed); tests/validate_lunar_export_offboresight_spice.rs (flown_orbiter_export_matches_spice_geometry_and_scipy_pattern; documented_working_point_matches_anise_propagation_and_scipy_pattern)
Tracking-loop loss of lock and spoof pull-in under interference Loss of lock computed from loop dynamics instead of a power ratio: carrier (Costas) and code (non-coherent early/late) 1σ thermal jitter against C/N₀ with the squaring loss, against the stated rules 3σ_PLL + θ_e ≤ 45° and 3σ_DLL + ramp lag ≤ d/2 chips; drop and re-lock C/N₀ thresholds with the binding loop named and the hysteresis DERIVED from the wider pull-in bandwidth rather than asserted; the declared time to lose lock from a two-threshold lock detector with confirmation dwells, reported separately from the physical phase-escape time (Viterbi mean time between cycle slips, in log₁₀ s because it spans hundreds of decades); the largest code slew and carrier Doppler rate the victim's loops can follow; and the DENIAL RADIUS the loop dynamics imply reported alongside the existing power-ratio radius with their signed difference as its own named field. Runnable as the tracking-loop scenario kind ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — The engine's own sdr correlator (sdr::correlate / synth_if / CaCode) stepped forward on seeded synthetic IF at a calibrated C/N₀ — a separate code path reaching the same numbers by numerical correlation of sampled IQ rather than by an algebraic jitter expression, so it is a different route and not a restatement — plus standard tabulated modified-Bessel I₀ values for the cycle-slip term. Loop theory per Kaplan & Hegarty ch. 8 and Viterbi/Gardner for the slip time. The row stays ReferenceImpl/MODELLED: the cross-check lives in this same codebase, and the bessel_i0 check validates one special function rather than the tracking model, so promoting the row on that basis would be self-serving labelling. ExternalDataset would need a recorded raw-IF dataset with ground-truth C/N₀ and an annotated loss-of-lock instant (TEXBAT/OAKBAT class); none ships in this tree, and even with the IQ those datasets publish no per-epoch loop-state truth, so a declared loss-of-lock time could only be validated against some other receiver's lock detector, which is a modelled choice and not an oracle. The loop bandwidths, integration time, correlator spacing, pull-in ratio, dwells, jammer power and antenna gains are representative band figures, not a datasheet. 0.30 round 2, GNSS-SDR 0.0.19 (GPL-3.0, run as a program) on independently generated IF (pre-registered 468e7f10, amendments to the measurement method disclosed), a finding (stays MODELLED): closed-loop PLL and DLL jitter agree within 8 % at 35 to 45 dB-Hz, the 10 Hz/s dynamic stress within 1 % and the first-order code ramp lag within 2 %; at 30 dB-Hz the PLL jitter is 21 % higher and the DLL jitter 32 % lower, the measured 15-degree-rule thresholds sit 1.5 dB above the engine, and the second-order loop slips 0.5 to 2 decades more often than the first-order slip-time bound. 0.30 revision: the Costas slip time now uses the loop SNR rho/4 (half-cycle slips); the default jitter_table log10_mean_time_to_cycle_slip_s falls from 11.58 to 2.10 at the 25.47 dB-Hz threshold tracking_loop (composing sdr, jamming) tracking_loop::tests (open-loop Costas discriminator jitter against sdr::correlate stepped forward on seeded synthetic IF, 3 pooled noise realisations × 900 epochs, agreeing to 0.63% over 35-45 dB-Hz, with the squaring-loss term required to fit at least 3× better than the no-squaring-loss form wherever it is resolvable; the ~32 dB-Hz atan-discriminator saturation asserted rather than merely stated, so the validity limit is pinned; closed-loop σ against a stepped sdr Costas loop over 4000 epochs to 3.7%; first-order DLL ramp lag against a stepped sdr DLL to 0.17%; bessel_i0 against tabulated I₀ to 7.4e-8; the hysteresis width required to fall in [5·log₁₀ r, 10·log₁₀ r] across 4 ratios × 2 integration times × 3 bandwidths); api::tests::tracking_loop_kind_round_trips_through_the_dispatch; tests/tracking_loop_gnss_sdr_oracle.rs::finding_is_pinned
Lunar-surface-point coordinate covariance from a VLBI delay schedule, kept distinct from the Earth-station one A third datum choice, all-stations-fixed, that holds every Earth station and estimates the BEACON's Moon-body-fixed coordinates alone — the configuration a lunar surface-point uncertainty is actually quoted for, since Earth station coordinates are an input to the delay model rather than an unknown of it. It exists because the station-level covariance and the surface-point covariance are DIFFERENT QUANTITIES separated by the lever arm ρ/B, and nothing previously stopped one being quoted against the other. The emitted beacon_link block carries ρ, the longest baseline, the lever arm, the surface-point form of the equipartition link c·σ_τ·(ρ/B)·√(g/N), the computed per-coordinate beacon sigma and their ratio — the ratio null rather than misleading whenever the beacon is unestimated or the matrix rank-deficient. B is taken as the LONGEST baseline present, the most favourable one, so the ratio can only understate. Runnable as datum = "all-stations-fixed" with estimate_beacon = true, which is refused with a message naming the missing input when the beacon is not estimated ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — Closed-form identities, with no external oracle claimed or available. The lever arm is checked against ρ/B and the two equipartition forms against each other to 1e-15 — algebraic identities, so they catch a wiring error and nothing else, and are labelled as such. The substantive result is MEASURED rather than asserted: a delay from a fixed baseline constrains the beacon's DIRECTION, so the line-of-sight component reaches the information matrix only through the near-field range term, and the test reads the resulting anisotropy off the emitted spectrum instead of deriving it. AM-HM makes √(p/trace(M)) a hard floor, so an isotropic-equipartition link can only ever UNDERSTATE, and the computed-over-equipartition ratio is exactly the anisotropy it discarded. MEASURED on the Goldstone-like/Canberra-like pair whose chord is 10726.748 km: over 112 sampled days, 36 admit no mutually visible epoch at all at a 10° mask, the most ever mutually visible is 17 of a 49-sample schedule, and on the 73 viable days the three-component ratio runs from 113.9× to four orders of magnitude more, median 1513×, while restricting to the two transverse directions the line of sight does not starve gives 3.94× to 25.8×, median 7.8×. WHAT THIS ROW DOES NOT CLAIM: any of those figures as a property of a real campaign. It establishes that the surface-point quantity is now COMPUTED rather than assumed, and that it cannot be silently interchanged with the station-level one. Stays ReferenceImpl/MODELLED: no published lunar-VLBI surface-point covariance exists to validate against, the stations and beacon site are illustrative rather than surveyed, and the ephemeris, clocks, troposphere and Earth-orientation parameters are held FIXED, so this is a Cramér-Rao bound for a reduced parameter set and optimistic in its own right. The same quantity on the kernel path (beacon on the DE440 Moon) is validated on its own row, "…, kernel path"; on this analytic path the smallest beacon sigma is 3.9 % below that row's SPICE oracle, which is why this row stays MODELLED lunar_vlbi_fim (composing lunar_vlbi, fim, cio, lunar_frame, frames) lunar_vlbi_fim::tests (7 lib tests: every datum spelling round-trips through parse/as_str and an unknown one is refused; holding every station without the beacon is refused with an error naming estimate_beacon; the lever arm is asserted EQUAL to ρ/B and the beacon equipartition EQUAL to the station equipartition times it, both to 1e-15, with a further assertion that the lever arm exceeds 10 so the two budgets are not confusable on this geometry; the fixture's published baseline is pinned to 10726.748 km and its 49-sample schedule asserted to yield strictly fewer than 49 mutually visible observations; the beacon spectrum on a single baseline is measured to span at least five decades and the resulting ratio asserted above 1 by AM-HM and above 100 in fact; the station-plus-beacon layout is asserted rank-deficient with BOTH computed fields null while the modelled comparand still reports. Plus a guard on the fixture itself: a top-level key spliced after an array-of-tables becomes station data instead, so the splice point is asserted and the parsed scenario checked to carry the key — the failure mode is a run that silently uses a different configuration from the one the test names)
Lunar differential PNT — correction-link residual budget The three terms a differential correction picks up between the epoch it is computed at and the epoch it is used at, each previously left as unmodelled headroom: reference-station survey error (correlated across satellites, baseline-independent, ~1:1 position transfer and provably not DOP-amplified), correction ageing (the frozen orbit-error vector re-projected onto the line of sight the engine's own propagator puts the satellite on one latency later, plus c·σ_y(τ)·τ clock drift from the calibrated power law), and uniform link quantization over an exact ±(orbit_err + clock_err) full scale with step²/12 variance. Reported in both the range and position domains, beside — never in place of — the existing residual and protection level, with a latency curve beside the single figure InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed-form identities and self-consistency: the uniform-quantizer step²/12 variance, the exact (GᵀG)⁻¹GᵀRG(GᵀG)⁻¹ covariance propagation collapsing to σ·PDOP for equal σ, the survey term's 1:1 transfer as a consequence of û_user ≈ û_ref, and switching-off quadrature closure. The PDOP cross-check against orbit::dop shares the [−û, 1] normal matrix, so it is a consistency check and is labelled as one rather than an independent oracle. No ExternalDataset is available or claimed: no lunar surface station has a published surveyed accuracy, no lunar differential-correction link has a published latency or message format, and the quantization result is a closed form rather than a measurement. RTKLIB — already the external-code oracle for the single-difference and weighted-least-squares kernel — could be driven with a deliberately mis-surveyed base to confirm the 1:1 survey transfer, but that is independent code over the same first-order line-of-sight algebra. MAGNITUDES ARE MODELLED: the survey default is this crate's own lunar frame-realisation allocation rather than a measured station, the latency and bit count are ILLUSTRATIVE inputs, and growth of the broadcast ephemeris error VECTOR itself is not modelled at all — stated in the emitted ageing-law string, because it is the term most likely to dominate a real link lunar_dpnt lunar_dpnt::tests (a purely-additive guard whose key-set delta is exactly {correction_link, units} with every pre-existing value bit-identical against literals captured before the change; survey error does NOT decorrelate with baseline while the orbit term does, and survives a zero baseline where the orbit term is exactly zero — the structural check that catches wiring the term into the wrong place; a 1 m station error transfers 1:1 and is proved not DOP-amplified; zero latency reproduces the un-aged residual bit-for-bit and the residual is monotone in latency, with the emitted curve equal to direct runs; the quantization step halves exactly per bit and σ² = step²/12, and the full scale tracks the injected magnitudes; each term switched off in turn recovers the other two in quadrature; equal per-satellite σ propagates to exactly σ·PDOP and that PDOP agrees with orbit::dop; every emitted field carries a unit and a provenance class, checked in both directions)
Lunar reference-station coverage and accuracy map Monte Carlo sweep of the lunar differential-PNT model over a south-polar user grid and a day of epochs (the lunar-station-coverage kind): for a differential reference station at a known south-polar site, per point and over the region, the percentile corrected and uncorrected position error (3-D, horizontal, vertical), availability with a reason for each unavailable epoch (user_lt4, station_missing_sat), coverage against a threshold stated before the run, DO-229E protection levels, the coverage radius per azimuth sector, and the correction-link budget at the station and at the worst point. Not a statement about the performance of any real system; not affiliated with or endorsed by any agency InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Arithmetic re-computed by an independent numpy script on exported cases (scripts/gen_lunar_station_ref.py, numpy 2.5.4; pre-registered in tests/fixtures/lunar_station/PREREGISTRATION.md, committed alone in 2d43d3d5 before the first run): on 20 cases with every error term on, the visible sets and status are identical, the raw range errors agree to 1.4e-14 m, the position-error vectors and magnitudes to 1.4e-9 m against a 1e-6 m bar, and each point's p95 equals numpy.percentile bit for bit; the station corrections MISSED their 1e-9 m bar (worst 3.73e-9 m, 15 of 20 cases), and with them the corrected range errors: checked in 60-digit arithmetic, both sides are within double-precision rounding of the exact value, the survey term being a difference of two 1e7 m ranges whose last-place unit is 1.86e-9 m; recorded, not tuned. The kind reduces exactly to the lunar-differential-pnt kind at one point, one epoch and one trial. The error model, the decorrelation model and every threshold are this project's own or ILLUSTRATIVE; nothing here is a statement about any real system lunar_station (over lunar_dpnt, lunar_service) tests/lunar_station_coverage_reference.rs (one_point_one_epoch_one_trial_reduces_to_lunar_differential_pnt: to 1e-12 m with and without receiver noise; zero_baseline_floor_is_zero_in_every_trial: 0 to 1e-9 m; survey_floor_matches_the_survey_transfer_prediction: p95 within the 5 % band stated before the run; coverage_is_non_decreasing_in_the_threshold; corrected_error_grows_with_distance_along_an_azimuth; three_satellites_are_unavailable_with_a_reason_and_no_error; a_satellite_the_station_does_not_see_is_reported; deterministic_for_a_seed_and_moved_by_another; the_work_guard_refuses_an_oversized_grid; the_bundled_scenario_states_a_source_for_every_input; the_result_is_labelled_modelled_with_the_honesty_statement); tests/lunar_station_numpy_oracle.rs (the pre-registered numpy re-computation, recorded with its miss); lunar_service::tests::south_polar_ring_grid_is_the_published_comparison_grid; tests/lunar_differential_pnt_reference.rs and the registry and cross-platform goldens unchanged (additivity); tests/field_units_global.rs (every emitted field described, no exemption)
Lunar terrain horizon masks from a stated profile or a polar DEM Per-site azimuth-dependent horizon masks for the lunar-station-coverage kind (the reference station and every user point) and the moonlight-service-volume grid and its per-satellite export site (each export row gains clears_terrain), in the 0.36 skyline table format (skyline::Skyline, linear in azimuth with wrap at 360 deg; a stated profile and a DEM horizon at one site combine as their pointwise maximum): a stated [terrain] station_horizon or user_horizon labelled with its source, and/or a horizon ray-marched over a south polar stereographic DEM (the LRO LOLA gridded polar layout, read from a descriptor that fixes its size and SHA-256, or a latitude/longitude realdata::lola_dem tile with [terrain] dem_tile_path, echoed with its SHA-256) along great circles of the lunar sphere with exact curvature, from a stated mast height, at a stated azimuth step and range. A satellite counts at a site when it clears the flat mask_deg and the horizon at its azimuth (lunar_service::topocentric); an epoch the horizon leaves with fewer than four satellites at a point, where the flat mask gives four, is counted as the unavailable reason terrain_masked. The vendored DEM is a crop of the public-domain LOLA LDEM_75S_240M product, 5 x 5 block-mean resampled to 1200 m (data/lunar-dem/NOTICE.md). Absent, every site keeps the flat mask and every document is byte-identical InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed-form surfaces (InternalConsistency): the bare-sphere dip, a crater in a plateau on the sphere with an observer on and off its centre, and an analytic cone against its own rasterisation. On the real crop, an independent numpy ray-cast (scripts/gen_lunar_terrain_ref.py, numpy 2.5.3; pre-registered in tests/fixtures/lunar_terrain/PREREGISTRATION.md, committed alone in 4fa71559 before the script existed) agrees at five sites: site heights to 1.0e-11 m and all 1800 horizon elevations to 5.5e-10 deg against 1e-6 bars, truncated-ray counts exact; this checks the arithmetic, not the terrain. No published polar horizon or illumination figure has been reproduced: the vendored 1200 m crop smooths the sub-kilometre relief that published illumination studies resolve, so the DEM horizons are a MODELLED line of sight over a resampled real DEM, not a validated horizon. The station site and constellation stay ILLUSTRATIVE; nothing here is a statement about any real system lunar_terrain (over skyline, lunar_service::topocentric_basis); lunar_station; lunar_service (coverage_masked, masked_visible) lunar_terrain::tests (bare_sphere_horizon_is_the_dip: the ray march reproduces -acos(R / (R + a)) to 1e-3 deg at every azimuth; a_cone_on_a_lat_lon_tile_matches_the_analytic_cone: the same cone sampled onto a 0.005 deg latitude/longitude tile agrees with the analytic cone to 0.25 deg; a_lat_lon_tile_is_none_outside_and_wraps_longitude; crater_in_plateau_matches_the_closed_form: a flat-floored crater on the sphere, observer at the centre and 4 km and 7 km off it, against the closed-form rim elevation atan2((R + H) cos s - (R + a), (R + H) sin s) with s from the spherical rim-crossing equation, to 0.01 deg at every azimuth; rasterised_cone_matches_the_analytic_cone: a cone rasterised onto a 200 m polar stereographic grid and read through the grid sampler agrees with the analytic cone to 0.25 deg; projection_round_trips_through_the_rasteriser_layout; bilinear_reproduces_a_plane_exactly; stated_horizon_goes_through_the_skyline_rules; an_empty_skyline_is_exactly_the_flat_test); tests/lunar_station_terrain.rs (without_terrain_the_document_has_no_terrain_keys; a_zero_horizon_under_a_positive_mask_is_the_flat_run, for both kinds; a_horizon_only_removes_satellites_and_a_wall_removes_everything: user_lt4 keeps its flat count and the epochs a horizon costs are terrain_masked (availability itself can rise, because a horizon can hide a satellite the station does not see), and an 89 deg horizon at the station leaves nothing available; bad_terrain_sections_are_refused; the_vendored_crop_loads_and_is_oriented_as_the_source: Shackleton and Haworth crater floors low, the Malapert massif high, the mirror image not; the_station_site_horizon_from_the_crop; service_volume_dem_points_outside_the_crop_keep_the_flat_mask; a_lat_lon_dem_tile_gives_the_station_the_crop_horizon: a tile resampled from the vendored crop gives the station the crop horizon to 0.22 deg (bound 0.5 deg, fixed before the run), with the tile echo and units, and dem_path with dem_tile_path refused; the_export_site_is_masked_by_the_terrain: every export row clears the terrain exactly when it is visible and at or above the site horizon at its azimuth, the geometry does not move, the CSV gains the column only with terrain; the_horizon_matches_the_preregistered_numpy_ray_cast); tests/prediction_frozen.rs and the registry and cross-platform goldens unchanged (additivity)
Lunar reference-station multipath and receiver-hardware terms The optional [receiver] section of lunar-station-coverage (LRS-02): elevation-dependent multipath sigma(el) = a + b exp(-el / el0) at the user and at the station (the RTCA DO-229 airborne functional form, its a = 0.13 m, b = 0.53 m, el0 = 10 deg as defaults; on the Moon every value is ILLUSTRATIVE), white at the user and first-order Gauss-Markov over epochs at the station (rho = exp(-dt / tau)); early-minus-late DLL thermal code noise sigma = L_c sqrt(B_L d / (2 C/N0) (1 + 2 / ((2 - d) T C/N0))); per-channel inter-channel biases constant over a trial, at the user and at the station. Station terms enter its corrections, user terms the raw and corrected measurements, each on its own seeded stream. Absent, every document is unchanged InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed forms and statistics of the model's own draws (InternalConsistency): the DLL formula against a hand computation, the DO-229 form, the zero-baseline difference of two receivers, the Gauss-Markov lag-1 correlation. No lunar multipath or receiver measurement exists to compare with; the values are ILLUSTRATIVE and nothing here is a statement about any real receiver lunar_receiver; lunar_station lunar_receiver::tests (multipath_is_the_do229_form; dll_noise_matches_a_hand_computation: 0.825279 m at 45 dB-Hz, 0.5 Hz, d = 1, 20 ms; bad_sections_are_refused); tests/lunar_station_ext.rs (receiver_absent_or_silent_is_the_plain_run; zero_baseline_multipath_is_the_difference_of_two_receivers: sample sigma sqrt(2) a within 6 %; station_multipath_is_gauss_markov: lag-1 correlation exp(-dt / tau) within 0.01, unit variance within 2 %; inter_channel_biases_are_constant_over_a_trial); tests/prediction_frozen.rs and the goldens unchanged (additivity)
Lunar reference-station ephemeris-error growth over the correction latency The optional orbit_err_growth_m_per_s input of lunar-station-coverage (LRS-03): a correction applied latency_s after it was computed misses the growth g latency_s of the broadcast orbit error, g isotropic of 3-D RMS rate, drawn per satellite and trial on its own seeded stream (range 1-sigma rate tau / sqrt(3)), on top of the frozen-error line-of-sight re-projection. Absent, every document is unchanged. A K5 addendum to the published-claims comparison, pre-registered alone, runs K5 at 0.001, 0.01 and 0.1 m/s (ILLUSTRATIVE) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — The growth term's closed-form sigma and the first-order propagation check (InternalConsistency). The K5 addendum (tests/fixtures/lunar_station_published/ADDENDUM-LRS03.md, pre-registered alone in f9ce1284): K5 fails at every rate, corrected p95 3-D 369.8 m, 2315 m and 22797 m against a 1.5 m bar (292.96 m recorded without growth), as stated before the run. No public source gives a lunar growth rate: ILLUSTRATIVE lunar_station (orbit_growth_range_sigma_m) tests/lunar_station_ext.rs (growth_absent_or_zero_is_the_frozen_error_run; the_growth_term_has_the_closed_form_sigma: the growth-on minus growth-off link error has sample sigma rate tau / sqrt(3) within 6 % over 1600 draws; linear_growth_is_the_first_order_propagated_error: a velocity error dv propagated with the in-tree two-body integrator from the scenario orbit moves the position by dv tau to within 1 % at 60 s and 600 s); tests/lunar_station_published_oracle.rs::k5_growth_addendum_run (ignored, the recorded addendum)
Lunar reference-station solution modes: height constraint, three satellites, static-user window The optional [solution] section of lunar-station-coverage (LRS-06): a height pseudo-measurement row up . dx = e_h of stated 1-sigma weighted against range rows, a three-satellite minimum allowed only with it, and a weighted least-squares solve over the last window_epochs epochs with a shared static position and one clock per epoch (a filter's answer for a static position with no process noise over the same data; the epochs' errors are treated as independent). Absent, the snapshot solve and every document unchanged. An addendum to the published-claims comparison with the sources' solution style, pre-registered alone InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — The snapshot reduction and the solver's closed-form cases (InternalConsistency). The addendum (tests/fixtures/lunar_station_published/ADDENDUM-LRS06.md, pre-registered alone in 2b4c34b5) with a 1 m height constraint, three satellites and a 6-epoch window (ILLUSTRATIVE settings; the sources state a filter, a height constraint and three satellites but not their settings): K1 to K5 fail and K6 passes, 1 of 6 as in the recorded run; the R300 corrected p95 3-D error falls from 280.6 m to 2.11 m (horizontal 0.90 m, not scored) and coverage stays 0. The window's independence assumption favours it. Not a statement about any real system lunar_solution; lunar_station (solution_figures) lunar_solution::tests (one_epoch_without_height_is_the_snapshot_solve: equals lunar_dpnt::position_error_vector_from_range_errors to 1e-8 m, a loose height row changes nothing, a tight one pins the height error; three_satellites_need_the_height_row; a_window_shares_the_position; bad_sections_are_refused); tests/lunar_station_ext.rs (the_default_solution_mode_is_the_snapshot_solve: every figure to 1e-6 relative; height_aiding_and_a_window_do_what_they_say); tests/lunar_station_published_oracle.rs::solution_style_addendum_run (ignored, the recorded addendum)
Lunar reference-station accuracy and coverage against published claims The lunar-station-coverage kind run under the public assumptions of the published material on a lunar differential reference station (four navigation satellites in 24 h frozen elliptical orbits, 10 m 95 % SISE, 0.30 m code noise, 1 s and 600 s correction latency, a sub-decimetre station survey, the published example station site, the 300 km and 600 km south-polar circles) and scored against the sources' numeric claims under six one-sided bars pre-registered before the run: coverage of the whole south pole at sub-metre p95 (K1, K2), sub-metre and decimetre-level corrected p95 (K3, K4), sub-metre kept at 600 s latency (K5), and accuracy kept from 10 km to 500 km baseline (K6) ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — Reference: the numeric claims of five public sources registered with URL, retrieval date, SHA-256 and licence in tests/fixtures/lunar_station/SOURCES.md (arXiv:2602.08432v3; IOAG Cislunar PNT Workshop 2025 and 2026 slides; UNOOSA ICG WG-B Lunar PNT, June 2024), transcribed with page references in tests/fixtures/lunar_station_published/CLAIMS.md. Bars, cases and inputs were pre-registered in tests/fixtures/lunar_station_published/PREREGISTRATION.md (revision 2, ebac1e14, committed alone before the run). 0.36 first run, a finding (stays MODELLED): 1 of 6 bars passes. Coverage is 0.00 on both circles against >= 0.95, and the corrected p95 3-D error is 280.6 m (300 km), and 293.0 m at 600 s latency, against <= 1.5 m. The decimetre bar (K4) could not pass at the sources' 0.30 m code noise, which reflects a conflict between the sources rather than a model result. K6 passes (ratio 1.39 against <= 1.5), but as a ratio of two geometry-dominated figures it is evidence about decorrelation in neither direction. Cause: the satellites' elements are not public, and on the ILLUSTRATIVE in-tree elements a user and the station share four satellites above 5 deg in only 8.2 % (300 km) and 6.3 % (600 km) of epochs, at near-singular geometry (uncorrected p95 3.8 km against the sources' < 10 m). The sources' simulations used a filter, a height constraint and three satellites in common view, which the snapshot kind does not model. The comparison therefore neither confirms nor refutes the published 'sub-metre over the whole south pole'. It shows that this model's result depends on orbits that are not published. Not a statement about any real system; not affiliated with or endorsed by any agency lunar_station (over lunar_dpnt, lunar_service) tests/lunar_station_published_oracle.rs::recorded_finding_one_of_six_bars_passes (the recorded figures against the registered bars); tests/lunar_station_published_oracle.rs::published_claims_comparison_run (ignored, about 7 s in release: re-runs the six registered cases and asserts the recorded figures)
ARAIM with simultaneous multi-satellite fault hypotheses araim_reference::add_v42_subset_plan: the ADD v4.2 subset-determination rule (P_THRES, FC_THRES, monitored subsets fewest-removed first) generalised from pairs to simultaneous combinations of up to max_order satellite and constellation events, with the exact prior P_no fault prod q_e; add_v42_protection_levels_to_order runs the ADD v4.2 protection-level path on it (order 2 is the existing path exactly). raim::araim_subset_raim (opt-in): advanced RAIM over that hypothesis set, each monitored subset one (p_fault, T, b, sigma) mode in the integrity-risk sum, unobservable subsets moved to the unmonitored risk, the budget scaled by the ADD allocation of the unmonitored risk, and the subset of largest normalised separation reported when a fault is detected. Priors needing deeper subsets than max_order are refused, never truncated InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency (InternalConsistency): the order-2 reduction to the MAAST-checked ADD v4.2 path, independent re-derivation of the priors, and a constructed two-satellite fault. No MAAST or RTKLIB run beyond pairs has been made, so the deeper hypothesis sets and the subset RAIM's protection levels are not externally checked. araim_subset_raim shares araim_dual_raim's simplifications (one sigma for integrity and accuracy, one clock, the plain normal tail): it is not ADD-conformant araim_reference (add_v42_subset_plan, add_v42_protection_levels_to_order); raim (araim_subset_raim, SubsetRule) tests/raim_multi_sv_subsets.rs (deeper_orders_change_nothing_when_pairs_suffice; triples_are_refused_at_order_two_and_planned_deeper: N_fault,max >= 3, the unmonitored risk within P_THRES, a subset removing three or more satellites monitored, and more than ten monitored priors re-derived independently as P_no fault q^k to 1e-12; a_two_satellite_fault_is_found_as_a_pair: no alarm fault-free, and a 30 m bias on two satellites detected with the pair as the subset of largest normalised separation); tests/araim_reference_vectors.rs and tests/integrity_araim_stanford_oracle.rs unchanged (the order-2 path is the MAAST-checked one)
RAIM beside the clock-holdover figures of merit The optional [integrity] section of the clock kind (clock_integrity::run): from a stated site and constellation presets (geometry::sky_geometry), at every integrity epoch while the GNSS timeline is not denied, snapshot RAIM (raim::snapshot_raim: parity chi-square test, slope protection levels) on the satellites above the mask with seeded Gaussian residuals of the stated sigma and an optional stated bias; a separate integrity_fom block with per-epoch verdicts, protection levels, and availability. Denied epochs are reported unavailable, never extrapolated; the holdover figures of merit are unchanged and, without the section, the output is byte-identical InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency (InternalConsistency): the protection levels are those of snapshot_raim, which is validated against RTKLIB in its own row, recomputed on the same geometry; fault-free and injected-fault behaviour. The sky is a representative preset geometry (not a dated almanac), the residuals are synthetic and sigma, the alert limits and the probabilities are stated inputs; nothing here is a statement about a real receiver's availability clock_integrity (run, sky_at, IntegrityCfg); scenario (Scenario::integrity); report (RunResult::integrity_fom); api (clock dispatch) tests/clock_integrity.rs (the_block_is_separate_and_absent_by_default: holdover figures unchanged, 111 denied epochs unavailable with no protection level, refused with runs > 1; protection_levels_are_the_snapshot_raims_on_the_same_sky: every sampled epoch's HPL and VPL equal a zero-residual snapshot_raim on the same preset sky exactly, and the fault-free run raises no alarm; a_stated_bias_is_detected_while_it_lasts: a 60 m bias alarms on exactly the 10 epochs it covers; every_integrity_field_has_a_unit); clock_integrity::tests; the clock goldens unchanged
Spatial, noisy, multi-family cislunar arc-length observability The cislunar arc-length observability threshold in the SPATIAL six-state CR3BP rather than the planar four-state, across DRO, L2 halo and L2 near-rectilinear halo families, with measurement noise entering the Gramian and TWO criteria reported because there is no single honest one: the published rank criterion, which is provably invariant to a homoscedastic measurement sigma (whitening multiplies the observability matrix by a scalar, leaving the relative singular-value spectrum and hence rank, defect and condition unchanged), and an estimability criterion — the first arc at which the formal 1σ position uncertainty of the chief's initial state falls below a stated bound — which is the one that does move with noise. Each threshold carries the epoch-grid bracket it sits in; an unreached criterion is null with a reason. Planar mode remains the default and out-of-plane families are refused there rather than flattened into a state that cannot represent them InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — An independent row-echelon rank by Gaussian elimination with partial pivoting confirms every six-state rank verdict — a different algorithm sharing no code with the eigen/SVD route under test. The 6×6 CR3BP state-transition matrix this composes carries its own ReferenceImpl oracle against SciPy variational integration, and the halo/NRHO initial conditions come from a corrector that reproduces the published L2 southern 9:2 Gateway orbit. The existing square-root-information-filter leg is explicitly NOT counted as corroboration: it consumes the same Jacobians and reduces to the same normal matrix, so it is a consistency check between two numerical machines, and the emitted extension label says so. NOT externally anchored, and ExternalDataset is therefore declined rather than borrowed from the STM's row: the threshold arc lengths themselves depend on the MODELLED constellation design, the epoch grid, and — measurably, by up to 40× — on the singular-value tolerance. The published planar 2.09 h is reproduced exactly at rel_tol = 1e-6 and is itself tolerance-dependent (10.25 h at 1e-4, 0.42 h at 1e-8), which is a property of the criterion rather than of the orbit. No public dataset publishes an arc-length observability threshold for a chosen cislunar constellation. MEASURED RESULT: the spatial six-state threshold is 22.17 h for the L2 NRHO and 40.42 h for the L2 halo, and DOES NOT EXIST for the planar-DRO family the published claim was derived on — rank 4 of 6 with datum defect 2 and two exactly-zero eigenvalues, a structural defect no arc length recovers cislunar_observability, observability_gramian, intersat_range, cislunar_srif cislunar_observability::tests and observability_gramian::tests (the default document pinned bit-for-bit by FNV-1a of its JSON, summary and SVG, with explicit-default values asserted to be a no-op and the eight extension keys asserted ABSENT so the capture cannot be regenerated into a self-comparison; the additive units block excluded from the freeze by being stripped and re-hashed against the constant pinned before it existed, which proves rather than assumes that nothing released moved; rank invariance under a homoscedastic sigma asserted at σ = 0, 0.1, 1, 10, 100 m; σ_pos asserted to scale exactly linearly with σ to 1e-6 relative; the DRO null space asserted to be exactly the z and ż coordinate axes with the two causes separated — a range row between coplanar spacecraft has û_z = 0, and the CR3BP out-of-plane block decouples exactly at z = 0; spatial Jacobians against central finite differences and against the crate's independent 3-D range-rate observable; out-of-plane families refused in planar mode)
Operational-style Earth-orientation prediction error, measured predicted-versus-final A least-squares bias-plus-rate fit over a trailing window plus the principal periodic terms — annual, semi-annual and the two principal zonal tides for UT1; Chandler, annual and semi-annual for the pole — extrapolated with the last in-window residual carried forward: the class IERS Bulletin A uses, in place of the persistence predictor the published horizon rested on. Scored the only honest way: a forecast for T+h built from rapid Bulletin A rows at or before T, measured against the LATER-PUBLISHED Bulletin B final at T+h, with persistence scored over the identical epoch set against the identical finals beside it. A target epoch with no published final is dropped rather than re-scored against the rapid column; a periodic term the window cannot constrain is reported as rejected with the cycles it actually spans; an incomplete window is refused rather than quietly shortened ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — Three independent routes, none of them a published prediction-accuracy figure. (1) An analytic signal with known coefficients — the only way to exercise the periodic machinery, since no committed series is long enough to admit an annual term. (2) The textbook closed-form least-squares solution, different algebra from the matrix solve under test, on real rows. (3) The genuine archived Bulletin A prediction rows the real 2026 product publishes, compared per lead as an AGREEMENT statistic and explicitly not as an error: 0.256 ms at 1 day, 0.695 ms at 2 days, 1.252 ms at 3 days, drifting to 3.885 ms at 9 days. So this is Bulletin A's CLASS, close at short lead, not Bulletin A. The predicted-versus-final residuals are real measured quantities over real IERS rows, but their magnitude is checked only against the DIRECTION of the comparison, never against an IERS-published accuracy number — reading a real product is provenance, not an oracle. MEASURED: at day 1 the operational predictor gives 3.78 m of Moon-frame error against persistence's 11.39 m (3.01×), at day 2 10.23 m against 21.72 m (2.12×), at day 3 20.33 m against 30.57 m (1.50×) — and it is WORSE beyond three days (0.87× at 5 days, 0.43× at 10), which the report emits rather than showing only the horizons that flatter it. NOT reproduced: the autoregressive residual filter and the tabulated zonal-tide reduction, the 365-day operational window is unreachable with the committed data, and NO archived earlier vintage of the series exists in this repository — so the archived-vintage table reports no rows rather than scoring a synthesised one. 0.30 external comparison, a finding (stays MODELLED): scored against the same finals over 178 archived Bulletin A issues with the crate's default 15-day window, the predictor's UT1 MAE is 2.4x to 12.6x Bulletin A's at 1 to 10 days (bar 1.5x) and 5.32 ms at 10 days, outside the 0.36 to 3.13 ms range of the 2nd EOP PCC; the pole is 1.5x to 1.85x Bulletin A's (inside 1.5x only at 6 and 7 days); 19 of 21 pre-registered conditions fail. Correction to route (3): the 2026 product rows it was compared with carry the IERS I (measured) flag, not P, so those agreement figures are against measured rapid values, not Bulletin A predictions. 0.30 round 2, a least-squares plus autoregressive predictor with the zonal tides removed analytically, against 178 archived Bulletin A issues at the round-1 bar (pre-registered 65a3a1f7), a finding (stays MODELLED): 12 of 21 conditions hold; the UT1 MAE is 1.73 to 2.11x Bulletin A at 2 to 10 days (bar 1.5x) while the pole is within 1.27x at every lead. 0.30 revision: with the offline input now classified by IERS flag, the route-(3) agreement figures are against real Bulletin A predictions (0.256/0.695/1.252/3.885 ms at 1/2/3/9 days against rapid rows -> 0.133/0.421/0.839/2.786 ms) frame_eop, realtime_frame_eop frame_eop::tests, realtime_frame_eop::tests and tests/operational_eop_predictor_reference.rs (analytic-signal coefficient recovery to 1e-9 at a 365-day window; a bias-plus-rate fit equal to the closed-form ordinary-least-squares slope and intercept to 1e-12 on real rows; TWO look-ahead detectors that wreck the rapid UT1 and pole columns of every row after the issue epoch — leaving the Bulletin B finals intact — and demand bit-identical output, mutation-verified to turn 10 tests red when the fit barrier is loosened by exactly one day; an independently rebuilt epoch list; a target's Bulletin B block blanked and the epoch shown to leave the table; term admission checked at 6, 15, 150 and 365-day windows; monotone row counts; and a frozen pre-change capture of the default report asserted field for field with no tolerance, which additionally asserts the capture does not contain the new keys so it cannot be silently regenerated into a self-comparison); tests/operational_eop_predictor_bulletin_a_oracle.rs::predictor_mae_against_bulletin_a_and_the_pcc_range_finding; tests/operational_eop_ls_ar_bulletin_a_oracle.rs::ls_ar_predictor_against_bulletin_a_finding; tests/eop_prediction_beyond_table.rs (the opt-in EopSeries::with_ls_ar_prediction extension beyond the last row: in-table answers bit-identical, forecast rows equal to ls_ar_predict, frame arguments past the table follow the forecast instead of clamping; internal consistency)
Lunar frame datum from an observing campaign The seven-parameter Helmert datum propagated from a SIMULATED OBSERVING CAMPAIGN instead of recovered from an injected transform. Earth stations observe a sourced catalogue of lunar-surface beacons over an explicit schedule; the lunar-VLBI delay partials are accumulated into a beacon-coordinate Fisher information matrix and pushed through the Helmert design A = [I₃ | [p]ₓ | p] into H = AᵀM_bA, so the reported datum accuracy is a function of the observing programme — exactly linear in the delay sigma and monotone in the arc through the libration the report MEASURES. The datum defect is the subject rather than a footnote: rank, defect, condition number, spectrum, unobservable directions in the seven-parameter basis, the weakest direction even at full rank and each parameter's share of it are emitted on every run, and any parameter the campaign does not constrain is published as NULL with a status. Beacon-error correlation is MEASURED, not assumed — exactly zero with the stations held fixed, and printed with its cost when they are estimated. Runnable as the lunar-frame-campaign scenario kind ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — Closed-form identities and an independent in-repo route, with no external oracle claimed. The Helmert design — the only new derivative in the module — is re-derived by central finite difference of lunar_frame_realise::apply_helmert, a path sharing no expression with the analytic form. The accumulation it composes is lunar-vlbi-fim's, whose Jacobian is finite-differenced against lunar_vlbi::vlbi_delay_s there, and whose linear-algebra kernel is separately externally anchored against numpy in tests/fim_observability_reference.rs — this row borrows neither status. The physics oracle is structural rather than numerical: a beacon delay partial is the near-field DIFFERENCE of two near-parallel unit vectors, so the worst-determined translation direction MUST be the body-fixed direction to Earth, and the test asserts the computed answer against the separately measured direction. MEASURED: campaign-derived translation sigma 6.3975 m against the injected-transform scenario's 0.3125 m recovery error (20.5× tighter), while rotation and scale run the OTHER way at 2.32× and 13.5× looser — the injected path assumes one isotropic sigma and so spreads its error uniformly across seven parameters, which the delay observable does not. Rank 7/7 but condition 3.8e5, with one direction 99.57 % pure translation-toward-Earth and forty times worse than any other. WHAT THIS ROW DOES NOT CLAIM: that the campaign figure is right in absolute terms. It establishes that the figure now DERIVES from a schedule, a geometry and an error model rather than from a planted answer. Stays ReferenceImpl/MODELLED: no published lunar-VLBI campaign-plus-datum-covariance pair exists, the station network and delay sigma are ILLUSTRATIVE inputs (the beacon catalogue is sourced, the campaign is not), observations are treated as independent while a real session's troposphere and clock are correlated between nearby scans, and the ephemeris, clocks, troposphere and Earth-orientation parameters are held FIXED. 0.30 external comparison, a finding (stays MODELLED): with every beacon Jacobian row rebuilt from NAIF SPICE light times (DE440, ITRF93, MOON_ME; pre-registered aad03856), the schedule, Helmert rank, datum sigmas (within 4.7e-3), condition, weakest direction (0.07 deg), libration sweep and arc ordering agree on six scenarios within the pre-registered 1 % / 0.2 / 0.05 deg. NumPy on the committed engine Jacobian agrees to 3e-14 where the stations are fixed. With the stations estimated it differs by 6.8e-6 against a pre-registered 1e-9, whose condition-number premise was wrong (Helmert condition 2.1e8; independent NumPy routes disagree by 3e-6; a contribution from the engine 1e-9 pseudo-inverse fallback is not ruled out), so the row is not promoted on that pre-registration. 0.36 re-registration at a condition-scaled bar (pre-registered 3855e840; t = max(1e-12, 10 kappa 2^-53) from the conditioning of the joint information and its Helmert reduction), a finding (stays MODELLED, NOT MET): step 0 rules the pseudo-inverse fallback OUT for the 6.8e-6 gap (no matrix upstream of the Helmert matrix falls back on the six original scenarios, tightest margin a factor 2.6), the SPICE leg still holds on all six, and NumPy agrees within the bar on six of eight scenarios (default, the two arcs, the 3x delay sigma, the collinear defect and the fresh stations-fixed run on 2026-12-01; worst 0.13 of its bar). It fails on stations_estimated (datum sigmas up to 6.8e-6, condition 9.1e-6, independence-discarded norm 3.5e-6, against t = 5.9e-7), and on the fresh date the south-pole beacon has no observation, so the beacon information is rank-deficient (pseudo-inverse fallback upstream of the Helmert matrix in both fresh scenarios) and the unchanged NumPy oracle cannot evaluate stations_estimated_fresh (singular matrix). Results: docs/design/evidence/mr05-lunar-datum-cond/RESULTS.md lunar_frame_campaign (composing lunar_vlbi, lunar_vlbi_fim, fim, lunar, lunar_frame_realise, frames, cio, lunar_frame) lunar_frame_campaign::tests (21 lib tests: the Helmert design against a central finite difference of lunar_frame_realise::apply_helmert — the module the datum is FOR, which computes no derivative and so pins the [p]ₓ sign convention — all 84 design entries agreeing to < 1e-6; a pure network translation read back as a pure translation with < 1e-6 leakage into the other six parameters; the datum sigma exactly linear in the delay sigma to 1e-8 over a 3× change on all seven parameters; a 16 h arc measured worse and a 48 h arc measured better than 24 h, with the emitted libration sweep ordered the same way; the worst translation axis asserted to BE the dominant axis of the separately measured body-fixed direction to Earth and worse than the others by > 5×, a physics oracle nothing in the solver was told about; three collinear beacons producing a defect with every datum sigma NULL and the null directions emitted in the seven-parameter basis; offblock_fraction and inter-beacon correlation exactly 0.0 with the stations fixed and both > 0 with them estimated; the comparison block's injected-transform figures shown equal to an independent run of that scenario to 1e-14 relative rather than transcribed; a guard that no injected/recovered datum appears anywhere in the document; the lunar-frame-realisation emission pinned byte-for-byte by FNV-1a-64 over json‖summary‖svg for three input shapes, fingerprinted before the work began); tests/lunar_vlbi_campaign_spice_oracle.rs::lunar_frame_campaign_finding_stations_estimated_p2_precision (gated; the strict lunar_frame_campaign_matches_spice_geometry_and_numpy stays ignored); tests/lunar_frame_campaign_mpmath_oracle.rs::lunar_frame_campaign_datum_matches_mpmath_extended_precision (finding; founder decision 2026-10-02, option A: this row stays MODELLED and does not borrow the separate row's status; against a 50-digit mpmath oracle, pre-registered 826dd676, the engine's stations-estimated datum sigmas are within their a-priori backward-error bound, 9.7e-6 off on 2024-01-01, and the 1e-9 bar was below what any double-precision route reaches, the best, a NumPy QR projection, being 5.5e-9 off; the evidence backs the separate row 'Lunar frame datum covariance with the stations estimated, against 50-digit extended precision'); tests/lunar_frame_campaign_pinv_fallback.rs::finding_step0_fresh_beacon_information_falls_back (pinned); tests/lunar_frame_campaign_cond_bar_oracle.rs::finding_p2_condition_scaled_bar_not_met_on_the_estimated_scenarios (pinned)
Independent-estimator corroboration of the cislunar arc-length threshold A batch least-squares estimator that RECOVERS the chief's initial state from simulated inter-satellite measurements over growing prefixes of the same epoch grid the rank-vs-arc table uses, with the measurement partials taken as central finite differences of the composed forward model. It consumes none of the machinery the threshold was measured with — no analytic Jacobian row, no variational state-transition matrix, no singular-value or eigen decomposition, no rank tolerance, no square-root information filter — and shares only the dynamics, the initial conditions, the scalar observable and the epoch grid, each named in the emitted document. Two criteria, both swept: noise-free recovery (the rank analogue) and Monte-Carlo estimability (the estimability analogue, measured against a known truth rather than predicted from a covariance). Runnable as the cislunar-arc-recovery scenario kind ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — A separate estimator in this codebase on a different algorithm and a disjoint code path: nonlinear weighted Gauss-Newton with finite-difference partials, its verdict read as a measured state-recovery error in km and mm/s. It has no expression in common with the Gramian's rank-and-covariance route, and the separation is ENFORCED by a source-text guard rather than asserted. MEASURED on the published planar DRO grid: the ESTIMABILITY criterion is CORROBORATED — the measured Monte-Carlo boundary is 5.739130 h against the formal 5.739130 h (ratio 1.0000), and the measured RMS reproduces the formal 1σ over 21 arc lengths to a geometric-mean ratio of 0.9804. The RANK criterion is NOT corroborated as a recoverability boundary: the estimator recovers from 0.782609 h against the Gramian's 2.086957 h, ratio 0.375, and at 1.826087 h — the last prefix the rank read scores 3 of 4 — recovers to 1.96e-5 of the a-priori displacement. The recovery boundary is unmoved over three decades of its own bound while the rank threshold spans 'never' to 0.782609 h over four decades of rel_tol, and the two coincide exactly at rel_tol = 1e-8. That span was first recorded as reaching 0.260870 h; that figure was an ARTEFACT, produced by a rank read that counted 4 directions from 2 measurement rows below the f64 noise floor, and it is corrected here rather than left standing. The rank read is now bounded by Sylvester's inequality with the reason emitted, and the corrected span saturates at exactly the arc where the independent estimator recovers, which strengthens this row's cross-validation rather than weakening it: the published 1e-6 is a conservative singular-value CONVENTION, not a statement about recoverability. Same pattern spatially: NRHO 9.290323 h against 21.677419 h, halo 22.978723 h against 39.829787 h, with estimability agreeing exactly in both. The planar-DRO six-state recovers at no arc, independently reproducing that family's structural datum defect from an estimator told nothing about it. NOT externally anchored — the dynamics and initial conditions are shared with the analysis under test and no public dataset publishes such a threshold — so ExternalDataset is declined cislunar_arc_recovery, batch_ls cislunar_arc_recovery::tests and tests/cislunar_arc_recovery_reference.rs (both boundaries and their ratios pinned on the published grid; the measured error curve compared to the formal covariance row by row with a per-row factor-of-two bound and a geometric-mean bound; a NEGATIVE CONTROL — the planar-DRO six-state — asserting the criterion CAN fail and that the unregularised estimator diverges past 1e6 km rather than returning a plausible small error; parameterisation invariance asserted on every prefix to 1e-3 relative; a source-text guard that strips comments, string literals and the test module and then fails on any mention of the Jacobian, STM, SVD-rank or SRIF machinery, mutation-verified by injecting a forbidden call; a test-only check that the finite differences equal the analytic rows, so the linearisation is known good while the analytic route stays absent from the estimator; determinism asserted byte-for-byte; the released cislunar-observability document pinned by key set, canonical fingerprint and summary line)
Lunar service volume from real, retrieved constellation geometry Accepts a tabulated Moon-centred state ephemeris (the evaluation of an SPK/BSP kernel) or a published constellation definition behind ephemeris_path, runs the identical coverage / DOP / protection-level sweep against it, and emits the σ_URE ranging requirement it implies BESIDE the unchanged illustrative Keplerian and perturbed results with the difference as its own named quantity. Every figure carries a provenance class that distinguishes kernel-derived from published-element-derived from modelled, so the two can never be confused in a downstream quotation InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — The GEOMETRY is external and hashed: three fixtures whose numbers come only from documents retrieved with URL, retrieval date and SHA-256, regenerable by committed generators that verify the upstream hash and ABORT rather than emit a number — the LANS interoperability-demonstration reference constellation (NASA NTRS 20250009447, SHA-256 d1b916be…), the LNCSS case studies (NAVIGATION 70(4) navi.613, CC BY, SHA-256 4e294687…), and a genuine flown-spacecraft ephemeris for LRO, Danuri, Chandrayaan-2 and CAPSTONE evaluated from JPL's own reconstructed kernels via Horizons. NO lunar-navigation constellation kernel exists publicly — Moonlight/LCNS, LCRNS and LNSS are not flying and NAIF publishes nothing for them — and none was invented. The DERIVED σ_URE requirement has NO external oracle (nobody publishes the ranging accuracy a 50 m lunar HPL demands over this service volume), so it is checked against its own algebraic identity and, independently, by re-running the whole sweep at the computed requirement and confirming availability flips there. MEASURED: the published 8-satellite design needs σ_URE 2.9044 m at 100 % coverage against the illustrative constellation's 0.3591 m at 37.85 % — an 8.09× revision of a published number under programme rule R4. The qualitative conclusion survives (LNIS-class 30 m still does not close a 50 m south-polar HPL) but the shortfall was overstated eightfold. The 5-satellite LANS demo yields ZERO protection-level samples — five satellites cannot give the six-in-view a single-fault hypothesis set needs — and the requirement field is ABSENT rather than fabricated; likewise for the four real spacecraft at 0 % coverage. InternalConsistency is the honest kind: the INPUT data is external and hashed, but the quantity this row is about is validated only against itself. 0.30 external comparison, a finding (stays MODELLED): against the LNCSS case-study statistics of navi.613 on 346 grid points, 4 of 12 availability statistics fall outside the pre-registered 2 percentage points (case A: -4.0, +22.5 and -3.6 pp; case B: -12.1 pp). Likely causes: elements read in the wrong frame, two-body Kepler over 15 days against the paper's unstated force model, and a grid not reproducible from the text. The PDOP half was not evaluable (LANS prints no numeric statistic); the comparison test is committed ignored. 0.30 round 2, a finding (stays MODELLED): against an Orekit 12.2 / Hipparchus 3.1 oracle computing the whole report (Orekit propagation, DOPComputer visibility and DOP, Hipparchus-composed MHSS protection levels, the requirement solved per sample; pre-registered 3c8e879a) on all five retrieved geometries and two grids, 155 of 160 values agree within the pre-registered bars (2 pp, 5 %, 1 %), including the sigma_URE requirement for LNCSS A and C (3.879072208 m on both sides for case A) and the absent requirement for LANS and the orbiters. LNCSS B on the dense grid fails on its worst-sample statistics (sigma_required 0.000923 against 0.001511 m, hpl_max 1.63e6 against 0.99e6 m) where near-singular geometries (PDOP about 1e6) amplify the metre-level position agreement; its p95 requirement agrees (1.6343 against 1.6357 m). The worst-sample requirement is ill-posed on degenerate geometry. Against navi.613: 4 of 12 still outside 2 pp (pinned) lunar_ephemeris, lunar_service lunar_ephemeris::tests (format and frame parsing; Lagrange interpolation exact at nodes and on a linear track off-node; ICRF elements take the IAU 2015 reduction and are byte-equal to an explicit icrf_to_iau_moon application; true↔mean anomaly round-trips against a forward Kepler solve; malformed files refused with the reason named). lunar_service::tests (with ephemeris_path unset the report's key set and SHA-256 are pinned; the Keplerian row equals the standalone Keplerian run field for field; the identity σ_required · HPL_max / σ_URE = AL, then an END-TO-END re-run at the computed requirement reaching 100 % protection-level availability and a re-run 1 % above it not reaching it; every emitted numeric field of both new blocks walked from the produced JSON for a unit and a provenance class; the committed fixtures matched to their source tables satellite for satellite; a horizon past the end of a table refused); tests/lunar_service_requirement_orekit_oracle.rs::lncss_b_dense_finding_is_unchanged; tests/lunar_service_volume_orekit_oracle.rs::service_volume_matches_orekit_on_identical_ephemeris_and_grid
Unit and provenance declared for every reported quantity A machine-readable schema giving unit, provenance class and definition for every numeric field of every scenario report, plus a single global gate that runs every registered scenario kind and fails if an emitted numeric field lacks either. The provenance vocabulary is closed and each class carries an evidence tier, with two classes deliberately mapped to inherits-scenario-label and depends-on-input rather than being assigned a tier the class does not determine InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — The emitted document itself: every numeric leaf must resolve to an entry in that document's own units block. There is no external unit registry to check a DECLARED unit against, so a declared unit is a reviewed assertion and not a verified one — the gate verifies COMPLETENESS and WELL-FORMEDNESS, not truth, and Validated would be wrong because nothing external confirms that m is the right unit for a field named _m. An independent name-suffix cross-check was run over the 1,434 fields described AT THAT TIME: of the 691 carrying a unit-bearing suffix, 40 disagree with the declared unit and all 40 are explained (per-second suffixes, minima, aperture-seconds, newton-metres against a nanometre-looking suffix), so no wrong unit surfaced. That cross-check has not been re-run since, and coverage has grown past it — the figure is left at what was actually measured rather than restated at the current total. At the time of that change (0.27.0), coverage moved from 7 of 56 kinds to 60 of 61, and from 389 of 1354 fields to 1,742 of 1,744 (docs/field-units-schema.json, which a staleness check keeps current). NO kind remains uncovered (ceiling 0, FUT-28, 0.36): the last was sweep-nd, two of whose columns are caller-keyed so their units are data; they are now described as mixed - see note and the unit of every position is read from the SWEPT pack's own units table into key_units and metric_units (or taken from the axis's declared unit, which must agree with the pack's when both exist; null when neither exists, stated rather than guessed). cislunar-observability was the one before it, and came off the list when its released document gained a units block: the additivity pin that had named units as a forbidden key now PROVES the addition is additive instead — strip the block back off and the document still hashes to the two constants frozen before it existed, so a released value that moved underneath the addition still fails. The work also surfaced twelve unit or documentation defects in existing code, reported rather than fixed under R1 field_schema tests/field_units_global.rs (all 61 registered kinds run, one document shape each: every numeric leaf must resolve to an entry in that document's own units block; a malformed entry counts as missing for EVERY kind, exempt or not, so a placeholder buys no coverage; the exemption list may not exceed its pinned ceiling, a listed kind that turns out to be fully covered FAILS the gate so the list cannot be padded, and a registered kind absent from the runner table fails so a new pack cannot slip in unexamined — which it did, catching both kinds added after this work began; a one-way ratchet on the described-but-undefined backlog; and a staleness check on the committed schema document); field_schema::tests
Lunar reference-station geodesy: added retroreflector and VLBI beacon against the five-array datum Optional extra_reflectors and extra_beacons inputs on the lunar-llr-datum scenario add a station_geodesy block: the five-array Helmert information from the archived lunar laser ranging slice plus the information an added retroreflector (ranged at the archived normal-point epochs at which the ranging station is above its horizon, each with that normal point's archived weight) and an added VLBI beacon (observed by the lunar-frame-campaign network and schedule with the Earth stations fixed, through the lunar-vlbi-fim delay partials) at stated sites put on the seven-parameter datum, re-solved, with each Helmert parameter's 1-sigma before and after, their ratio, the before and after norms, and the extreme eigenvalues of the Fisher difference. Absent or empty, the report is unchanged InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency only: each added site is a distinct point and a laser range or a fixed-station VLBI delay touches one point, so its information A_p^T M_p A_p is positive semi-definite and adds; the test checks the Fisher difference and every variance against that. The five-array result is the existing real-data row and is unchanged. The added reflector reuses epochs scheduled for the five existing arrays, an ILLUSTRATIVE schedule, and the added beacon's network, schedule and delay sigma are the ILLUSTRATIVE lunar-frame-campaign inputs; the site is an ILLUSTRATIVE south-polar position. A south-polar site sees the Earth low on its horizon or not at all, which the existing look-angle tests express; neither site is ranged continuously. The figures are Cramer-Rao bounds for a reduced parameter set, not a solved datum and not a statement about any real station lunar_llr (over lunar_frame_campaign::beacon_information, schedule_for and solve_datum_information, lunar_vlbi_fim) tests/lunar_station_geodesy.rs (empty_or_absent_extra_lists_are_bit_identical: empty lists and the baseline example give the default report and summary byte for byte; an_added_site_never_increases_any_variance: the smallest eigenvalue of H_after - H_before is non-negative to 1e-9 of the largest, every after/before sigma ratio is at most one, and both added sites are observed; the_rest_of_the_report_is_the_five_array_result; every_station_geodesy_field_has_a_unit; a_beacon_list_inside_the_campaign_block_is_refused); scenarios/lunar-station-geodesy-baseline.toml and scenarios/lunar-station-geodesy-with-station.toml (same archived schedule and the same VLBI campaign block)
Gate integrity — a green that means what it says Three structural guards over the verification process itself, each closing a class of defect that reached the canonical gate as an intermittent or spurious red. (1) Every constructed temp path in the Rust sources must carry a per-call unique component; a process id is rejected, because cargo runs the library tests as parallel threads of ONE process and the pid is shared by all of them. (2) Every byte-for-byte or hash pin must declare, next to itself or in its module header, what it covers and what it deliberately excludes — so a cross-cutting change can tell at a glance which pins are in scope and which have silently become repository-wide change detectors. (3) A green is claimable only from the FULL suite: scripts/gate.sh runs cargo test --all, captures the true exit code with no pipe in the way, and writes a receipt naming the commit, the integration-binary count, the test count and the duration; the pre-push check refuses a push whose commit no valid receipt names, on a clean tree. Repeatability is sampled separately by scripts/check-repeatability.sh, which runs the library suite N times and fails if the set of passing tests differs. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed-form: each guard is run over a fixed known-bad snippet that must fire and a fixed known-good snippet that must stay silent, both literal constants the detector cannot influence. The two known-bad snippets are the F22 and F25 defects in their original shape. This is an INTERNAL oracle and the row is MODELLED accordingly: it proves the guards discriminate the defect from its fix, not that the classes they describe are exhaustive. Their stated blind spots — shared state that is not a path, a pin held in a short named constant, a rare race that three runs do not sample, and a receipt that anyone who can write the file can forge — are written out in the module documentation of tests/source_guards.rs and in each script's header rather than left to be discovered. scripts/gate.sh, scripts/check-gate-receipt.sh, scripts/check-repeatability.sh, scripts/install-gate-hook.sh tests/source_guards.rs (9 tests: both guards over the whole source tree, plus mutation fixtures that grade each guard in both directions — the F22 pattern reported on both colliding paths, the shipped atomic-sequence fix accepted, a half-fix reported on exactly the path that lost its unique component, a tempfile handle and an inherited unique directory accepted, a wall clock rejected; an undeclared pin reported, a declared one accepted, a scope without an exclusion rejected, a declaration in the enclosing test's doc comment accepted and shown not to leak to the next test; and each pin spelling — hex, decimal, digest string, byte length, named byte count, golden file — seen while algorithm constants, RNG seeds and small cardinality checks are not)
Composed timing PL — P0-seeded holdover ride-through PL(τ)=max(TPL_handover,HPL(τ)); lower-semicontinuous PL(0+)≥PL(0−); K(IR/2) running-max; τ/τ³/τ⁵ phase exponents InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Property tests (monotonicity, no-drop-at-handover) + exponent lint against holdover::coast_phase_variance src/integrity/composed_pl.rs integrity::composed_pl::tests (monotone, P0-floor, K(IR/2), exponents, lower-semicontinuity)
Composed timing PL — LIL a.s. envelope (impossibility + consistency) No finite worst-case holdover (Brownian sup diverges); IR-allocated HPL consistent with Hartman-Wintner envelope as IR→0 InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed-form a.s. envelope √(2Dt·lnln t) identity + HPL-dominance check; Baweja arXiv:2606.24210 impossibility seam src/integrity/lil_envelope.rs integrity::lil_envelope::tests (divergence, threshold, IR-tightening dominance)
Heterogeneous UTC(k) traceability-bias integrity overbound Per-source bias overbound b = (U/k_cov)·Phi^-1(1-tail/2) + ageing, inflating a published Type-B expanded uncertainty to an allocated integrity tail; bridges to tpl_scalar as bias_s InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Independent numpy + stdlib-statistics reproduction of the overbound closed form (InternalConsistency). The BIPM Circular-T [UTC-UTC(USNO)] series is a CITED input only — it is the SAME series already Validated for the R4 holdover-coverage row and is NOT re-validated here; reproducing its values proves nothing about R2. Deep integrity tail is Modelled. 0.30 external comparison, a finding (stays MODELLED): on the BIPM per-laboratory UTC-UTC(k) files (102 laboratories, 105 024 rows with published uncertainties) the overbound b = 2.576 u at the 1e-2 tail is exceeded by 50.8 % of rows (Clopper-Pearson 95 %: 50.4 to 51.1 %) and by more than 1 % at 101 of 102 laboratories. The published u is the uncertainty of the BIPM's determination of UTC-UTC(k), not a bound on the offset, which routinely runs to many times u; the overbound as specified does not bound real UTC(k) traceability bias. 0.30 round 2, an overbound of the realised UTC-UTC(k) offsets trained on 2015-2022 and tested on 2023-2026 BIPM Circular T data (pre-registered a212810e, pooled exceedance at most 1e-2), a finding (stays MODELLED): the pooled exceedance is 0.0333 (694 of 20 826 rows over 82 laboratories; 0.0127 without the 430 rows that have no bound by rule). D9 round 3, a pooled hierarchical ageing bound (utck_bound), pre-registered 698f3842 and scored prospectively on Circular T issues from 465: not yet run (issue 465 was published on 2026-10-12 with about 285 test values; the pre-registered 1000-value rule needs issues to about 468, and the run needs the archived 2026-09-30 per-laboratory files, since BIPM has since rewritten 87 of the 113) src/integrity/hetero_budget.rs integrity::hetero_budget::tests + tests/hetero_budget_reference.rs; tests/hetero_budget_utc_k_oracle.rs::overbound_exceedance_on_real_utc_k_finding (data-gated: skips with a message when the BIPM series is absent); tests/hetero_budget_utc_k_realised_overbound_oracle.rs::realised_offset_overbound_finding; tests/utck_bound_prospective_oracle.rs (D9 round 3, prospective, not yet run: Circular T 465 appeared on 2026-10-12, and the pre-registered 1000-value rule needs issues to about 468)
Correlated traceability-bias cross-covariance (common-mode-unsafe allocation) N×N bias cross-covariance with rho·b_i·b_j off-diagonals for sources sharing a UTC(k) realizer; PROVEN correlated_fused_bias >= independent_fused_bias (naive independent allocation under-bounds the fused bias -> optimistic -> unsafe) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Independent numpy reproduction of the cross-covariance and the correlated-vs-independent fused bias inequality (InternalConsistency). Representative source set; Modelled scenario. src/integrity/hetero_budget.rs integrity::hetero_budget::tests (correlated_fused_bias_dominates_independent_when_correlated, rho_one_single_realizer_recovers_linear_sum) + tests/hetero_budget_reference.rs
Common-mode consistency statistic (separation-blind shared-reference fault) Score statistic (1^T Omega^-1 r)^2/(1^T Omega^-1 1) ~ chi^2_1 for a common-mode shift that solution separation (contrasts orthogonal to 1) cannot see; a common-mode shift inflates it while pairwise separations stay flat InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Independent numpy reproduction of the statistic + property test that a common-mode injection inflates it (InternalConsistency). Modelled scenario. 0.30 round 2 (pre-registered 47c45647), blocked (stays MODELLED): numpy 2.3.5 LAPACK gesv reproduces the statistic value on 261 committed cases (within 3.5e-15 well-conditioned, 1.2e-9 at condition up to 6.1e7); the chi-square(1) null law is a cited theorem and the flat pairwise separations an identity with no engine output to compare, so the scoping awaits an owner decision src/integrity/gls_commonmode.rs integrity::gls_commonmode::tests (common_mode_shift_inflates_statistic_but_not_contrasts, post_fit_common_mode_statistic_is_zero) + tests/gls_reference.rs; tests/gls_common_mode_statistic_numpy_oracle.rs::common_mode_statistic_matches_numpy_lapack
Lunar datum null-space classification (LLR rank-additivity + libration defect-lift) Classification of the internal-ranging datum problem: a single range observation contributes rank 1 (6-dimensional null space); the origin-X and scale pair is near-null and physical DE440 libration lifts the defect to zero while the pair stays near-degenerate InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Engine-reproduced geometric structure plus the closed-form 2x2 Schur identity; consistent in STRUCTURE with Sosnica et al. 2025 (arXiv:2510.15484), whose reported magnitudes are NOT reproduced here. The classification is structural; the correlation/CRLB magnitudes under real geometry are MODELLED (reflector coordinates and orientation held fixed). 0.30 external comparison, a finding (stays MODELLED): against Sosnica et al. 2025, the range-Fisher origin-scale correlation (-0.993 / -0.988) is within 0.05 of the published -0.97, but on the paper's own five-reflector geometry the equal-weight 7-parameter Helmert correlation is -0.78 (the published value rests on per-reflector errors the paper does not print), and the origin CRLB (0.6 to 1.2 mm at 3 mm range noise) is 96 to 98 % below the paper's 3.07 cm against a 20 % tolerance. Magnitudes not reproduced lunar_identifiability, lunar_datum tests/lunar_datum_identifiability_reference.rs (single_internal_range_row_has_six_dim_datum_null_space; extending_the_librating_arc_lifts_the_origin_scale_degeneracy); tests/lunar_datum_sosnica_oracle.rs::origin_scale_correlation_and_crlb_disagree_with_the_published_geometry
Multi-technique lunar datum information (LLR + lunar VLBI + orbiter range) Datum-Jacobian rows for Earth-reflector LLR range, two-station lunar-VLBI differential delay, and orbiter-to-beacon range over the 7-parameter datum, combined into one consistently-preconditioned Fisher; demonstrates that off-radial (orbiter / depth-diverse) tracking breaks the origin-X to scale degeneracy where transverse VLBI helps only indirectly InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Analytic-vs-finite-difference cross-checks of each technique's partials (internal); the improvement DIRECTION is a geometric fact. Beacon locations, schedules and noise are MODELLED/representative (see tests/fixtures/llr_geometry/NOTICE.md). lunar_datum, lunar_identifiability lunar_datum::tests (LLR/VLBI/orbiter analytic partials vs finite difference); lunar_identifiability::tests (adding_an_offradial_technique_collapses_the_origin_scale_degeneracy; transverse-vs-radial via crlb_diag)
Lunar LLR datum geometry substrate (principal-axis reflectors, ground stations, analytic range partials) The five near-side retroreflector arrays in PA body-frame metres and the LLR ground stations in geodetic coordinates; reflector body-to-inertial placement through the DE440 PA orientation; analytic partials of Earth-to-reflector range with respect to the 4-parameter datum; and the LLR-only Fisher matrix exhibiting the lunocentre-X to scale degeneracy that motivates the 7-parameter analysis ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — The computation is checked internally: every analytic partial against a finite difference, and the zero-datum case against the nominal range. The CATALOGUE is checked externally and independently - the DE440 principal-axis coordinates (Park et al. 2021, tests/fixtures/llr_geometry/de440_retroreflectors_pa.csv) are cross-checked against Table 6 of the DE430 surface-coordinates memorandum (tests/fixtures/lunar_llr/de430_retroreflectors_pa.csv, machine-extracted from a SHA-256-verified PDF by tests/fixtures/lunar_llr/generate_de430_retroreflectors_pa.py) and agree to 1.12 m, while the mean-Earth realisation of the same five arrays differs by 672 to 871 m. The DEGENERACY STRUCTURE is checked against a published result: Sosnica et al. 2025, 'Definition and Realization of the International Lunar Reference Frame', arXiv:2510.15484, which reports for the lunar principal-axis frame a lunocentre-X to scale correlation coefficient of r = -0.97, and that LLR fails to reach the actual centre of mass of the Moon with an accuracy better than 12 cm because of that correlation. This module recovers the same structure (|corr(t_x, scale)| between 0.9 and 0.9999, datum defect <= 1) from an LLR-only Fisher design. The corroboration is across ephemerides, not a round trip: the paper combines INPOP21a, DE430 and EPM2021, whereas this module is driven by DE440 libration. What is NOT reproduced is magnitude - the correlation here is about -0.988 against their -0.97, and the 4-parameter CRLB is sub-millimetre against their 12 cm achieved floor, because orientation and reflector coordinates are held fixed here and solved there. Geometry and degeneracy structure only; no accuracy claim about a solved datum. 0.30 external comparison: the measured-range parts of this module (reflectors(), stations_itrf(), the DE440 PA placement and the barycentric light time llr_bcrs_one_way_m) are validated in their own row, LLR measured-range model, against 192 ILRS normal points (RMS 2.81 m against 10 m). This row stays MODELLED because the measured comparison does not exercise the rest of its claim. The geodetic station catalogue stations() rounds APOLLO to 0.001 deg; with a geocentric light time it gives 22.7 m on the same points (test reflector_ranges_against_ilrs_normal_points; 96 m with the earlier element-wise orientation interpolation). The analytic range partials and the LLR-only Fisher are computed through llr_range_m and reflector_inertial with the analytic Moon series (ephem::moon_position, about 0.3 deg from the GCRS) and no light time lunar_llr_geometry lunar_llr_geometry::tests (reflector_and_station_catalogs_are_well_formed, analytic_partials_match_finite_difference, llr_one_way_range_is_earth_moon_scale, zero_datum_reproduces_nominal_range, llr_only_fisher_shows_strong_com_x_scale_degeneracy); tests/lunar_pa_frame_realisation_guard.rs; tests/llr_datum_degeneracy_reference.rs; tests/lunar_llr_geometry_range_oracle.rs::reflector_ranges_against_ilrs_normal_points
Range to clock-offset degeneracy in one-way lunar ranging, and the geometric-diversity design law The per-node radial-range to receiver-clock-offset degeneracy is exact at 1 m to 3.336 ns (one over c). The {scale, offset} Schur-complement marginal (coupled_marginal_fisher) shows that in a geometrically diverse network two-way ranging lifts the marginal by about the same factor as an equal count of additional one-way data, while in the idealised single-node regime the two-way lift is orders of magnitude larger. The design law that follows: geometric diversity, not two-way ranging as such, is what separates lunar frame scale from timescale offset in one-way ranging; a two-way or external time tie is required only in the low-diversity or single-user regime. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Schur-complement marginal Fisher of the coupled information matrix, in closed-form linear algebra, checked against the two limiting regimes it predicts. The 1 m to 3.336 ns equivalence is the definition of the metre via c and is not an empirical result. The observation networks are representative Modelled geometry, so the design law is a statement about the geometry presented to it and carries no claim about any fielded lunar network. lunar_gauge lunar_gauge::tests (coupled_marginal_well_posed_network_is_psd, coupled_marginal_twoway_equals_more_oneway_in_diverse_network, coupled_marginal_twoway_lift_three_orders, oneway_range_row_has_correct_temporal_entries, twoway_range_row_has_zero_at_offset_and_rate, time_tie_row_equals_pure_offset_vector, rate_tie_row_has_correct_structure)
Representative multi-technique measurement menu and the additive Fisher combination rule MeasurementBlock holds one candidate measurement campaign as a 7x7 Fisher information contribution plus a scalar relative cost; block_from_rows builds one from raw datum-Jacobian rows so every block is preconditioned identically through lunar_identifiability::assemble_multi_info; combine sums the information of a chosen subset, which is the correct rule because Fisher information is additive across independent measurements; representative_lunar_menu supplies a deterministic four-block menu (LLR, a transverse VLBI limb beacon, a near-side orbiter and a far-side orbiter). The budget-constrained design optimiser that consumes this menu is not part of this crate. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Additivity of Fisher information across independent measurements is a closed-form property, checked here against an independently written element-wise sum and against the order-invariance and monotonicity that follow from it. NOTE ON EVIDENCE: the combiner previously had no test at all, and the one test in the module summed the two information matrices inline instead of calling it, so a broken combiner would have left the module green; the test now goes through combine and fails when it is mutated. All beacon locations, orbiter geometry, per-technique precisions and relative costs are representative choices rather than mission values (see tests/fixtures/llr_geometry/NOTICE.md), so every degeneracy metric and CRLB figure reached through this menu inherits the Modelled status of lunar_identifiability::decompose. lunar_techniques lunar_techniques::tests (combine_is_additive_order_independent_and_empty_is_zero - empty selection gives the zero matrix, a single selection is the identity, a pair equals an independently written element-wise sum, and the result is invariant under selection order; adding_a_block_never_reduces_the_degeneracy_metric - monotonicity under added information; radial_diversity_beats_transverse_for_breaking_the_degeneracy - the far-side orbiter block raises the degeneracy metric more than the transverse VLBI block)
Cross-provider consistency tolerance for a mixed-provider user consistency_tolerance: inverts a user position budget to a per-parameter inter-provider Helmert agreement requirement (origin/scale/rotation) at a reference lever arm, optionally inflated by the P1 single-provider realization CRLB InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Worst-case triangle bound on the Helmert point-Jacobian action (closed form) lunar_interop_budget lunar_interop_budget::tests (monotonicity in budget; RSS budget reduction under a per-provider CRLB; worked rotation tolerance at the lunar lever arm; binding-term = rotation)
Multi-provider lunar interoperability error budget and frame-vs-ephemeris design law interop_budget: reducible (common frame-tie) vs irreducible (dynamics) split under PerProvider / CommonFrameTie / CommonEphemeris conventions, with the irreducible-fraction design-law metric (~0.69 on real DE440/INPOP/EPM: a common frame tag alone leaves the dominant floor) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — RMS aggregation of the Validated per-pair splits under each convention (closed form) lunar_interop_budget lunar_interop_budget::tests (CommonEphemeris zeroes the budget; CommonFrameTie < PerProvider; irreducible_fraction > 0.5 on the real splits; convention ordering)
Byzantine block-spark detect/identify bound on the autonomous per-node lunar network (T3) byzantine_bound instantiates the secure-state-estimation coding / sparse-observability bound on the per-node network geometry: a Byzantine peer injects an arbitrary linear combination of the measurements it participates in, and the network DETECTS any coalition of ≤ f = block_spark − 1 peers and uniquely IDENTIFIES any coalition of ≤ ⌊(block_spark − 1)/2⌋, where block_spark is the smallest peer-coalition whose stacked effective signatures P⊥·B_T are column-rank-deficient. Peer detectability is FULL COLUMN RANK of P⊥·B_j (a nonzero-but-rank-deficient block is a nonzero attack that lands in range(G) and leaves no residual), not merely P⊥·B_j ≠ 0 InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Geometric instantiation of the block-wise spark / secure-state-estimation bound (Fawzi–Tabuada–Diggavi 2014; Shoukry–Tabuada 2016; block-wise spark of Donoho–Elad 2003; Candès–Tao 2005) — NOT the Lamport–Shostak–Pease 3f+1 consensus threshold ('Byzantine' names the arbitrary/colluding fault MODEL only). The specific tolerated-fault count is a Modelled property of the representative network geometry, checked for self-consistency by hand-constructed analytic cases and the count formulas lunar_faultobs lunar_faultobs::tests — byzantine_c3_rank_deficient_but_nonzero_is_undetectable (nonzero yet rank-deficient block ⇒ block_spark 1, f_detect 0; independent columns ⇒ block_spark 2, f_detect 1), byzantine_real_network_uniform_bias_is_clock_offset (a peer owning all of a node's measurements = a clock-offset error ∈ range(G), undetectable, with a clear Gram spectral gap), byzantine_redundant_net_identifies_at_least_one (six independent single-measurement peers ⇒ block_spark 7, f_identify 3), byzantine_analytic_spark_identity_projector + byzantine_detect_identify_relations (P⊥ = I hand cases pin f_detect = block_spark − 1, f_identify = ⌊(block_spark − 1)/2⌋)
Autonomous-holdover temporal-gauge floor for the self-referential lunar constellation (T4) holdover_floor establishes that in an ensemble of autonomous nodes connected only by inter-node measurements the common clock rate (δα_j += 1 ∀j) is an ensemble-time free parameter lying in N(GᵀWG): no amount of additional inter-node ranging can observe it (rate_in_gauge = true, temporal_gauge_dim = 2 with the common offset). This is the genuine holdover floor — the temporal analog of the rigid-frame position gauge. Adding one external absolute-rate tie (a direct link to an off-network reference) expels the common rate from the null space (rate_in_gauge = false, temporal_gauge_dim = 1), proving the floor is a real gauge, not an oscillator-model artefact InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Ensemble-time free-parameter argument (Percival 1978; Lewandowski & Thomas 1991) instantiated on the representative real-DE440 per-node network: a relative-residual null test of the analytic common-rate generator against GᵀWG, with the tie-broken contrast distinguishing the genuine gauge from an oscillator-model artefact. Representative Modelled geometry, not a certified timing budget lunar_faultobs lunar_faultobs::tests — holdover_floor_self_ref_and_anchored (self-referential net: the common rate lies in N(GᵀWG), temporal_gauge_dim 2; after one external rate-tie row: rate expelled from the gauge, temporal_gauge_dim 1 with the common offset surviving)
Provider common/differential split, one-rank-deficiency unification, and protection-gap slope (T5 / §0 / g7) Three facets of the single decomposition ℝ^{state_dim} = N(GᵀWG) ⊕ range(GᵀWG) with the 8-dim datum⊕timescale gauge as N(G) and the state_dim − 8 = 32 observable directions as range(G): (T5) provider_mismatch_split classifies a common multi-provider bias (∈ range(G)) as UNDETECTABLE — needing an external tie — and a differential bias (∉ range(G)) as self-monitored / DETECTABLE; (§0) the unification is that the SAME range(G) blind subspace governs the undetectable fault class, so the datum gauge N(G) and the fault-blind subspace range(G) are one geometry, not two; (g7) slope returns the Brown protection-gap slope ‖Π_obs Δx̂‖ / ‖P⊥b‖_W → ∞ for a fault b ∈ range(G) (estimator corrupted with zero parity) and finite for a detectable fault InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed-form parity-projector / pseudo-inverse algebra on the representative real-DE440 per-node network: the common/differential split, the N(G) ⊕ range(G) unification and the Brown (1992) protection-gap slope all follow from range annihilation P⊥·G = 0. Representative Modelled geometry, not a certified protection level lunar_faultobs lunar_faultobs::tests — provider_mismatch_split_common_undetectable_differential_detectable (common bias undetectable, differential detectable), slope_infinity_in_range_finite_detectable (g7: slope ∞ for b ∈ range(G), finite for b ∉ range(G)), pernode_rank_is_state_dim_minus_eight (§0: rank(GᵀWG) = state_dim − 8, the 8-dim gauge is the entire null space with a >1e6 spectral gap)
ITU-T telecom synchronisation masks with PASS/FAIL and margin Transcribed limits of ITU-T G.8272 (07/2025) PRTC-A/B, G.8272.1 (2024) Amd. 1 (07/2025) ePRTC locked and ePRTC-A holdover (including the Table 3 time-error envelope), G.8273.2 (2023) Amd. 2 (11/2025) T-BC/T-TSC classes A-D and G.8271.1 (2022) Amd. 3 (05/2025) reference point C, each open or closed interval as the table states it, with every 'for further study' entry left out; a verdict and a margin at the binding point per check, and the time to exceed each budget. Runnable as the telecom-timing scenario kind InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Transcription of the named Recommendations (freely downloadable from itu.int), each limit carrying its table or clause, listed with every unconfirmed or unimplemented item in docs/TELECOM-TIMING.md; the breakpoint-continuity identities the tables imply are checked in the tests. A standards transcription with internal consistency checks, not a conformance test and not an external validation. 0.30 round 2 (pre-registered 0f8c3f11), blocked (stays MODELLED): the ten mask values and thirteen ePRTC-A holdover values the Recommendations print as worked numbers (G.8272 Figs. 1-2, G.8272.1 Amd.1 cl. 8.2.1 and Figs. V.1-V.3, G.8271.1 Amd.3 Figs. 7-2 to 7-4) are reproduced inside half a printed unit, most of them table constants or breakpoints; G.8271.1 Fig. 7-2 labels 200 ns at 1.3 s against its own Table 7-1 (197.5 ns). The G.8273.2 class A-D limits have no printed worked value, and the G.8272.1 ePRTC locked breakpoint labels (on solid construction lines) were excluded by the pre-registered selection rule, so those remain transcriptions telecom_timing (MASKS, eprtc_a_holdover_limit_ns, check_curve, check_mask) telecom_timing::tests (mask_boundaries_follow_the_tables_exactly — open and closed ends, the τ = 400 s gap of G.8271.1 Table 7-3, continuity at every breakpoint the tables imply; a_curve_exactly_on_the_limit_passes_and_just_above_fails; eprtc_a_holdover_envelope_follows_table_3; a_coarse_record_is_not_evaluated_against_a_filtered_mask); tests/telecom_timing_reference.rs (telecom_timing_kind_round_trips_through_the_dispatch); tests/telecom_masks_itu_printed_values.rs (mask_values_match_the_numbers_the_recommendations_print; figure_7_2_label_at_1_3_s_is_not_its_own_table_value)
ITU-T frequency-synchronisation wander-generation masks (G.811, G.812, G.8262, G.8262.1) Seven constant-temperature MTIE and TDEV wander-generation masks for the telecom-timing kind: G.811 (09/1997) PRC (autonomous), G.812 (06/2004) Types I, II and III, G.8262 (10/2024) EEC Options 1 and 2 and G.8262.1 (11/2025) eEEC (locked mode), including the power-law pieces the tables write (8 τ^0.5 and the like), each interval open or closed as printed, measured through the 10 Hz filter the clauses state (taken as applied before sampling); the reference scenario scenarios/telecom-synce-eec.toml sets a free-running OCXO against the three EEC masks. Not implemented: the variable-temperature allowances, holdover, transients, jitter and the G.811 frequency accuracy InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Transcription of the named Recommendations (downloaded from itu.int on 2026-10-13), every row re-read against the text, with the breakpoint continuity the printed coefficients imply bounded in the tests (for example 40 · 10^0.4 = 100.48 ns against the 100 ns plateau of G.812 Table 4). A standards transcription with internal consistency checks, not a conformance test and not an external validation. G.812 (06/2004) is listed as superseded by a pre-published 08/2026 edition and G.811 has an Amd. 1 (04/2016); neither could be read, so neither is checked. The free-running OCXO scenario overstates the oscillator's contribution at observation intervals long against a loop's time constant; it says nothing about any equipment clock telecom_timing (MASKS, Segment::tau_exponent, MeasurementFilter::LowPass10HzAtSource, MaskCondition::Autonomous) telecom_timing::tests (g811_prc_masks_follow_clause_6_1; g812_masks_follow_tables_3_4_6_and_7; g8262_masks_follow_tables_1_3_4_and_5; g8262_1_eeec_masks_follow_tables_1_and_3; a_linear_piece_is_evaluated_without_powf; wander_masks_pass_a_quiet_white_fm_flicker_series; wander_masks_fail_the_same_series_scaled_up)
Clock-log formats (RINEX clock, TimeLab ASCII, TAPR TICC) read to a normalised phase series clock_log::read_input: one parser layer that turns a RINEX clock file (AS/AR records of one named clock, versions 2 and 3.00 to 3.04), a TimeLab-style ASCII phase or frequency log, or a TAPR TICC timestamp or interval log into a uniform phase grid, with tau0 stated, from a header, or the median spacing, every gap, off-grid reading and duplicate counted, and a refuse, longest-run or linear gap policy; wired opt-in into the telecom-timing series ([series.clock_log], adding a clock_log block) and the clock kind ([clock_log], adding a measured block with ADEV, TDEV and MTIE, the table's SHA-256 and the phase SHA-256; runs = 1). Without the table both kinds are byte-identical InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Pre-registered in tests/fixtures/clock_log/PREREGISTRATION.md (committed alone, 05bb1d17, before the fixture existed); recorded in RESULTS.md. Three seeded synthetic logs, one per format (a TICC gap of three epochs, a RINEX second clock to ignore), read back by an independent reader written from docs/CLOCK-LOG-FORMATS.md by the same author: grid, gap and fill counts equal and the largest phase difference 0 s (bar 1e-13 s). allantools 2024.6 oadev, tdev and mtie on that phase agree within a relative 2.5e-14 (bar 1e-10) at every averaging factor it evaluates; it does not evaluate MTIE over the whole record, which the engine reports, so that one point per log has no oracle value and the bar as worded is not met there. MODELLED: synthetic logs, and the reader oracle shares the author; real TimeLab, TICC and RINEX clock files from instruments were not compared clock_log (read_input, MeasuredPhaseReport, MEASURED_UNITS, TELECOM_LOG_UNITS); telecom_timing (SeriesInput::clock_log); api (clock kind [clock_log]) clock_log::tests (hand-written logs per format: headers, separators, units, frequency integration, TICC channels and modes, gaps and policies, refusals); tests/clock_log_allantools.rs (the pre-registered comparison: b1_each_log_reads_to_the_reference_phase; b2_adev_tdev_and_mtie_agree_with_allantools; b3_a_telecom_series_read_from_a_log_equals_the_same_samples; b3_the_clock_kind_measured_block_is_opt_in)
Clock-log formats linuxptp (ptp4l, phc2sys, ts2phc) and chrony (tracking, statistics) read to a normalised phase series clock_log::read_input with the formats ptp4l, phc2sys, ts2phc, chrony-tracking and chrony-statistics: the logged offset of a linuxptp servo line (ns, the line's own bracketed time stamp, readings before the servo first reports s2 left out and counted) or of a chrony tracking or statistics log (s, by column position, UTC date and time) becomes a uniform phase grid through the same gap policies as the other formats; a source selector (clock) names one of several interfaces, clocks or addresses; the logs feed the telecom-timing series, the clock kind and the holdover-test kind InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Fixtures written for Kshana from the public line layouts of the daemons, with made-up values (NOTICE.md in the fixture folder); no log from a real installation was read and no oracle compares the parse with another reader, so a layout that differs between daemon versions can still be refused or misread. The estimators fed by the phase series are the ones validated against allantools in the rows above clock_log (parse_linuxptp, parse_chrony, grid_timed_offsets) clock_log::tests (ptp4l_reads_the_locked_offsets_in_ns; linuxptp_reads_only_the_named_program; ts2phc_gap_is_refused_or_filled; linuxptp_reads_syslog_prefixed_lines_and_picks_an_interface; linuxptp_refuses_a_servo_that_never_locks_and_backwards_stamps; chrony_tracking_reads_the_local_offset_in_seconds; chrony_statistics_needs_a_source_when_there_are_two; chrony_columns_of_the_other_log_are_not_read; clock_selector_is_refused_for_timelab_and_ticc_only) on the fixtures in tests/fixtures/clock_log/linuxptp_chrony/
Holdover test scored from an operator-supplied time-error record The holdover-test kind: a time-error record (a linuxptp, chrony, TICC, TimeLab or RINEX clock log, or time_s,time_error_ns pairs) is split at the two times the operator states for GNSS removal and restoration into a baseline, a holdover and a recovery step; the baseline is measured against the ITU-T masks written for a locked clock and the holdover against those written for holdover or an autonomous clock, the ePRTC-A holdover envelope and the time-error budgets; the holdover reports the least-squares frequency offset the system held, and the recovery whether and when |TE| came inside a stated band and stayed for a stated dwell, with the peak and the largest step. Every limit is the one the telecom-timing kind transcribes; the two times are the operator's statement and are not verified InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Hand computation on records built from formulas whose slope, step, extremum and recovery time are known before the run (the tests state them), and the masks, envelope and budgets of the telecom-timing rows above. No laboratory measurement of a real holdover was scored and no external oracle was compared, so the kind makes no claim about any clock or system; a timing-lab partner is needed before any per-clock-class figure could be promoted holdover_test (HoldoverTestScenario, recovery, linear_fit); telecom_timing (check_mask, check_envelope, budget_results) holdover_test::tests (the_record_is_split_at_the_stated_times; holdover_figures_match_a_hand_computation; recovery_is_timed_from_the_restoration; masks_are_measured_on_the_step_their_condition_names; a_record_with_no_baseline_says_so; bad_inputs_are_refused_with_the_reason; the_report_carries_the_label_the_units_and_no_conformance_word; a_ptp4l_log_is_scored_end_to_end)
GNSS signal availability in the Space Service Volume and beyond, compared with the ICG SSV booklet The gnss-ssv kind's availability sweeps: per constellation (GPS, GLONASS, Galileo, BDS, QZSS, NavIC) and combined, the share of (user, epoch) pairs with at least one and at least four signals and the longest outage, for a user on a sphere (the booklet's 2,562-point global shell, 14 days at 1 minute) or on a trajectory (GEO, HEO, lunar transfer), from the Keplerian orbits of the booklet's annex C, a constant minimum radiated power inside the reference off-boresight angle, Earth blockage by the sphere plus 50 km and a C/N0 threshold; user antennas from the booklet's table B10 ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — The ICG Space Service Volume booklet (UN OOSA ST/SPACE/75, 2018), itself a simulation, compared under a pre-registration committed before the run (xval/gnss-ssv/PREREGISTRATION.md; results in xval/gnss-ssv/RESULTS.md, pinned by tests/ssv_booklet_results.rs, misses included). Run 1 on the pre-registered reading: the minimum-radiated-power constants and the lunar bar agree (S0, S6 met); the upper and lower SSV, RF-threshold, GEO and HEO bars are NOT MET, almost all through GLONASS, for which the booklet gives 20 and 28 degrees in tables B2 and B6 and 26 and 34 degrees in table 4.2. A diagnostic variant with table 4.2's angles agrees in every cell of the upper SSV, lower SSV and the six GEO missions (it does not replace run 1; RF, HEO and lunar cells still miss). The measured GPS L1 panel patterns are not reproduced by the parametric stand-in (RMS 6 to 9 dB against a 3 dB bar). Agreement shows the booklet's stated method is reproduced, not that GNSS signals behave so ssv (constellations, geom, sweep, pattern, check) ssv::geom::tests (the_grid_has_the_booklets_2562_points_on_the_unit_sphere; the_interval_form_equals_the_general_predicate; a_user_behind_the_earth_is_blocked_and_one_beside_the_limb_is_not); ssv::sweep::tests (a_small_shell_run_is_internally_consistent; pdop_of_a_regular_tetrahedron_like_set_is_finite_and_a_flat_set_is_not); ssv::pattern::tests (table_b10_antenna_reads_as_gain_against_angle_from_the_boresight)
Limb-ray ionosphere, plasmasphere and atmosphere effects on grazing GNSS signals, and the weak-signal receiver design, in the gnss-ssv kind A Chapman ionosphere, a Gallagher-type plasmasphere and a neutral atmosphere (refractivity bending, oxygen absorption, defocusing) integrated along the straight ray between transmitter and user: slant total electron content, its plasmaspheric part, excess delay, tangent altitude and the loss on grazing links; and a weak-signal receiver design (coherent and non-coherent integration, data-bit limit, aiding, Doppler search) that sets the C/N0 threshold from the acquisition and tracking-loop models InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed forms and published magnitudes in the tests (a Chapman layer's peak and the bending of the surface limb, a few TECU of plasmasphere on a GPS-to-GEO ray); the receiver design reuses the acquisition and tracking-loop models and their tests. No measured limb-sounding or weak-signal reception data is compared with it ssv (limb, weak) ssv::limb::tests (the_chapman_layer_peaks_at_its_height_with_its_density; the_surface_limb_bends_about_one_and_a_third_degrees; plasmaspheric_tec_is_a_few_tecu_for_an_equatorial_gps_to_geo_ray); ssv::weak::tests (longer_integration_lowers_the_acquisition_threshold; aiding_narrows_the_search_and_the_loop; a_conventional_receiver_is_far_above_the_ssv_signal_levels); ssv::scenario::tests (the_limb_medium_adds_statistics_and_can_cost_signals; a_weak_signal_receiver_replaces_the_fixed_threshold)
Onboard GNSS navigation filter for high-orbit and lunar-transfer spacecraft The gnss-ssv kind's [navigation] mode: a nine-state extended Kalman filter (position, velocity, receiver clock bias and drift, a solar-radiation-pressure scale) on pseudoranges whose availability, noise and C/N0 come from the same link geometry as the sweeps; truth is integrated with J2, Sun and Moon third-body and radiation pressure with shadow, the filter models J2 and the third bodies and estimates the radiation pressure; reports position and velocity errors inside and above the GNSS orbits, the longest measurement gap and the mean NEES InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Simulated truth against the filter's own estimate (a consistent filter's mean normalised estimation error squared is about 3 for the position) and determinism for a fixed seed. No flight or recorded high-orbit GNSS data is compared; the Sun and Moon are low-precision circular stand-ins ssv::nav (run_nav, Ekf) ssv::nav::tests (the_filter_converges_where_signals_are_plentiful_and_is_deterministic; the_covariance_is_consistent_with_the_error; without_signals_the_filter_coasts_and_the_gap_is_reported); ssv::scenario::tests (navigation_and_formation_run_and_report)
Relative navigation of a multi-spacecraft formation in a highly elliptical orbit from GNSS The gnss-ssv kind's [formation] mode: a chief and deputies each run the absolute filter; the deputy's position relative to the chief is estimated by subtracting the absolute estimates and by a relative filter on single-differenced pseudoranges of the signals both craft track, with the relative dynamics the difference of two nonlinear trajectories InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — The same simulated truth as the absolute filter: the relative filter's error against the true relative state, and the check that it does at least as well as subtracting two independent absolute fixes. No flight formation data is compared ssv::formation (run_formation, RelEkf) ssv::formation::tests (differencing_beats_subtracting_absolute_estimates_and_is_deterministic); ssv::scenario::tests (navigation_and_formation_run_and_report; formation_needs_navigation_and_one_mode_only)
Navigation and timing error budget of a chain of mission phases from launch to entry (mission-thread) The mission-thread kind: a document of phases, each one of eight registered kinds, run in order with the 6x6 covariance, the clock and the frame handed on under a stated rule (carry; inflate, white acceleration noise over a stated gap on a straight-line model; reacquire, dead reckoning then the source floor, never below it, never a reset); frame conversions GCRF, MCI and MCMF and timescale conversions through TT, each its own budget row, with the Moon's state from an optional DE440 kernel cut and the analytic series as the stated fallback; the margin against a stated requirement, the weakest link, the events and a timeline figure. Every number is a stated input or a model of one InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Hand calculations in the tests (the straight-line covariance growth, the mean sidereal rotation, the secular lunar clock rate) and, for the Moon's state only, the committed DE440 kernel cuts against pinned JPL Horizons values (worst 2.6 m and 7e-6 m/s). No mission data is compared with the chain; its phases are rows of their own. The document is a stated chain with ILLUSTRATIVE inputs, public sources only and no agency endorsement mission_thread (scenario, handover, conversions, budget, phase) mission_thread::scenario::tests::a_thread_runs_hands_over_converts_and_names_the_weakest_link; mission_thread::scenario::tests::bad_documents_fail_with_the_reason; mission_thread::handover::tests::inflate_never_shrinks_a_sigma_and_matches_the_hand_calculation; mission_thread::handover::tests::reacquire_sets_an_axis_to_the_floor_only_where_the_floor_is_smaller; mission_thread::conversions::tests::mci_mcmf_round_trip_returns_the_state_and_the_covariance; mission_thread::conversions::tests::tt_to_ltc_shifts_bias_and_drift_by_the_secular_rate_and_back; mission_thread::conversions::tests::the_committed_kernel_cuts_agree_with_pinned_horizons_values; tests/field_units_global.rs (the report's units block)
Launch and ascent to a parking orbit with GNSS acquisition and fade (launch-ascent) The launch-ascent phase: a constant-velocity position and velocity covariance with white acceleration noise (the dead-reckoning grade), a GNSS fix of stated accuracy applied after the acquisition time and outside stated fades, a bias-and-drift clock disciplined by the same fixes, and the parking-orbit insertion state InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — The Riccati steady state and the hand calculation of the prediction in the tests. Nothing here models a launch vehicle or a receiver; every number is a stated input mission_thread::earth::launch (LaunchAscent) mission_thread::earth::launch::tests::with_gnss_the_sigma_settles_near_the_fix_and_an_outage_lets_it_grow; mission_thread::earth::launch::tests::before_acquisition_the_sigma_only_grows_and_a_longer_acquisition_is_worse; mission_thread::earth::launch::tests::a_phase_that_does_not_list_gnss_never_uses_it; mission_thread::earth::launch::tests::bad_models_and_entries_are_refused; mission_thread::earth::filter::tests::repeated_updates_reach_the_riccati_steady_state
Relative navigation to the docking envelope in low Earth orbit over sensor legs (leo-rendezvous) The leo-rendezvous phase: the relative state in the target's LVLH axes with the closed-form Clohessy-Wiltshire transition, a 6x6 Kalman covariance with white acceleration noise and position updates whose variance is the sensor's at the current range, over legs of a stated sensor (ILLUSTRATIVE optical camera, lidar and radio-ranging forms); the docking window is the time from which the relative sigma stays inside the capture envelope to the end of the phase. The chaser's absolute covariance is handed on unchanged and a row says so InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — A one-axis hand calculation of the predict and update in the test; the Clohessy-Wiltshire transition is the one cw_dynamics checks against an independent numerical integration. The sensors are ILLUSTRATIVE and no real rendezvous is compared mission_thread::earth::rendezvous (LeoRendezvous); cw_dynamics; mission_thread::sensors mission_thread::earth::rendezvous::tests::the_relative_sigma_falls_through_the_legs_and_opens_a_docking_window; mission_thread::earth::rendezvous::tests::without_relative_sensing_the_sigma_only_grows_and_no_window_opens; mission_thread::earth::rendezvous::tests::the_covariance_recursion_matches_a_one_axis_hand_calculation; mission_thread::earth::rendezvous::tests::bad_models_and_a_duration_mismatch_are_refused; mission_thread::sensors::tests::the_cross_range_error_grows_with_range_and_the_floor_dominates_up_close
Trans-lunar injection and cislunar cruise: propagated mean state and covariance with tracking updates (tli-and-cruise) The tli-and-cruise phase: the mean state by the engine's Cowell propagator (Earth point mass and J2, the Sun and Moon as third bodies, the Moon from the thread's DE440 kernel where it covers the segment and the Sun from the analytic series); the covariance by a forward-difference state-transition matrix of that propagation (the nominal run and six perturbed runs per segment) with white acceleration noise; the TLI burn's size and pointing error; gnss-ssv fixes whose availability and PDOP come from the space-service-volume sweep along an osculating orbit standing in for the arc; range and range-rate tracking along the geocentric direction scaled by the ground-network duty, with the Joseph-form update InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Liouville's theorem (the determinant of the state-transition matrix of the conservative part is one) and a finer difference in the tests; the mean state is compared with a public trajectory in the row below, which it misses. The burn error, the updates and the covariance are not compared with anything mission_thread::earth::tli_cruise (TliCruise); propagator; ssv::sweep mission_thread::earth::tli_cruise::tests::the_stm_is_symplectic_for_the_conservative_part_and_matches_a_finer_difference; mission_thread::earth::tli_cruise::tests::with_no_tracking_the_covariance_is_the_stm_propagation_of_the_entry_and_the_burn; mission_thread::earth::tli_cruise::tests::range_tracking_shrinks_the_line_of_sight_and_leaves_the_plane_of_the_sky; mission_thread::earth::tli_cruise::tests::the_thread_kernel_serves_the_moon_inside_its_window_and_the_series_outside; mission_thread::earth::tli_cruise::tests::gnss_ssv_fixes_are_applied_where_the_sweep_finds_four_signals; mission_thread::earth::tli_cruise::tests::a_phase_that_lists_a_source_the_model_lacks_is_refused_and_unknown_keys_too
Entry interface covariance, corridor probability, peak deceleration and landing footprint (entry) The entry phase: the return coast of tli-and-cruise with no burn, ending at the entry interface; the flight-path angle and its sigma from the full covariance by a finite-difference gradient; the probability that the angle is inside a stated corridor; the peak deceleration at the nominal angle and at both corridor edges from the engine's planar ballistic point-mass entry (skip-out detected) beside the Allen-Eggers closed form; the landing footprint from a stated downrange sensitivity and the interface covariance across the orbit plane. No lift, guidance or heating is modelled InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Hand calculations in the tests (the angle sigma is the perpendicular velocity sigma over the speed; the Gaussian mass in a corridor). The planar entry is the engine's own and the Allen-Eggers form is a closed-form comparison; no flown entry is compared mission_thread::earth::entry (Entry); reentry mission_thread::earth::entry::tests::the_flight_path_angle_and_its_sigma_follow_the_velocity_error_over_the_speed; mission_thread::earth::entry::tests::the_corridor_probability_is_the_gaussian_mass_inside; mission_thread::earth::entry::tests::the_phase_reports_the_interface_the_corridor_the_peaks_and_the_footprint; mission_thread::earth::entry::tests::the_steep_edge_peaks_higher_and_a_limit_below_it_is_flagged; mission_thread::earth::entry::tests::bad_corridors_unknown_keys_and_burn_keys_are_refused
Ground-network coverage and tracking duty for a thread phase ([ground_network] of mission-thread) The ground-network overlay: stations with a minimum elevation, the visibility of the vehicle on a stated geometry (the entry state flown two-body with J2, the Moon's position for the cruise, or a stated duty), station handovers that lose a stated time each, and the resulting duty passed to the phase's ground-tracking update rate; the longest interval with no station in view is a budget row InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Zenith and antipode geometry checks and the expected visibility of a distant target in the tests. No real network, antenna or schedule is modelled mission_thread::earth::ground_network mission_thread::earth::ground_network::tests::a_vehicle_over_a_station_is_seen_and_one_on_the_other_side_of_the_earth_is_not; mission_thread::earth::ground_network::tests::the_moon_is_in_view_of_three_well_spread_stations_most_of_the_time; mission_thread::earth::ground_network::tests::handover_losses_reduce_the_duty_and_never_below_zero; mission_thread::earth::ground_network::tests::a_stated_duty_is_passed_through_and_bad_documents_are_refused; mission_thread::scenario::tests::the_overlay_sets_the_tracking_duty_of_a_phase_that_lists_ground_tracking
Relative navigation to docking in a lunar orbit (lunar-orbit-rendezvous) The lunar-orbit-rendezvous kind and phase: a joint two-vehicle batch Gauss-Newton estimate over the arc (twenty-one parameters: both states and persistent signal-in-space position biases, common and independent), grown over a quarter, a half and the whole arc with step halving, from an absolute fix per vehicle (AFS pilot code-tracking bound, ILLUSTRATIVE relay set) and a crosslink range, under the crate's lunar force model; the mean normalised estimation error squared, the Clohessy-Wiltshire check on a circular orbit and the 6x6 covariance handed on InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Self-consistency under a pre-registration (xval/mission-thread-lunar/PREREGISTRATION.md, results and the estimator history in RESULTS.md): the mean NEES of the relative state is 5.85 to 5.93 against the band 5.2 to 6.8 in four configurations, MET on the fourth estimator design after three sequential-filter designs missed; the truth and the estimator share one force model, so this says nothing about model error. The propagator it shares is compared with LRO and CAPSTONE in a row below lunar_rendezvous (LunarRendezvousScenario); lunar_phase; mission_thread::lunar lunar_rendezvous::tests::b1_mean_nees_is_inside_the_registered_band_in_all_four_configurations; lunar_rendezvous::tests::circular_cw_check_is_within_the_pre_registered_bar; lunar_rendezvous::tests::same_seed_gives_identical_documents; lunar_rendezvous::tests::b6_handover_without_a_measurement_only_propagates; mission_thread::lunar::tests::every_phase_runs_and_returns_a_modelled_outcome; tests/mission_thread_lunar_oracles.rs
Landing-dispersion budget at a lunar polar site (lunar-descent) The lunar-descent kind and phase: a five-state per-axis inertial error model (position, velocity, accelerometer bias, tilt, gyro bias) over a powered descent, aided by AFS fixes (standalone or differential, with the clock-aided three-relay case), a terrain-relative fix (the engine's terrain-nav matcher on synthetic relief, or a Cramer-Rao bound on a LOLA DEM with an aperture-problem rule) and lunar time, with a Monte Carlo touchdown ellipse InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — The closed-form inertial drift, the reused kinds' own results and the calibration of the 3-sigma ellipse (the fraction inside agrees with its expectation) in the tests. No flown or tested landing is compared lunar_landing (LunarLandingScenario); lunar_phase; terrain_nav lunar_landing::tests::b4_with_no_aid_the_landing_error_is_the_closed_form_inertial_drift; lunar_landing::tests::b4_each_aid_reports_exactly_what_the_reused_kind_gives; lunar_landing::tests::b3_ellipse_calibration; lunar_landing::tests::a_plane_gives_no_fix_the_aperture_problem; lunar_landing::tests::a_bowl_matches_the_closed_form_bound; lunar_landing::tests::three_relays_make_the_fix_depend_on_the_clock
Surface positioning and timing availability by site and season at the lunar poles (lunar-surface) The lunar-surface kind and phase: relay availability and PDOP, Earth and Sun visibility and a disciplined surface clock for each site and season, with the terrain skyline of moonlight-service-volume; a single-site run equals that kind's availability and PDOP to the bit ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — Exact equality with the existing kind for one site, and monotonicity checks, in the tests. The relay set is ILLUSTRATIVE and no surface measurement is compared lunar_surface_map (LunarSurfaceMapScenario); lunar_phase lunar_surface_map::tests::b5_equals_the_service_volume_for_a_single_site; lunar_surface_map::tests::b5_equals_the_service_volume_with_the_real_terrain; lunar_surface_map::tests::terrain_never_adds_availability; lunar_surface_map::tests::timing_is_at_least_either_source_and_the_season_moves_the_earth_and_sun; lunar_surface_map::tests::same_inputs_give_identical_documents
Powered ascent from a lunar polar site to an insertion orbit (lunar-ascent) The lunar-ascent kind and phase: the five-state per-axis inertial error model run over a powered ascent with specific force along the path, aided by AFS fixes and lunar time, reporting the insertion position and velocity covariance carried to orbit and the engine-cutoff dispersion (reported, not carried) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — The closed-form inertial drift and monotonicity checks in the tests. No flown ascent is compared lunar_ascent (LunarAscentScenario); lunar_phase lunar_ascent::tests::with_no_aid_the_insertion_error_is_the_closed_form_inertial_drift; lunar_ascent::tests::the_aid_never_hurts_and_the_velocity_is_carried_with_its_correlation; lunar_ascent::tests::a_stale_tt_clock_costs_a_three_relay_fix; lunar_ascent::tests::the_same_inputs_give_identical_documents
The lunar force model propagation against public reconstructed lunar-orbiter and cislunar trajectories The propagator the lunar kinds share (GRAIL GL0660B degree and order 150, Earth and Sun third bodies, relativity, DE440 lunar orientation) compared with the public JPL Horizons trajectories of LRO (24 h, 10 minute samples) and CAPSTONE (one 6.5 day revolution, one hour samples), under bars fixed in a committed file before the run ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — JPL Horizons spacecraft ephemerides for LRO and CAPSTONE, against bars pre-registered in xval/mission-thread-lunar/PREREGISTRATION.md (Amendments 1 to 6). LRO: MET, 33 m largest 3-D difference and 2.4 m RMS radial against 500 m and 60 m. CAPSTONE: NOT MET, a 136.8 km end-position difference against 25 km and a 28.4 km periapsis difference against 10 km, the causes not isolated. The row is Modelled because the CAPSTONE bar is missed and the comparison tests the shared propagator, not any filter, signal or budget lunar_od (LunarForceModel); precise_od; mission_thread_lunar_oracles (example) tests/mission_thread_lunar_oracles.rs::the_stored_numbers_meet_or_miss_the_registered_bars_as_recorded; tests/mission_thread_lunar_oracles.rs::the_fixtures_match_their_recorded_hashes
The cislunar mean-state propagation against the public Artemis I trajectory (tli-and-cruise) The mean-state propagation of the tli-and-cruise phase (Cowell, Earth point mass and J2, the Sun and Moon third bodies, the Moon from a DE440 cut) compared with the public JPL Horizons trajectory of Artemis I over a 72 h coast arc from 2022-11-16 18:00 TDB, at 12 hour epochs, under bars fixed in a committed file before the run ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — JPL Horizons target -1023 (the NASA navigation as-flown post-TLI trajectory), against bars pre-registered in xval/mission-thread/PREREGISTRATION.md (Amendment 1 changes only the request span). NOT MET and asserted as missed: 45.3 km largest position difference against 5 km, and 0.249 m/s velocity difference at 72 h against 0.05 m/s. A diagnostic written after the verdict places the miss in five impulsive velocity steps of 0.09 to 0.22 m/s in the reference (the pre-registered reading that the window held no burn was wrong); over the other 67 hours the model reproduces the next hourly state to a median of 0.38 m. Tests the mean state of one coast arc only: no covariance, filter, update or other phase mission_thread::earth::tli_cruise; propagator; mission_thread_oracle (example) tests/mission_thread_oracle.rs::the_stored_numbers_miss_the_registered_bars_as_recorded; tests/mission_thread_oracle.rs::the_diagnostic_places_the_miss_in_five_impulsive_events_not_in_the_force_model; tests/mission_thread_oracle.rs::the_kernel_cut_and_the_recorded_inputs_match_their_hashes
Cold-atom interferometer error terms: Raman laser-phase noise, wavefront-curvature bias and fringe-ambiguity resolution inertial::cai_error_terms (library functions, not yet reachable from a scenario kind): the Raman-phase weighting function of a square-pulse three-pulse interferometer (Cheinet et al. 2008, Eq. 8) with the white-phase closed form (pi/2)^2 S_phi0/tau_R and a numeric route for any spectrum; the laser frequency noise the retro-reflection delay does not cancel (Le Gouet et al. 2007, Eqs. 9 to 11); the pure-defocus wavefront bias sigma_v^2/R of a thermal cloud and its reduction by a detection radius; the wrong-fringe-index probability erfc(pi/(sqrt(2) s)) for a classical-accelerometer aid and for two interrogation times, and its inverse InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Each closed form against an independent numerical route in the tests (frequency-domain quadrature of the exact transfer function and delay filter, a Monte Carlo over atoms for the wavefront bias, a Monte Carlo over shots for the fringe index) and its limiting cases. One published worked value: Cheinet et al. 2008 (arXiv:physics/0510197, Sec. IV) state that at tau_R = 20 us a white Raman phase noise below -111 dB rad^2/Hz is needed for 1 mrad per shot; the white term alone gives 0.99 mrad (the paper derives the level with its Eq. 17, flicker plus white). Internal consistency and one worked value, not an external validation; higher-order aberrations and any specific laser's noise are not modelled inertial::cai_error_terms inertial::cai_error_terms::tests (raman_transfer_short_pulse_limit_matches_the_acceleration_transfer_function; white_raman_phase_closed_form_matches_quadrature; short_pulse_band_limited_closed_form_matches_quadrature; cheinet_2008_white_phase_noise_requirement_is_reproduced; delay_term_closed_form_matches_exact_filter_quadrature; defocus_phase_is_position_independent_and_tilt_cancels; curvature_bias_monte_carlo_matches_closed_form; curvature_bias_limiting_cases; classical_aided_resolution_monte_carlo_matches_closed_form; multi_t_resolution_monte_carlo_matches_closed_form; ambiguity_limits_and_inverse)
Oscillator holdover presets from public datasheets Four presets — OCXO (Microchip OX-208), rubidium (Microchip 8040C), caesium (Microchip 5071A high-performance tube) and CSAC (Microchip SA.45s) — each carrying its datasheet's Allan-deviation maxima, aging and temperature bound; a non-negative least-squares white + flicker + random-walk frequency-noise fit scaled to envelope every datasheet point, a flicker floor never below the longest-τ figure, linear aging and a sinusoidal temperature term, synthesised as a seeded holdover after a GNSS loss InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — The four named Microchip datasheets (document numbers and URLs in each preset and in docs/TELECOM-TIMING.md) for the input figures; the closed-form aging ramp and the fit's envelope property as internal checks. How the figures become a noise model — the fit, the floor rule, the 30-day month, the linear temperature reading — is a modelling choice; no preset is a measurement of a unit. 0.30 round 2, one-sided bars against measured units (pre-registered 43d19980), a finding (stays MODELLED): the IGS station THU2 Symmetricom 8040C in ESA MGEX final clocks has an Allan deviation 0.35 to 0.87 of the rubidium preset but a holdover error 1.07 to 1.60 of it; the 5071A record sits outside the caesium preset to 1000 s (measurement white phase noise, 30x at 1 s) and in holdover (1.15 to 8.74); the worst 2011 production SA.45s is 1.26x the CSAC preset at 1 s; the OX-208 has no measured record (blocked) telecom_timing (PRESETS, fit_noise, with_flicker_floor, synthesize_holdover); models (ClockModel) telecom_timing::tests (every_preset_carries_a_named_datasheet_and_figures; the_noise_fit_envelopes_every_datasheet_point; pure_aging_matches_its_closed_form — the discrete aging ramp within 0.1 % of (1/2)·D·t² over a day; same_seed_same_series_and_hash_different_seed_different_series); tests/oscillator_presets_measured.rs (caesium_finding_pinned; rubidium_finding_pinned; csac_finding_pinned; ocxo_preset_has_no_measured_record)
Seconds until a free-running clock leaves a time-indexed slot's guard, and the fix cadence that keeps it inside The slot-timing kind: the predicted error E(t) = k·√(σ₀² + σ_x²(t)) + (|y₀| + |c_T·ΔT|)·t + ½|D|t² inverted for the breach, the time left, the resynchronisation interval net of the fix latency and fixes per day, each term itemised with the dominant one named; clocks from the six ClockClass defaults (TCXO, OCXO and RAFS added, each citing one datasheet), the telecom-timing presets, an inline datasheet or a measured record; a breach beyond the source's longest averaging time flagged as extrapolated InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed forms for each term alone and the independent holdover::holdover_seconds root-find; the datasheet figures are the named documents (docs/SLOT-TIMING.md). A class default rests on an assumed red-noise floor and a datasheet source is an envelope of maxima, so neither is a measurement of any unit slot_timing (predicted_error_s, breach_after_sync_s, terms_at, slot_budget, ClockNoise::from_datasheet, SlotTimingScenario); clock_state (ClockClass::Tcxo, Ocxo, Rafs, source) tests/slot_timing_igs_holdout.rs (10 GPS Block IIF satellite clocks, 14 days of IGS final clocks: 8 within the 1.5 bar, G25 and G30 optimistic by up to about 2x, pinned); tests/slot_timing_ocxo_holdout.rs (a measured OCXO: held-out prediction never optimistic, 0.59 to 0.70 of the measured breach; in sample within 0.98 to 1.17; without the fix-frequency term the in-sample prediction is optimistic at every threshold); slot_timing::tests (fix_frequency_uncertainty_alone_is_linear_in_time; reduces_to_the_holdover_inversion — every class against holdover::holdover_seconds to 1e-9; white_fm_with_fix_error_has_its_closed_form; flicker_floor_alone_is_linear_in_time; ageing_alone_is_quadratic_in_time; frequency_offsets_add_in_magnitude; the_error_at_the_breach_is_the_guard; datasheet_fit_envelopes_every_point; datasheet_classes_match_their_presets_at_one_second; a_breach_beyond_the_datasheet_is_flagged_as_extrapolated; the_report_carries_the_result_and_a_unit_for_each_field)
Timing protection level for a receiver in orbit under GNSS spoofing orbital_timing::orbital_timing, reachable as the slot-timing kind's spoofing section: circular-orbit speed and period, the longest time a ground spoofer can reach the satellite per pass, the clock-aided monitor floor and CUSUM detection latency, the conditional protection level (floor plus coast over the latency), the pull a spoofer at a stated maximum ramp rate accumulates before the satellite leaves its footprint or an independent check runs, and whether each ground-contact or crosslink check is independent of one ground spoofer InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Reduction to the existing timing protection level and the circular-orbit and spherical-Earth visibility closed forms. Conditional on detection, one terrestrial spoofer at a stated ramp rate, an overhead pass on a non-rotating Earth; not validated on a spoofed receiver in orbit orbital_timing (orbital_timing, visibility_half_angle_rad, max_pass_s, crosslink_neighbour_is_outside_footprint) orbital_timing::tests (reduces_to_the_terrestrial_tpl — exactly tpl::timing_protection_level_ns when the clock has no flicker, white-phase or random-run term; leo_geometry_matches_its_closed_forms; crosslink_independence_follows_the_footprint; an_independent_check_caps_the_ramp_before_the_pass_ends; a_crosslink_inside_the_footprint_does_not_count; a_ramp_below_the_reference_is_never_detected)
L-band spectrum waterfall with per-band J/S and effective C/N0 under a scripted jammer timeline The spectrum kind: a frequency-by-time grid of the L-band power spectral density (thermal floor k T_sys with T_sys = T_ant + 290 K (F - 1), the signals at their interface-specification minimum received powers, and continuous-wave, narrowband, chirp and matched-noise jammers with on/off times), each cell averaged over its bin and row (chirps exactly over whole and partial sweeps, jammers by duty), per-band effective C/N0 = [1/(C/N0) + sum (J/S) kappa]^-1 per row, J/S per band, in-band J/S, and an SVG waterfall with C/N0 bars. The report carries a cross-check against the jamming kind's chain on the same link inputs InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Reduction to the existing jamming kind's anti-jam equation and link budget (the same code, called on the same inputs), and the k T0 F noise-floor closed form. The signal spectra underneath are the validated row above; the jammer powers, timeline and front-end bandwidths are scenario inputs, the spectra are continuous (no spreading-code lines), and no automatic gain control, blanking or antenna pattern acts on the jammer. No measured jammed spectrum is in the repository to check the composite against. The jamming kind's Q table (CW and narrowband 1, broadband and swept 2 since 0.36: the textbook values, pinned to the navsignal closed forms) agrees with this model's CW value and differs from what it derives for noise matched to C/A (1.5) and for flat null-to-null noise without in-band normalisation (2.2); the report prints both spectrum (SpectrumScenario, SpectrumModel::bin_psd_w_per_hz, SpectrumModel::band_state, effective_cn0_multi_dbhz, system_temp_k, Jammer::power_fraction_in, Jammer::duty) spectrum::tests (agrees_with_the_jamming_kind_chain — J/S equal to jamming::j_over_s_db and effective C/N0 equal to jamming::effective_cn0_dbhz with Q = 1/(R_c kappa) to 1e-9 dB, and the 32.105 dB anchor of the jamming kind's own test; noise_floor_is_kt0f; chirp_window_splits_whole_and_partial_sweeps; duty_weights_partial_rows; demo_scenario_runs_and_denies_l1_while_l5_survives; defaults_run_with_no_jammer; bad_inputs_are_refused)
Uranus and Neptune from Standish Table 1, Pluto, and planetary velocities Positions of Uranus and Neptune from Standish Table 1 (the default inside 1800 AD to 2050 AD), Pluto from the 1992 Table 1 row the current JPL page no longer lists, and the heliocentric velocity of every planet: the two-body derivative with the mean motion the elements imply plus the turning of the ellipse by the perihelion, inclination and node rates ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — Measured against JPL Horizons DE441 (the same committed fixtures), but not validated: Table 1's stated figures for Uranus and Neptune are exceeded by up to 2.0 and 5.2 times against DE441 heliocentric positions (Neptune meets them against barycentric positions, which suggests the fit was not heliocentric), the page states no error for Pluto, and no published bound exists for the velocities. Tables 2a/2b meet their own figures for Uranus and Neptune and are covered by the validated row ephem (standish_state, StandishElements::state_at_mean_anomaly, Planet::Pluto); solar_system (position_label) tests/solar_system_horizons_reference.rs (standish_table1_uranus_and_neptune_exceed_the_nominal_error: pinned at 2.04 and 5.16 times the nominal longitude error, under six times; pluto_from_the_1992_row_is_measured_not_validated: within 39 arcsec and 1.14e9 m; standish_velocities_track_horizons_to_one_percent: worst 3.7e-3 of the speed); ephem::tests (standish_velocity_is_the_derivative_of_the_position; pluto_has_no_table2_row_and_no_stated_error)
Positions of the Moon and seven major moons (Phobos, Deimos, the Galilean moons, Titan) The geocentric Moon from the Montenbruck & Gill series (whose -1.3972 deg per century term already refers it to the J2000 equinox), and planetocentric positions and velocities of Phobos, Deimos, Io, Europa, Ganymede and Callisto from the JPL Solar System Dynamics mean elements in each moon's Laplace plane with the mean-longitude rate taken from the IAU synchronous rotation rate (the table prints the period to too few digits to hold the phase), and of Titan from the IAU rotation model (the moon on minus the body-fixed x axis at the mean distance), because Titan's printed Laplace-plane row does not reproduce Horizons even at its own epoch ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — Measured against JPL Horizons satellite ephemerides (DE441, MAR099, JUP365, SAT441) committed in tests/fixtures/solar_system/horizons_satellites_icrf.csv with the query and retrieval date; no published accuracy exists for mean elements or for the rotation-model placement, so the pinned bars catch regressions and do not validate. Mean elements omit the resonant and solar perturbations, and Phobos' secular acceleration is not modelled ephem (satellite_state, Satellite, SatelliteMethod, moon_icrf, moon_icrf_velocity); ephem_provider (AnalyticSolarSystem) tests/solar_system_horizons_reference.rs (moons_track_horizons_to_the_measured_angles: worst angular error seen from the planet over 2000 to 2040, Phobos 5.65 deg, Deimos 0.38, Io 0.40, Europa 1.63, Ganymede 0.22, Callisto 0.27, Titan 3.31; geocentric_moon_tracks_horizons: 0.046 deg); ephem::tests (moons_sit_at_their_mean_distance_and_move_at_their_mean_speed); ephem_provider::tests (earth_and_moon_balance_about_their_barycentre)
Physical constants of every solar-system body and the whole-system report Body gains Mercury, Venus, Jupiter, Saturn, Uranus, Neptune, Pluto, Phobos, Deimos, Io, Europa, Ganymede, Callisto and Titan (gravitational parameter, reference radius, J2 where published with the radius it is referenced to, IAU pole and prime meridian), a name lookup and a BodyFacts record (NAIF code, class, parent, equatorial and mean radius); the solar-system kind reports them for all eighteen bodies with the positions, light times and an orbit track over one revolution, each body labelled VALIDATED or MODELLED InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Transcription of published constants, each cited where it is defined: gravitational parameters from the JPL Horizons body records and the JPL satellite physical-parameter table, radii from the JPL physical-parameter tables (IAU WGCCRE 2015), poles and prime meridians from the IAU Working Group on Cartographic Coordinates and Rotational Elements (mean values, without the T-rate and periodic terms), J2 from Smith et al. 2012, Iess et al. 2018 and 2019, and Jacobson 2009 and 2014. Checked for internal consistency (the Jupiter rotation period against the System III rate, each J2 against its reference radius), not against an external oracle. 0.30 round 2: the GM values were adopted from gm_de440 and the Phobos and Deimos elements from pck00011, so 0 of 84 constants of the fourteen added bodies now differ from NAIF (was 12), which is a transcription check and is not counted. 0.36: the IAU body-fixed orientation and the GM of the fourteen added bodies are split out to their own VALIDATED row ("IAU body orientation and gravitational parameter of the fourteen added solar-system bodies"); this row keeps what is left. J2 and the mean radius are cited, not validated; the positions in the report rest on their own rows; and the report prime_meridian_deg for the Earth, the Moon and Mars stays on conventional constants (up to 6.6e-3, 2.8e-2 and 9.6e-4 rad from IAU_<BODY>). 0.30 revisions: Phobos GM 7.087e5 -> 7.087546066894452e5, Deimos 9.62e4 -> 9.615569648120313e4, Uranus 5.7939506103e15 -> 5.793951256527211e15, Neptune 6.83509997e15 -> 6.835103145462294e15, Pluto 8.69326e11 -> 8.696138177608748e11 m³/s²; Phobos equatorial radius 13.1 -> 13.0 km; prime_meridian_deg now includes the quadratic and periodic terms body (Body::by_name, Body::facts, Body::prime_meridian, SOLAR_SYSTEM, BodyFacts); solar_system (SolarSystemScenario, position_label) body::tests (every_catalogue_body_resolves_by_name_and_carries_its_record; a_zonal_field_is_referenced_to_its_sources_radius; retrograde_rotators_have_negative_rates_and_periods_match_the_iau_rate); solar_system::tests (defaults_report_all_eighteen_bodies_with_tracks; earth_heliocentric_distance_is_one_au_and_period_one_year; a_planet_track_closes_on_its_orbit_and_starts_at_the_epoch_position; moons_orbit_their_planets_at_their_mean_distance; pluto_outside_its_table_is_an_error_not_a_guess; every_emitted_number_has_a_unit); tests/body_constants_naif_oracle.rs::only_the_conventional_constants_of_other_rows_differ
Positioning around any solar-system body with a local constellation and a deep-space link from Earth The body-pnt kind: an orbiter or a surface lander around a body chosen by name navigates with one-way pseudoranges from a Walker navigation constellation around the body (two-body orbits with the body's J2 secular drift, an unknown user clock) and an optional clock-free two-way range from the Earth, the Earth's direction and distance from the analytic ephemeris at every epoch; lines of sight blocked by the body's sphere and a surface elevation mask; per epoch the constellation-only GDOP and PDOP (orbit::dop), the formal position uncertainty with and without the Earth row, and seeded Gauss-Newton fixes (batch_ls::gauss_newton) each way, with the body-to-Earth light time and round trip InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed forms and self-consistency: Kepler's third law for the relay period, the orbit radius and the surface radius held over the run, adding a measurement never increasing the formal uncertainty, and the seeded errors agreeing with the covariance. The relay orbits ignore third bodies (Jupiter's pull on relays around Europa is not modelled), the noise is Gaussian at stated levels and the measurement model is instantaneous, so this is not validated against any mission's navigation data body_pnt (BodyPntScenario, formal_sigma, fix_error); orbit (dop); batch_ls (gauss_newton); mars_pnt (chord_clears_sphere); mars_frame (bodyfixed_to_inertial) body_pnt::tests (relay_period_is_keplers_third_law_for_the_body; an_orbiter_keeps_its_radius_and_a_lander_sits_on_the_surface; the_earth_range_never_worsens_the_formal_uncertainty; seeded_fix_errors_are_consistent_with_the_formal_sigma: the root-mean-square of each fix error over its own formal sigma in [0.6, 1.5]; earth_light_time_is_minutes_at_mars_and_the_run_is_deterministic; defaults_run_around_mars_and_every_number_has_a_unit)
Coverage and dilution-of-precision maps for arbitrary multi-constellation designs at scale, around any central body The constellation-design kind beyond the two pinned cases: explicit and multi-shell designs, several constellations per run with one receiver clock per constellation, the Earth, the Moon and Mars from the body constants, the BeiDou preset (medium-orbit phase and 118 deg E inclined-geosynchronous crossing modelled), per-cell satellites in view, GDOP, PDOP, HDOP, VDOP and availability, downsampled ground tracks, and a sub-satellite-latitude visibility prefilter that runs a 5 000-satellite design on a 10 deg grid in a fraction of a second InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency: the brute-force elevation scan, the hand-computed and orbit::dop reductions, and the closed-form Walker and geosynchronous geometry. Two-body orbits with an optional secular J2, a spherical body with the local vertical along the radius, geometric visibility only (no signal power, satellite health, terrain or third-body perturbation), and the relative phase between systems taken from different reference epochs, so it is not a snapshot of any date. 0.30 review, a finding (stays MODELLED): the presets meet the published one-sided DOP-availability floors (BeiDou OS Performance Standard 3.0, Galileo OS SDD) at 100 %, but with the engine's PDOP doubled in a scratch copy they still meet them (worst point 99.36 %), so the floors cannot detect even a 100 % error in the quantity this row computes; tightening them after the run would be a post-hoc tolerance. Promotion needs a two-sided comparison of DOP values on identical geometry with a pre-set tolerance. 0.30 round 2 (tests/coverage_dop_full_oracle.rs, pre-registered a4d6f086), a finding (stays MODELLED): Orekit 12.2 positions, elevation, azimuth and ground tracks with gnss_lib_py 1.0.4 GDOP/PDOP/HDOP/VDOP (common clock) and a numpy inverse (one clock per constellation) agree on every bar on the Galileo, GPS, BeiDou, Galileo+GPS (one clock each) and a 1584-satellite Earth design (DOP within 2e-14 relative, identical fix, availability and visibility counts). On the Moon and Mars designs the elements, positions, visibility and tracks agree, but DOP exceeds the pre-set 1e-9 relative bar in cells whose largest PDOP is 1434 or more (up to 8e-6), and 4 cells differ by one fix epoch on numerically singular geometry (engine pivot 1e-10 against numpy rank), so the row is not validated. 0.30 revisions: the TDOP/GDOP reference clock is now the lowest-numbered constellation in view (constellation-multi-gnss-coverage global GDOP max 2.2236 -> 2.1205, mean 1.122 -> 1.131), and per-constellation visible counts are summed as integers constellation (coverage, ConstellationDesignScenario, beidou_slots, body_by_name) constellation::tests (prefilter_matches_brute_force_exactly — every map and counter equals a scan with the direct elevation test; five_thousand_satellites_on_a_coarse_grid — 5 000 satellites, prints the run time and the pair tests kept; a_clock_per_constellation_needs_one_more_satellite; beidou_geo_and_igso_geometry; lunar_shell_runs_around_the_moon; presets_are_earth_only_and_errors_are_clear; preset_counts); tests/constellation_availability_published_spec_oracle.rs::presets_meet_the_published_dop_availability (regression check only); tests/coverage_dop_full_oracle.rs::finding_is_pinned; tests/coverage_dop_gnss_lib_py_oracle.rs (regression)
A chained mission across scenario kinds on one shared timeline The campaign kind's phases: each phase runs one or more scenarios of existing kinds through run_toml, reads their outputs into named channels (clock time error and guard, mean effective carrier-to-noise density ratio and tracking floor, vertical protection level and alert limit, position error, satellites tracking, alarm flags) by per-kind presets or explicit result paths, places them at the phase start and holds them onto a common grid, with phase boundaries and events; state is handed on by carry (a channel continues from the previous phase's end value), handoff (a previous phase's number written into the next scenario) and end_at (a phase ends at a time a run computed, such as a spoofing monitor's detection time); a campaign hash and a digest over every member result InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Composition identities against the stand-alone runs of the same kinds: a one-phase campaign reproduces the stand-alone output bit for bit, the carried offset equals the previous run's own last sample, and the phase ended by end_at has exactly the run's detection time as its length. The additive carry across a phase boundary and the zero-order hold are modelling choices, and each phase is as good as the kind that ran it; no chained mission has been checked against a measured one campaign (run_campaign_detailed, run_chain, presets, extract, to_svg) tests/campaign_composition_reference.rs (a_one_phase_clock_campaign_reproduces_the_standalone_run_bit_for_bit, a_one_phase_integrity_campaign_reproduces_the_standalone_run_bit_for_bit, a_one_phase_jamming_campaign_reproduces_the_standalone_run_bit_for_bit — the member result byte-identical to the stand-alone run and every aligned value equal to the stand-alone series; the_chained_mission_hands_state_on_and_ends_the_spoofing_phase_on_detection; a_handoff_writes_the_previous_phase_number_into_the_next_scenario; malformed_campaigns_fail_loudly)
Parameter sweeps and seeded Monte Carlo ensembles over any scenario kind The campaign kind's sweep (one to three dotted keys of any kind, on the generic sweep's axis values, optionally an ensemble at every node) and monte_carlo sections: realisation k runs at base_seed + k; each metric reports mean, standard deviation, nearest-rank 5th/50th/95th percentiles and a fixed-seed percentile-bootstrap 95% confidence interval on the mean (inertial::metric_stat); metric units read from the swept kind's own units block InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — The closed form of the phase random walk under white frequency noise, variance q_wf tau (NIST Technical Note 1337), for the statistics machinery, and byte equality with the stand-alone runs for the seeding. It checks the ensemble arithmetic on the engine's own clock model, not an external dataset campaign (run_sweep, run_monte_carlo, ensemble); sweep (GenericAxis, coords_of, set_dotted_value); inertial (metric_stat) tests/campaign_composition_reference.rs (a_fixed_seed_ensemble_is_byte_stable_and_each_realisation_is_the_standalone_run; the_ensemble_mean_and_spread_match_the_white_fm_closed_form — 200 seeds of a white-frequency-noise clock coasting tau = 3010 s: the true mean 0 inside the reported interval, the interval half-width within 25% of 1.96 sigma/sqrt(n), and the sample variance inside the two-sided 99% chi-square interval of sigma = sqrt(q_wf tau) = 16.459 ns; calibration ensemble (CAP-10, pre-registered d224fbc0, docs/CALIBRATION-ENSEMBLES.md, tests/calibration_ensembles.rs): over 200 independent ensembles the interval covers the true mean on 192 (inside the Binomial(200, 0.95) 99 % region [181, 197]) and the chi-square check passes on 196, while the single-seed percentile tolerance (p05 and p95 within 0.3 sigma) passes on only 183 of 200, NOT MET against the pre-registered 190, a seed-fragile check recorded rather than loosened; a_one_node_sweep_and_a_one_member_composition_read_the_standalone_number)
Several scenarios under shared conditions, with a combined summary The campaign kind's compose section: named shared values (for example one jammer's power and position) written into each member at the keys it binds them to, every member run, and per metric the smallest, largest and mean value across the members with the member named; metric units must agree across members InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Composition identity against the stand-alone run. The shared-condition arithmetic is bookkeeping; the physics is that of the member kinds, each with its own row campaign (run_compose) tests/campaign_composition_reference.rs (a_one_node_sweep_and_a_one_member_composition_read_the_standalone_number — a one-member composition reads the stand-alone number and result digest)
Bounded optimisation of one metric over campaign parameters The campaign kind's optimize section (CAP-32): one to three dotted scenario keys bounded to [lo, hi] on a lin or log scale, one metric read by result path, goal minimize, maximize or target; method grid (the sweep's axis values) or a deterministic Nelder-Mead simplex in normalised coordinates with box projection and the standard coefficients; a missing or non-finite metric scores worst and stays in the trace; with runs > 1 the metric is the mean over common seeds; every evaluation is a real run of the named kind, listed in trace and counted in the reproducibility digest InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal only: the exact -20 log10(range) closed form of the link equation, an independent brute-force grid over the same kind, and the Rosenbrock function. Round 1's 1-D bar is NOT MET (the pre-registered box excluded the 3 dB solution; the optimiser stopped at the bound), recorded in docs/design/evidence/cap32-optimize/RESULTS.md and not re-scored. The optimum is local to the box and the start; no global-optimum claim campaign::optimize (run_optimize, nelder_mead) tests/campaign_optimize_reference.rs (pre-registered 21b64e52 and, after a round-1 protocol miss, 824e9bc1: p2_prime_interior_target_range_matches_the_closed_form — 1-D target solve within 6.1e-15 of r* = r0 10^((m(r0) - 3)/20) in 96 evaluations; p3_prime_contour_target_grid_and_nelder_mead and p3_grid_matches_brute_force_and_nelder_mead_does_at_least_as_well — the grid method's best bit-equal to an independent 41 x 41 brute-force loop over run_toml, Nelder-Mead at least as good in 177 and 161 evaluations; p4_nelder_mead_reaches_the_corner_maximum; p5_the_document_is_byte_stable_and_counts_agree; p2_round1_not_met_the_box_excludes_the_closed_form, which pins the recorded round-1 miss); campaign::optimize::tests (nelder_mead_meets_the_preregistered_rosenbrock_bar: f* = 1.7e-20 in 234 evaluations; a_non_finite_score_is_never_the_best; the_grid_mapping_is_the_sweeps)
Low Earth orbit positioning, navigation and timing signal designs: code tracking, acquisition, GNSS compatibility and a band trade for any system The leo-signal kind: parameterised signal designs (band, transmit bandwidth, ITU allocation; acquisition, data and pilot components with BPSK(n), BOC(m,n), MBOC or flat spectra, power shares, FDMA sub-carriers, code lengths and data rates) from compiled-in public preset files (Xona Pulsar, Iridium STL, Starlink signal of opportunity, CentiSpace, a generic C-band design and generic UHF/L/S/C/wide-C designs, each with its source URL and unpublished values labelled REPRESENTATIVE) or written inline; per signal the band-limited power spectral density, in-band power fractions, Gabor bandwidth, code jitter against C/N0 and spacing and the ranging accuracy, the acquisition search space, square-law detection probability and mean serial and code-parallel acquisition time, the spectral separation coefficient into and from GPS L1 C/A, Galileo E1, GPS L5, Galileo E5a, E5b and AltBOC with the C/N0 degradation, and the CW, wideband and matched J/S tolerance from the spectrum kind's SSC chain; a band trade of ionospheric delay, free-space loss, ranging accuracy at equal C/N0 and equal EIRP and jammer tolerance; and qualitative shape checks of a design against a described measurement InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — The validated closed forms of the two rows above, the square-law false-alarm identity P_d(snr = 0) = P_fa and Holmes's mean acquisition time, and reduction to the spectrum kind's own SSC chain (the same Jammer::ssc code). The designs themselves are inputs: presets marked REPRESENTATIVE or WORKSHOP are not published specifications, enhanced Feher QPSK, code shift keying and OFDM spectra are approximated, and the shape checks compare shapes, not calibrated levels. leo_signal (LeoSignalScenario, SignalDesign, Component, Shape, code_jitter_m, gabor_bandwidth_hz, detection_probability, threshold_for_pfa, mean_acquisition_time_s, ssc_leo_into_gnss, ssc_gnss_into_leo, jammer_tolerance, gnss_victim, preset, public_signal) leo_signal::tests (every_public_preset_parses_and_cites_a_url; detector_reduces_to_pfa_and_grows_with_snr; detection_probability_with_several_looks_matches_the_noncentral_chi_square; mean_time_of_a_perfect_detector_is_half_the_cells; compatibility_ssc_magnitudes_match_independent_quadrature; to_spectrum_band_is_consistent_with_the_design; jammer_tolerance_orders_cw_matched_wideband; e5_centred_signal_hits_e5a_and_e5b_equally; defaults_run_on_the_generic_band_preset; inline_signal_and_bad_inputs); tests/leo_signal_reference.rs (every bundled system-agnostic scenario runs with no workshop data, the band trade's ionospheric ratios equal (f_ref/f)^2 and its free-space differences 20 log10(f/f_ref), the jitter at the reference C/N0 sits between its Gabor bound and its unlimited-band form, the workshop-parameter scenario's E5 shape checks are consistent when that file is present, and no source file compiles that file in)
Multi-band spectrum waterfall (UHF, L, S, C) with designed signals and per-band jammers The spectrum kind extended beyond the L band: bands given as a preset signal design (drawn with every component, band-limited to the transmit bandwidth, C/N0 and J/S referred to the tracked component) or as a custom carrier and modulation; extra waterfall panels over any frequency range on the same timeline and colour scale; a wideband (barrage) jammer beside CW, narrowband, chirp and matched noise; per-band J/S and effective C/N0 from the unchanged spectral separation coefficient chain InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Reduction to the existing spectrum chain and the jamming kind's anti-jam equation (a single-component band gives the same numbers as before the extension) and the signal spectra of the validated rows. The jammer powers, timeline, front-end bandwidths and the designed signals are inputs, and a designed signal is truncated at its transmit band (no out-of-band emission). spectrum (Band::unit_psd, Band::tracked_power_dbw, BandDesign, BandCfg, PanelCfg, SpectrumScenario, Waveform, multi_band_svg); leo_signal (SignalDesign::to_spectrum_band) tests/leo_signal_reference.rs (the multi-band waterfall runs with four panels, the UHF, L5-band, S and C jammers each deny only their own band, and a plain-band run is unchanged by the extension); leo_signal::tests::to_spectrum_band_is_consistent_with_the_design; spectrum::tests (agrees_with_the_jamming_kind_chain)
A LEO-PNT pass and its per-band link budget against the MEO GNSS satellites in view The leo-pass kind: satellites from a designed pass, elements, a TLE through SGP4 or a Walker constellation from constellation-design; per band and epoch the look angles, range, closed-form range rate and range acceleration (checked each run against central differences and reported), free-space loss, EIRP with an isoflux, Gaussian or flat pattern, a patch, hemispherical or isotropic user antenna, ITU-R P.676-10 Annex 2 gaseous attenuation, P.618 rain and scintillation, P.2109 building entry loss, polarisation mismatch, system noise temperature, C/N0, Doppler and Doppler rate, and the first-order delay from a Klobuchar or vertical-TEC slant TEC scaled by the Chapman fraction below the satellite; ionosphere-free pairs with code noise at the pass peak; Galileo or GPS carriers from their interface-document received powers through the same receiver InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed forms and self-consistency: the range-rate and range-acceleration identities against numerical derivatives, the isoflux gain cancelling the range growth, the textbook polarisation-loss limits, the qualitative LEO-versus-GNSS observation (a bell-shaped pass of minutes peaking several dB above flat 44-51 dB-Hz GNSS carriers). The EIRPs and patterns are published received powers turned into an EIRP or representative choices, the gaseous term is the superseded P.676-10 simplified method, and nothing is compared with a measured LEO C/N0 leo_pass (LeoPassScenario); leo_link::geometry (design_pass, link_geometry, numerical_check, SatMotion, UserMotion); leo_link::antenna; leo_link::itu (p676_gaseous_attenuation_db); leo_link (system_noise_temperature_k, cn0_dbhz) leo_pass::tests (the_leo_pass_is_a_bell_above_flat_gnss; closed_form_doppler_agrees_with_the_numerical_derivative: under 0.01 Hz and 0.01 Hz/s; indoor_uhf_suffers_less_building_loss_than_c_band; rain_attenuates_c_band_more_than_s_band; iono_delay_scales_as_one_over_f_squared_across_bands; a_fully_custom_band_needs_no_preset; a_walker_constellation_and_a_tle_satellite_both_run; defaults_run_with_no_preset_named_and_every_number_has_a_unit); leo_link::geometry::tests (kepler_velocity_is_the_derivative_of_the_position; a_designed_pass_reaches_the_requested_elevation; closed_form_range_rate_and_accel_match_central_differences_for_two_body_motion); leo_link::antenna::tests
Named LEO-PNT system presets with stated sources, and a system-agnostic engine leo_link::presets: generic multi-band (UHF, L, S, C), generic C band, Xona Pulsar X1/X5, Iridium STL, Starlink as a Doppler-only signal of opportunity, CentiSpace and an optional Celeste IOD preset, each with its source marked PUBLIC (with URL), REPRESENTATIVE or WORKSHOP, the workshop one in the optional Celeste IOD preset file, compiled in only when that file exists; every band and orbit overridable in a scenario, and a scenario may name no preset at all InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Transcription of the cited public figures and a consistency check: an EIRP set from a published minimum received power predicts the published maximum within 0.5 dB with a flat pattern. That is a check of the range spread, not a validation of any satellite's antenna; representative presets make no claim about a real system leo_link::presets (SystemPreset, BandPreset, all, by_id, gnss_meo); leo_pass (resolve_bands) leo_link::presets::tests (every_preset_is_sourced_and_self_consistent; only_the_celeste_preset_is_sourced_from_the_workshop); leo_link::presets::xona_pulsar::tests (the_eirps_reproduce_the_published_minimum_power_at_ten_degrees; a_flat_pattern_lands_the_zenith_power_near_the_published_maximum: within 0.5 dB of -139.1 and -136.2 dBW); leo_link::presets::iridium::tests; leo_pass::tests (a_fully_custom_band_needs_no_preset)
Low-energy positioning: time to first fix and energy per fix against duty cycle leo_link::energy and the leo-pass kind's [iot] section: coherent integration capped by the Doppler rate, square-law non-coherent sums to a detection threshold, a Doppler-bin search over the orbit's static-user envelope (cold) or an aided window (hot), parallel or serial code search, navigation-message time on a cold start, energy per fix and battery life across fix intervals, for each LEO band and the GNSS signal InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency of a stated design model: every power, threshold and search choice is an input, and the model ignores bit-edge ambiguity, missed detection and re-acquisition. Not compared with a measured receiver leo_link::energy (fix_budget, duty_curve, IotReceiver, IotSignal); leo_pass (iot_section) leo_link::energy::tests (stronger_signals_and_smaller_doppler_windows_fix_faster; the_doppler_rate_caps_the_coherent_time; battery_life_grows_with_the_fix_interval_toward_the_sleep_floor); leo_pass::tests (the_run_is_deterministic_and_bad_inputs_are_rejected)
Mid-pass LEO navigation message update with a continuity check at the switch The leo-navmsg midpass-update analysis: the highest pass over a user within a search span, messages on a global schedule with usage periods centred in their fit windows, and at each switch the 3D position jump, the clock jump, the user pseudorange jump, the largest jump over any visible line of sight (closed form over the nadir cone), the range error before and after, and PASS/FAIL against a threshold InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency (the jump identity and the cone bound against brute-force sampling). The threshold is an input; no published LEO continuity requirement is pinned leo_navmsg (LeoNavmsgScenario::midpass, worst_case_jump, elevation, geodetic_to_ecef) leo_navmsg::tests::a_mid_pass_update_is_continuous (every switch's range jump equals the change in range error, and a corrected 300 s fit updated every 150 s passes a 5 cm threshold); leo_navmsg::tests::a_keplerian_only_update_over_a_long_interval_is_flagged; leo_navmsg::tests::worst_case_jump_bounds_every_line_of_sight (the closed form bounds a dense sampling of the cone)
Documented binary encoding of the LEO navigation message with a quantisation-error budget leo_navmsg::codec: Kshana's own frame (preamble, version, model, length, payload, CRC-24Q) for the four ephemeris models, the clock polynomial, SVID, issue of data, band, health, a Klobuchar set, NeQuick-G coefficients and UTC parameters, every field with a stated width and step (field_table), quantisation with range refusal, and a budget of the largest position and clock change a half-step change of each field makes over the validity window InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Round-trip identities and the budget itself. The format is Kshana's own, modelled on the published message components and the Galileo ICD field set; it is not the bit layout of Celeste or any other system (none is public), so there is no external layout to validate against leo_navmsg::codec (encode, decode, write_payload, read_payload, field_table, quantisation_budget) leo_navmsg::codec::tests (signed_fields_round_trip_through_the_bit_packer; week8_resolves_near_the_reference); leo_navmsg::tests::every_model_round_trips_through_the_binary_frame (every model within 2 mm of the exact message after decoding, re-encoding bit-identical, a flipped bit rejected by the CRC); leo_navmsg::tests::every_field_of_the_budget_stays_under_a_millimetre
RINEX-4-style and CSV exports of LEO navigation messages leo_navmsg::text: a RINEX-4-style block (> EPH record header, satellite and epoch line with three clock terms, D19.12 broadcast-orbit lines) with system letter L and record types KP16, KRAC, LU22 and APOL, labelled in every header as a Kshana extension not part of RINEX 4.02, and a CSV table with a default column schema and preset schemas, each with an importer InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Round trips and the calendar arithmetic. RINEX 4.02 defines no LEO navigation records (IGS RINEX 4.02), so the layout is a documented extension with arXiv 2401.17767 cited as prior art; no external reader of it exists to check against leo_navmsg::text (rinex_export, rinex_import, csv_export, csv_import, calendar, from_calendar) leo_navmsg::text::tests (calendar_round_trips_and_knows_the_gps_origin; d19_is_rinex_shaped); leo_navmsg::tests::rinex_and_csv_round_trips (every model within 0.1 mm after the text block, the CSV exact)
ATOMIC zero-clock ECEF polynomial and the synthetic five-altitude LEO model comparison the EcefPoly variant of leo_navmsg::elements::EphemerisModel: a per-axis ECEF polynomial with no clock terms, the relativistic term from -2 r.v/c^2, scored against a steered clock. Also the model-comparison analysis (liu_comparison over LIU2025_TABLE), which fits the 22-parameter model at the paper five altitudes over 20-minute arcs of a Kshana-integrated orbit and prints the result beside the published SISRE InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — ATOMIC model facts from InsideGNSS (6th-order polynomial, about one minute validity, 30 s refresh, clock steered, 24 cm clock error). These are descriptive facts with no published numbers to compare against. The five-altitude table prints Liu et al. 2025 SISRE (8.88, 6.21, 2.87, 2.11 and 0.75 cm at 320, 475, 786, 966 and 1336 km over a 20-minute arc) beside Kshana fit on its own integrated orbit (4.25, 2.87, 2.20, 1.25 and 0.51 cm; ratios 0.46 to 0.77), not pinned, because the paper fitted real precise orbits and the truths differ. The 22-parameter model and fit themselves are validated against real orbits in the row Liu et al. 2025 22-parameter LEO ephemeris model and its fit on real precise orbits. 0.30 revision: the table figures moved with the paper-convention fit (GRACE-A 5.40 -> 4.25 cm, GRACE-C 4.12 -> 2.87, Sentinel-2A 2.95 -> 2.20, HY-2A 2.38 -> 1.25, Sentinel-6A 0.70 -> 0.51) leo_navmsg::elements (EcefPoly, ephemeris_at); leo_navmsg (liu_comparison, LIU2025_TABLE) leo_navmsg::tests::liu22_beats_the_16_parameter_set_over_a_20_minute_arc; leo_navmsg::tests::the_ecef_polynomial_fits_a_minute_to_millimetres; leo_navmsg::tests::every_preset_resolves_and_the_atomic_preset_selects_the_zero_clock_polynomial
Positioning from LEO Doppler, single- and multi-satellite, with clock-drift and velocity states Batch Gauss-Newton positioning from range rate with analytic partials (d rho_dot / d r = -(I - u u^T)(v_s - v_u)/rho, d/dv = -u, d/d drift = 1), a constant user velocity as an option, a height pseudo-measurement for a surface user, damped steps; the formal covariance at the truth; along-track, cross-track and vertical projections; the single-pass accuracy against the user's cross-track offset; the time of closest approach. The leo-pvt kind's doppler mode adds the error against window length and a Doppler-only signals-of-opportunity mode (the starlink-sop preset) InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency: noise-free recovery, the kinematic identity rho_ddot = (|v|^2 - rho_dot^2 + d.a)/rho differentiated numerically, zero Doppler at closest approach, the mirror solution of a single pass, and seeded errors against the formal covariance. The Starlink figure of Kozhaya, Saroufim and Kassas (NAVIGATION 72(1), 2025: about 2 m in 20 s with three satellites) is a comparison only: the modelled receiver, with a perfect ephemeris and every error in a 30 Hz Doppler sigma, is several times less accurate over the same window, and the paper's receiver and measurement rate are not reproduced leo_fusion::doppler (solve, formal_covariance, single_pass_geometry, offset_site, closest_approach); leo_fusion::pvt_kind (run_doppler) leo_fusion::doppler::tests (range_acceleration_obeys_the_kinematic_identity_and_vanishes_doppler_at_closest_approach; noise_free_multi_satellite_doppler_recovers_the_user: to 1 mm and the drift to 1e-6 m/s; a_single_pass_has_a_mirror_solution_across_the_ground_track; the_cross_track_error_grows_as_the_pass_goes_overhead; velocity_states_are_recovered_for_a_moving_user); leo_fusion::pvt_kind::tests (doppler_positioning_improves_with_the_window_and_is_deterministic: the weighted residual RMS in [0.8, 1.2] and the error under four formal sigmas); tests/leo_fusion_scenarios.rs (leo_doppler_positioning_forms_a_fix_and_the_cross_track_error_explodes_overhead; starlink_doppler_only_mode_runs_without_ranging); tests/starlink_doppler_published_proxy.rs (a pre-registered proxy against the published data-set-3 percentiles of "Unveiling Starlink for PNT", doi:10.33012/navi.685: with 3 satellites (47 deg mask), no height aid and 30 Hz, the p90 3-D error is 92.2 m at 20 s and 870 m at 8 s against the published 2 m and 10 m, so both factor-of-two bars are NOT MET, on the high side, and asserted as missed; docs/design/evidence/cap11-starlink-doppler-proxy/)
Joint GNSS and LEO pseudorange positioning with inter-system biases and per-signal error models Weighted least-squares Gauss-Newton fixes over any mix of systems, one receiver clock per system (the inter-system bias estimated with the position) or a known broadcast offset on the reference time scale; per-measurement sigmas supplied by the caller, by default the engine's delay-lock-loop thermal noise (navsignal::dll_code_jitter_chips) at the C/N0 of the elevation combined with the signal-in-space range error; unweighted DOP (GDOP, PDOP, HDOP, VDOP, TDOP) in the local geodetic frame, formal east-north-up sigmas and the bias sigmas; the leo-pvt joint mode compares GNSS-only, LEO-only and fused fixes and sweeps the DOP against the number of LEO satellites added InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — A hand-derived four-satellite DOP (one satellite at the zenith and three on the horizon 120 deg apart, whose normal matrix inverts by hand), the structural identity that a system with its own clock and one satellite adds no geometry, noise-free recovery of position, clock and bias, and seeded errors against the covariance. Internal checks only; not compared with a receiver's output. 0.30 external comparison, a finding (stays MODELLED): on a multi-GNSS IGS day (ABMF 2018-05-13, GPS and Galileo C1C, broadcast ephemeris, Klobuchar) the inter-system bias agrees with RTKLIB v2.4.2-p13 rnx2rtkp (median difference -0.11 ns after the 0.30 broadcast group-delay fix, -0.35 ns before; bar 1 ns), but only 93.6 % of 280 epochs (93.2 % before the fix) are within 3 m of the ITRF2020 coordinate against the pre-registered 95 %. RTKLIB itself reaches 88.2 % on the same data, so the bar is beyond single-frequency broadcast positioning at this station and day rather than a solver discrepancy; the comparison test is committed ignored. 0.30 round 2, stricter inputs at the unchanged 3 m / 95 % / 1 ns bar, a finding (stays MODELLED): with the Galileo E1/E5a ionosphere-free pair (pre-registered ca98316f) 79.9 % of epochs are within 3 m (RTKLIB 67.9 %); with precise CODE MGEX orbits, clocks, satellite antenna offsets and code biases (pre-registered 0d7f6e5f) 94.2 % (RTKLIB 94.1 %), and the inter-system bias differs from RTKLIB by -1.03 ns because RTKLIB single mode ignores satellite antenna offsets (+0.04 ns when both omit them) leo_fusion::joint_pvt (solve, dop, code_sigma_dll_m, SystemClock); leo_fusion::system (SystemCfg, System); leo_fusion::pvt_kind (run_joint) leo_fusion::joint_pvt::tests (dop_matches_the_hand_derived_zenith_plus_three_horizon_case: HDOP = VDOP = sqrt(4/3), TDOP = sqrt(1/3), PDOP = sqrt(8/3), GDOP = sqrt(3) to 1e-9; a_lone_satellite_with_its_own_clock_adds_nothing_and_a_known_offset_does; a_noise_free_fix_recovers_position_clock_and_inter_system_bias; seeded_fixes_agree_with_their_formal_covariance; dll_noise_is_the_textbook_figure_for_gps_l1_ca); leo_fusion::pvt_kind::tests (fusing_leo_never_worsens_the_median_pdop_and_the_isb_is_recovered); tests/leo_fusion_scenarios.rs (meo_leo_fusion_beats_gnss_alone_and_recovers_the_leo_bias); tests/joint_pvt_dual_freq_itrf_rtklib_oracle.rs::dual_frequency_finding_is_pinned; tests/joint_pvt_precise_itrf_rtklib_oracle.rs::precise_product_finding_is_pinned
Precise point positioning convergence with GNSS only and with LEO augmentation A float PPP extended Kalman filter on ionosphere-free code and phase: static coordinates, a white receiver clock, one inter-system bias per extra system, a random-walk zenith wet delay mapped by 1/sin(elevation), a float ambiguity per satellite arc added at rise and dropped at set, and the precise orbit-and-clock error common to a satellite's code and phase, processed as one correlated two-row update in a Joseph-stabilised form; measurements simulated from the same model; convergence time (errors below the thresholds until the end of the run), error curves and the run-averaged position NEES for GNSS only and each LEO case, run as the leo-ppp kind ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — The NEES chi-square test is an internal consistency check (truth and filter share the model). The trend is compared with Li et al., LEO constellation-augmented multi-GNSS for rapid PPP convergence, J. Geod. 93:749-764 (2019), doi 10.1007/s00190-018-1195-2: multi-GNSS 9.6 min shortened to 7.0, 3.2, 2.1 and 1.3 min with 60, 96, 192 and 288 LEO satellites. The bundled scenario gives 7.4, 4.8, 3.2, 2.7 and 2.3 min with its own representative 1000 km, 60 deg shells, noise and stations; the paper's constellations, noise and convergence definition are not reproduced, so this is a MODELLED consistency of the trend (monotone shortening, the largest constellation under a third of the GNSS-only time), not a validation leo_fusion::ppp (run, PppScenario, LI_2019) leo_fusion::ppp::tests (the_filter_is_consistent_over_monte_carlo_seeds: 24 seeds, run-averaged NEES mean in [2.4, 3.6] and at least 75% of epochs inside the two-sided 95% chi-square band; measured with 150 seeds, mean 2.84 GNSS only and 2.87 with LEO; leo_augmentation_shortens_convergence; same_seed_same_answer_and_every_number_has_a_unit); tests/leo_fusion_scenarios.rs (ppp_convergence_of_the_bundled_scenario_shortens_monotonically)
LEO-assisted time transfer to UTC against C/N0 and the receiver oscillator Clock measurements from every LEO satellite in view at a known position, combined by inverse variance from the pseudorange noise model, filtered by a two-state (phase, frequency) Kalman filter whose process noise is the oscillator class's white and random-walk frequency noise (slot_timing::ClockNoise, clock_state::ClockClass; the coast variance of holdover::coast_phase_variance), a seeded truth clock from the same levels, and the IS-GPS-200 section 20.3.3.5.2.4 system-time-to-UTC expression with a broadcast-offset uncertainty added as a per-run bias; the leo-pvt timing mode sweeps oscillators and C/N0 offsets InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency: the published offset expression evaluated by hand, the normalised error over 40 seeds, and the floor set by the offset uncertainty. The NIST figure for Iridium timing receivers with a miniature atomic clock (under 40 ns from UTC(NIST) over 40 days) is a comparison only; the bundled Iridium scenario gives 10 to 11 ns RMS at nominal power with its representative 5 m range error. Flicker frequency noise and ionospheric delay are not simulated leo_fusion::timing (simulate, utc_offset_s, system_to_utc_s); leo_fusion::pvt_kind (run_timing) leo_fusion::timing::tests (the_utc_offset_follows_the_is_gps_200_expression; continuous_tracking_approaches_the_measurement_floor_and_gaps_cost_time; the_filter_is_consistent_over_seeds; the_utc_offset_uncertainty_sets_a_floor); tests/leo_fusion_scenarios.rs (leo_timing_error_grows_as_the_c_n0_falls)
Named LEO PNT systems as optional data presets, each with its source System-agnostic inputs: every system is Walker shells, explicit elements or a GNSS preset, a signal (carrier, chip rate, bandwidth, received power or C/N0 range), a SISRE, a Doppler sigma and a clock model; presets fill only what a scenario leaves out, one file each with sources marked PUBLIC (with a URL), WORKSHOP or DERIVED and the unpublished values listed as representative: Xona Pulsar X1/X5, Iridium STL, Starlink signals of opportunity, CentiSpace, a representative C-band system, the ATOMIC zero-clock ephemeris model, and one workshop-derived preset in the optional Celeste IOD preset file, withheld by deleting that file and its scenarios InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Transcription of the cited public values, checked for structure (every public source has a URL, Walker patterns divide evenly, the C/N0 from received power over kT at 290 K), not against an external oracle. Representative values are named in each preset and are illustrative leo_fusion::presets (all, by_id, cn0_range_dbhz, noise_density_dbw_hz); leo_fusion::system (SystemCfg::build) leo_fusion::presets::tests (every_preset_has_a_source_and_every_public_source_a_url; only_one_preset_uses_workshop_material; noise_density_at_290_k_is_minus_204_dbw_per_hz); tests/workshop_preset_isolation.rs (only_the_listed_files_name_the_workshop_preset; workshop_numbers_live_only_in_the_preset_file_and_its_scenarios: source-text scans of src, scenarios and tests); leo_fusion::system::tests (a_preset_fills_what_the_scenario_leaves_out; a_system_needs_no_preset; pseudorange_sigma_falls_with_elevation_and_never_below_the_sisre)
One LEO-PNT system end to end: signal design, pass link budget, navigation message and fused positioning, each stage's output handed to the next The leo-pnt-chain kind: a leo-signal design (public preset or inline) sets a leo-pass band's centre, bandwidth, chip rate and EIRP split; the pass gives the tracked-component C/N0 and band-limited code jitter per epoch; a least-squares C/N0 line in sin(elevation), the leo-navmsg message's SISRE (fitted at the pass satellite's orbit, plus a stated orbit-determination term in root-sum-square) and the design's carrier and chip rate go to every LEO system of a leo-pvt joint fix and, optionally, to the LEO cases of leo-ppp; every hand-off is reported with its value and unit InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Self-consistency of the hand-offs: each handed-on value equals the upstream stage's own output, and mutating an upstream input moves every downstream figure that depends on it. The stages keep their own labels; the chain adds no physics and no external oracle leo_pnt_chain (LeoPntChainScenario); leo_pass (BandCfg::signal, design_tracking); leo_navmsg (LeoNavmsgScenario::broadcast_sisre); leo_fusion::pvt_kind; leo_fusion::ppp leo_pnt_chain::tests (a_sine_line_fit_recovers_its_line); tests/leo_pnt_chain.rs (every_upstream_change_moves_the_downstream_figures: a stronger EIRP, a longer fit interval and a larger orbit-determination term each move the handed-on value and the fused fix; the_handed_on_values_are_the_stage_outputs; a_band_design_splits_the_eirp_and_reports_the_design_jitter; the_pass_export_reproduces_the_engine_range)
Spoofing detection by LEO Doppler and pass-geometry consistency The leo-pass kind's [spoofer] section: a spoofer counterfeits, self-consistently in range and range rate, the signals seen at a claimed position that jumps and/or is pushed from the true one after an onset (per LEO band and for the MEO GNSS signal); the receiver predicts every range rate from the broadcast orbit and an independent prior position and velocity, and tests the measured range rates with a generalised least-squares chi-square statistic over a window of epochs (clock drift a nuisance or with a prior), on the GNSS channels, the LEO channels and all channels, with frequency-lock-loop thermal noise from C/N0 (Kaplan & Hegarty 2006, section 5.6.2); detection probability from the non-central chi-square law at a stated false-alarm probability, detection declared at a stated missed-detection probability InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed forms and identities, not an external measurement: the range-rate gradient against a central difference, the information-form statistic against the dense covariance form, a pure clock drift giving zero, a prior-explained push giving at most |dx|^2/sigma_p^2, the statistic quadratic in a jump. No detection figure is compared with a measured attack; the spoofer is idealised (no power, angle-of-arrival or correlation-peak signature) leo_link::spoof (range_rate_position_gradient, line_of_sight, fll_frequency_jitter_hz, doppler_consistency_window, doppler_consistency); leo_pass (SpooferCfg, spoof_section) leo_link::spoof::tests (the_gradient_is_the_derivative_of_the_range_rate; fll_jitter_matches_the_formula_by_hand; a_common_mode_residual_is_a_clock_drift_and_is_not_detected; with_no_prior_and_equal_noise_the_statistic_is_the_scatter_about_the_mean; a_push_the_prior_explains_is_not_detected; a_velocity_push_is_hidden_by_a_loose_velocity_prior_only; the_information_form_equals_the_covariance_form); tests/leo_resilience_verticals.rs (the_monitors_are_silent_before_the_onset; the_doppler_statistic_is_quadratic_in_the_jump; leo_range_rates_see_a_jump_that_gnss_range_rates_do_not)
Spoofing detection by cross-band consistency of a multi-band LEO signal For every LEO satellite and pair of ranging bands the [spoofer] section forms the geometry-free pseudorange combination, removes the receiver's ionospheric model and tests its epoch-to-epoch step against the two bands' code noise and a stated tolerated unmodelled ionospheric rate (two-sided Gaussian, exact detection probability); a spoofer that counterfeits some bands and not others, or every band without the ionosphere, is seen at its onset; one that counterfeits every band and simulates the ionosphere is not, which the result states InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Identities: the onset step of an ionosphere-free spoofer equals the pair's modelled ionospheric delay difference, the threshold is the two-sided normal quantile times the step's standard deviation plus the rate bound. The receiver's ionospheric model is the engine's, so the authentic residual is zero in the mean by construction; no external oracle leo_link::spoof (cross_band_step); leo_pass (spoof_section: pairs, cross_band) leo_link::spoof::tests (the_cross_band_threshold_and_power); tests/leo_resilience_verticals.rs (a_ground_spoofer_leaves_the_ionospheric_step_and_an_ionosphere_aware_one_does_not; a_one_band_spoofer_is_seen_by_the_cross_band_monitor_at_the_onset; the_monitors_are_silent_before_the_onset)
Ionosphere sounding: slant TEC from the dual-band delay of a LEO pass For every band pair of a leo-pass satellite the report gives the slant total electron content the geometry-free code combination recovers at the pass peak, (P2 - P1) f1^2 f2^2 / (40.3 (f1^2 - f2^2)), and its 1-sigma from the two bands' thermal code noise, so any multi-band LEO-PNT design can be traded as an ionosphere sounder InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — The first-order dispersion identity, exact by construction against the engine's own first-order delay (whose 1/f^2 scaling is VALIDATED against IS-GPS-200 in its own row); the precision is thermal code noise only, without multipath or inter-frequency biases. 0.30 round 2, measured (pre-registered bd9812bd), a finding (stays MODELLED): the CODE global ionosphere map CODG1330.18I against ABMF C1C/C2W code with the CODE biases gives 33 of 36 arc means within 3 TECU (worst +6.84 TECU on an evening arc; per-epoch RMS 3.95 TECU), against a bar of every arc; not validated leo_pass (IonoFreePair::geometry_free_stec_tecu, geometry_free_stec_sigma_tecu); leo_link::iono::geometry_free_stec_tecu tests/leo_resilience_verticals.rs (the_geometry_free_tec_is_the_pass_slant_tec: equals the pass's slant TEC at the peak to 1e-9 and its sigma equals the RSS code noise over 40.3 (1/f1^2 - 1/f2^2)); tests/geometry_free_tec_gim_oracle.rs::geometry_free_finding_is_pinned
Maritime trust score: the aggregation of the monitors' evidence into a 0-100 score and its three bands Each monitor reduces its evidence to a ratio of statistic to threshold; the score is 100 minus the sum over monitors of weight times a clamped linear ramp of the ratio (0 up to 0.5, 1 at 1.5), clamped to 0 to 100 and rounded to 0.1, with bands at 90 and 55; each epoch lists the monitors that deducted and their points. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Implementation against specification, NOT an external oracle: a clean-room Python re-implementation (scripts/maritime_score_cleanroom.py), written by a reader given only docs/RECEIVER-TRUST.md and docs/MARITIME-TRUST.md and not the Rust source, agrees with score_from_ratios on 600 ratio vectors (score, band, points and the order of deductions, difference 0), after the documentation was completed where the first reader found it silent or inconsistent (tie order, rounding, the ratio of a pass-or-fail monitor, two examples whose numbers did not match the formula). That shows the documentation is sufficient and the code does what it says. WHAT IS NOT CHECKED, and why the row stays MODELLED: the rule itself (the weights, the ramp, the band edges, the evidence hold) is this project's own, pre-registered but with no external source, and nothing here shows that a score of 80 or 40 means what a navigator would want it to mean on real interference; no figure of that kind is given. The monitors' thresholds are likewise this project's own (Row A checks only their arithmetic). receiver_trust (score, monitors, live) tests/maritime_trust_reference.rs::t5_score_matches_the_clean_room_reading_of_the_documented_rule; receiver_trust::score::tests (monotone in every statistic, adding a monitor never raises the score, healthy statistics stay at 100)
Interference source region: a feasible emitter region from aircraft and ship position reports A feasible region for where a source of degraded navigation reports can be, from ADS-B (NIC/NACp) or AIS position reports: radio line of sight on a 4/3-earth radius from the report height and an emitter antenna height range, a limited effective range for the unknown power, affected units pulling the posterior toward their reach and unaffected units with line of sight pushing against it, grouped into sessions in time and space. Output is highest-density regions at stated confidence levels, a posterior centroid with a moment ellipse, session start, end, duration, affected area and distinct-aircraft count above the publication minimum, a time-of-day profile and hours per day. Terrain-free; a single source per session; the credibility is conditional on the model. Optional fusion with a TDOA fix from geolocation. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — None external yet. Synthetic forward-inverse round trips only, from a generator that shares the estimator's model, so they check the code and the calibration of the stated levels under that model and nothing about real emitters. An external check against the published Jammertest 2025 transmitter sites was pre-registered (docs/emitter-region/PREREGISTRATION.md, signed off by the owner before any scored run) and run once (docs/emitter-region/RESULTS.md): ADS-B NOT ASSESSABLE (2 scheduled sessions, fewer than the registered minimum of 4) and AIS NOT ASSESSABLE (no published session), so no bar was tested and the row stays MODELLED interference_map::emitter (estimate, sessions, build_units, profile, GaussianFix::from_tdoa), interference_map::emitter_out (locate), kshana interference-map locate interference_map::emitter unit tests (projection round trip, horizon figure, synthetic forward and inverse round trips: the known emitter lies inside the stated region at about the stated rate, edge cases, session clustering, profile, privacy and wording); tests/interference_map_cli.rs locate cases
Trust telemetry SIEM events: Log Event Extended Format (LEEF) over syslog Band-change (or per-epoch) events as Log Event Extended Format 2.0 payloads in an RFC 5424 envelope over UDP or TCP, with a documented field mapping. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — WHAT IS CHECKED: this crate's own exact-string tests of the documented LEEF field mapping, and the RFC 5424 envelope fields; no maintained open-source LEEF parser exists (a search of the Python package index found none), so the format is checked against its own specification read by the same author, not against an external oracle. WHAT IS NOT: whether the LEEF payloads are accepted by any vendor's parser or SIEM; the escaping rules beyond the documented ones; behaviour of a real syslog collector. telemetry (syslog: leef, rfc5424, SyslogSink; time) telemetry::syslog::tests (exact LEEF strings, escaping, severity, RFC 5424 envelope, delivery timeouts and reconnection); tests/telemetry_cli.rs
Receiver-trust interference thresholds calibrated on the JammerTest 2024 dataset receiver_trust::calibration::run_dataset: the pre-registered calibration of the C/N0-drop, AGC and jamming-indicator monitors on the public JammerTest 2024 dataset (Zenodo 15911589, GPL-3.0-or-later, fetched at run time, never vendored): per folder a 1 s timeline from mon_rf.csv and rinex.csv, the monitors run once, each post-calibration epoch labelled clean or jamming from the folder's attack_log (shifted from CEST to UTC, 60 s guard), every threshold swept over a fixed grid, the smallest threshold with pooled clean false-alarm probability at most 0.01 selected, and leave-one-folder-out held-out counts; a UBX reader cross-check. The selection ships only as the opt-in profile [monitors] profile = "jammertest-2024-calibrated" (cn0_drop_db 1.5, agc_k_sigma 3.5, jam_ind_threshold 29); the default rule and every output without it are unchanged ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — The dataset's published event logs (attack_log windows), as event truth, under the pre-registration xval/jammertest-trust/PREREGISTRATION.md (committed alone, 0987266, before the harness ran). First and only run (xval/jammertest-trust/RESULTS.md): 14 of 24 folders evaluable (7 with jamming), 3,502 clean and 9,560 jamming epochs. Held-out clean false-alarm probability: cn0_drop_db 0.0231 (81/3502) against a 0.02 bar, FAIL; agc_k_sigma 0.0003, pass; jam_ind_threshold 0.0094, pass; union of the three: false alarms 0.0328, detection 0.807 against 0.05 and 0.50, pass. By the registered rule the row is MODELLED (one bar failed). Narrow: one receiver type (u-blox ZED-F9P), one event, scheduled one-minute slots as truth (detection a lower bound; clean means outside the logged windows); calibrated on the CSV logs, and the UBX reader gives more false alarms on two folders. Maritime trust-score bands are not calibrated receiver_trust::calibration (run_dataset); receiver_trust::monitors (MonitorConfig::profile, JAMMERTEST_2024_CALIBRATED); realdata::jammertest; examples/jammertest_trust_calibration.rs tests/receiver_trust_jammertest_calibration.rs::the_recorded_calibration_reproduces (ignored, data-gated by KSHANA_JAMMERTEST_DIR: the recorded selection, held-out counts, bar verdicts and verdict); receiver_trust::calibration::tests (time stamps, window pairing and the time-zone shift, labels, guard bands, exclusion, selection); receiver_trust::monitors::tests::threshold_profile_is_opt_in
Jammertest scoring: a receiver log scored per scheduled test (detection latency, missed alarms, false alarms, time to recover) against the published test plan jammertest::{plan, score, dataset} (kshana jammertest import|score): the NPRA test catalogue and transmission plan (MIT, fetched with a pinned SHA-256, never vendored) read as scheduled truth with the catalogue ids preserved; a receiver-trust run scored per test (first alarm minus planned start, detected/late/missed against a tolerance, time to the first alarm-free stretch, alarms outside every slot and its guard), with a signed evidence pack that carries the scorecard. The schedule is planned slots, not recorded on-air times ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — The plan's slot counts per test area (76, 77 and 45 slots, of which 61, 63 and 32 transmit) were counted independently with a script over the same JSON; the 2024 dataset's attack_log windows as event truth, under xval/jammertest-score/PREREGISTRATION.md (committed alone, 123dc1e, before the scorer ran). First and only run (xval/jammertest-score/RESULTS.md): the registered minimum-data rule FAILED (4 scorable jamming windows from 4 of 12 UBX folders against a minimum of 10 windows from 2 folders: 5 folders dropped by the baseline rule, 3 UBX logs carry only GPS time of week), so bars B1 to B4 are not assessable; nothing was loosened or re-run. v2 (xval/jammertest-score/PREREGISTRATION-v2.md, committed alone, data handling only: GPS-time-only logs placed from the date, the 12 CSV-only folders, a moving-platform session for moving rovers; same bars and minimum-data rule): 14 of 24 folders kept but 7 scorable jamming windows, minimum-data rule failed again, no bar assessable (RESULTS-v2.md). Scheduled truth: a planned slot is not an on-air record, a miss may be a test that never ran, a latency is from the planned start, and clean means outside the planned slots. Detection by measurement-domain monitors says nothing about a low-power spoofer. One receiver type (u-blox ZED-F9P). The 2025 SimulaMet NMEA dataset is not used (no stated licence, subscription-gated) jammertest::plan (parse_catalog, parse_plan, import, import_attack_log, events_toml); jammertest::score (score_run); jammertest::dataset (run_dataset); jammertest (score_log, score_pack); examples/jammertest_score_2024.rs tests/jammertest_plan_roundtrip.rs (data-gated by KSHANA_JAMMERTEST_PLAN_DIR: slot counts per test area of the 2025 plan, catalogue ids, TOML round trip); tests/jammertest_score.rs (a synthetic log with a known drop: detected, missed, not-evaluable, false-alarm run, signed pack carrying the scorecard); jammertest::plan::tests; tests/jammertest_score_2024.rs (data-gated by KSHANA_JAMMERTEST_DIR: the recorded run)
Compliance mapping to public frameworks compliance (kshana compliance-report): a mapping from Kshana outputs to clauses of public frameworks by number only, filled from the runs given; a result counts for a capability only when it carries the evidence the mapping names, an empty set evidences nothing, and the wording is "supports evidence for"; the report is not a finding that any framework is met and not a rating or approval by anyone. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — References checked against a script-extracted heading index of the cited public documents read 2026-10-10 (tests/compliance_references.rs). WHAT IS CHECKED: 49 cited clause, section, paragraph or heading references exist in the cited document, and 7 cited URLs resolved on the recorded date (2 via a second route); negative controls fail. WHAT IS NOT: that any paraphrase, mapping or gap is correct; EN 16803 clauses (paid, catalogue text only); later revisions; the index is not an independent implementation. compliance tests/compliance_report.rs::mapping_is_well_formed; tests/compliance_report.rs::wording_rule_holds_in_mapping_report_and_docs; tests/compliance_report.rs::empty_set_evidences_nothing; tests/compliance_report.rs::statuses_follow_the_runs_present; tests/compliance_references.rs
Marine integrations: Signal K plugin, OpenCPN gate stream and score panel, reference build The trust score, band, reasons, gate state and receiver-reported position published under navigation.gnss.kshana in a Signal K server with a warn, alarm and normal notification (integrations/signalk); the gated NMEA stream, with the fix marked invalid while trust is collapsed and a PKSHT sentence per cycle, served to OpenCPN over TCP by the gate itself or by a small relay, and a native OpenCPN score panel that reads the PKSHT sentence (integrations/opencpn); and systemd units and a container that run the gate (deploy/reference-build). Where these show output they carry the advisory statement: Advisory software, not type-approved navigation equipment (IEC 61108, IEC 61162): the operator remains responsible for the navigation of the vessel. IntegrationRun exercised against a real host application; an integration run is not an independent oracle — WHAT IS CHECKED, stated narrowly: that these integrations work against the real software they are written for. EVIDENCE is committed at integrations/signalk/evidence/README.md (with its JSON files) and integrations/opencpn/evidence/README.md (with its screenshots and logs), each with the script that reproduces it. (1) Signal K: the plugin loaded into the pinned signalk-server 2.33.0 npm package, in a private loopback-only network namespace, fed synthetic data. The server's own REST and WebSocket interfaces showed the published paths, the score metadata, and a notification that went absent, warn, alarm, normal (after the hold) and warn again when the data stopped. With the real kshana run by the plugin on the NMEA the server itself received, the notification went warn then alarm and the reported position was published; the server's own navigation.position was written by its NMEA provider, never by the plugin. Re-run against live JSON schema 1.2. (2) OpenCPN: the plugin built against the OpenCPN plugin API header and wxWidgets 3.2.4, loaded into the Ubuntu 24.04 package of OpenCPN 5.8.4 under a virtual display; OpenCPN loaded it, ran its initialisation and handed it the PKSHT sentences of the gated stream, and the panel turned red on the untrusted band. In one clean run, OpenCPN's own ship position stopped updating, and its fix indicator dropped, when the gate marked the fix invalid. A second run fed directly by the gate's TCP listener showed delivery to the plugin but not a clean before-and-after. (3) The relay tests replay a recorded excerpt of the gated stream through a real TCP socket and check what a consumer receives (the bytes unchanged, valid checksums on every sentence including the rewritten ones, GGA and RMC agreeing, one PKSHT per cycle with the gate field where the fix is invalid), and the end-to-end script checks that a consumer of the gate's listener receives exactly the bytes the same gate writes to standard output. (4) The PKSHT parsers (JavaScript and C++) are run over sentences recorded from kshana output and reject a wrong checksum, version or a score outside 0 to 100. (5) The systemd units are checked with systemd-analyze verify (systemd 255, binaries stubbed) and with guards for a shell in ExecStart, the restart policy and the sandbox keys; the container entrypoint's argument handling is checked with a stub binary. WHAT IS NOT: there is no external oracle for any value these integrations show. The trust values themselves are the rows above, and an integration run shows only that the plumbing carries them; that is why this row is MODELLED and not VALIDATED (docs/VALIDATION.md). No real vessel, receiver, long run, other version of either host, other operating system or desktop was used; all data are synthetic text and nothing here is a measurement. The notification's sound and visual handling by a real Signal K client, OpenCPN's toolbar button, preferences and stale state, and packaging for the OpenCPN plugin manager were not exercised. The systemd sandbox keys were checked for syntax only, not run under a live systemd, and the container image build and its health check have no committed evidence here. No detection or false-alarm figure is claimed. Advisory software, not type-approved navigation equipment (IEC 61108, IEC 61162): the operator remains responsible for the navigation of the vessel. receiver_trust (live: the gate, its TCP listener, PKSHT); outside the crate: integrations/signalk (JavaScript), integrations/opencpn (JavaScript relay, C++ native plugin), deploy/reference-build (systemd units, container) tests/receiver_trust_live_cli.rs (the gate and its TCP listener, Rust side); integrations/signalk/test/adapter.test.js, integrations/signalk/test/model.test.js and integrations/signalk/test/plugin.test.js (24 Node tests on recorded synthetic output); integrations/opencpn/test/relay.test.mjs (5 Node tests); integrations/opencpn/test/e2e-live.mjs (the real binary to a TCP consumer, run by hand and in CI); integrations/opencpn/plugin/test/pksht_test.cpp and integrations/opencpn/plugin/test/trust_state_test.cpp (C++ checks of the PKSHT parser and the panel state); deploy/reference-build/check-units.sh and deploy/reference-build/test-entrypoint.sh
BOC(1,1) tracking: DLL scaling and bump-jump ambiguity resolution (opt-in) The boc field of iq::track::LoopConfig (opt-in, None by default): the three DLL discriminators rescaled to read the code error in chips with unit slope on the sine BOC(1,1) main peak, and a bump-jump monitor on very-early and very-late correlators at one subcarrier half-period (0.5 chip) that jumps the code NCO towards the main peak when an up/down counter reaches N (8 by default). Without the option every output is unchanged. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency against injected truth and closed forms, under bars pre-registered at 700d95df (docs/design/evidence/boc-bump-jump/). A BeiDou B1C data signal (PRN 19, 5 MS/s) generated by iq::scene: with the option off a side-peak start stays false-locked at the predicted ±(0.5 + d/4) chip (measured ±0.549); with it on, one jump towards the main peak at 0.08 s and a late-window RMS of 0.0008 chip at 45 dB-Hz and 0.0048 chip at 35 dB-Hz; no jump from the main peak at 35, 40 and 45 dB-Hz over 4 s; the scaled EMLP slope 0.94 to 0.99 on the sampled signal (unscaled 3.6 to 3.8). The bump-jump detector alone, on correlator triples with the exact BOC(1,1) noise covariance, made no false jump in 100 000 updates at 25 to 45 dB-Hz and detected 1000 of 1000 side-peak starts at 35 dB-Hz. NOT MET (finding F1): the pre-registered unit-test grid for the scaling includes offsets outside the discriminators' linear range, where the scaled readings miss the offset by up to 48 %. RE-RUN 0.41 (D8a row 5, 19c6b3518): MET on re-run with the opt-in exact inverse of each discriminator on the ideal BOC(1,1) peak (the linear scaling stays the default; every existing output unchanged): all 27 grid points within 10 % (worst 4.6e-15, by construction, stated in advance); sampled-signal slopes 0.995 to 1.011 (linear 0.938 to 0.994); B1, B2, B3 and B5 hold on registered and fresh seeds. WHAT IS NOT CHECKED: field IQ, band-limited front ends, composite MBOC/QMBOC replicas, and any external receiver. iq::track::boc (BocKind, BocTracking, BumpJump, boc11_dll_scale); iq::track::channel (the bump-jump taps and Channel::bump_jumps) tests/iq_boc_bump_jump.rs (b1_b2_b3_side_peak_and_false_jumps_on_the_iq_chain, b4_scaling_on_the_sampled_signal, b5_false_jump_rate_and_detection_at_correlator_level); iq::track::boc unit tests (b4_unit_grid_misses_are_the_recorded_ones: the pre-registered B4 unit-test bar kept as written, its recorded misses asserted as finding F1)
IQ ionospheric scintillation channel (Cornell model) against measured 50 Hz GPS L1 scintillation iq::channel::scint, the Cornell scintillation model (Rice intensity, second-order Butterworth spectrum, phase arg z) driven at a measured window's S4 and intensity decorrelation time, compared on what it generates beyond those two inputs; realdata::scint50 reads the measured log, detrends it and runs the comparison. ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — Measured data under bars pre-registered at 653a2195 (xval/scint-malindi/): Zenodo record 16941224 (INGV, Malindi, 18 March 2023, GPS PRN 26, 50 Hz intensity and carrier phase, CC BY 4.0, SHA-256 checked). 22 qualifying 60 s windows (N1 met). MET: the intensity distribution (Kolmogorov-Smirnov D 0.0415, bar 0.05) and the phase scintillation tied to S4 (median measured/model sigma-phi 0.779, bar 2/3 to 3/2). NOT MET (finding F1): the model's deep-fade fraction is 2.38 times the measured (bar 0.5 to 2) and its mean fade 3.51 times as long (bar 2/3 to 3/2). Finding F2: the registered processing reads the model's wrapped phase, which a self-check exposed; B3 repeated post hoc with the phase unwrapped gives 0.804. WHAT IS NOT CHECKED: other nights, stations, latitudes or signals; receiver noise in the model. The row stays MODELLED. iq::channel::scint (Scintillation, ScintParams); realdata::scint50 (parse_log, segments, measured_windows, model_windows, compare) tests/iq_scint_malindi_measured.rs (cornell_model_verdict_is_the_recorded_one, the registered verdict asserted as recorded, finding F1; finding_model_fades_are_deeper_and_longer_than_measured; posthoc_b3_with_the_model_phase_unwrapped, reported only; data-gated, fetched by scripts/fetch_scint_malindi.sh); realdata::scint50 unit tests (model_data_through_the_harness_shows_the_wrapped_phase_finding, finding F2)
Cell-averaging CFAR option in IQ acquisition iq::acq::ca_cfar and ca_cfar_cells (opt-in): a cell of an acquisition grid is compared with the mean of reference cells of its Doppler row (guard and stride lags, wrapping round the period), at a factor alpha set from the closed-form CA-CFAR false-alarm probability for M non-coherent blocks (ca_cfar_pfa, ca_cfar_alpha). The sample-power detector stays the default and every existing output is unchanged. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Closed form, under bars pre-registered at 8af30331 (docs/design/evidence/acq-cfar/). The CA-CFAR false-alarm probability for Gamma(M) cells, against Monte Carlo of the exact model: 18 of 18 cases within 3 binomial sigma. On every cell of iq::acq searches (GPS L1 C/A, 2.5 MS/s, 210 000 cells each) at a design 1 %: 0.977 % and 0.969 % on Gaussian noise and 1.006 % and 0.999 % on 2-bit quantised noise (M = 1 and 4; bar plus or minus 20 %); decisions unchanged when the input is scaled. NOT MET (finding F1): on a noise-free 2-bit signal the detection and its cell are right, but 1.28 % of the off-peak cells of the peak's row (bar 1 %) exceed the threshold, at the code's deterministic correlation sidelobes. RE-RUN 0.41 (D8a row 3, 1059c34e8): MET on re-run with the opt-in row reference set (CfarConfig::with_reference: reference cells every stride-th lag round the whole Doppler row): 0 of 2495 off-peak cells above on the registered signal and 3, 4, 0 and 0 on four fresh signals (bar 1 %), all detected in the right bin; C2/C3 0.969 to 1.033 % on seen and fresh seeds; the 16-cell window stays the default and its control reproduces 0.40. One candidate tried, on development PRNs 2-6 (disclosed). WHAT IS NOT CHECKED: other CFAR variants, two-dimensional windows, band-limited front ends, field data. iq::acq (CfarConfig, ca_cfar, ca_cfar_cells, ca_cfar_pfa, ca_cfar_alpha) tests/iq_acq_cfar.rs (c1_closed_form_matches_monte_carlo_of_the_exact_model, c2_false_alarm_rate_on_gaussian_noise, c3_false_alarm_rate_on_two_bit_noise, c5_decisions_do_not_depend_on_the_input_scale; c4_noise_free_two_bit_signal_verdict_is_the_recorded_one, the registered verdict asserted as recorded, finding F1, pinned by finding_noise_free_sidelobes_exceed_the_cfar_rate); iq::acq unit test ca_cfar_closed_form_reduces_to_the_textbook_case_and_inverts
Spectrum model: GLONASS, BeiDou and Galileo E6 bands (opt-in) spectrum::default_band resolves, by name only (MORE_BAND_NAMES), GLONASS L1OF and L2OF on every FDMA channel K = -7 to 6 (BPSK, 0.511 Mchip/s), BeiDou B1I (BPSK(2)), B1C (MBOC(6,1,1/11)), B2a and B3I (BPSK(10)) and Galileo E6 (BPSK(5)), with the carriers and minimum received powers of their interface control documents; the default band set and every existing output are unchanged. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Published interface control documents and closed forms, under bars pre-registered at 502af4a7 (docs/design/evidence/spectrum-bands/): GLONASS ICD Edition 5.1, BDS-SIS-ICD B1I 3.0, B1C 1.0, B2a 1.0 and B3I 1.0, Galileo OS SIS ICD Issue 2.1. MET: every carrier, chip rate and received power as transcribed (28 GLONASS channels), BPSK first nulls at the chip rate, the B1C composite equal to MBOC(6,1,1/11) as its ICD's power table gives, the C/N0 path identity, and byte-identical spectrum scenarios. NOT MET: the unit-area bar, which was unattainable as written (finding F1; the areas equal the closed-form in-band fraction), and the per-bin agreement of the IQ layer's B1I and B1C waveforms with the model envelope (1.26 and 1.56 dB against 0.5 dB, finding F2; GLONASS 0.07 dB), because Gold and Weil codes have uneven line spectra; band-averaged the main lobes agree within 0.25 dB. WHAT IS NOT CHECKED: recorded IQ, other signals, intra-system interference. spectrum (default_band, MORE_BAND_NAMES, GLONASS_CHANNELS) tests/spectrum_more_bands.rs (s1_new_bands_carry_their_icd_values, s2_nulls_and_b1c_parts, s4_cn0_paths_agree_on_the_new_bands; s2_closed_form_densities_verdict_is_the_recorded_one, finding F1, pinned by finding_s2_areas_are_the_closed_form_in_band_fraction; s3_iq_layer_verdict_is_the_recorded_one, finding F2, pinned by finding_s3_per_bin_errors_follow_the_code_line_spectrum; posthoc_s3_band_averaged_shape, reported only)
LunaNet AFS tertiary codes and message layer (SB1 BCH, CRC-24Q, interleaver) against LSIS-AFS V1.0 iq::signals::lunanet::afs_q_tertiary_bits, afs_q_tiered; iq::lunanet_afs: synchronisation pattern, SB1 BCH(51,8) encoder and 256-hypothesis decoder, CRC-24Q, the 60 x 98 block interleaver, a symbol-stream checker (kshana lunanet-afs-check) and a test-stream generator with placeholder subframes. The rate-1/2 LDPC coding of subframes 2 to 4 is not implemented (its matrices are in a separate annex). ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — LSIS-AFS V1.0 (as above): the length-1499 Legendre sequence (Table E-1, identical) and the tertiary first and last 24 chips (Tables E-2 to E-6: 419 of 420 columns identical; the document prints the same last 24 chips, A14850, for PRN 147 and PRN 151 and the generator reproduces PRN 151's, so the PRN 147 entry is most likely a misprint; the bar of 420 of 420 is NOT MET and the miss is pinned); the Figure 8 worked example of the SB1 code (one example: 0x045 encodes to 0x229F61DBB84A0); CRC-24Q against the catalogue check value 0xCDE703 for ASCII 123456789; the document's own frame arithmetic. Bars pre-registered at e9d5e69. One miss on record and one worked example for the message layer, so the row stays MODELLED. WHAT IS NOT CHECKED: LDPC and the CRC words inside subframes 2 to 4, message content, and any recorded stream iq::lunanet_afs; iq::signals::lunanet (afs_q_tertiary_bits, afs_q_overlay_bits, afs_q_tiered); surface (lunanet_afs_check_spec, lunanet_afs_check_symbols, lunanet_afs_generate) tests/lunanet_afs_codes.rs (b4_legendre_1499_matches_and_tertiary_codes_match_except_one_printed_column, the_spec_check_reports_every_bar_and_pins_the_b4_miss); iq::lunanet_afs::tests (sb1_round_trips_every_field_and_corrects_flipped_symbols, generated_streams_pass_and_damage_is_found); tests/lunanet_afs_cli.rs
Standards packs: scenarios scored against bars stated before the run standards_pack (kshana standards-pack): the DHS Resilient PNT framework test profiles for levels 1 to 4, IMO MSC.1/Circ.1575 accuracy levels and integrity evaluation, and ICAO Doc 9849 Appendix F monitor, assess and mitigate packs: each test runs a bundled scenario kind and compares result fields with bars stated in the pack, and tests that need a receiver log are listed as NEEDS INPUT and not scored. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — None external for the scenario results: every pack test runs a MODELLED scenario kind. The bars are the pack author's stated profile (the DHS framework states no values; the IMO accuracy limits are Table C-1 of MSC.1/Circ.1575, read in full; the ICAO pack follows ICAO's own RFI Mitigation Plan presentation because Doc 9849 is a paid publication and was not read), committed before any scored run in xval-style PREREGISTRATION.md files under standards/. A MET bar says a modelled scenario met a stated bar, nothing about a product standards_pack; compliance (standards-pack facts in compliance-report) tests/standards_packs.rs (pinned_outcomes: the status of every test, including the misses L4-T1 and the four IMO accuracy tests); standards_pack::tests
Laboratory round-trip evidence pack (scenario, test conditions, receiver log, score) evidence::roundtrip (kshana evidence round-trip) and the kshana.test-conditions/1 receiver-log export of kshana bench-export: a signed pack that records the scenario hash, the stated conditions' hash, the log hash and the score against the stated events, and refuses conditions that disagree with the scoring events or a log whose hash is not the stated one. No signal is written, replayed or scheduled. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — None external: the pack links hashes and a MODELLED receiver-log score, checked on synthetic data (the exported NMEA of a bundled scenario treated as the receiver's log). No laboratory run is claimed evidence::roundtrip, evidence::assemble, interop::testbench (write_conditions_json), iq::campaign::conditions tests/round_trip_pack.rs (pack_links_scenario_conditions_log_and_score_and_verifies, conditions_that_disagree_with_the_scoring_events_are_refused, a_stated_log_hash_that_does_not_match_is_refused, published_schema_names_every_field_the_engine_writes)
IQ tracking engine against GNSS-SDR 0.0.19 on independent recordings The full IQ-layer tracking engine (iq::track through kshana iq track: acquisition hand-off, correlators, NCOs, second-order 15 Hz Costas PLL, first-order 2 Hz carrier-aided EML-envelope DLL, lock indicator and C/N0 estimators) on GPS L1 C/A at 30 to 45 dB-Hz. ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — GNSS-SDR 0.0.19 (GPL-3.0-or-later, the Ubuntu 24.04 package, run as a separate program; only derived numbers committed) tracking the same numpy recordings (independent of the engine), both measured against the analytic truth. Bars pre-registered at b1f25cce, amended before any test recording at 9496b6b0 (a 10 Hz FLL during pull-in only in both receivers, after the registered calibration failed on a wrong GNSS-SDR hand-off, finding F3). MET at 30, 35, 40 and 45 dB-Hz: carrier jitter within 4.3 %, code jitter within 4.6 % and Doppler mean and spread of GNSS-SDR's. NOT MET: the engine's NWPR C/N0 reads 2.3 to 7.1 dB below GNSS-SDR's SNV (finding F4, the known NWPR limit; its M2M4 is within 0.06 dB of truth); the phase lock indicators differ by definition (F5); at 30 dB-Hz GNSS-SDR slipped twice and the engine not (F6). GNSS-SDR's own hand-off locked to a wrong frequency in 3 of 30 calibration runs. WHAT IS NOT CHECKED: other signals, data-bit wipe-off, re-acquisition, field recordings. The row stays MODELLED. iq::track (Channel, LoopCore, design); iq::cli::track tests/iq_track_gnss_sdr_oracle.rs (calibration_passes_for_both_receivers, registered_bars_give_the_recorded_verdict, recorded_numbers_are_pinned), on numbers derived by tests/fixtures/iq_track_gnss_sdr_oracle/make_fixture.py
CRPA antenna gains in the jamming kind against an independent numpy recomputation The jamming kind's optional [crpa] section: a per-channel beam toward each satellite (null-steering with the jammer as the null, or MVDR on sigma^2 I + P_j a_j a_j^H), scaling each link's noise by ||w||^2 and the jammer by |w^H a_j|^2 before the existing anti-jam C/N0 equation. ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — An independent numpy recomputation (xval/crpa-jamming/oracle.py, no shared code: numpy steering vectors, numpy.linalg.solve and inv) of every link of the jamming-demo geometry with a 4-element square array, under both weightings. Bars pre-registered at 716de66a. MET: A1 (all 150 scenario results byte-identical without the section, after a fix: the first build added the crpa units to every jamming run's units table), A2 (one element equals no array to 1e-12 dB), A3 on the array noise gain and effective C/N0 (912 link-weightings within 1e-9 dB, worst 2.1e-14 dB) and on the null-steering jammer null (below -200 dB on both sides), A4 (MVDR within 0.1 dB of null-steering at a JNR of 80 dB). NOT MET: A3 on the MVDR jammer gain, 194 of 456 links over 1e-9 dB on 0.36 portable maths (202 on host maths; docs/revisions/STUDIO15-batch4-rebaseline.md) (worst 1.7e-6 dB) on residuals of -100 to -188 dB, where float64 cancellation limits both implementations (numpy's inv and solve disagree with each other on 169 links, worst 7.9e-7 dB); the effective C/N0 these feed is unaffected. WHAT IS NOT CHECKED: mutual coupling, element mismatch, wideband processing, multiple jammers, any antenna hardware. A recomputation of the same equations, not an external oracle; the row stays MODELLED. jamming (CrpaCfg, crpa_weights, run_jamming); crpa (null_steering_weights, mvdr_weights, covariance) tests/jamming_crpa.rs (a1_crpa_units_only_with_the_section, a2_one_element_is_no_array, a3_verdict_is_the_recorded_one, a4_mvdr_tends_to_the_null_at_high_jnr), against xval/crpa-jamming/expected.json from xval/crpa-jamming/oracle.py
Terrain shadowing of the jammer in the jamming kind against an independent numpy recomputation on a real SRTM tile The jamming kind's optional [terrain] section: the great-circle terrain profile between jammer and receiver on an SRTM .hgt tile with a k-factor Earth bulge, the dominant knife edge (largest Fresnel-Kirchhoff nu) and the single knife-edge loss of ITU-R P.526-15 section 4.1, subtracted from the jammer's received power. ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — An independent numpy recomputation (xval/jamming-terrain/oracle.py, no shared code: its own .hgt read, bilinear interpolation, WGS 84 round trip, profile, bulge, nu and J(nu)) of ten jammer placements around a receiver at Badwater Basin on the committed real SRTM tile tests/fixtures/terrain/N36W117_sub6.hgt. Bars and placements pre-registered at 3b0ebdd4. All MET: additivity (all 150 scenario results byte-identical without the section); every placement's profile points and obstacle equal and nu and loss within 1.6e-10 (bar 1e-9); the loss never rises as the jammer rises from 2 to 4902 m; the loss lowers every J/S by exactly itself and nothing else; J(nu) within 1e-12 dB of the oracle's. Findings: placements across the Black and Funeral Mountains lose 44 to 48 dB; two valley-floor placements lose 8 and 15 dB from the Earth bulge alone at 2 m antenna heights, the single knife-edge model's grazing case. WHAT IS NOT CHECKED: any measured propagation, multiple-edge diffraction, ground reflection, clutter, the DEM's own error. A recomputation of the same model, not an external oracle; the row stays MODELLED. jamming_terrain (TerrainCfg, jammer_terrain, knife_edge_loss_db); jamming (run_jamming_sky) tests/jamming_terrain.rs (b1_terrain_units_only_with_the_section, b2_every_placement_matches_the_independent_numpy_recomputation, b3_the_loss_never_rises_as_the_jammer_rises, b4_the_loss_reaches_every_js_and_nothing_else, b5_the_knife_edge_function_matches_the_reference_expression), against xval/jamming-terrain/expected.json from xval/jamming-terrain/oracle.py
Acquisition hysteresis and the front-end quantiser in the jamming kind against independent recomputations The jamming kind's optional [acquisition] section (a satellite is acquired at or above an acquisition threshold after a re-acquisition delay and held while at or above the tracking threshold) and [front_end] section (the AGC reading 10 log10(1 + J/N) and the ADC's Gaussian-input quantiser loss taken off every link, flagged as not valid for non-Gaussian jammers). ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — An independent Python recomputation of every acquisition flag (xval/jamming-acq-agc/hysteresis.py) from the engine's per-epoch effective C/N0, an independent numpy Monte Carlo of the quantiser loss (xval/jamming-acq-agc/quantiser_mc.py, its own optimum-step search, 2^22 samples), and the IQ layer's AGC loop. Bars pre-registered at 2ca31ee1, with a supplementary run set at 2ef7427a. MET: additivity (all 150 scenario results byte-identical without the sections); every flag equal on the supplementary runs (1824 links, 732 of them showing the hysteresis); monotone in the threshold; the quantiser loss within 0.0007 dB of the Monte Carlo at 1 to 4 bits (bar 0.02 dB); the AGC reading within 0.012 dB of the AGC loop (bar 0.05 dB). NOT MET: the registered hysteresis runs (jamming-demo at 10 to 30 dBW) were uninformative, with every link lost, and their H2 and H4 are met only trivially. RE-RUN 0.41 (D8b row 7, 0ea0da3df): MET on re-run on a 12-power ladder fixed from the scenario file before any engine run (-34 to -21 dBW): 2614 of 5472 link-epochs in the informative 25-32 dB-Hz band (bar 10 %); H2 and H4 hold; all 5472 flags agree with hysteresis.py, 2626 showing the hysteresis; no engine change. Disclosed: the ladder rule was written after supplement 1 had shown where the thresholds lie. Finding: with a CW jammer a 1-bit ADC loses about 5 dB more than the Gaussian figure the engine applies, and flags as not valid. WHAT IS NOT CHECKED: the acquisition search itself, AGC dynamics in time, any receiver hardware. Recomputations of the same model, not an external oracle; the row stays MODELLED. jamming_rx (AcquisitionCfg, AcqState, FrontEndCfg, front_end); jamming (run_jamming_sky); iq::frontend::quant (optimum_step_sigma) tests/jamming_acq_agc.rs (h1_g1_units_only_with_their_section, h2_no_hysteresis_is_no_hysteresis, h2s_no_hysteresis_is_no_hysteresis_on_the_supplementary_runs, h3_flags_match_the_independent_recomputation, h3s_flags_match_the_independent_recomputation_on_the_supplementary_runs, h4_monotone_in_the_acquisition_threshold, h4s_monotone_in_the_acquisition_threshold_on_the_supplementary_runs, g2_quantiser_loss_matches_the_independent_monte_carlo, g3_agc_reading_matches_the_iq_layer_agc_loop), against xval/jamming-acq-agc/expected_hysteresis.json, expected_hysteresis_s1.json and expected_quantiser.json
Capped FLL pull-in below the default design's FLL-to-PLL hand-over floor (opt-in) iq::track's opt-in carrier.fll_pull_in_max_s (the fll_pull_in_max_s field of iq::track::LoopConfig): under fll_assist = pull-in, the FLL hands over to the PLL after a fixed pull-in time whatever the PLI, with a matching return dwell until the PLI first reaches fll_off_pli. InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Internal consistency against injected truth: a synthetic data-free GPS L1 C/A source (PRN 13, 1500 Hz, 4.1 MHz, 8 s, ten noise seeds) whose carrier phase is known, under bars pre-registered at 8aceabcb (docs/design/evidence/fll-handover-floor/). MET: the control (the uncapped default never hands over in 9 of 10 seeds at 33 dB-Hz); additivity (default hash and the existing tracking tests unchanged); pull-in of a 100 Hz-off hand-off at 45 dB-Hz. NOT MET: with a 1.0 s cap, hand-over and hold in every run (16 of 20 at 33 dB-Hz, 8 of 20 at 31 dB-Hz; the rest cycle between forced hand-overs and the FLL's return) and phase jitter within 25 % of the PLL alone (10.8 against 6.1 degrees at 33 dB-Hz). RE-RUN 0.41 (D8a row 4, 74ba62787): with the opt-in carrier.fll_handover_mean_s (the PLL seeded at the mean NCO Doppler of the pull-in's last 0.5 s), still NOT MET: at 33 dB-Hz hand-over and hold 20 of 20 on seen and fresh seeds with jitter within 1 % of the PLL alone (this half met), but at 31 dB-Hz 15 of 20 seen and 6 of 20 fresh, jitter ratio 1.8 and 2.8. Development seeds 1001-1010 recorded, nothing tuned on them. WHAT IS NOT CHECKED: data bits, other signals and sample rates, field recordings. The default is unchanged; the row stays MODELLED. iq::track (LoopConfig, FllGate, design); iq::track::channel (the FLL gate) tests/iq_fll_handover_floor.rs (registered_bars_give_the_recorded_verdict, d1_the_key_is_part_of_the_hash_only_when_set, d4_the_capped_design_pulls_in_a_100_hz_handoff_error), on tests/fixtures/fll_handover_floor/results.csv
Write a JPL Horizons state table as a CCSDS OEM, a CCSDS OPM or an SPK kernel, and read it back kshana ephem-export (and ephem_export in Python, WebAssembly and MCP): a JPL Horizons vector table is written as a CCSDS OEM 2.0, an OPM 3.0 or an SPK of type 13 or 9 (frame code 1, ICRF). Values and epochs are copied, not computed, and the engine reads the written file back and reports the comparison ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — The engine's own reader on the files it wrote (same codebase). The C7 reference integration has no bar: Orekit 13.1.9 and Basilisk 2.12.2's SPICE read the files back exactly (Orekit's km to m conversion named as rounding further), and ANISE 0.10.6 evaluates the SPK no further from the written states than SPICE does; GMAT is not done until its CI job is green. A one-off check outside the repository found the SPK byte for byte equal to the kernel SPICE's spkw13 writes from the same states. Carries data only; says nothing about any propagation ephem_export tests/ephem_export_capstone.rs (4321 of 4321 CAPSTONE states read back with the same bits from the OEM and the SPK; the SHA-256 of each file pinned through the CLI); the flight-dynamics workflow (integrations/flight-dynamics/: Orekit, Basilisk and ANISE notebooks; docs/design/evidence/c7-flight-dynamics-adapters/RESULTS.md)
Optical-navigation measurement model: apparent direction, pinhole projection with distortion, and partials opnav::measure: the apparent direction of a body centre (converged Newtonian light time and stellar aberration, the SPICE CN+S correction) or of a catalogue star (aberration only), projected through a pinhole camera with Brown-Conrady distortion in the OpenCV projectPoints convention at a given attitude quaternion, with the partials of the pixel with respect to the spacecraft position and velocity ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — SPICE (spiceypy 8.3.0, CSPICE N0067) and OpenCV 5.0.0, under bars pre-registered in docs/design/evidence/c5a-optical-navigation-model/: O1 body directions within 0.0016 mas of SPICE CN+S (bar 1 mas), O2 stars within 3e-8 mas, O3 projection within 1.3e-11 px of OpenCV, O4 end to end within 3.8e-8 px (bar 1e-4 px), O6 additivity: MET. O5 NOT MET: 258 of 432 partial elements differ from central differences at the registered 1 m and 1 mm/s steps by more than 1e-6 relative (the largest elements agree to about 1e-7 to 1e-9; a no-bar diagnostic at 1 km and 1 m/s cuts the worst relative difference from 1.0 to 8e-4, pointing to difference round-off, not proven). RE-RUN 0.41 (C5a v2, PREREGISTRATION-v2.md, 755bb1719): O5 v2 MET against an independent complex-step oracle (xval/c5a-opnav-v2/): the analytic partials agree within 2.3e-11 of each row's largest element on 72 measurements, v1's 36 and 36 fresh (bar 1e-6 of the row's largest element, chosen after v1 and weaker than v1's for small elements; the oracle's own values within 3.6e-8 mas of SPICE and 4.6e-11 px of OpenCV); O1 to O4 on the 36 fresh measurements met (3.7e-3 mas, 2.3e-8 mas, 4.7e-11 px, 8.4e-8 px); observer-relative central differences, reported with no bar, still put 144 of 288 rows above 1e-6 (worst 4.0e-5 of the row's largest). v1's O5 NOT MET stands as recorded. WHAT IS NOT CHECKED: image processing, the body's figure or phase, attitude error, any real camera opnav tests/c5a_opnav.rs (36 measurements against the committed SPICE and OpenCV oracle output; the recorded verdicts asserted, the O5 miss included); tests/c5a_opnav_v2.rs (the v2 partials against the complex-step oracle output on 72 measurements)
CAPSTONE NRHO propagation with DE440 third bodies and one radiation-pressure parameter c3_force::C3Model: the A2 lunar force model with the Sun and Earth from a DE440 kernel plus Venus and the Jupiter system barycentre as point masses (M1), and optionally cannonball radiation pressure k = Cr A/m with Earth and Moon conical shadows (M2). With no kernel and no radiation pressure it is the A2 model bit for bit ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — JPL Horizons reconstruction of CAPSTONE (-1176), under bars pre-registered in docs/design/evidence/c3-capstone-nrho-force-model/. C3-R MET on A2's window W0 (21.66 km end position, 4.24 km periapsis; bars 25 and 10 km). C3-H NOT MET on the held-out windows E, H1, H2 (end position 37.25, 36.23, 49.65 km; periapsis met). C3-S NOT MET (k fitted on E: H1 12.92 km met, H2 57.13 km). A2 is not met on re-run. RE-RUN 0.41 (C3 v2, PREREGISTRATION-v2.md, cc8c300a0): C3-S v2 MET on the fresh span G (Horizons -1176, 2023-07-01 to 2023-09-28) with k estimated per window from its first 78 samples (M3): end position 0.21, 0.60 and 0.73 km and periapsis radius 11, 4 and 87 m on G1, G2 and G3 (bars 25 km and 10 km); G1 is marked low-information (a 10 m or 1 cm/s change in its start state moves the end position by up to 18.1 km) and its verdict counts as registered. M1 alone also meets both bars on G (5.07 to 13.63 km, periapsis 2.07 to 4.68 km), so G is a less demanding span than F; with its own k, H2 is still missed (57.82 km, no bar). v1's C3-H and C3-S NOT MET stand. Nothing here identifies CAPSTONE's real area-to-mass ratio. The reconstruction is the reference, not truth c3_force tests/c3_force.rs (kernel off equals A2 bit for bit; radiation term against its closed form and zero in both umbrae; the control on W0, gated); tests/c3_verdicts.rs (the recorded verdicts, misses included); tests/c3_verdicts_v2.rs (the committed G windows and k values; the recorded v2 verdict)
Impulsive steps in the cislunar coast and the C2 step detector The tli-and-cruise phase's optional impulses list (t_s from the phase start, dv_mps in GCRF) adds each step to the mean state, shortening a step to land on it; without impulses every output is unchanged. mission_thread::impulses::detect flags hours whose one-hour velocity residual exceeds 0.01 m/s and gives one impulse per event hour at its midpoint ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — JPL Horizons reconstruction of Artemis I (-1023), under bars pre-registered in docs/mission-thread/PREREGISTRATION-C2.md: NOT MET on W1 (17.3 km against 2 km; 0.0177 m/s against 0.01 m/s); W2 not run (the published burn times leave 42.8 h, not 72 h). A diagnostic after the verdict shows four of the five steps in the reconstruction carry position jumps no velocity step within one hour can produce. v2 (docs/mission-thread/PREREGISTRATION-C2-v2.md, 036c3f1be): NOT RUN. By the registered rule a fresh 72 h window W3 after W1 needs at least 120 h between published burns (24 h clear on each side); the longest gap after W1 in NASA's published Artemis I timeline is 105.9 h (return trajectory corrections 4 to 5), so W3 does not exist. No v2 code was written and no Horizons state of any v2 period was fetched (xval/mission-thread-c2-v2/README.md); v1's NOT MET stands. The impulse support itself is checked on synthetic data only mission_thread::impulses tests/mission_thread_c2_impulses.rs (synthetic only: start impulse equals a changed start velocity bit for bit; a mid-phase impulse equals stopping, adding and continuing; two known mid-hour steps recovered; malformed tables refused); tests/mission_thread_c2_verdict.rs (the recorded verdict, the miss included)
Space RF geolocation bounds for a surface emitter seen from low Earth orbit: one satellite, two- and three-satellite formations, and several passes fused space_geoloc: the constrained Cramer-Rao bound (the emitter on the WGS 84 ellipsoid) of a static surface emitter from one satellite's frequency of arrival over a pass (S1), from a two- or three-satellite formation's time and frequency differences (F2, F3), and from several passes fused (MP), with the noise per measurement from a free-space link budget; space_geoloc::ccrlb_with_receiver_errors adds receiver position and velocity errors as Gaussian nuisance parameters (Cao et al. 2015), and space_geoloc::solve_f3 is a Gauss-Newton estimator for F3 ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — Bars pre-registered in docs/design/evidence/m1-space-rf-geolocation/ (results a41eb6d06). All MET: B1, an independent numpy recomputation (xval/m1-geolocation/oracle.py, no shared code) over 60 cases (S1, F2, F3 x P1-P10 x AIS, a 30 dBm jammer): worst relative difference 3.0e-10 and worst orientation 3.0e-11 rad (bars 1e-6), every pass identical; B2, the published case of Cao et al., Chin. J. Aeronaut. 2015, Fig. 1 (25 plot readings, bar 20 %): worst +5.5 % (at a receiver-location error of 0.75 km), 22 of 25 within 1 %; B3, the F3 estimator against the bound (AIS, P1-P10, 1000 trials each, bar 0.9 to 1.25 x DRMS and 99 % converged): ratios 0.979 to 1.019, 1000 of 1000 converged at every point; B4, the fused information equals the sum of the per-pass information to 6.7e-16 relative and DRMS never rises with another pass; B5 additivity. WHAT IS NOT CHECKED: no flown system and no real RF data; no clock or orbit-knowledge error, multipath, AIS slot collisions seen from orbit, ionosphere at VHF or emitter motion; the link budgets are representative, not measured, and the radar classes isotropic (an upper bound), so the bounds are optimistic space_geoloc tests/space_geoloc_m1.rs (B1 against the committed numpy oracle output; B2 against the 25 values transcribed in docs/design/evidence/m1-space-rf-geolocation/reference.csv; B3 and B4 in release; B5 additivity)
Dark-vessel and AIS-integrity decisions from RF fixes against AIS reports m4_logic::decide: from an AIS stream and an RF fix stream (no identities on fixes), one class per identity, NORMAL, DARK (fixes with no matching AIS), GAP, POSITION-OFFSET (AIS position inconsistent with the RF fixes) or IDENTITY-DUPLICATE, and a dark or associated flag per fix; v1 decides by single-fix gates and a vote, v2 (opt-in parameters) by fix sequences for dark tracks and a time-consistent test for offset onsets. m4_dark_vessel generates the synthetic Baltic scenes. Every output describes data consistency, never intent InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — Synthetic scenes from the engine's own generator (about 2 000 vessels per seed in the Baltic), against bars pre-registered in docs/design/evidence/m4-dark-vessel-ais-integrity/. v1 (seeds 1000-1009, 20 000 vessels, ea8557adb): NOT MET on B2, dark recall 0.848 (bar 0.95; precision 0.999 meets its 0.80 part), and B4, offset recall 0.807 at 5 km (bar 0.85) and 0.846, 0.825 and 0.871 at 10, 20 and 50 km (bar 0.98 each); MET on B1 (false alarms 0.0050, bar 0.01), B3 gaps (600 of 600), B5 identity duplicates (600 of 600), B6 determinism on Linux and B7 additivity. v2 (seeds 2000-2009, 165db008b): NOT MET on B2, dark recall 0.877 (bar 0.95; precision 0.897), and B4, offset recall 0.396 at 5 km (bar 0.85) and 0.689, 0.650 and 0.646 at 10, 20 and 50 km (bar 0.98 each), lower than v1; MET on B1 (0.00006), B3 and B5 (1.000), B6 on Linux and B7; 141 offset vessels are decided DARK under v2. v3 (a turn model for dark tracks, a global assignment and collision-tolerant offset onsets, M4Params::v3; signed 10 November 2026; seeds 3000-3009, db06dc2ce): MET on B1 (false alarms 0.00075), B2 (dark recall 0.994, 1 392 of 1 400; precision 0.867), B3 and B5 (1.000), B6 on Linux and B7; NOT MET on B4, offset recall 0.489 at 5 km (bar 0.85) and 0.646, 0.675 and 0.661 at 10, 20 and 50 km (bar 0.98 each); 206 offset vessels are decided DARK and 501 NORMAL. M4 stays NOT MET (B4). WHAT IS NOT CHECKED: real vessels, real RF fixes or real AIS reception; a flag says nothing about intent (gaps and offsets have ordinary causes) m4_logic; m4_dark_vessel tests/m4_generator.rs (seed 0 byte-identical twice and equal to its pin); tests/m4_verdicts.rs (the recorded v1 and v2 verdicts, misses included; seeds 1000 and 2000 decided twice give the same decision and the recorded confusion matrix; the v3 verdict and seed 3000 decided twice)
Interference-source location from orbit, from a ground network, and from both combined m5_hybrid: in a synthetic Baltic scenario, a three-satellite formation's fix of a surface or elevated interference source from its pass (link budget and detection probability per epoch), a coastal ground layer by power differences (locate_pd), and a hybrid that fuses both, with the information bound of each layer; v2 (m5_hybrid::run_v2) starts the space solver from a coarse search over the sea points and gives the ground layer 30 reports per site per draw ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — Bars pre-registered in docs/design/evidence/m5-jammers-from-orbit-hybrid/, on a synthetic scenario (the scored class E30: 200 placements x 20 draws = 4 000 draws). v1 (ac44ae420): NOT MET on B1 to B3: success space 0.630, ground 0.000, hybrid 0.630 (bar: hybrid at least 0.680); medians hybrid 56.08 m, space 56.07 m (bar 44.86 m); p95 hybrid 359 km against ground 263 km (bar: at most the smaller). v2 (seeds 4600 and 4601, 4a09a6c9e): NOT MET on B1 to B3: success space 0.990, ground 0.00025, hybrid 0.990 (bar 1.040, which no estimator can reach); medians hybrid 7.352 m, space 7.351 m (bar 5.881 m; common set 262 draws); p95 hybrid 71.300 m against space 71.297 m (missed by 3.5 mm). MET in both: B4, the link budget and detection against an independent numpy recomputation (xval/m5-jammers-from-orbit/oracle.py) within 3e-14 dB and 7e-21 in probability at P1 to P10; B5, the hybrid bound never larger than a finite layer bound (0 violations in 600 cases); B6 determinism on Linux. The hybrid equals the space layer to millimetres; the ground layer as shipped does not locate (B3a's synthetic-gate miss carried over). WHAT IS NOT CHECKED: any real source, satellite or receiver m5_hybrid tests/m5_b4.rs (link budget and detection against the committed numpy oracle output); tests/m5_verdicts.rs (the recorded v1 and v2 E30 verdicts, misses included; the B5 bounds; two-placement runs give the pinned bytes)
Monitoring-network planner: detection and TDOA location-accuracy maps, and station placement planner (kshana planner map|place): for an interference source of a stated power at every cell of a site grid, each station's detection probability, the network's, the probability that enough stations detect to locate it, and the TDOA DRMS and 95 % ellipse the detecting stations bound (free space); planner::place chooses m stations from candidates, exhaustively up to 10 000 subsets, otherwise greedy followed by a single-exchange search (v1's greedy alone kept by name); v2 flags ill-conditioned cells ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — An independent numpy and standard-library oracle (xval/planner/oracle.py), committed with its outputs before any planner code, under bars pre-registered in docs/design/evidence/b1a-planner/. v1: NOT MET on P1 (detection within 1.9e-13; 4 of the line layout's 619 locatable cells, collinear with every station, miss the 1e-9 relative DRMS bar by 1.3e-9 to 2.6e-9), P2 (52 of 54 barred cells within 5 %; the square's cell 1293 at 1.097 and the circle's at 0.717) and P4's greedy part (0.2754 against the best of 1 000 random subsets, 0.2790; the exhaustive part chose the oracle's optimum, objective 0.1689); P3, P5 (the same bytes on the Linux CLI, Python, WebAssembly and on Linux, macOS and Windows) and P6 MET. v2 (new layouts, 98ff742b4): P1 MET (1 662 locatable cells within 1e-9 relative, none with a condition number above 1e8), P2 MET (46 of 60 drawn cells in the regime, all within 5 %), P3 and P6 MET, P5 MET on Linux (the cross-platform half is met when the reproducibility matrix runs the test on macOS and Windows); P4 NOT MET: on 40 candidates with m = 7, greedy and exchange give 0.350982 against the best of 1 000 random subsets, 0.353361 (greedy alone 0.324212, no bar). v3 (greedy, double exchange and 8 restarts, kept by name; signed 10 November 2026; a new 48-candidate instance with m = 8, 060ee2a07): P4 MET, objective 0.440809 (median DRMS 19.23 m) against the best of 1 000 random subsets, 0.410470; P1 to P3 and P6 MET, re-run unchanged; P5 MET on Linux (the macOS and Windows half is pending, as for v2; the v3 placement's consistency check did not complete when the container restarted, and the printed values are pinned). B1a part 1 is MET on Linux; B1b starts when P5's cross-platform half is green. WHAT IS NOT CHECKED: any real site; the maps are free-space predictions and the DRMS is a lower bound planner tests/planner.rs (v1 P1 to P5, misses included); tests/planner_v2.rs (v2 P1 to P5; the pentagon map's SHA-256 pinned); tests/planner_v3.rs (the v3 P4 values pinned, ignored by default, about 1.5 h)
Area trust state from several reference stations area_trust (kshana area-trust, Python and WebAssembly): each station's epochs on a 1 s grid (Stale after 5 s with no epoch) combine into one area state with k = max(2, ceil(N/3)): UNKNOWN with fewer than 2 live stations, UNTRUSTED with at least k untrusted, DEGRADED with at least k degraded or worse or any untrusted (v2, selected by the stations document's area_rule field: at least m untrusted, m = 2 for up to 6 stations and 1 above), else TRUSTED; a worse state is published at once, a better one after 10 s. v3 (a kshana.area-measurements/1 document with per-satellite inputs, area_trust::v3): per epoch, when at least k stations exceed H_s, the one satellite whose removal brings every alarmed station under its H_s is flagged SATELLITE_FAULT and every station's fix is recomputed without it; loss of lock alone no longer degrades a station; the aggregation is v2's. area_trust::synth and area_trust::v3::fault_replay build seeded replays with injected events ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — Bars pre-registered in docs/design/evidence/b5-area-trust/. T1 against an independent Python standard-library recomputation of the rule (xval/area-trust/oracle.py and oracle_v2.py); T4 on real IGS observation files (SHA-256 values in xval/area-trust/MANIFEST.tsv and MANIFEST_v2.tsv). v1: T1 MET (43 117 grid seconds of seven seeded replays, 4 to 50 stations, 520 events; the oracle's bytes); T2 MET (all 267 events with at least k stations in alarm raised the expected alert; none of the 253 with fewer raised UNTRUSTED); T3 MET (220 injected events at 100 stations, 1 Hz, over MQTT: webhook and MQTT p95 1.004 s, maximum 1.015 s; bars 5 s and 10 s); T5 MET for the files and surfaces built; T4 NOT MET: 23 alerts to DEGRADED over 13 area-days (1.77 per area-day; bar 1), none to UNTRUSTED (bar 0.1), Madrid (MADR, CEBR, YEBE, VILL), 2025-01-07 to 01-19. v2 (a two-station floor for areas of up to 6 stations, a068a3eb9): T1 MET (43 165 grid seconds, the v2 oracle's bytes), T2 MET, T3 MET (p95 1.004 s, maximum 1.013 s), T5 MET; T4 NOT MET: 16 alerts to DEGRADED or worse over 13 area-days (1.23 per area-day; bar 1), 9 of them to UNTRUSTED (0.69 per area-day; bar 0.1), Goddard (GODS, GODE, GODN, USN7), 2025-07-25 to 08-06; no alert came from one station alone. v3 (a common-mode satellite-fault screen across the area's fixes, loss of lock alone no longer degrading, signed 10 November 2026; the diagnosis found unhealthy broadcast records in use and a stale-record satellite fault, and the engine now skips unhealthy GPS records): T1 MET (520 epochs and 520 grid seconds of four satellite-fault replays equal oracle_v3.py's bytes; errors within 1e-6 m), T2 NOT MET (123 of 127 injected common faults flagged and cleared, 4 not where the remaining geometry is weak; 2 of 67 two-satellite epochs explained by one), T3 MET (220 events at 100 stations over MQTT, webhook and MQTT p95 1.003 s and 1.004 s, maximum 1.006 s; the screen is not in its path), T4 MET (1 alert to DEGRADED or worse and 1 to UNTRUSTED over 26 area-days, 0.038 each; Goddard and Wettzell, 18 to 30 May 2026, the pre-registration's 2025 window having no quiet fortnight, disclosed before any fetch), T5 MET (command line, Python and WebAssembly); B5 v3 NOT MET (T2). WHAT IS NOT CHECKED: AGC, the jamming indicator, the clock monitor and OSNMA on the real-data days (not in the files); Galileo and BeiDou health; any real interference event area_trust tests/area_trust.rs (the v1 and v2 timelines equal the oracles' bytes every second; T2 alerts; boundary rules; the live rule equals the timeline; the T4 misses and T3 v2 recorded); tests/area_trust_igs.rs (T4 and T3 on the fetched IGS files, ignored by default; v3 T4 reproduces xval/area-trust/t4v3_result.json); tests/area_trust_v3.rs (v3: T1 against oracle_v3 through the library and the command line, the recorded T2 verdict, the generator writes the committed documents); tests/python/test_bindings.py; web/smoke.mjs
Interference-source location from power differences across fixed monitoring stations locate_pd: each station's C/N0 drop (and AGC rise, where its dB-per-unit scale is stated) is turned into an interference power at the antenna; a log-distance model with the reference power profiled out, the path-loss exponent and source height marginalised and censored terms for stations that see nothing gives a posterior on a grid around the network, with its 95 % region and centroid. v2 averages each station's power over the session with one shadowing term per station, no tempering, on the stations' hull buffered by 10 km; v1 is kept as recorded ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — Synthetic networks drawn from a model that differs from the locator's on purpose, with an independent numpy recomputation (xval/locator-power-difference/oracle.py), under bars pre-registered in docs/design/evidence/b3a-power-difference-locator/. v1 gate (seeds 1001-2000, tau 1/60, f6b4a3336): S1 coverage MET (0.976; bar 0.90); S2 NOT MET (median 95 % region 52.5 % of the search domain; bar 25 %); S3 NOT MET (median centroid error 2.55 x the median nearest-neighbour station spacing; bar 0.5 x). v2 gate (session-level shadowing, seeds 4001-5000, 53ca11af5): NOT MET on S1 (0.890; bar 0.90; the 34 of 1 000 sessions not located count against it), S2 (26.1 %; bar 25 %) and S3 (1.45 x; bar 0.5 x); S4 determinism platforms only (Linux debug against release; the CI job b3a-v2-determinism runs it on Linux, macOS and Windows; the CLI, Python and WebAssembly half is not assessable, the locator has none of those surfaces); the numpy recomputation agrees on seeds 4001-4020 (centroids within 2.5e-10 m). By the pre-registration the real run on Jammertest 2027 is not made with this method. WHAT IS NOT CHECKED: any real interference; the C/N0 and AGC monitors themselves locate_pd tests/locator_power_difference_synthetic.rs (the v1 gate rows reproduce; the recorded v1 verdict); tests/locator_power_difference_v2.rs (12 v2 gate seeds reproduce bit for bit, debug against release; the recorded v2 verdict, the misses included; the development run seen before the gate)
Interference-source location by time difference of arrival across fixed monitoring stations locate_tdoa: from 10 ms snapshots at 4 Msps time-tagged by each station's clock, the station with the largest measured jammer-to-noise ratio is the reference; each other station's delay is the cross-correlation peak refined by a parabola, with a sigma from the Knapp-Carter bound for the measured SNRs and the reference's mean-square bandwidth plus both clocks (the pairs share the reference clock's covariance); the source is located on a spherical Earth at a known height by a grid search over the stations' hull buffered by 10 km and Gauss-Newton, with a 95 % ellipse and a chi-square test of the residuals at 0.999 that gives not located. locate_tdoa::session draws the synthetic sessions (CW, chirp and wideband noise jammers, two-ray ground reflection with 6 dB shadowing, 20 ns station clocks) ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — Synthetic sessions under bars pre-registered in docs/design/evidence/b3b-tdoa-locator/ (B3a's bars), with an independent numpy recomputation of the locator (xval/tdoa-locator/oracle.py). Gate (seeds 6001-7000, 1 000 sessions, eed00fd84): NOT MET on T1 (coverage 0.044; bar 0.90), T2 (median area share 1.000; bar 0.25) and T3 (3.35 x the median nearest-neighbour spacing; bar 0.5); 872 sessions not located (CW 334 of 334, chirp 324 of 333, noise 214 of 333). The parabolic refinement misplaces a one-sample-wide correlation peak by up to 125 ns against a stated sigma of about 28 ns, so the chi-square test rejects most fits; the sawtooth chirp's correlation repeats inside the lag window; a CW has no bandwidth. The numpy recomputation agrees on 19 of seeds 6001-6020 within the registered tolerances; on seed 6002 Gauss-Newton diverges in both and the scored outputs agree. By the pre-registration no real run is made with this method. WHAT IS NOT CHECKED: any real jammer, station or clock locate_tdoa tests/locator_tdoa.rs (the recorded gate verdict, the misses included; seeds 6001-6020 against the numpy oracle; the whole gate reproduces its recorded bytes, ignored by default and run on Linux, macOS and Windows by the b3b-determinism CI job)
TEXBAT spoofing-detection benchmark: per-window baseline IQ scores and power-and-distortion scores bench::texbat (kshana bench texbat-windows and texbat-pd): streams one TEXBAT recording (complex int16, 25 Msps), refuses a file whose SHA-256 or size differs from the pinned manifest and then writes nothing, acquires PRNs 1 to 32 once and tracks them through the recording, and writes per 1 s window the early-minus-late imbalance S, the prompt-power fluctuation P and the window score against synthetic thresholds (the 99th percentiles over the 61 of 64 synthetic windows that acquire); texbat-pd adds the in-band power rise over the recording's own windows 0 to 59 (tau 1.0 dB). Writes scores only, never IQ samples ExternalDataset a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled — TEXBAT (Humphreys et al., ION GNSS 2012): two clean and eight spoofing recordings, spoofing windows counted from 110 s, under bars pre-registered in docs/design/evidence/b4a-benchmark-classes/PREREGISTRATION-E5-v2.md (E5 v2: window AUC of spoofing at least 0.70 over all ten recordings) and PREREGISTRATION-E5-PD.md (E5-PD: the same bar on windows 60 and later). Scored once on 11 November 2026 (kshana bench texbat-score over the ten committed score files, xval/bench-e/texbat-v2/E5-SCORE.json, 571cb9d19); every scoring rule, the thresholds, the onset and the window rules were committed before the first TEXBAT score file (9 November). E5 v2 NOT MET: AUC 0.6941 (2 729 spoofing and 922 nominal windows; bar 0.70). E5-PD MET: AUC 0.7410 (bar 0.70). Reported without a bar: recording-level AUC 0.8125 (E5 v2); per spoofing recording, E5-PD: ds1 0.466, ds2 1.000, ds3 0.418, ds4 0.821, ds5 1.000, ds6 0.584, ds7 0.897, ds8 0.750 (three of the eight below 0.6). An independent Python standard-library recomputation (xval/bench-e/texbat-v2/oracle_e5.py, exact pairwise AUC) agrees to 1e-12. The thresholds come from synthetic data only; the recordings are not redistributed (hashes and score files only). The detector stays MODELLED. WHAT IS NOT CHECKED: real receivers in the field; attacks outside TEXBAT bench::texbat; bench::cli tests/texbat_e5v2.rs (the score rules and classes; a file that does not match its pin writes nothing; a power-and-distortion run refuses a windows file of another recording; the synthetic thresholds, ignored by default, about 16 minutes in release; the AUC arithmetic on synthetic documents; the recorded E5 score equals the committed one)
RTKLIB .pos solution reader for receiver-trust Reads an RTKLIB solution file (calendar or GPS week/TOW time, latitude/longitude or ECEF position, satellites used) into the receiver-trust timeline (receiver_trust::machines::rtklib). InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — None external: no RTKLIB-produced file was read, and the column layout is from the RTKLIB manual. Checked on self-written files only; the ECEF conversion reuses frames::ecef_to_geodetic, which has its own rows receiver_trust::machines::rtklib (read_rtklib_pos); receiver_trust::LogFormat::RtklibPos receiver_trust::machines::rtklib::tests (lat/lon epochs, week/TOW and ECEF, dms refused, hostile input); tests/receiver_trust_machines.rs::rtklib_pos_runs_as_a_receiver_log; integrations/gnss_lib_py/test_bridge.py
NovAtel OEM7 ASCII and binary logs (BESTPOS, RANGE, RXSTATUS) for receiver-trust Reads BESTPOS (position), RANGE (C/No per signal) and RXSTATUS (the receiver's jammer flag, as the epoch's self-report) from ASCII and binary OEM7 logs, CRC-checked, read-only (receiver_trust::machines::novatel). InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — None external as a pass bar. The field layouts and CRC follow the public OEM7 documentation (docs.novatel.com); the CRC routine was checked once against the CRC the documentation states for its own BESTPOSA example (cited, not quoted). Fixtures are self-written; no log from a real receiver was read receiver_trust::machines::novatel (read_novatel, novatel_crc32); receiver_trust::LogFormat::Novatel receiver_trust::machines::novatel::tests (pinned CRC, ASCII and binary records, bad CRC skipped, hostile input); tests/receiver_trust_machines.rs::novatel_jammer_flag_reaches_the_receiver_self_report
RTCM 3 MSM4 and MSM7 carrier-to-noise reader for receiver-trust Reads the C/N0 of every signal cell of RTCM 3 MSM4 and MSM7 messages (GPS, GLONASS, Galileo, SBAS, QZSS, BeiDou, NavIC) from a frame stream, CRC-24Q checked (receiver_trust::machines::rtcm3). Layouts from the BSD-licensed pyrtcm tables, not from the RTCM standard text. ReferenceImpl checked against a separate implementation in this same codebase — independent of the unit under test, but not externally authoritative — ReferenceImpl in a one-off check, not a test in the suite: pyrtcm 1.2.0's decoder reads the same self-written frames to the same C/N0 and epoch time. It shares its tables' source with this reader, so it checks the bit handling, not the layout. No capture from a real receiver or base station was read receiver_trust::machines::rtcm3 (read_rtcm3, crc24q); receiver_trust::LogFormat::Rtcm3 receiver_trust::machines::rtcm3::tests (CRC-24Q catalogue check value, MSM4/MSM7 C/N0 and epoch merging, GLONASS time and SBAS id mapping, bad CRC and other messages)
GNSS-SDR monitor adapter for receiver-trust Reads GNSS-SDR Monitor (Gnss_Synchro) and PVT-monitor messages, relayed to JSON lines with the proto field names, into per-channel C/N0, fix, satellites used, HDOP and sky (receiver_trust::machines::gnss_sdr; integrations/gnss-sdr/relay.py). InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — None external: field names come from the GNSS-SDR documentation; neither the reader nor relay.py was run against a live GNSS-SDR or a real capture receiver_trust::machines::gnss_sdr (read_gnss_sdr_monitor); receiver_trust::LogFormat::GnssSdr receiver_trust::machines::gnss_sdr::tests; integrations/gnss-sdr/example.jsonl
IMU log ingest, gyro heading input and Allan fit of hybrid sensor parameters Reads an IMU CSV (documented columns, or the EuRoC layout); integrates the yaw rate into the heading the heading-course monitor reads ([log.imu]); and fits the accelerometer and gyro noise parameters of the hybrid and fusion scenarios from a stationary log by overlapping Allan deviation (imu-fit). InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — None external: the fit is checked on synthetic white-noise logs with known coefficients, the heading on constant yaw-rate logs. No real IMU log was fitted, and q_aa is not fitted receiver_trust::machines::imu, imu_fit; surface::imu_fit; scenario [log.imu] receiver_trust::machines::imu::tests; receiver_trust::machines::imu_fit::tests (known white-noise coefficients recovered within 10 %, refusals, TOML parses as AccelCfg); tests/receiver_trust_machines.rs (heading agreement and disagreement, inline carrier, imu_fit)
Home Assistant MQTT discovery and state exporter for trust telemetry A JSON state document and Home Assistant MQTT discovery messages for the trust stream, printed as text on every surface and published over MQTT 3.1.1 QoS 0 by the CLI (telemetry::mqtt; trust-telemetry --mqtt-tcp, --print-mqtt, format mqtt). InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — None external: the packets were read by a loopback listener written for the test, not by a real broker, and Home Assistant was not run telemetry::mqtt (discovery, state_json, connect_packet, publish_packet, MqttSink); surface::TelemetryFormat::Mqtt telemetry::mqtt::tests (packet bytes, loopback broker, dead broker counted); tests/receiver_trust_machines.rs::trust_telemetry_mqtt_text_has_discovery_then_state
ROS 2 receiver-trust package and gnss_lib_py bridge A ROS-free bridge that writes fix and satellite messages as NMEA and scores them through the Python binding (integrations/ros2/kshana_trust), and a gnss_lib_py NavData to receiver-trust bridge through the rtklib-pos format (integrations/gnss_lib_py). InternalConsistency checked against its own closed-form / analytic identity — catches transcription and coefficient errors, but is not an external oracle — None external: the ROS node was not run on a live ROS 2 graph, and the ublox_ubx_msgs field names were not checked against a running driver. gnss_lib_py (MIT) was run for the bridge test integrations/ros2/kshana_trust (bridge.py, trust_node.py); integrations/gnss_lib_py/kshana_gnss_lib_py.py tests/receiver_trust_machines.rs (rtklib_pos_runs_as_a_receiver_log: the format the gnss_lib_py bridge writes, run through receiver-trust); the Python tests of the bridges are integrations/ros2/kshana_trust/test/test_bridge.py (bridge with a mock engine), integrations/ros2/kshana_trust/test/test_engine_integration.py (the real wheel scores a steady fix nominal and a 1.1 km jump untrusted) and integrations/gnss_lib_py/test_bridge.py (real gnss_lib_py 1.1.0 and the wheel), run with pytest, not by cargo

233 capabilities labelled MODELLED.