# r29: evolved numerical spacetime in PF workflows The portable vacuum BSSN solver now supplies the metric used by an explicit `numerical_plane` apparatus mode in Simulation, Comparison, Precision and Assurance. This is a bounded numerical-relativity verification environment. It does not replace the existing Earth/satellite models with a gauge wave. ## What is physically connected The same evolved lapse and spatial metric determine three-dimensional null photon paths through the plane-symmetric chart, moving reception events, observer frequency ratios, proper-time clocks, memory intervals and detector time tags. An optional declared Gaussian receiver mode changes accepted-pair probability using the actual propagated frequency ratio. Its bandwidth and temporal pulse assumptions are checked for consistency. Scenario 3 evaluates the pinned PF selector on geodesic logarithms computed in that numerical metric and mapped into an orthonormal frame at the anchor. It retains Scenario 2's physical releases and quantum state. A frame construction does not itself create better fidelity or a new physical synchronization law. The reported logarithm is a numerically checked direct branch, without a claim of global uniqueness. | Workflow | r29 numerical-plane behavior | |---|---| | Simulation | Actual photon, clock, gate, memory, spectral-receiver and PF calculations using evolved fields | | Comparison | The same apparatus at two grid resolutions; differences in actual observables, with recorded inputs and sources | | Precision | Repeated actual simulations under declared applicable parameter uncertainty; seeded draws and numerical evidence | | Assurance | Runs the numerical precision workflow, captures source/configuration provenance and records scoped audit findings | | Scientific integrations | Existing portable/native research studies plus the new fixed published clock-and-link reference suite | | Other published/component benchmarks | Retain their own source-defined inputs; a spacetime solver is not injected into a benchmark that has no compatible geometry | The optional causal mission-quantum modules use this metric for supported classical messages and memory durations. Optical diffraction/focusing, Earth occultation, atmospheric propagation, QKD security qualification, arbitrary curved-metric uploads, matter, rotating bodies, AMR and black-hole mergers are outside this numerical-plane mode. Unsupported Earth/TLE and global scheduling options are rejected instead of silently reinterpreted. ## Start on Windows 1. Extract the complete r29 ZIP into a new directory. 2. Run `setup_research_worker.bat` if the Python 3.12 research environment is not installed for this directory. 3. Open `Launch_PF_Research.bat`. 4. In Simulation, Comparison, Precision or Assurance, choose the numerical-plane apparatus preset. Use the provided configuration first. The standard Windows research environment is intended to run this NumPy/SciPy solver without WSL or native Cactus. The recorded r29 scientific and service executions were performed on Linux with Python 3.12; actual Windows execution is not established by those records. The SaaS presets invoke the same scientific code under bounded workloads. The retained HTTP/worker tests exercise a local service and actual subprocesses, not a deployed cloud system. Native Einstein Toolkit, MATLAB/Simulink and instrument integrations retain their existing external runtime, license and hardware requirements. The portable solver is a separate limited implementation, not a complete Einstein Toolkit clone. kuibit/native Toolkit studies remain separately identified. ## Reproduce from the command line Use the installed research Python (`.venv_research\Scripts\python.exe` on Windows, or the research environment's `python` on Linux) in the package root. Choose new empty output directories so existing evidence is preserved. ```text python run_privileged_frame_simulation.py --config configs_r29/simulation_numerical_plane.json --scenario all --output results_r29_simulation python run_comparison.py --config configs_r29/comparison_numerical_plane.json --output results_r29_comparison python run_precision_analysis.py --config configs_r29/precision_numerical_plane.json --output results_r29_precision python run_risk_audit.py --config configs_r29/assurance_numerical_plane.json --output results_r29_assurance python run_research_integrations.py --config configs_r29/published_clocks_and_links.json --output results_r29_references ``` The raw results include the actually evolved fields, array hashes, coordinate conventions, rays, clock rates and coupling provenance. Numerical reports export NPZ/CSV data, PNG/SVG/PDF figures, HTML and Markdown. View the generated numerical spacetime report alongside the ordinary workflow results. ## Evidence and interpretation `RESEARCH_REVIEW_R29.md` and `research_sources_r29/numerical_mission_sources.json` document the primary-source review, exact source versions, retrieval hashes, equations, conventions, potential benchmark targets and known discrepancies. The catalogue is a record of research and target definitions; it is not a record that every listed experiment has been reproduced. The independent numerical validator uses the exact gauge-wave coordinate transformation to Minkowski coordinates to check off-axis light cones, frequencies and geodesic logarithms. It also inspects recorded numerical fields, clock quadrature, gate probabilities and quantum-state consistency. A gauge wave is flat spacetime in nontrivial coordinates; this is a stringent coordinate and numerical-coupling test, not a test of Earth's measured gravitational field. Keeping the same prescribed coordinate tracks while changing gauge-wave amplitude generally changes the physical observer trajectories. Differences between those runs are not a demonstration that a coordinate transformation alone changes an invariant measurement. The new published reference study distinguishes four rounded published clock values from equation verification by PF's production clock, photon and spectral routines. Source rounding controls the printed-value tolerances. The corrected Kohlrus arXiv v6 convention is used for spectral propagation; inconsistent numerical examples in Bruschi 2014 are documented and excluded as targets. The existing public detector/aggregate benchmark can be rerun separately. It remains retrospective reanalysis with its original calibration and dataset limits. Neither matching a published equation nor reanalyzing one detector dataset establishes mission-wide experimental accuracy. Current release acceptance is recorded in `validation_r29/NUMERICAL_WORKFLOW_VALIDATION.json`. It binds actual execution artifacts to their sources. Earlier `validation_r24` through `validation_r28` records are historical; source changes do not promote them to fresh r29 qualification. Experimental accuracy, independent external replication, PF-specific operational advantage and commercial superiority still require separately demonstrated evidence.