HomeDocs-Technical WhitePaper20-EFT.WP.Metrology.TimeBase v1.0

Chapter 12 — Boundaries & Anomalies (Leap Seconds / Virtualization / GNSS Events)


One-line objective: Under challenging boundary conditions—leap seconds, virtualized clocks, and GNSS source anomalies—preserve the monotonicity of tau_mono and consistency of the published ts, quantify risk, and deliver an auditable governance loop.


I. Scope & Targets

  1. Covered
    • Time scales & leap seconds: mappings among TAI/UTC/GPS/UT1, leap_event ∈ {+1,-1,0}, and UTC_smear policies.
    • Virtualization & containers: vCPU preemption, TSC stability, guest↔host clock source switching, and monotonicity guarantees.
    • GNSS anomalies: spoof/jam, ionospheric disturbances, 1PPS/ToD mismatch, GPS week rollover, multi-constellation resilience.
  2. Inputs
    Real-time observables: offset/skew/J, 1PPS bias, PDOP, CN0, stall_ms (guest clock stalls), wn_rx (GNSS week count).
  3. Outputs
    • Policy & control: leap_apply or UTC_smear, holdover mode, source_fallback, adjustments to warp(t).
    • Manifest: manifest.time.boundary.* (events, thresholds, actions, and signature).

II. Terms & Variables


III. Axioms P512- **


IV. Minimal Equations S512- **


V. Governance Flow M50-12 (Detect → Classify → Isolate → Correct → Reinstate → Audit)

  1. Detection
    Continuously monitor offset/skew/J, 1PPS, PDOP/CN0, stall_ms, wn_rx.
  2. Classification
    A: leap-second event; B: virtualization stall/migration; C: GNSS (spoof/jam/ionosphere/rollover).
  3. Isolation
    Suspend phase steps; remove GNSS from servo (quarantine); in virtualization, switch to monotonic_raw and enter holdover.
  4. Correction
    • Leap seconds: apply leap_step or UTC_smear(t) per policy;
    • Virtualization: limit frequency / pin CPUs / enable invariant_tsc or kvmclock corrections;
    • GNSS: reselect constellations, enforce PDOP/CN0 gates, repair WN_full, re-calibrate antenna/cable delays; re-admit after holdover reconvergence.
  5. Reinstatement
    Using median/MAD, taper isolated-source weight to zero, then probe up; resume voting once contracts pass.
  6. Audit
    Emit manifest.time.boundary.*: event, thresholds, actions, residual U, and signature.

VI. Contracts & Assertions


VII. Implementation Bindings I50-12*


VIII. Cross-References


IX. Quality SLIs & Risk Control

  1. SLIs
    • leap_applied_flag, smear_window_active, smear_slope_max;
    • stall_ms_p95/p99, guest_tsc_invariant, offset_1pps_p95;
    • gnss_use_ratio, spoof_alerts_count, wnro_events, holdover_duration_s.
  2. Risk policies
    • Priority: holdover > multi-source median > PTP > NTP > GNSS (quarantined).
    • Gray re-admission: low-weight join → pass observability gates → increase weight.
    • Injection drills: periodic leap-second simulation, VM pause injection, spoof/jam sandbox—verify C50-121…127.

Summary

*, the system maintains tau_mono monotonicity and ts consistency under extreme conditions, sustaining the two T_arr formulations and publication SLOs.I50-12*, and C50-12, M50-12, S512-, P512-. Via GNSS anomalies, and virtualization, leap seconds for three boundary classes—closed-loop remediation, and a detection gates, scale mappingsThis chapter sets out

Copyright & License (CC BY 4.0)

Copyright: Unless otherwise noted, the copyright of “Energy Filament Theory” (text, charts, illustrations, symbols, and formulas) belongs to the author “Guanglin Tu”.
License: This work is licensed under the Creative Commons Attribution 4.0 International (CC BY 4.0). You may copy, redistribute, excerpt, adapt, and share for commercial or non‑commercial purposes with proper attribution.
Suggested attribution: Author: “Guanglin Tu”; Work: “Energy Filament Theory”; Source: energyfilament.org; License: CC BY 4.0.

First published: 2025-11-11|Current version:v5.1
License link:https://creativecommons.org/licenses/by/4.0/