The direction

Three engines sit on the project’s main branch: the TypeScript reference, a protocol test in Python, and a complete second engine in Rust. All three pass the same suite, 224 conformance fixtures and 10 probe files, identically over five consecutive runs, and no model is called anywhere: every "model" in the demos is a timed stand-in.

The 7th and 8th of November 2026 filled the MCP surface out (describe_network became the sixth tool), built the team decision demo, and built the ground: strength between connections kept as engine state, each deposit ageing until the engine evaporates it, and a seeded draw that routes a reply that names no destination (decision 0012).

The Rust engine serves neuron-engine mcp over stdio: a network can be checked or described before any traffic, run outright or started as a job and polled, its trace read back, and the SPEC, the conformance notes, the trace format and the schema served as resources. The desk is deliberately not on it: the page is the person’s surface.

Where it is going, the repo’s direction note says plainly: the run is the multiplayer table, the desk page is the door people use, MCP is the door workers use, and the network file is the house rules. The four gaps that note collects (grants at the desk, holds that survive a restart, presence, quiescence) are issue #30 on the public repo.

Not a product and nothing on npm: the specification is a 0.1 draft, the direction note is a concept the code does not implement yet, and nothing here is a live run.