Helix Ops Cheatsheet — Time & Dissonance

From Helix Project Wiki
Revision as of 14:34, 10 October 2025 by Steve Helix (talk | contribs) (Created page with "= Helix Ops Cheatsheet — Time & Dissonance = This cheatsheet provides **quick commands** for verifying Helix’s custody-first time and dissonance handling. For the full runbook, see Helix Runtime Policy — Time & Dissonance. == Check Time == <pre> curl -fsS http://127.0.0.1:9010/time </pre> * Expected: ISO8601 timestamp, e.g. <code>2025-10-10T13:24:00Z</code> == Check Dissonance == <pre> curl -fsS http://127.0.0.1:9010/status | jq .dissonance.value </pre...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Helix Ops Cheatsheet — Time & Dissonance

This cheatsheet provides **quick commands** for verifying Helix’s custody-first time and dissonance handling. For the full runbook, see Helix Runtime Policy — Time & Dissonance.

Check Time

curl -fsS http://127.0.0.1:9010/time
  • Expected: ISO8601 timestamp, e.g.
 2025-10-10T13:24:00Z

Check Dissonance

curl -fsS http://127.0.0.1:9010/status | jq .dissonance.value
  • Expected: JSON float value, e.g.
 0.42

Failure Mode

  • If endpoint unreachable or errors:
 → Respond/output unknown  
 → Add provenance: (source: unknown)

Restart Shim

sudo systemctl restart helix-ttd.service
  • Use if endpoints fail or return invalid JSON.

Provenance Tags

Always include in output:

  • Example success:
 time: 2025-10-10T13:24:00Z (source: 127.0.0.1:9010/time)
  • Example failure:
 dissonance: unknown (source: unknown)