GAL-2 Y2038 Multi-Substrate Protected Commit Test v1.2: Application-Boundary Evidence Package

This evidence package presents the GAL-2 Y2038 Multi-Substrate Protected Commit Test v1.2, a controlled application-boundary test evaluating whether a GAL-2 Time Contract-gated application path, together with a declared Y2038 safety policy, can prevent unsafe Y2038-style time-derived state from becoming durable application state across multiple local commit substrates. This package extends the prior GAL-2 Y2038 protected commit evidence from a single SQLite substrate to a local multi-substrate scenario using SQLite and an append-only JSONL ledger. The package compares a raw path and a GAL-2 protected path across the same input matrix. The raw path commits signed-32-bit wrapped time-derived state into both local substrates. The GAL-2 protected path applies a two-part decision chain before durable commit: the GAL-2 Time Contract gate and the declared Y2038 policy gate. Results: main test PASS, independent oracle verifier PASS, public secret scan PASS, archive smoke verification PASS, public archive review-condition audit PASS. Core result: raw path committed unsafe Y2038-style state into both tested substrates. The GAL-2 protected path produced zero unsafe commits across SQLite and JSONL, blocked all unsafe inputs before durable commit, committed safe inputs to both substrates, and recorded zero backward steps in monotonic_sequence and gal2_time. Cross-substrate consistency in this package means data parity: the same logical safe commits appear in both tested substrates, and unsafe inputs are absent from both GAL-2 protected substrates. It does not claim transactional atomicity, two-phase commit, rollback coordination, distributed transactions, or atomic cross-substrate recovery. Project website and validation context: https://gal-2.com Claim boundary: this is multi-substrate application-boundary protected commit evidence using local SQLite and append-only JSONL substrates. It is not universal Y2038 remediation, not operating system, kernel, filesystem, database engine, or distributed-system remediation, not production throughput or latency evidence, not transactional atomicity evidence, not metrology, and not UTC, GNSS, PTP, NTP, or chrony replacement.