OFSClock

How OFS works

Units, conversion, and the dual-display interface

Core idea

OFS does not change Earth’s rotation, seasons, or ISO/UTC. It changes the interface used by humans and systems to coordinate: ISO/UTC remains authoritative; OFS adds a deterministic daily display token (Civil), a system ordering pulse (FT), and optional semantics (MT).

Units & symbols (normative)

  • 1 day (interface baseline) = 86,400 seconds
  • 1 day = 10 Φ (Phase)
  • 1 Φ = 10,000 ψ (Pulse)
  • 1 day = 100,000 ψ
  • 1 ψ ≈ 0.864 seconds = 864 ms
  • Civil token format: Φ.0xxxx

"." is a separator, not a decimal point. Φ ranges 0–9. ψ ranges 00000–09999 (fixed 5 digits).

Why 1Φ = 10,000ψ?

It is a normative resolution choice: large enough for machine scheduling and smooth UI, small enough to avoid precision-driven surveillance pressure. The standard treats ISO as authoritative; Civil is an interface.

GMT+8 mapping table (exact examples)

Time (GMT+8)OFS Civil
02:000.08333
04:001.06666
06:002.05000
08:003.03333
10:004.01666
12:005.00000
14:005.08333
16:006.06666
18:007.05000
20:008.03333
22:009.01666

Dual-display block

ISO (authoritative): 2026-02-20 21:00 GMT+8Civil (human interface): 8.07500FT (system ordering): 2193…MT (optional): consent + privacy + causality

Leap seconds

OFS Civil uses a mean-day interface baseline (86,400 seconds/day) for stability. UTC leap seconds may produce an 86,401-second day; implementations may smear or map the extra second. ISO/UTC remains authoritative; OFS is an overlay.

Safeguards

  • No ψ-level monitoring of individuals.
  • No productivity scoring based on pulses.
  • Default attention protection (batching and boundaries).
  • MT is privacy-first: restricted/private by default unless explicitly public.