R / 04 / Active programme
Computer interaction needs a native, inspectable boundary.
Nimbus investigates a reproducible Chromium baseline, Nimbus-owned identity and shell, native content filtering, and a Rust-native, client-neutral MCP companion for local-first human and agent work.
Research question
How can a browser become a trustworthy computer-interaction surface without surrendering product identity or local authority?
Workstreams
The programme is worked as a system.
Reproducible browser baseline
Control upstream intake, patches, build inputs, release gates, and product identity around a Chromium foundation.
Native interaction surface
Expose browser and computer capabilities through explicit, inspectable primitives for people and agents.
Local-first companion
Develop a Rust-native, client-neutral MCP surface whose useful operation does not depend on a hosted control plane.
Privacy & performance gates
Measure filtering, network behaviour, startup, memory, responsiveness, and regression before release claims advance.
Evidence gate
What would move the claim forward?
Research maturity advances through named evidence, not through the passage of time or the confidence of the presentation.
- 01Reproducible upstream baseline
- 02Permissioned interaction trace
- 03Privacy and network inspection
- 04Performance release gates
Current boundary
The limit is part of the result.
Nimbus remains in active development. Native browser, filtering, MCP, privacy, and performance claims advance only when their respective release gates are met.