
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, on the premise that 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:
solidity/generated.sol).lean/proof.lean checks 1-safety, the P-invariants and a unique deadlock over the net's 16 reachable markings by decide (not re-run for this update). That is one finite net checked by evaluation — a whole class of nets proven safe is still a different post.The November promise was that the blog would keep its roots in markdown, code, and flow diagrams, but each post would also carry a live model: a JSON-LD Petri net you can inspect, copy, and run — literate modeling, code and concept sharing the same page. A handful of posts kept it — tic-tac-toe and knapsack link their nets into the pflow.xyz editor — but most don't, and the concept posts almost never carry a model at all.
The series was meant as recursion rather than nostalgia — re-entering past ideas to see what survives composition.
September 2026: the August roster listed a "Z3/SMT" post that was never on the original list; the November line was Coq, and it is now matched to the Lean proof form. The pflow-polyglot link returned a 404 (the repository lives under stackdump, not pflow-xyz). The live-model paragraph was a promise restated as if it were kept; it now says where it was and wasn't. The Solidity line notes that bitwrap.io is no longer hosted.