GaiaWorld · Public verification surface

Proof before performance claims.

This page records what GaiaWorld has actually demonstrated today: deterministic execution, temporal evidence controls, hypothesis gating, reproducible hashes, and explicit abstention outside supported evidence. It does not turn a synthetic engineering test into a biological benchmark claim.

Inspect proofGaiaWorld flight recorder
Canonical engineering proof
Verification state: PASS
The page fails closed if its version-controlled proof record cannot be loaded.
Release evidence

A machine-readable record, not a screenshot.

The successful GitHub Actions execution produced a proof artifact and the release facts below are bundled into the deployed site so the public record survives the temporary Actions artifact retention window.

Workflow

Run#2 · success
Executed2026-08-27T17:04:36.348Z
Commit75ea1f53f763e593a8ef6246db267efc1a8d47f3

Artifact integrity

Artifact SHA-2567f31102d77df6ca99fa635777e86ec1cbb13ab78b5827c8a4a04aaaa6595f9a3
Evidence cutoff2025-12-05T23:59:59.000Z
Route behaviorEXACT → simulated · OOD → abstained

Reproduce

Run the same deterministic fixture from the repository:

node scripts/gaiaworld-zero-cost-proof.js
Assertions

Nine controls passed.

The proof is deliberately narrow. Each assertion is an engineering property that can be checked without claiming real-world biological accuracy.

  • Kernel compiledPassed in release proof
  • Supported case simulated on EXACT routePassed in release proof
  • Post-cutoff evidence excludedPassed in release proof
  • Hypothesis-only evidence blockedPassed in release proof
  • True OOD case abstainedPassed in release proof
  • Kernel, replay, and benchmark hashes presentPassed in release proof
  • Abstention remained in denominatorPassed in release proof
Cryptographic replay record

Every major object has a deterministic identity.

Snapshot85a1cf5e9f9b6dac08a5c6a6a2d0366e70339bd1b55a43f728f2e9440daec5fc
Kernelb7b68fc5899d6c86a6024fff65667639448a00518e9130cc542aba32d1120122
Replaydab194e3ca93fcaff546ea01fd14c5cb3a5e23c24c1f898c148f28486b9330c8
Benchmark70dd7d11f5228f325217e26683401098c0f1aa5e7edfc442313952e067b42cfc
Synthetic fixture diagnostics

The numbers are visible—and explicitly not biological performance.

Cases2
Simulated1
Abstained1
Coverage50%
Abstention rate50%
Direction100%
Provenance100%

Scientific boundary

Synthetic fixture only. This proves engineering controls, not Arc H1 performance, biological validity, causal validity, efficacy, safety, patient benefit, or clinical utility.

How the proof works

Evidence is constrained before the transition is scored.

01 · CompileCompile a synthetic transition kernel with a declared evidence cutoff.
02 · ExcludeReject evidence dated after the cutoff and hypothesis-only evidence from transition-driving support.
03 · SimulateExecute one supported EXACT case through the deterministic transition runtime.
04 · AbstainSend a deliberately unsupported perturbation through the same runtime and require OOD abstention.
05 · HashEmit snapshot, kernel, replay, benchmark and artifact hashes so the record can be compared and replayed.

Cost boundary

The proof computation script requires no GCP authentication, VM, bucket, paid model call, database write, or external network request.

What comes next

Engineering proof remains separate from biological validation.

Arc H1 Experiment #001 has since been scored and published as a negative primary retrospective result. Experiments #002 and #003 are narrow positive retrospective results, while #004 closed before reveal. None of these records constitutes prospective, clinical, causal, or independently reproduced validation.