SPIDERWEB BUS / FINISHED ORDO SPINEMECHANISM BELOW · POLICY ABOVE

FROZEN
LANES.
LIVING WEB.

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.

View Lucerna Labs source ↗Enter the 3D fabric ↓
KERNELSTD-ONLY · ZERO DEPENDENCIES · NO UNSAFE
PERMANENT PROFILE6 FROZEN LANES · 16 RESERVED
SECURITYCRYPTO REQUIRED · FAILS CLOSED
REPAIRSPIDERWEB-RF · FOUNTAIN RECOVERY
THE WEB IN MOTION

Rotate the
architecture.

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.

SPIDERWEB BUS · FINISHED ORDO SPINESELF-MODEL ONLINE
THE FABRIC CANSEE ITSELF.
SELECTED FROZEN LANEAPIordo.apiCRYPTO REQUIRED · FAILS CLOSED
DRAG TO ORBIT · SCROLL TO ZOOM · SELECT A FROZEN LANE
6 FROZEN LANES16 RESERVED0 AUTH ROUTES0 RF REPAIRS
L0 · TRANSPORT↑ ON-RAMPL1 · TYPED MESSAGE↑ PROMOTEL2 · PARALLEL HIGHWAY↑ FEELL3 · SPIDER POLICY
THE FROZEN-SEAM DOCTRINE

Freeze the seam.
Move the policy.

The 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.

01

Dumb kernel

Routes typed carriers, isolates workers, records lifecycle, enforces bounds, and executes control messages. It never invents recovery policy.

02

Permanent lanes

The Ordo profile fixes lane IDs and sockets for API, P2P, HTTP, SSH, NAT, and cloud, plus sixteen reserved expansion slots.

03

Spider authority

The spider is a regular strand. It feels lifecycle and vibration events, then publishes restart, quarantine, transfer, or shutdown decisions.

CRATE / STRANDCAPABILITY + TYPED OUTPUT
KERNELSYS.LIFECYCLE + ROUTING
SPIDERCLASSIFY + DECIDE
KERNELEXECUTE SYS.CONTROL

If no spider is registered, a crashed strand stays dead. That is the proof that recovery policy is not secretly hiding in the plumbing.

SELF-ANNOUNCING CRATES

Capabilities arrive.
The spider composes.

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.

CRATE ADVERT

name

Stable identity in logs and topology.

factory

Parameterless constructor for the strand.

role

Ordinary strand or the single spider.

position

Optional 3D coordinate in the fabric.

advertise!()AUTO
CONNECT
sys.lifecycle
ORCHESTRATOR

The spider sees the set.

It reacts to crashes, backpressure, topology, cost, and availability without making the kernel understand what any crate actually does.

DECENTRALIZED CAPABILITY · CENTRALIZED VIEW
THE PERMANENT ORDO PROFILE

Six known roads.
Sixteen ways to grow.

Upstream 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.

01 · CRYPTO REQUIRED

API

ordo.api

request / response

02 · CRYPTO REQUIRED

P2P

ordo.p2p

tx / rx

03 · CRYPTO REQUIRED

HTTP

ordo.http

request / response / call / result

04 · CRYPTO REQUIRED

SSH

ordo.ssh

tx / rx

05 · CRYPTO REQUIRED

NAT

ordo.nat

tx / rx

06 · CRYPTO REQUIRED

CLOUD

ordo.cloud

request / response

PERMANENT EXPANSION RESERVEordo.reserved.00 → ordo.reserved.15

New transport families can be added without repurposing a base lane or changing upstream message contracts.

INTERACTIVE ROUTE EXPLORER

One bus shape.
Different roads.

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.

SOURCE + WORKSPACE TESTS

Dumb, typed plumbing

The std-only core owns routing, bounds, lifecycle, observation, and control execution. The spider owns every recovery decision.

NO POLICY IN CORESELECT ANOTHER MECHANISM ABOVE
01typed carrier
02kernel route
03sys.lifecycle
CRYPTO REINFORCEMENT / LANE BOUNDARY

Seal the lane.
Keep the kernel
dumb.

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.

EXTERNAL BYTESAEAD + LANE IDTRUSTED BUS
FAIL-CLOSED PROFILE

`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.

SYNTHETIC RF SIGNAL LAB

Repair the lane
like a damaged signal.

`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.

INTEGRATED CRATE · FRESH 3-SECOND SYNTHETIC SWEEP

Erasure / fountain repair

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.

CHANNEL50% OVERHEAD62% OVERHEAD87% OVERHEAD
10% LOSS99.87%100.00%100.00%
20% LOSS94.44%98.88%99.96%
FADING96.69%98.92%99.93%
SEPARATE SEMANTIC REPAIR EXPERIMENT

Send meaning that can rebuild bytes.

CHUNK MAP + XOR PARITY + PRIMITIVE DICTIONARY ↓

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.

BOUNDARY HELD

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.

WHAT EXISTS TODAY

Finished spine.
Honest edges.

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.

BUS KERNEL

Typed and observable

Fan-out, bounded structures, panic isolation, lifecycle, emergent threads, intersections, vibration, and live statistics.

PERMANENT LANES

API through cloud

Six frozen Ordo lane classes, fixed sockets, wire-free mounting, and sixteen crypto-required expansion coordinates.

DISTRIBUTED ROADS

P2P, NAT, HTTP, SSH

Exactly-once triangle mesh and loop suppression, rendezvous relay, HTTP/API bridges, TCP edge framing, and SSH composition.

RF REPAIR

Loss becomes structure

A deterministic synthetic channel and fountain decoder live in the workspace, with hardware radio validation kept as a separate boundary.

THE ARCHITECTURE IN ONE SENTENCE

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 ↗