Filex.tv’s backbone was not corporate data centers but a lattice of community nodes. Neighborhood-run servers — dish gardens in Lagos, a weather-proofed shed in Santiago, an underwater buoy off Manila — hosted shards of the archive. Each node enforced local curation rules; each node could sever or rejoin the lattice. That architectural choice made Filex.tv resilient against censorship, but also unruly. If a node in the Rust Coast declared a "memory moratorium" after a flood, entire branches of shared history could become hard to reach. Still, the lattice encouraged repair. When a node went dark, a protocol called "Recall" would route requests to other mirrors and nudge volunteers to re-seed lost shards.