Seven layers, one posture
The stack
The book reads a human life as a stack of seven layers, from the body you run on to the people around you. Choose a numbered point in the scene to explore each one.
Layer 1 of 7 · Chapter 2
Chassis
The body as hardware
In the scene: the body.
Specs over shame.
You are not a spark trapped in meat. You are a terminal with limits, filters and failure modes. Any honest talk about meaning has to start with the physical layer.
Key ideas
- Limits are documentation, not a sign of being fallen: power, sleep, sensory filters, delays and developmental windows describe the machine.
- Bodies show engineering fingerprints: backup systems, messaging networks, shared parts, and security that can attack its own hardware.
- Tiredness, hunger and stress raise the noise floor and change what you experience.
- Different body and brain configurations are different settings, not holiness scores.
What it does not claim
- It does not prove every ghost story. Most claims fail a proper check.
- It does not ban talk of an afterlife, but any such idea has to survive what we know about brains.
From Chapter 2: The Hardware Problem. Read the chapter guide for Chapter 2
Layer 2 of 7 · Chapter 3
Syntax
DNA as readable code
In the scene: the DNA strand inside the body.
Inspectable language beats sealed story.
DNA is readable code, not mystical dust: four letters, genes as routines, regulation as control flow, and shared libraries across species.
Key ideas
- Gene expression is code that runs differently depending on context.
- Life looks versioned under load: variation as change sets, selection as harsh testing, leftovers that remain.
- A "defect" often depends on the environment.
- Original Sin reads better as inherited firmware debt than as a moral stain.
What it does not claim
- Readable source ends lazy dogma; it does not make us gods.
- It does not settle who wrote the code. That question waits for the next layer.
From Chapter 3: DNA as Syntax. Read the chapter guide for Chapter 3
Layer 4 of 7 · Chapter 5
Bandwidth
How much signal gets through
In the scene: the signal waves around the head.
Audit before names.
Everyday awareness is filtered "dial-up". Bandwidth can climb through twilight sleep, trained attention and immersion to rare sudden downloads. These are systems events, not sainthood.
Key ideas
- Signal-to-noise: how much structure survives compared with static.
- Cases like Tesla, Ramanujan, Loewi, Poincaré and McClintock keep the category open.
- Keep the method (what was documented) separate from the event (what was reported).
- Stabilise, reduce noise, sort, and interpret last.
What it does not claim
- These cases do not prove a named deity of any tradition.
- They do not prove a prophet class, or that every vision is signal.
- They are no reason to skip looking after your body first.
From Chapter 5: Bandwidth & System Downloads. Read the chapter guide for Chapter 5
Layer 5 of 7 · Chapter 6
GUI
Symbols as dashboards
In the scene: the cards in the hand.
GUIs are tools, not servers.
A dial-up receiver cannot show the raw feed, so people invent symbol dashboards. Tarot is the worked example. A GUI is a tool, not the server.
Key ideas
- Symbols are lossy compression; ritual is a session protocol.
- Sibling tools such as the I Ching, runes, astrology and dream logs belong to the same class.
- The reader is the display driver; the cards do not choose.
- Hygiene: settle first, ask a clear question, keep the session short, check against real life.
What it does not claim
- It does not prove the future is fixed and readable.
- The deck is not God, spirit or the network root, and the reader is not a prophet.
- Fraud exists, but fraud does not cancel useful compression.
From Chapter 6: The Analog GUI. Read the chapter guide for Chapter 6
Layer 6 of 7 · Chapter 7
Ops
Running the receiver on purpose
In the scene: the console beside the figure, with a moon and a checklist.
Hot boards invent cosmologies.
Lower the noise, raise the signal, keep your method. Look after sleep, food, stimulation and body load before reaching for oracles.
Key ideas
- Check your noise floor each week.
- Seven moves for any claim: strip the branding, demand a mechanism, break it down, simulate, try to disprove it, iterate, and hold mystery open.
- Outbound honesty: clear requests, no panic bargains, and log what really happened.
- If a sort keeps failing, fix the noise floor before the theology.
What it does not claim
- Maintenance improves judgement. It does not buy salvation or prove the mesh.
- Comfort is not confirmation.
From Chapter 7: Optimizing the Receiver. Read the chapter guide for Chapter 7
Layer 7 of 7 · Chapter 8
Mesh
Living on the shared highway
In the scene: the other people around the figure, linked by lines.
Audit beats altar.
You live among other people and other signals. Sort the traffic, read the climate of the groups you are in, and keep your agency.
Key ideas
- Four traffic classes: hostile, maintenance, residual and human.
- Judge communities by their climate, not their logo: some return your agency, some farm dependency.
- You are a sender and an amplifier too. Rate-limit rumour.
- Stabilise, sort, and interpret last.
What it does not claim
- A feeling is not the identity of an entity.
- The physics of the mesh is not settled; those questions stay open.
- No new church, no prophet licence.
From Chapter 8: Operating in the Mesh. Read the chapter guide for Chapter 8