Runtime lineage
Does the active build import or execute the Atom runtime, renderer, engine, or primitive stack?
Original systems that stand on their own architecture. They may use a bus. They may be hybrid. They may connect to Ordo. None of those words automatically make them Atom or Spiderweb.
Browse verified builds ↓Each entry states exactly what it inherits, what it does not inherit, and which behaviors were proven in current source.

My first application: a Rust-native, radio-first creator command center designed as a lightweight alternative to hardware-hungry creator stacks.

An adaptive defensive VPN cluster with operator-signed membership, hybrid post-quantum sessions, adaptive mesh paths, warm-standby transport, and fail-closed orchestration.

A coordinated memory hierarchy that turns secondary GPUs into warm cache for the primary, stages upcoming blocks in the background, and reports RAM spillover instead of hiding it.
Every future entry is checked against four boundaries before it appears here.
Does the active build import or execute the Atom runtime, renderer, engine, or primitive stack?
Is the bus actually Spiderweb—with layers, ramps, emergent threads, intersections, and vibration—or merely another typed bus?
Hybrid must be qualified: database retrieval, cryptography, transport, compute, or another specific composition.
Source, tests, simulations, benchmarks, and live behavior are labeled separately so a design claim never masquerades as field proof.
Atom-built work and independent work can strengthen each other without pretending they share the same foundation.
Return to Atom ↗