GAL-2 Technologies

GAL-2 Technologies GAL-2 Time Contract for resilient digital infrastructure. Governed time before application state. gal-2.com

Application-facing temporal governance, holdover, rejoin, fail-closed behavior and IXOYE Witness Layer. GAL-2™ Technologies — Global Alignment Layer | Fractal Time. Eliminating drift & leap seconds for finance, IoT & telecom. Founded by Francisco Edgardo Torres Alvarado, visionary entrepreneur bringing the future of time.

06/15/2026

.

A timestamp can look valid… and still be unsafe to consume.That is why we built GAL-2 Time Contract.Not to replace UTC, ...
06/15/2026

A timestamp can look valid… and still be unsafe to consume.

That is why we built GAL-2 Time Contract.

Not to replace UTC, NTP, PTP, GNSS, or atomic clocks.

To govern the moment before an application commits state.

RC5.7 evaluator preview is now available:

macOS notarized.
Linux Preview Docker ARM64 GPG signed.
IXOYE advisory witness included.

GAL-2 governs.
IXOYE witnesses.

Precision protects the reference.
GAL-2 protects the consumer.

GAL-2 RC4 evidence is now public.We completed a 120-hour official characterization run:72 hours of controlled holdover.1...
06/07/2026

GAL-2 RC4 evidence is now public.

We completed a 120-hour official characterization run:

72 hours of controlled holdover.
14,279 contract samples.
0 backward steps.
1 documented FAIL_CLOSED boundary row.
Clean recovery back to LIVE.

The key result:

GAL-2 did not pretend safety past the declared boundary.

It failed closed.
It documented it.
It rejoined cleanly.

This is what governed time for software means.

DOI:
https://doi.org/10.5281/zenodo.20582981

Validation:
https://www.globalalignmentlayer.com/validation

What happens when time becomes trusted state?• Not just synchronized.• Not just displayed.• Committed.• Written into a d...
05/26/2026

What happens when time becomes trusted state?

• Not just synchronized.
• Not just displayed.
• Committed.
• Written into a database.
• Stored in a ledger.
• Used in an audit trail.
• Trusted by an application.

Most timing systems are built to answer:

“What time is it?”

But modern software needs another question answered first:

“Should this time be allowed to become trusted application state?”

That is the boundary GAL-2 is focused on.

GAL-2 is not another clock.

It does not replace UTC, GNSS, PTP, NTP, chrony, grandmasters, hardware clocks, or existing timing infrastructure.

Keep your timing stack.

GAL-2 sits closer to the application and exposes a Time Contract that software can intentionally check before time-derived data becomes trusted durable state.

• Infrastructure-compatible.
• Application-integrated.
• Non-disruptive to the timing stack.
• Intentional at the application boundary.

Because bad time does not stay inside the clock…

• It becomes a corrupted log.
• A broken ordering sequence.
• A stale authorization decision.
• A bad transaction.
• A ledger inconsistency.
• A record that should never have been trusted.

The deeper question is not only:

“What time is it?”

The deeper question is:

“Should this time be allowed to become truth?”

That is the category GAL-2 is building toward.

Temporal governance before time becomes state.

gal-2.com


Timing

Not another patch.Most timing systems are built to answer one question:“What time is it?”But real software often fails a...
05/24/2026

Not another patch.

Most timing systems are built to answer one question:

“What time is it?”

But real software often fails at a different boundary:

“Should this time be allowed to become trusted application state?”

That is where GAL-2 is focused.

GAL-2 has now closed the fifth layer of its public Y2038 evidence corpus:

1. Legacy mediated-time delivery
2. SQLite protected commit
3. SQLite + JSONL local multi-substrate durability
4. Local Postgres protected commit
5. Local latency characterization

The pattern is consistent:

Raw time-derived state can become unsafe.

A GAL-2 protected path checks the Time Contract before durable commit.

Unsafe inputs are blocked.

Safe inputs pass.

The decision is auditable.

Each layer was published with strict claim boundaries, public artifacts, structurally independent oracle verification where applicable, public secret scans, hash manifests, and hash-sealed evidence records.

This is not a claim that GAL-2 universally “solves Y2038.”

This is not metrology.

This is not a replacement for UTC, GNSS, PTP, NTP, chrony, or atomic clocks.

This is application-boundary temporal governance.

The current timing stack delivers time.

GAL-2 governs whether that time should be allowed to become trusted application state.

That is the difference.

Temporal governance before time becomes state.

How many systems expose this boundary as a public, application-facing Time Contract?

GAL-2 Time Contract v1.0 now has a public evidence chain.Pre-registered before ex*****on:https://doi.org/10.5281/zenodo....
05/23/2026

GAL-2 Time Contract v1.0 now has a public evidence chain.

Pre-registered before ex*****on:
https://doi.org/10.5281/zenodo.20262207

Official results package after completion:
https://doi.org/10.5281/zenodo.20357131

The 5-day adversarial characterization evaluated application-facing Time Contract behavior under controlled upstream interruption conditions.

Final run:

14,397 contract samples
14,397 consumer rows
7,200 health rows
1,442 usage snapshots

Global observed invariants:

0 fetch failures
0 monotonic_sequence backward steps
0 gal2_time backward steps

The scheduled adversarial phases included short, medium, and hard upstream interruption scenarios.

Observed Time Contract states included:

LIVE
HOLDOVER
DEGRADED
REJOIN
FAIL_CLOSED

During the hard interruption phase, GAL-2 entered FAIL_CLOSED with health=red and safe_to_consume=false after hard holdover policy expiration.

That is the boundary GAL-2 is built for:

not just asking “what time is it?”
but asking “can this time safely become application state?”

Claim boundary:

This is application-facing Time Contract evidence under controlled upstream interruptions.

It is not a UTC replacement claim.
It is not a GNSS, PTP, NTP, chrony, time card, grandmaster, or atomic clock replacement claim.
It is not a metrological accuracy claim.
It is not a formal UTC traceability claim.

GAL-2 does not replace timing infrastructure.

It governs whether time is safe to consume before it becomes application state.

Pre-registered first.
Published results after.

gal-2.com

Most timing systems are built to answer one question:“What time is it?”But production software often needs a different q...
05/14/2026

Most timing systems are built to answer one question:

“What time is it?”

But production software often needs a different question answered first:

“Can this time safely become application state?”

That is the boundary GAL-2™ Time Contract is built for.

A timing incident does not only live inside a clock.
It can become a bad commit, a broken ledger, a corrupted log, a failed authorization decision, a stale cache, or an ordering failure across distributed systems.

Leap-second-like discontinuities.
Y2038-style legacy boundaries.
GNSS degradation.
Stale references.
Backward steps.
Recovery out of phase.

These are not just timing problems.
They are application-state problems.

GAL-2 does not replace UTC, GNSS, PTP, NTP, chrony, atomic clocks, or grandmasters.

Keep your timing stack.

GAL-2 sits closer to the application and serves governed gal2_time through a Time Contract with:

safe_to_consume
valid_until
mode
reason
monotonic_sequence
source_lineage

When timing conditions are healthy, applications consume governed time normally.

When timing conditions degrade, GAL-2 can preserve bounded monotonic continuity where policy allows, perform controlled rejoin when the reference returns, or fail closed before unsafe time becomes committed state.

Precision protects the reference.

GAL-2 protects the consumer.

GAL-2™ Time Contract is currently available for technical pilots, architecture review, and design-partner evaluation.

Resilience Infrastructure GNSS PTP NTP Y2038

GAL-2 API-Backed Contract Source Isolation v2 is now published on Zenodo.This evidence package documents a 60-minute sus...
05/12/2026

GAL-2 API-Backed Contract Source Isolation v2 is now published on Zenodo.

This evidence package documents a 60-minute sustained operational source-isolation monitor in which a general-purpose Mac client consumed a local SNTP feed derived from the current GAL-2 Time Contract and backed by the live GAL-2 API.

Tested chain:

GAL-2 API → GAL-2 daemon → Time Contract → Mac A SNTP Bridge → Mac B Network Time

Key results:

60-minute sustained monitor
61/61 client samples
79/79 safe responses
Modes observed: LIVE, REJOIN
Source lineage: gal2_api → gal2_daemon → contract_v1
Result: PASS

DOI: https://doi.org/10.5281/zenodo.20143004

Boundary: this test supports operational source isolation and contract-gated local time consumption. It does not claim physical oscillator control, UTC replacement, UTC traceability certification, production readiness, or clock accuracy superiority.

Raw time keeps going. GAL-2 knows when to stop.

Raw time keeps going.GAL-2 knows when to stop.Most systems keep consuming time even when they should not.GAL-2 Time Cont...
05/04/2026

Raw time keeps going.
GAL-2 knows when to stop.

Most systems keep consuming time even when they should not.

GAL-2 Time Contract introduces a local application-facing contract that helps software know whether time is still safe to use before it acts.

Precision protects the reference.
GAL-2 protects the consumer.

Not all time should be trusted.

gal-2.com

Address

254 Chapman Road, Ste 208 #23982
Newark, DE
19702

Website

Alerts

Be the first to know and let us send you an email when GAL-2 Technologies posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Shortcuts

Share

Category