One-page laboratory brief · prospective protocol

Monitored-Recurrence Reference-Switch Experiment

A lab-facing entry point for a sealed A1 reference-switch proposal using first-detection recurrence resonances.

Question

Does a reciprocal switch between two physically qualified scheduler roles move the location of the same monitored-recurrence transition?

Not a claim

No existing Barkai-group result is interpreted as evidence for QTT. This protocol contains no laboratory result.

First stop condition

If the A1 terminal graph cannot be certified before data, the outcome is TARGET_NOT_ACTIVATED, not a theory verdict.

Frozen point targets
Ordinary quantum-control target
R_MRRS = 1

This is the registered result after ordinary clock transfer and a qualified reciprocal role swap.

Conditional QTT A1 target
R_MRRS = cos(pi/8) = 0.9238795325...

This target is executable only once the pre-data activation certificate is signed.

The preregistered power gate is logarithmic: u_Delta <= 0.0158347184 for bare five-standard-deviation separation; the declared design goal is u_Delta <= 0.008. Failure produces QUALIFIED_BUT_UNDERPOWERED, not support for either target.

Platform and protocol checklist
  1. 1. Monitored system. Identify a finite-dimensional evolve-measure-restart system and phase-merger transitions that can be mapped without visual selection.
  2. 2. Qualified roles. Build the disciplined and autonomous scheduler roles, plus their ordinary clock-transfer function. An autonomous device is not automatically an A1 terminal.
  3. 3. Activation packet. Freeze Hamiltonian lock, role swap, transfer, finite-N model, covariance decision, raw schema, blindness firewall, and source-to-hardware reasoning before target blocks.
  4. 4. Controls. Use hidden-sign frequency offsets, trigger latency, timing jitter, gain, and drift injections. The paper requires a primary restart horizon N >= 1024 unless a pre-data simulation justifies equal or better root resolution.
  5. 5. Open one frozen estimator. Report the point comparison, uncertainty, eligibility diagnostics, and every failed gate. No replacement angle or post-hoc exception is allowed.
A practical contact point

A first conversation should decide whether the platform can realize the terminal topology and whether the controls are credible. Before a campaign begins, agree in writing on scope, authorship, data access, budget, and release terms. The point is a clean test, not a vague signal hunt.

Sources and packets