Research OS and Compute
Reproducible research, with the method attached.
One Lab Compute runs registered regression, time-series, simulation, optimization and spatial methods. Each run binds its code, input snapshot, seed, parameters, cost, artifacts and independent verification into an append-only receipt.
Built · local proof plane; GCP bootstrap pending
The problem
A result without its run context is hard to trust.
Research teams need to know which question was registered, which inputs were available and exactly how an output was produced. The Research OS makes those parts of the result.
Architecture
Registered questions, manifests and governed evidence.
The compute plane separates orchestration, execution and evidence. Brain, AION and AOK remain under research governance; they are not buyer-facing products or active autonomous authority.
- Versioned compute manifests
- Deterministic seeds and parameters
- Container and data-snapshot identity
- Receipts for completed, refused, failed and cancelled runs
Current boundary
Proof execution is not forecasting or autonomous authority.
The deterministic local proof plane is built. Google Cloud execution is pending least-privilege account bootstrap. AION execution, forecasting and learning authority remain inactive. No AGI, ASI or autonomous-science claim is made.
Next step