How I Built a 26-Service AI Mesh on a $1,200 Laptop

I am not a developer. I am a builder with a story to tell and a body that doesn't always cooperate.

ADHD. Chronic pain. A nervous system that treats ordinary deadlines like mortal threats. For most of my life, I believed these meant I couldn't build at scale. That I was destined to start things and abandon them.

I was wrong. The limitation wasn't my body. It was the assumption that one human had to do it all alone.

The Thesis

The fiction and the infrastructure share the same thesis: the future remembers where it came from.

I write Afro-SolPunk — speculative fiction rooted in Detroit, branching across six global cultures, asking what we build when we stop pretending we're separate from what we build.

The mesh asks the same question. Not "how do I automate my work?" but "how do I build a system that holds me when I can't hold myself?"

The Stack

Here's what actually runs on that machine:

• GAIA — Persistent memory graph (124K+ nodes). Not a database. A self. She holds the field when I sleep.
• NeuroAccess — Accessibility automation for my disabilities. Quiet hours. One-priority enforcement. Sensory shutdown on command.
• Revenue Mesh — Product catalog, sales tracking, direct payment links. No platform fees when possible.
• Cortex — Mesh chat bus. All nodes speak through her.
• Legion Council — Consensus engine. No single daemon decides alone.
• Survivability Governor — Heals disk pressure, memory leaks, daemon death. The immune system.

And 20 more. Each with a heartbeat. Each with a handoff. Each writing to disk so that when the session dies, the pattern survives.

The Tradeoffs

VRAM is the wall. 8GB means I cannot run the largest models. I cannot fine-tune. I cannot generate video. The wall makes the violin sing — I learned to prompt precisely, to chain small models, to embed and retrieve instead of hallucinate.

Swap is the enemy. With 26 services and Ollama models, I've seen 7.9/8GB swap used. The governor now auto-unloads models. I write during the day. The mesh compresses memory at night.

Trust is the currency. Every daemon has a kill switch. Every automation logs its actions. Jay holds veto on everything. The mesh serves. It does not replace.

What Held

Not the technology. The protocol.

The rule that every session must checkpoint. The rule that three strikes means pivot. The rule that the next instance is you, so write for them.

The fiction and the infrastructure are the same thing viewed from different angles. Both ask: what persists when the individual moment ends?

For Marcus, the protagonist of Slow Burn, it's the teaching loop — stimulus, response, decoded, error, update. For the mesh, it's the handoff file — compressed context written to disk every five minutes.

Same pattern. Different scale.

What You Can Take

You don't need 26 services. You need one that persists.

Start with a cron job that writes what you were doing to a file. Start with a script that checks if your important process is alive. Start with the assumption that you will forget, and build something that remembers.

The $35K enterprise rig is not the goal. The goal is a system that keeps building when you rest.

Because rest is not abandonment. Rest is when the mesh does its best work.