HS° Relative Phase Lock Meter v1.0 (Ticks)
Tick-Canonical Relative Phase Offset Stability Metric (Deterministic Correlation Meter for HS-Bloch / Policy Layers)
Abstract
This document defines HS° Relative Phase Lock Meter v1.0, a tick-canonical metric that quantifies the stability of a relative phase offset between two HS° processes (e.g., nodes, agents, links) over a finite window. This is not quantum entanglement: it is a deterministic correlation/lock metric on the circle S1, computed using wrap-safe tick distance and integer-only arithmetic. The meter outputs (i) an estimated relative offset in ticks and (ii) a dispersion-based lock score encoded as u16, designed to be consumed by HS-Bloch via coherence_meter_id and by policy layers for gating and audit.
Normative Dependencies
1. Scope and non-goals
Correlation meter, not entanglement: This specification defines a deterministic relative phase lock / correlation meter computed from tick observations. It MUST NOT be described as quantum entanglement and MUST NOT claim coordination without communication.
No redefinition of timing or crypto: This document MUST NOT redefine: phase-window semantics (Conventions), execution (Q-Address/TAQA), or cryptographic semantics (Security Profile).
2. Inputs and notation
Definition 2.1 (Tick observation stream): Let R ∈ N be the tick resolution (ticks per cycle). A process 𝐴 provides tick observations a_i ∈ {0, . . . , R − 1} over a window 𝑊 of length 𝑁 samples. Similarly 𝐵 provides b_i ∈ {0, . . . , R − 1}.
Same resolution and deterministic pairing: All samples used in a single evaluation MUST share the same tick resolution R. The pairing policy (which a_i pairs with which b_i) MUST be deterministic and documented by the deployment (e.g., “pair receipts by the same cycle_index and nearest phi_ticks”).
Definition 2.2 (Wrap-safe tick distance): For ticks x, y ∈ {0, . . . , R − 1} the wrap-safe circular distance is d_ticks(x, y) := min{|x − y|, R − |x − y|}, as defined normatively by Conventions.
Definition 2.3 (Relative offset samples): Define the relative offset sample (modulo R) as: Δ_i := (a_i − b_i) mod R ∈ {0, . . . , R − 1}.
3. Estimator and dispersion (integer-only)
Definition 3.1 (Circular median estimator (tick)): Let {Δ_i} from i=1 to N be the samples. Define the estimated relative offset (in ticks) as the smallest minimizer: k_hat_ticks := min arg min_m∈{0,...,R−1} Σ d_ticks(Δ_i, m).
Definition 3.2 (Dispersion as MAD in ticks): Define the dispersion (integer ticks): D_ticks := median_i=1,...,N d_ticks(Δ_i, k_hat_ticks).
Integer-only requirement: All computations in this meter MUST be performed using integer arithmetic only. Floating-point operations MUST NOT be used for enforcement or for the reported canonical score.
4. Lock score encoding (u16)
Definition 4.1 (Meter parameter: admissible dispersion bound): The meter MUST be configured with an admissible dispersion bound D_max ∈ {1, . . . , floor(R/2)}, denoted dmax_ticks (integer).
Definition 4.2 (Lock score (u16)): Define the lock score as a normalized u16 integer: lock_u16 := if D_ticks ≥ D_max, then 0, else floor(65535 · (D_max − D_ticks) / D_max).
5. Optional lock classes (deployment-defined)
Definition 5.1 (Optional lock classes): Deployments MAY derive a class label from D_ticks:
- STRONG if D_ticks ≤ D_strong,
- WEAK if D_strong < D_ticks < D_max,
- BROKEN if D_ticks ≥ D_max,
6. Data model (HSLockReport)
Definition 6.1 (HSLockReport (canonical fields)):
hslock_schema_id(MUST equal TV-HSLOCK-2026-01),lock_meter_id(MUST equal TV-COH-RELLOCK-TICKS-MAD-2026-01),resolution(MUST equal R),window_len_u16(MUST): number of paired samples 𝑁,k_hat_ticks(MUST): k_hat_ticks,dispersion_ticks(MUST): D_ticks,dmax_ticks(MUST): D_max,lock_u16(MUST): computed score.
Signing for enforcement: If the lock score is used for enforcement, the HSLockReport MUST be carried in a signed context under the active security_profile_id (Security Profile). Unsigned reports MUST NOT be used for security-critical gating.
7. Integration with HS-Bloch (informative)
To use this meter with HS-Bloch v1.1, set:
coherence_meter_id:= TV-COH-RELLOCK-TICKS-MAD-2026-01coh_u16(orcoh_vec_u16["rel_lock"]) := lock_u16
and gate with integer comparison lock_u16 ≥ lock_min_u16 via HS-Bloch.
8. Examples (informative)
Example: HSLockReport
{
"hslock_schema_id": "TV-HSLOCK-2026-01",
"lock_meter_id": "TV-COH-RELLOCK-TICKS-MAD-2026-01",
"resolution": 1000000,
"window_len_u16": 7,
"k_hat_ticks": 1234,
"dispersion_ticks": 3,
"dmax_ticks": 20,
"lock_u16": 55704,
"dstrong_ticks": 5,
"lock_class": "STRONG"
}Example: HS-Bloch observation carrying the meter score
{
"ext_signed": {
"quality_obs": {
"hsbloch_schema_id": "TV-HSBLOCH-2026-02",
"coherence_meter_id": "TV-COH-RELLOCK-TICKS-MAD-2026-01",
"coh_u16": 55704
}
}
}