Skip to content
#software testing Open access

Artian A1 Earth-Flyby Handshake Preregistration: A Prospective Dual-Link Test of the QTT Two-Clock Map

Oct 2026 · Zenodo (CERN European Organization for Nuclear Research) · 3 citations · 4 references
Advanced Frequency and Time Standards

Abstract

One spacecraft can carry two physically different radio handshakes. Their difference is a new, geometry-locked clock test. Historical Earth-flyby residuals cannot decide this test because they contain only one physical radio-clock history. This preregistration instead requires two simultaneous links on the same spacecraft: one continuously phase connected and one physically clock gated and reacquired. Each route is repeated with the electronics roles exchanged, and at least two nondegenerate route orientations are required. Both links use the same frozen conventional orbit, light-time, Earth-rotation, station, media, relativistic, and transponder model. For route \(p\), crossed hardware assignments \(A,B\) form \[ d_p=\frac{\Delta y_{p,A}+\Delta y_{p,B}}{2}, \] while the source geometry is computed before residuals are opened: \[ g_p=\left\langle2\,\frac{(\Omega_E\times\mathbf r_p) \cdot\mathbf v_p}{c^2}\right\rangle_p. \] A single free-offset flyby is not eligible, because \[ (\Omega_E\times\mathbf r)\cdot\mathbf v =\Omega_E\cdot(\mathbf r\times\mathbf v) =\Omega_E\cdot\mathbf h \] is nearly constant on a central-force arc. Crossed electronics cancel the leading hardware offset; opposite route orientation isolates the geometry-odd coefficient. After a frozen nuisance projection, the registered coefficient is \[ \boxed{ \widehat\kappa_{\rm A1}= \frac{\mathbf g^{\rm T}C^{-1}P_\perp\mathbf d} {\mathbf g^{\rm T}C^{-1}P_\perp\mathbf g}.} \] The prospective fork is \[ \boxed{ H_{\rm ordinary}:\widehat\kappa_{\rm A1}=0, \qquad H_{\rm QTT-A1}:\widehat\kappa_{\rm A1}=1.} \] The geometry amplitude is not fitted. A bare five-standard-deviation separation requires \(\sigma(\widehat\kappa_{\rm A1})\leq0.2\); the recommended design target is 0.1. Crossed roles, route orientation, station transfer, loopback, duplicate modes, and a sign-reversed holdout must preserve the coefficient. Three adversarial audits reject software-only arc splitting, the single-route/free-offset degeneracy, omitted conventional navigation terms, channel-specific source retuning, flexible geometry-absorbing nuisances, and untracked gate/reacquisition transients. Historical flyby and public radio-science records remain useful design constraints, but receive ARCHIVE_INELIGIBLE_NO_A1_VERDICT. Scientific status: matched-filter theorem and synthetic null/QTT fixtures closed; physical simultaneous dual-link hardware, mission covariance, and empirical verdict pending. Concept DOI: 10.5281/zenodo.21674819 Main book: Quantum Traction Theory: Main Book v10.01 Website: quantumtraction.org · Two Universes · Lexicon · Observatory The public files are the paper PDF first and the complete reconstruction ZIP second. Clock, ruler and signal-recovery qualification. Both registered predictions are constructed at the raw detector with explicit proper-time, coordinate-time, worldline, ruler and synchronization conventions. Each relativistic effect is counted once. Independently calibrated corrections carry their uncertainties through the common comparison; the tested rows cannot train a normalization that forces either answer. Blind recovery is required separately for both alternatives at every predeclared operating setting. The inherited targets and decision rules remain fixed. The included design study makes sensitivity explicit: for the Two-Test Gram classifier, a total ratio uncertainty of 0.0013 gives approximately 88.9% QTT-branch and 94.1% ordinary-branch power under the stated ideal model. These are conditional detection probabilities, not probabilities that a theory is true, and each instrument retains its own classifier. The complete apparatus packet must be sealed before acquisition and target access; historical campaign rules remain preserved. Reconstruction entry point. Start with current/CURRENT_RELATIVISTIC_EXECUTION.md in the ZIP. The shared execution contract refers once to the development filename CURRENT_EXECUTION_RC.md; that reference means CURRENT_RELATIVISTIC_EXECUTION.md in this release. The packaged README names the correct file. This navigation correction does not change the deposited files, scientific requirements or historical seals.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

GPT-Lab Sep 23, 2026

Requirements Don’t Live in Isolation: What We’re Exploring with Req-Space

Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…

GPT-Lab Sep 17, 2026

Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering

AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.