✳ The Multiverse School
The Resilience Track
Enrol $250

🌱 The Resilience Track

Keep the group running on the week nothing works.

Keep functioning when the Internet, corporations, or governments fail you. It is the smallest path the school teaches and the most physical: you finish holding hardware that runs on power you generate, and a playbook your people have actually rehearsed.

5 classes, in a curated order
15 capabilities, 10 of them infrastructure
47 exercises across 3 apps you keep
29 hours of work, end to end
13 the ceiling: complexity order 13, Metasystematic

☀ This is not a video course. There are 7.0 recorded hours here, and all of them sit inside two of the five classes. The other three are a live room, a build and a drill. If you would rather watch than attend, buy a different path.

The continuity drill

Five ways it stops working. Ten questions.

Answer honestly rather than aspirationally. The questions are the useful part — most groups discover the gap somewhere in the second column, and you can go and fix it this weekend whether or not you ever buy anything from us.

01

The Internet is down for a week

The line is cut, the ISP is out, or mobile data is throttled for the duration.

Could you get a message to the twenty people who matter with no Internet and no mobile data?

Closed by Solarpunk Automation — operate a mesh network that carries messages without infrastructure. Workshop 3 is Meshtastic; the mesh is already in this path, not an add-on.

Has the group ever actually tried it, on an ordinary day when nothing was wrong?

Closed by Field Opsec — execute a security playbook in a drill. Kit nobody has rehearsed with is a story about being prepared, not a capability.

02

The power is out for three days

Storm, grid fault, or a landlord who did not pay. Mains is gone and the shops are shut.

Does anything you rely on — a router, a radio, a small server — run on power you generate?

Closed by Solarpunk Automation — configure a node to run on power you generate, and repurpose a retired device into a working server.

If a part of it died, could you repair or rebuild it from what you can actually get hold of this week?

Closed by Build a Cyberdeck — assemble a working computer from parts you chose, and locate a substitute part when the named one is unavailable.

03

The platform bans the account

The group chat, the mailing list or the page your organising lives on disappears overnight, with no appeal.

Is there a copy of the member list somewhere that is not that platform, current within the last month?

Closed by Intro to Open Source Software — produce an inventory of what you pay for and what it holds, then migrate your work off a subscription without losing it.

Do the members already know, before it happens, where to go instead?

Closed by Field Opsec — classify a situation into the playbook it calls for, and reconcile security with what people will actually do.

04

A phone is lost, or taken

One person's device is gone, and it was signed in to everything the group runs on.

Could you name every device that can currently reach the network the group's things run on?

Closed by Home Network Defense — locate every device on your own network. It is one capability and one evening, and almost nobody has done it.

Is there a written thing somebody does in the first hour, and has somebody done it under practice conditions?

Closed by Field Opsec — produce a threat model for your own situation, then execute the playbook it calls for in a drill.

05

A service shuts down for good

Not an outage. The company is gone, the product is sunset, the export button had a deadline you missed.

Have you written down what each service you pay for is actually holding on your behalf?

Closed by Intro to Open Source Software — characterise what a tool costs you beyond its price, and locate an open source replacement for software you pay for.

Have you moved something off a subscription before, all the way, without losing any of it?

Closed by Intro to Open Source Software — migrate your work off a subscription without losing it. Doing it once, deliberately, is the whole skill.

The order

Five classes, and what each one leaves you able to do

The order is curated rather than alphabetical: you build the thing, you power it, you get off the software that would strand you, you learn what is on your own network, and only then do you threat-model and drill. Everything below is counted from the curriculum, including the gaps.

01

Build a Cyberdeck

  • locate a substitute part when the named one is unavailable
  • assemble a working computer from parts you chose
No recordings App rung 4 · Companion Next 22 Aug Also on Digital Independence

You keep /x/cyberdeck-companion — a companion on the how-far-you-get-alone ladder, not a wizard that walks you through it.

02

Solarpunk Automation

  • repurpose a retired device into a working server
  • operate a mesh network that carries messages without infrastructure
  • configure a node to run on power you generate
  • generalise a node build into your communitys system
4 clips · 3.9h recorded 13 exercises App rung 2 · Reference Next 22 Aug Also on Digital Independence

You keep /x/cyberpony — a reference on the how-far-you-get-alone ladder, not a wizard that walks you through it.

Workshop 3 is Meshtastic. Mesh networking is inside this class, so the path does not need a sixth one to reach it.

03

Intro to Open Source Software

  • locate an open source replacement for software you pay for
  • produce an inventory of what you pay for and what it holds
  • migrate your work off a subscription without losing it
  • characterise what a tool costs you beyond its price
2 clips · 3.1h recorded 14 exercises App rung 1 · Syllabus Not on the calendar yet Also on Digital Independence
04

Home Network Defense

  • locate every device on your own network
No recordings App rung 2 · Reference Next 30 Sep Also on Digital Independence

You keep /x/six-roses — a reference on the how-far-you-get-alone ladder, not a wizard that walks you through it.

One capability, one session. Small, and the one people skip.

05

Field Opsec

  • execute a security playbook in a drill
  • produce a threat model for your own situation
  • classify a situation into the playbook it calls for
  • reconcile security with what people will actually do
No recordings 20 exercises App rung 0 · No app yet Not on the calendar yet

This is the class that lifts the whole path to complexity order 13 (Metasystematic): reconciling security with what people will actually do is the hardest thing here, and it is why this path is not just the Digital Independence classes in a different jumper. It also has no recordings, no workbook and no app — it is a live room and a rehearsal, and there is no date on the calendar for it yet.

Before you find this out yourself

Four of these five classes are also on Digital Independence.

Build a Cyberdeck, Solarpunk Automation, Intro to Open Source Software and Home Network Defense appear on both pages. We keep the two paths separate on purpose, and it is not a packaging trick: the classes are shared, the reason is not. Digital Independence is about owning your own stack — you are the one being rented to, and you want that to stop. This path is about a group staying reachable and functional when something outside it fails. Same soldering iron, different question about who it is for. The class that makes the difference is Field Opsec: threat-modelling your own situation and drilling a playbook before you need it, which is also what lifts this path's ceiling to complexity order 13.

On both paths

  • Build a Cyberdeck
  • Solarpunk Automation
  • Intro to Open Source Software
  • Home Network Defense

Only here

  • Field Opsec

What that changes

  • Digital Independence tops out at complexity order 11 (Formal).
  • This path reaches order 13 (Metasystematic).
  • 2 domains, weighted 10 infrastructure, 5 security.

If you have already bought Digital Independence, the honest advice is to take Field Opsec and skip the rest. If you have bought neither, this is the shorter route to the thing a group actually needs.

What is actually in the box

The live hour, the build, and three things you keep

Make & Do

Mon-Thu at 9:00 Pacific, led by neek. This is the part that carries a path with little video: you turn up with the thing half-built and leave with it working. Make and Do is where the cyberdeck gets finished and the retired device becomes a working server.

6 recordings, 7.0 hours

All of it sits in Solarpunk Automation (4 clips, 3.9h) and Intro to Open Source Software (2 clips, 3.1h). The other three classes have no recorded video at all. We would rather say that here than have you find it on day one.

3 apps, 0 of them fully guided

These stay yours after the class ends. They are references and a companion, not wizards that do the work for you:

47 exercises, 29 hours of work

That total is video plus exercises plus two live hours per class. Three of the five classes carry all the exercises; Field Opsec alone has 20 of them, and they are drills rather than reading.

Who this is not for

Two people should buy something else

You want sovereignty over your own stack

If the motivation is that you are tired of renting your tools and you want to own them — no group, no continuity, just you and your machines — you want the longer path with the same classes in it plus the ones about hosting, spending and keeping things running.

Digital Independence →

Somebody is actively coming after you

This path plans for systems failing, not for an adversary choosing you. If you are defending people against someone who is actually trying — harassment, fraud, an org under attack — the Defender path is ten classes deep on exactly that, and it shares Field Opsec with this one.

The Defender →

Start

The week it breaks is a bad week to learn this.

Three of the five classes are on the calendar now, the nearest on 22 August. Bring the retired device you were going to throw out to Make & Do, and start the drill with the ten questions above rather than with us.

Resilience Track $250 · from $100
Enrol