![[background image]](https://cdn.prod.website-files.com/image-generation-assets/3987e624-ab42-4b2f-bd4e-b47e28dff173.avif)
![[background image] image of company location map (for a construction company)](https://cdn.prod.website-files.com/image-generation-assets/e9f7540f-af8e-4855-83b1-af33ba624f5c.avif)
Application-facing temporal governance for production timing stacks. Your timing stack delivers time. GAL-2 governs whether applications should consume it.
Public technical material
GAL-2 Time Contract is an application-facing temporal governance layer.
It serves governed gal2_time with contract semantics so applications can
continue within policy, rejoin under control, or fail closed before unsafe time becomes committed state.
A public architecture overview explaining GAL-2 as a software-defined temporal governance layer for continuity, ordering, and reconciliation under degraded timing conditions.
Open Architecture Whitepaper
The current product path is the local daemon and API-backed Time Contract.
Applications consume gal2_time instead of trusting raw system time directly for protected operations.
Fractal Time origin
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 serves
governed gal2_time before software commits trusted state.
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.
The public product surface is the Time Contract: gal2_time, safe_to_consume,
valid_until, mode, reason, monotonic_sequence, and
source_lineage.
GAL-2 helps protected applications continue within policy, hold over, rejoin under control, or fail closed before unsafe time becomes committed application state.