What problem does it solve? When building platform software that routes messages between subsystems, models often default to familiar patterns like pub/sub, actor model, or event sourcing. This Skill preserves Jesse's original spiderweb bus architecture — a layered, organic, elevation-based routing model — so agents write bus code that matches the intended design instead of substituting a generic pattern. ## Core Features & Use Cases - Four-Layer Architecture: Defines Transport (L0), Message (L1), Flow (L2), and Orchestration (L3) layers with Rust trait signatures for each. - Emergent Fabric Model: Threads form as messages flow, intersections emerge where threads cross, and on-ramps/off-ramps move messages between ground-level and parallel highway execution. - Vibration Propagation: Specifies backpressure, cost-aware routing, preloading, and cross-layer signaling as core architectural properties. - Use Case: When adding a bus layer or wiring nodes in Ordo, Nodus, or cumfy-llm, load this Skill first so the generated Rust code follows the spiderweb model rather than a standard message queue. ## Quick Start Read this skill before writing any bus or data-routing code, then implement the four layers with their trait signatures exactly as specified.
