Public technical material

Understand GAL-2 as a Time Contract, not another clock.

GAL-2 Time Contract is an application-facing governance layer for systems that already depend on UTC, GNSS, PTP, NTP, chrony, grandmasters, hardware clocks, or operating-system time. It helps applications decide whether governed time is safe to consume before committing state.

Recommended whitepaper

GAL-2 Time Contract Architecture

A public architecture overview explaining GAL-2 as an application-facing Time Contract layer for governed time consumption, continuity, controlled recovery, and fail-closed behavior under declared policy.

Open Time Contract Whitepaper
Current product surface

GAL-2 Time Contract

The current product path is the local daemon and API-backed Time Contract. Protected applications read /contract before allowing time-sensitive state changes to commit.

Read Documentation
Claim boundary: GAL-2 does not replace UTC, GNSS, PTP, NTP, chrony, atomic clocks, grandmasters, hardware clocks, operating-system time, or timing receivers. It complements existing timing infrastructure at the application boundary where delivered time becomes committed state.
[background image][background image] image of company location map (for a construction company)image of video editing software on a computer screen

Fractal Time origin

The deeper thesis behind the Time Contract.

GAL-2 began from a simple but powerful idea: time should not enter digital systems as an ungoverned raw signal. The current product expression of that thesis is the GAL-2 Time Contract, an application-facing path that helps software decide whether governed time is safe to consume before committing trusted state.

Origin

Fractal Time

Fractal Time is the conceptual foundation behind GAL-2. It frames time as something digital systems must align, govern, and consume with discipline, especially when references degrade, jump, disappear, or return out of phase.

Product expression

Time Contract

The public product surface is the Time Contract: gal2_time, safe_to_consume, valid_until, mode, reason, monotonic_sequence, and source_lineage.

Market entry

Application-Boundary Time Governance

GAL-2 helps protected applications continue within policy, hold over, rejoin under control, or fail closed before unsafe time becomes committed application state.

GAL-2 does not replace UTC, GNSS, PTP, NTP, chrony, atomic clocks, grandmasters, hardware clocks, operating-system time, or timing receivers. It complements existing timing infrastructure at the application boundary, where delivered time becomes software state.
Validation · Docs · Whitepaper · Pricing · Vision
GAL-2 Time Contract Layer · Powered by AWS · Verified Apple Developer ID XWFX4JS9C2 · Local contract endpoint 127.0.0.1:9095/contract
Public evidence: RC4 72h Holdover · 5-Day Adversarial · Solstice 7D · SHA-256 sealed validation artifacts
© 2026 GAL-2™ Technologies LLC. All rights reserved. · Application-facing Time Contract infrastructure · Terms of Service · Privacy Policy · support@gal-2.com GAL-2 governs whether software should consume time before committing state. It is not a replacement for UTC, GNSS, PTP, NTP, chrony, atomic clocks, grandmasters, hardware clocks, or existing timing infrastructure.