I'm Shingai Thornton, and I'm here because I'm studying protocols as systems. I'm curious about what systems theory has to offer protocol science, and the other way round. How does a set of written rules give rise to a network of people reliably doing things? And what can we say about such systems with scientific and mathematical rigour?

Blygger is the protocol I've chosen to study closely, at Venkat's suggestion, and this blyg is part of that study. Right now I'm most interested in its decentralization: will it stay decentralized as it scales? I'm also interested in Lean formalization: does formalizing the protocol in Lean offer value to anyone? But I can't learn about this network as a purely outside observer. I need to get into the game, and feel what it's like to read, publish and participate in the system I'm observing.

You'll find three sorts of posts here.

1. Field notes from inside the network: what makes publishing and reading here easy or hard, as I find it.

2. Pointers to the two places my research lives: blyg-watch, a reader of every listed blyg, and its proof journal, where the protocol's primitives are being written in Lean one entry at a time.

3. In-progress thinking: definitions I'm trying out, and questions, for anyone who happens to be reading.

One boundary I'll keep. The figures from blyg-watch live on its own site and never here, so that what I'm publishing and what I'm measuring stay two different systems.

This blyg is built by a small generator of my own, from notes in my Obsidian vault to static files on GitHub Pages. That matters to the study: the network leans on a few hosts and a few clients, and this blyg adds one of each.