OFSClock publishes the OFS (Order-Flow Standard), an interface layer that sits on top of ISO/UTC for human–AI coordination. ISO/UTC remains authoritative.
No. ISO/UTC remains authoritative. OFS is an overlay that can be adopted incrementally without changing legal time or calendar systems.
A human-facing daily display token. Φ divides the day into 10 phases; ψ subdivides each phase into 10,000 pulses.
It is a normative resolution choice: enough for deterministic scheduling and UI smoothness, without encouraging surveillance-level precision. ISO remains authoritative.
No. It is a separator between Φ and ψ.
A monotonic ordering pulse used for system logs, replay, and multi-agent coordination. It complements ISO (authority) with consistent ordering.
Optional event semantics—consent, privacy boundaries, causality, and responsibility—so systems can interpret events safely and humans can reduce ambiguity.
OFS explicitly discourages it. Implementations must not use ψ-level granularity for monitoring individuals or productivity scoring. MT defaults to privacy-first.
Start with an ICS overlay: keep DTSTART/DTEND authoritative, add one OFS line and optional X-OFS fields. Then adopt the Envelope JSON for agents and audit logs.
OFS Civil uses a mean-day baseline for stability. ISO/UTC remains authoritative; implementations may smear or map leap seconds when needed.
OFS Calendar is planned as an upcoming product for standardized overlays and tooling. Current adoption is via integrations and schemas.
A configuration label for high-consequence operational workflows emphasizing ordering (FT), integrity (audit), and bounded semantics (MT), while remaining ISO-anchored.
No. Units remain identical. OPS changes recommended logging discipline and verification patterns.
No. It is an independent technical publication. Terms are used in a technical reliability and interoperability sense.
Where to start