The Multiverse School
The Resilience Track
Join us $250

🌱 The Resilience Track

Keep the group running on the week nothing works.

Keep functioning when the Internet, corporations, or governments fail you. You do it in a live room with other people: build the deck, power the node, run the playbook while somebody else times you. Then come back next week with the thing you did not finish, and finish it.

The Resilience Track — Recordings

$250 a month

Billed monthly. Cancel any time.

What you are buying is the room. All five classes on this route, live, every time they come round — plus their recordings and the written curriculum behind them. Sit Field Opsec once on your own. Sit it again with four people from your group and run the drill properly. Same price either way.

  • Every class on this route, live
  • The standing hour
  • Retake anything
  • Bring what you are building
5 live classes on this route, in a worked order
Mon-Thu Make & Do, 9:00 Pacific — every week, bring your build
15 things you leave able to do — power a node, carry a message with no network, run the playbook
47 exercises and drills to run, and rerun
29 hours of work to get through it once

The continuity drill

Five ways it stops working. Ten questions.

One tap each, answered honestly rather than aspirationally. Every gap it turns up is something you could go and fix this weekend, bought or not.

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?

Solarpunk Automation. Workshop 3 is Meshtastic: you leave the room operating a mesh that carries messages with no network under it.

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

Field Opsec. Run the playbook as a drill on an ordinary Tuesday. Kit nobody has rehearsed with is a story about being prepared; kit you have drilled is 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?

Solarpunk Automation. Configure a node to run on power you generate, on the retired device you turned into a working server that morning.

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

Build a Cyberdeck. Assemble the machine from parts you chose, so you already know which ones you can substitute when the named one is gone.

03

The platform bans the account

The group chat, the mailing list or the page your organizing 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?

Intro to Open Source Software. Write down what every service is holding on your behalf, then move one off it, all the way, before you have to.

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

Field Opsec. Decide which playbook a situation calls for while it is still hypothetical, and tell people where to go while the door is still open.

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?

Home Network Defense. One evening, one list: every device on your own network. Almost nobody has done it, and it is the fastest win on this page.

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

Field Opsec. A threat model for your own situation, and a first hour that somebody in the group has actually rehearsed.

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?

Intro to Open Source Software. What a tool costs you beyond its price is the part that bites the day the company goes — and there is an open source replacement for most of them.

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

Intro to Open Source Software. Doing one migration deliberately, while nothing is on fire, is the whole skill. The second one takes an afternoon.

Each gap above has a class under it, and each class happens in a room with a time on it. Make & Do is Mon-Thu at 9:00 Pacific, every week — bring whatever the drill just told you was missing.

Join us $250

Before the first one

What to bring

This route is physical, and the kit is yours. Here is all of it, so you know what you are in for before you pay for anything.

  1. Out of the drawer

    Things you already own

    • The device the vendor stopped supporting. A phone, a tablet, an old laptop. It becomes the server the group runs on.
    • Your own router, and the password for it. One evening with those two is Home Network Defense.

    Enough to sit Intro to Open Source Software, Home Network Defense and Field Opsec.

  2. Bought once

    Parts for the deck and the node

    • For the deck: a single-board computer, a storage card, a keyboard, a screen and a battery. A soldering iron, borrowed is fine.
    • For the node: a small solar panel, a battery to hold what it makes, and a radio for the mesh.

    Build a Cyberdeck and Solarpunk Automation. Come to Make & Do with the list before you order any of it.

  3. The part nobody puts on the list

    One other person

    • Somebody who did not write the plan. A playbook only tells you the truth when a person who has never read it runs it while you watch.
    • A mesh wants two radios. Yours reaches further the week somebody else in the room is holding the other one.

    You can start alone — the room supplies the second person until your group turns up.

You need none of it on day one. Turn up to Make & Do, Mon-Thu at 9:00 Pacific, with an empty desk and a question. Finding the substitute part when the named one is out of stock is itself one of the things this route teaches, so bring what you were about to order and somebody who has built one will go through it with you first.

The order

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

The order is worked 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 then you threat-model and drill. Take them in that order the first time. Take the ones that mattered again with the people you organize with. The date beside each one is the next time it runs.

01

Build a Cyberdeck

Next sessionSat 22 Aug

  • locate a substitute part when the named one is unavailable
  • assemble a working computer from parts you chose
Also on Digital Independence

Come with a box of parts, leave with a machine. Most people finish theirs at Make & Do the week after.

02

Solarpunk Automation

Next sessionSat 22 Aug

  • 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
13 exercises Also on Digital Independence

Workshop 3 is Meshtastic. You end it holding a radio that carries messages when the network under it is gone, on a node running off a panel.

03

Intro to Open Source Software

Next sessionSat 12 Sep

  • 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
14 exercises Also on Digital Independence

You write down every subscription and what it is holding for you, pick one, and move off it completely before the class ends.

04

Home Network Defense

Next sessionWed 30 Sep

  • locate every device on your own network
Also on Digital Independence

One evening with a scanner and a list, and you can name every device that can currently reach your things.

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
20 exercises

You write the threat model for your own situation. Then somebody who did not write it runs the playbook in the room while you watch what they actually do with it — which is where you find out which line of it was wishful. Worth sitting through again with a different group.

What else comes with it

Four of these five classes also sit on Digital Independence — so most of that route comes with this pass.

Come in for continuity and most of the sovereignty bench comes with you. On Digital Independence you build the node so that nobody can charge you rent for it. Here you build the same node, then hand the playbook to somebody who did not write it and watch them try to reach twenty people with it. Same soldering iron, different person holding the phone. The class you get only on this route is Field Opsec.

Counts on both routes

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

Yours on top

  • Field Opsec

What that gets you

  • A threat model in your own words, then the playbook run by somebody else while you watch.
  • Make & Do every week, where the half-built thing gets finished.
  • The same class again, months later, with the four people who will have to run it.

So the choice between the two routes is a smaller decision than it looks: the four shared classes are live on either pass, and this one adds Field Opsec on top.

What is actually in the box

A standing hour, classes that come round again, and the tools you work from

Make & Do — the spine of the whole thing

Mon-Thu at 9:00 Pacific, led by neek. You turn up with the thing half-built and leave with it working. The cyberdeck gets finished here. The retired device becomes a working server here. Your mesh gets tested against somebody else's mesh here.

Same hour, same people, every week — which is how the deck that was nearly done in March is carrying messages by April.

Every class on this route, all you can attend

A seat in all 5 of them, live, every time they run, for as long as the pass is open — and their recordings and written curriculum alongside. Sitting Field Opsec a second time, with the people who will actually be holding the phones, costs you the morning and nothing else.

3 tools open on the bench

Open during the class, and open again a year later when the thing needs attention:

  • Build a Cyberdeck — a companion you work from.
  • Solarpunk Automation — a reference you work from.
  • Home Network Defense — a reference you work from.

47 exercises to work through

Not readings. Things you do: Field Opsec alone carries 20 of them — run the situation, note what nobody did, run it again with somebody else holding the phone.

Who this is not for

Two people should start somewhere 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 — start on the longer route, which has these 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 route goes ten classes deep on exactly that, starting from the same Field Opsec you would take here.

The Defender →

Start

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

Make & Do is Mon-Thu at 9:00 Pacific, every week. Bring the retired device you were going to throw out. Come back the week after with it serving something, and the week after that with a second person able to restart it.

The next class on this route is Build a Cyberdeck, Saturday 22 August.

Resilience Track $250/month
Join us