SSM-Clock—Guardrails & One-shot Alarm (5.3–5.4)

5.3 Optional guardrails (confidence, outliers)

If your stream also prints a confidence per tick:

tau_days=...
conf=0.98

you can gate accumulation:

if conf < min_conf: continue   # skip low-confidence tick

Defaults (v1.1). Keep off by default (min_conf = 0.0).
Optional outlier skip. If any per-channel |err_i| > 45 deg, skip that tick:

skip_tick = any( abs(err_i_deg) > 45.0 for i in channels )
if skip_tick: continue

Notes.

  • Guardrails are non-destructive: they do not rewrite the log; they simply decide whether to accumulate Delta_tau for SSM-Wait.
  • Keep thresholds gentle to avoid brittle behavior; confidence already reflects bowl sharpness.

5.4 One-shot alarm (optional, ASCII-safe)

Wrap the wait in a .cmd and act on exit code:

@echo off
cd /d "C:\Users\ASUS\Desktop\Clock"
python ssm_wait.py --manifest "clock_manifest.json" --tau_log "notes\tau_stream.log" --minutes 5
if %ERRORLEVEL%==0 (
  echo SSM-Alarm: fired after 5 minutes of symbolic time.
) else (
  echo SSM-Alarm: wait aborted (code %ERRORLEVEL%).
)

Guidance.

  • Keep the alarm local and simple; avoid networked side-effects in v1.1.
  • For Unix shells, mirror the logic with $? and a small sh wrapper.

Navigation

Back: SSM-Clock—Streaming & SSM-Wait (5.1–5.2)
Next: SSM-Clock—Validation Results (5.5)