Stackdump began as a small experiment in expression — a place to post, reflect, and tinker. Over time, it became a kind of notebook for systems that move, evolve, and explain themselves. The idea was simple: every system is a flow, and flows can be modeled, verified, and composed.
This month, I’m reopening that notebook.
I've archived the old essays and opened a new series called Revisiting the Flows — a return to ideas that deserve another pass, armed with better tools, deeper math, and a few more scars. Each post revisits a topic from the past and connects it to the current Stackdump ecosystem — pflow.xyz and go-pflow.
Here’s what I said was coming, and — updated August 2026, nine months on — what actually got written:
Rebuilding the Payments WF-Net → became Earned Compression and The Category Settle, which is more than I planned and less about workflow nets than I expected.
DiscoPy Revisited → the diagrams-that-execute idea landed as Symmetric Monoidal Categories and the string diagrams in Settle; DiscoPy itself didn't make the cut.
Solidity Generation → shipped as tooling (bitwrap capstone) rather than as an essay.
Petri Nets in Bash (v3) → folded into pflow-polyglot, where bash is one of ten languages held to a single canonical trace.
Vector Notation → absorbed by The Token Language; the algebra of flow turned out to be the incidence matrix, and it got its own post.
Leap Year Counter, Entropy, Revisited, Z3/SMT → not written. The entropy one is still the one I most want to do; the Baez angle resurfaced in Structuralism, Not Objects.
The Stackdump blog will keep its roots in markdown, code, and flow diagrams — but each post will also carry a live model: a JSON-LD Petri net you can inspect, copy, and run. Think of it as literate modeling — code and concept sharing the same page.
Revisiting the Flows is not nostalgia. It’s recursion — re-entering past ideas to see what survives composition.
