OFSClock

Use cases

What ships today (ISO-safe), and what OFS adds

Calendar coordination (humans)

What you ship today

Keep DTSTART/DTEND as ISO/Gregorian. Add one OFS line in DESCRIPTION and optional X-OFS fields.

What stays ISO

Legal time and calendar authority.

What OFS adds

A shared Civil token for quick coordination and consistent parsing.

Agents & automation (systems)

What you ship today

Agents exchange an OFS Envelope JSON for scheduling.

What stays ISO

Real-world anchoring and compliance.

What OFS adds

Deterministic ordering (FT) + optional semantics (MT) for intent, consent, and boundaries.

Audit logs & disputes (governance)

What you ship today

JSONL hash-chained entries (verifiable).

What stays ISO

Timestamp authority for legal interpretation.

What OFS adds

Replayable ordering (FT) and consistent event structure (Envelope/MT).

Attention-first daily rhythm (humans)

What you ship today

Phase-based blocks for planning; notifications at boundaries.

What stays ISO

Real-world clock remains visible.

What OFS adds

Less fragmentation; clearer time blocks.

Ops-grade timelines (operational)

What you ship today

FT-ordered event chains with hash-verified audit logs (VerifyChain).

What stays ISO

Authoritative timestamps for compliance and legal record-keeping.

What OFS adds

Deterministic ordering (FT), integrity audit trails, and bounded semantics (MT) via the OPS Profile configuration.