Dumb kernel
Routes typed carriers, isolates workers, records lifecycle, enforces bounds, and executes control messages. It never invents recovery policy.
The kernel acts like dumb plumbing. Crates announce what they can do. Six permanent, crypto-required lanes connect API, peers, HTTP, SSH, NAT, and cloud while the spider watches every vibration and decides how the system should respond.
Threads form from actual traffic. Intersections emerge where paths cross. Backpressure and lifecycle events propagate as vibrations through elevated layers. Drag to rotate; scroll to zoom.
ordo.apiCRYPTO REQUIRED · FAILS CLOSEDThe permanent contract is concrete: stable Ordo lane IDs and sockets live in code and in PERMANENT-LANES.md. Transport can evolve behind those coordinates without making upstream crates rewire themselves.
Routes typed carriers, isolates workers, records lifecycle, enforces bounds, and executes control messages. It never invents recovery policy.
The Ordo profile fixes lane IDs and sockets for API, P2P, HTTP, SSH, NAT, and cloud, plus sixteen reserved expansion slots.
The spider is a regular strand. It feels lifecycle and vibration events, then publishes restart, quarantine, transfer, or shutdown decisions.
If no spider is registered, a crashed strand stays dead. That is the proof that recovery policy is not secretly hiding in the plumbing.
A crate deposits a static advert. At boot, the registry collects the linked set and the bus connects it. The registry is plumbing; the spider remains the orchestrator.
Stable identity in logs and topology.
Parameterless constructor for the strand.
Ordinary strand or the single spider.
Optional 3D coordinate in the fabric.
It reacts to crashes, backpressure, topology, cost, and availability without making the kernel understand what any crate actually does.
DECENTRALIZED CAPABILITY · CENTRALIZED VIEWUpstream code mounts strands; it does not pass socket names around. The frozen profile owns the fabric coordinates, and every current or reserved lane inherits the same crypto-required stance.
ordo.apirequest / response
ordo.p2ptx / rx
ordo.httprequest / response / call / result
ordo.sshtx / rx
ordo.nattx / rx
ordo.cloudrequest / response
New transport families can be added without repurposing a base lane or changing upstream message contracts.
Select a mechanism to inspect how kernel traffic, fixed sockets, peer mesh, NAT/cloud routes, the AEAD skin, and RF repair meet at one bus-facing boundary.
The std-only core owns routing, bounds, lifecycle, observation, and control execution. The spider owns every recovery decision.
The Ordo profile requires a process-wide ChaCha20-Poly1305 skin before the bus opens. Each ciphertext is bound to its lane ID, making the wrong lane, wrong key, tampering, and replay explicit rejection paths.
`open_ordo_bus()` refuses to start without the installed global skin. SSH can still provide a transport tunnel underneath, while the bus skin protects the lane above transport. Generic constructors retain explicit plaintext and HMAC modes for other deployments; they are not the Ordo default.
`spiderweb-rf` is a real workspace crate. It models deterministic loss, fading, multipath duplication, corruption, and jitter, then adds XOR fountain shards so surviving equations can reconstruct missing chunks.
The bus workspace contains the RF channel and decoder. The parameter sweep below uses K=32 and roughly 5,556 seeded trials per cell to expose the recovery curve rather than a cherry-picked single packet.
In one representative deterministic matched-reference simulation, 4/8 raw chunks became 8/8 final chunks and reconstruction failure moved from 0.500 to 0.000 when dictionary IDs survived.
RF loss and fountain recovery are integrated into the bus workspace; the figures remain synthetic-channel evidence, not over-the-air hardware proof. The semantic repair result is a separate experiment and assumes a shared primitive dictionary.
The bus is not a mock-up behind the 3D viewer. The mechanisms below are present in the public Lucerna Labs source and passed the current workspace test, formatting, and warning-clean lint gates.
Fan-out, bounded structures, panic isolation, lifecycle, emergent threads, intersections, vibration, and live statistics.
Six frozen Ordo lane classes, fixed sockets, wire-free mounting, and sixteen crypto-required expansion coordinates.
Exactly-once triangle mesh and loop suppression, rendezvous relay, HTTP/API bridges, TCP edge framing, and SSH composition.
A deterministic synthetic channel and fountain decoder live in the workspace, with hardware radio validation kept as a separate boundary.
The kernel carries traffic, the lanes preserve their contracts, the crates announce capability, and the spider decides what the living web should do.
Inspect the finished bus on Lucerna Labs ↗