Order-Flow Standard (OFS-2.1)
Time, made interoperable.
A single global Flow-Time axis + a Meaning-Time layer for human–AI interoperability. Three profiles: Civil Display, System Flow, Meaning-Time.
Standard Seal
Time, made interoperable.
OFS 101 (for humans + AIs)
OFS is a dual-display interoperability standard for representing time without replacing legal time.
What it solves
What it is NOT
Examples
Diagrams
Dual-Display Layer
Keep law-readable time; add computable display without replacement.
Profiles
Start with Civil; add System/Meaning only when needed.
Adoption Path
Interface-first adoption: tools before institutions.
MT Event Schema
Meaning-Time adds boundaries to events, not surveillance.
Units & Symbols
Core Concepts
Symbol Reference
- Meaning
- 1/10 of a local day
- Range
- 0–9
- Note
- Day segmented for calm coordination
- Meaning
- 1/10,000 of a phase
- Range
- 00000–09999
- Note
- Fine resolution without minute-fragmentation
- Meaning
- Joins phase + pulse
- Range
- —
- Note
- Explicitly NOT a decimal point
Derivation
Definition
Order-Flow is a computable representation of change.
OFS defines:
Profiles
Format Card
Safeguards: Attention-First Defaults
No surveillance by default
Phase-batched notifications
No productivity scoring
Privacy levels for Meaning-Time events
Non-goals
- Not a monitoring framework
- Not a behavioral scoring system
- Not a replacement for legal time
Reference Implementation
SeqFlow (seqflow.ai) is the reference live interface for OFS adoption.
Start with Civil Display dual-display; integrate System/Meaning profiles as needed.
Adopt OFS without changing legal time: use dual-display via SeqFlow.
Adoption Path
Open Source SDK
Civil Display
Φ.ψψψψψ
Human clock + ISO dual-display
System Flow
FT integer
Monotonic epoch pulses
Meaning-Time
{ id, ftRange, causality, consent, privacy }
Event object with consent
import { formatDual, toOFSClock, nowFT, createMeaningEvent } from '@seqflow/ofs';
// Civil Display: dual-display format (ISO | Φ.ψψψψψ)
formatDual(new Date('2026-02-19T12:00:00Z'), 'Europe/London');
// => "2026-02-19T12:00:00Z | 5.00000"
// Derivation: 12:00 = 43,200 s; phase = 43200/8640 = 5; pulse = 0
// 6:00 AM example
toOFSClock(new Date('2026-02-19T06:00:00Z'), 'UTC');
// => "2.50000"
// Derivation: 6h = 21,600 s; 21600/8640 = 2.5 → Φ=2, ψ=50000? No:
// Φ=2, remainder = 21600-(2*8640) = 4320 s; ψ = 4320/0.864 = 5000 => "2.50000"
// System Flow: current Flow-Time pulse (monotonic integer)
nowFT();
// => 1740000000
// Meaning-Time: event with consent + privacy + causality
createMeaningEvent({
id: crypto.randomUUID(),
ftRange: [nowFT(), nowFT() + 10000],
causality: 'user-action:submit',
consent: 'explicit',
privacy: 'restricted',
});SDK Principles
Integration
Social
Share text includes ISO + OFS + standard link.
Governance & Credibility
Founder: Lucen Law
Operated by Arcer Governance LLP
A nonprofit public standard released from the UK.
Initiated by a Hong Kong founder, in collaboration with global AI practitioners.
Press Summary
OFS-2.1 is a dual-display interoperability standard for time representation. It defines Flow-Time for systems, Meaning-Time for human context, and a Civil Display profile for adoption—preserving legal time while adding computable structure.
- OFS-2.1 defines Flow-Time (FT) for machine ordering and interoperability.
- Meaning-Time (MT) adds causality, consent, and privacy to event representation.
- Civil Display keeps dual-display reversible to ISO 8601 — no legal time replacement required.
- Safeguards prohibit surveillance, scoring, and involuntary tracking by default.
- SeqFlow (seqflow.ai) is the reference live interface for OFS adoption.
Contact
Reach the OFS Standards Desk for inquiries, press, or SDK guidance.
standards.seal@ofsclock.com
Legal & Disclaimers
Safety-Critical Note
Not sole time source: OFS must not be used as the only time reference for safety-critical systems, transport, or medical applications.
Misuse (Anti-oppression)
OFS must not be used to build fine-grained behavioral monitoring, workplace scoring, or coercive scheduling systems. Any implementation that uses OFS data to surveil, rank, or penalize individuals violates the standard’s normative safeguards.
- Workplace surveillance via ψ-level logging is explicitly forbidden.
- Productivity scoring based on OFS pulses is explicitly forbidden.
- Coercive scheduling regimes built on OFS are explicitly forbidden.
Attention-first defaults are normative goals of the standard.