One Lab Compute

Make the run part of the result.

Compute records the question, inputs, method, limits and outcome together. A separate verifier checks the output. Failed, refused and cancelled attempts stay visible instead of disappearing.

Local proof plane verified · Google Cloud bootstrap pending

01 / Capabilities

Three bounded analysis packs.

Simulation

Monte Carlo, quasi-Monte Carlo, variance reduction, importance sampling, correlated shocks and copulas, bootstrap, scenario trees, Sobol, Morris, tail risk and deterministic stress

Deterministic proof

Fixed deterministic-stress fixture; direct-formula independent verifier

Optimization

Constrained, stochastic, Pareto and Bayesian optimization; knowledge-gradient and multi-fidelity provider plans

Deterministic proof

Fixed constrained-quadratic fixture; independent feasibility and objective verifier

Spatial and network

Spatial lag and error, exact CRS/version contracts, spatial-temporal lags, shortest paths, accessibility and geographic uncertainty

Deterministic proof

Fixed network fixture; independent Bellman–Ford and accessibility verifier

02 / Evidence receipt

What you can inspect.

Why: The registered question and the authority under which it was requested.
What: Exact dataset hashes, code commit, dependency lock, container digest, algorithm and parameters.
Where: Provider, region, resource ceiling and keyless security hooks.
What happened: Pass, refusal, failure or cancellation; every attempt remains evidence.
Cost and time: Measured runtime plus local-zero, measured or provider-estimated cost.
Can it be checked?: Artifact hashes, an independent verifier verdict and a reproduction command.

03 / Operations

Bounded before execution.

Admission checks provider, region, runtime, memory, concurrency and daily cost before a job starts. Cancellation, bounded retry, chained checkpoints and exact resume are supported. Retention evaluation never deletes evidence by itself.

Regional execution and explicit provider fallback require a new receipt
CMEK, private-network and confidential-compute hooks carry references—not secret values
Housing, Observatory and Assure receive narrow registered evidence interfaces
Brain/AION accepts proposal-only, local, zero-cost dry runs with no credentials or state writes

04 / Boundary

Compute does not decide what is true.

A passing receipt means the registered program produced an output that its independent numerical checks accepted. It does not authorize a forecast, certify compliance, activate AION, allocate resources, learn from production or change a customer system. Those authorities remain separate and inactive.