PeerWeave Devlog

Threads from the mesh

Slow, honest field notes from building PeerWeave—the moments when the stack actually breathes, along with the questions that show up in the middle of the night.

Teleidoscopes, mirrors, and the graph you don’t see

Why we named PeerWeave’s graph-reasoning engine after a toy you point at the world—and how one reality becomes many views.

From kaleidoscopes to teleidoscopes (no object cell—you point at the world), then to PeerWeave: one graph, many transforms, and invariants as “what stays true.” With diagrams.

Read the full log
  • peerweave
  • teleidoscope
  • graph

The first answer that stayed

A tiny milestone: the moment PeerWeave caught an AI answer inside its own mesh instead of losing it to somebody else's chat window.

An LLM talked about AI in agriculture—droughts, sensors, pests—and for the first time that conversation lived as a proper object inside a PeerWeave space, ready to sync to other peers and show up in the graph.

Read the full log
  • peerweave
  • systems
  • devlog

Other devlogs

Building my personal website

Why I chose static HTML over frameworks, how the three-faculty structure emerged, and what I'm building next.

A deep dive into the decisions behind this site: zero build tools, semantic HTML, vanilla JavaScript, and the three-faculty structure (Memoria, Imaginatio, Ratio) that organizes everything.

Read the full post
  • website
  • development
  • devlog