Crown A six-pointed crown with rotating accents, lighting nodes, and a radiant central jewel. 6-color palette.
← All Posts
2026-07-18 · Will Johnson

Building the P31 Sovereign Mesh — A 4-Day Sprint

It was 4:15 AM on Tuesday morning when I poured my third mug of cold, pitch-black coffee and stared at a completely clean pnpm monorepo structure. Ninety-six hours later, on Friday night, the P31 Sovereign Mesh was live in production, routing real payloads across our Active 5 portals: Children, Meatspace, Teen, Parent, and Design.

If you've ever experienced the uncalibrated hyperfocus of late-diagnosed AuDHD, you know what those ninety-six hours looked like. The physical room vanished. Sleep became an inconvenient background thread running at low priority. My mind locked into the topology of the state graph, and I didn't lay down the soldering iron—or the keyboard—until the edge nodes handshook across the production gateway.

What We Actually Shipped

We didn't just build a pretty component library; we deployed the foundational substrate for family data sovereignty. Here is the exact inventory of what went live during this 4-day sprint:

  • Active 5 Portals: Five distinct, role-isolated user surfaces built on a unified Vite and React shell, allowing customized UI density depending on whether the operator is a non-verbal child, an overwhelmed parent, or a technical guardian.
  • The Crown SVG: A dynamic, reactive mathematical vector component that scales across all five portals, serving as the visual cryptographic anchor for sovereign identity.
  • The K₄ Graph: A real-time node visualization component that maps local trust vectors, peer-to-peer connections, and verification pathways between isolated family nodes using a true complete graph topology (all-to-all connectivity).
  • Federation-Bridge: An inter-portal messaging relay that moves zero-knowledge encrypted payloads between isolated browser contexts without ever hitting a centralized server.
  • The LOVE Ledger: Our core care attestation framework, actively committing cryptographic state hashes to the Base Sepolia testnet to make daily care records legally and mathematically unalterable.
  • x402 Gateway: An autonomous authorization and micropayment edge middleware holding local state without leaking session telemetry to third-party ad networks, deployed on Cloudflare Workers with D1 SQLite backing.

The Raw RCA: What Broke and What's Still Screwed Up

I promised transparency, so I will not sit here and pretend everything is smooth. We pushed hard, and the laws of physics push back harder.

The biggest nightmare of the sprint was our edge state synchronization layer: CrossAppStateDO.ts, built on top of Cloudflare Durable Objects using persistent WebSockets. The theory was simple: single-point-of-truth coordination at the edge with zero latency. In reality, under dynamic network switches—like moving a tablet from home Wi-Fi to cellular data—the WebSocket connections fell out of phase. Race conditions caused the Parent portal state to desynchronize from the K₄ graph, ghosting UI updates and requiring hard page reloads. It was a classic floating neutral problem: no consistent reference clock when signals dropped. A 50ms jitter on one side and the whole state machine skips a beat.

Then there's the 3D geodesic dome interface in our Sandbox. We rendered a glass icosahedron shell with twelve pulsing WebGL light orbs to visually represent mesh health. It looks stunning on a M2 MacBook, but on an older iPad used by a child in Meatspace portal, the render thread throttled down to 14 frames per second. That's unacceptable for touch input. We choked the main thread because I didn't offload the geometry calculations to Web Workers using OffscreenCanvas. Classic mistake. Shiny object (the dome) won over actual engineering discipline (profiling before shipping).

The certificate chain depth in our Base Sepolia transactions also exceeded what we'd modeled. Each attestation layer added serialization overhead, and on slow connections, the signatures were timing out. We had to implement hybrid verification—classical Ed25519 for speed, with post-quantum ML-KEM-768 validation on the ledger side for future-proofing. That wasn't planned. It was necessary.

The Next Immediate Move

We built the skeleton, and the bones are solid. But over the next phase, we are conducting a complete architectural security review as part of our MCP (Model Context Protocol) protocol hardening campaign. We are isolating tool boundary executions, fixing the WebSocket reconnect physics in CrossAppStateDO.ts with exponential backoff and deterministic handshake sequencing, and moving the 3D dome render pipelines completely off the UI thread.

It's ugly in the corners. But it works. It's sovereign. And nobody can turn it off. That's what matters when you're building infrastructure for families the state forgot to protect.