---
layout: readme
title: Rust .me Integration Notes
image: https://neurons-me.github.io/docs/assets/img/me.png
---
# Integration Notes
Rust `.me` is currently usable as:
- a library crate from crates.io,
- a CLI,
- a JSON snapshot kernel,
- a runtime host with receipts,
- a benchmark target,
- and a semantic parity surface against TypeScript fixtures.
## Next Integration Target
The natural next host is `monad.ai`.
The first integration should not replace the entire TypeScript monad at once.
The safer path is:
1. keep monad's HTTP/WS surface,
2. mount Rust `.me` behind a narrow adapter,
3. route one kernel namespace through Rust,
4. compare results against TypeScript contracts,
5. then widen.
## Why Runtime Receipts Matter
`KernelRuntime::{write,execute}_with_receipt` returns:
- the operation result,
- exactly the events generated by that operation,
- persisted memory state.
That is the shape a host needs for:
- HTTP responses,
- WS broadcasts,
- local app subscriptions,
- NRP path streams,
- embedded process notifications.
## What Is Not Done
- No Rust HTTP server is part of this crate yet.
- No Node/Rust bridge has been selected.
- No WASM binding exists yet.
- No production monad replacement has been attempted.
This is intentional. The Rust kernel is now real; integration should be its own
controlled phase.