Revisiting the Flows

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 — from pflow.xyz and pflow.jl to Model@DAO and the Gno.land experiments.

Here’s what’s coming:

• Leap Year Counter as State Machine — when time itself becomes a Petri net.
• Entropy, Revisited — exploring information and energy through John Baez’s lens.
• Vector Notation — the algebra of flow.
• Coq — proving reachability and safety, one transition at a time.
• Merkle-DAGs and Memory — how CIDs trace immutable flows.
• Petri Nets in Bash (v3) — minimal syntax, maximal semantics.
• Solidity Generation — code as compiled causality.
• DiscoPy Revisited — drawing categorical diagrams that execute.
• Tic-Tac-Toe with Petri.jl — the game as an open system.
• Rebuilding the Payments WF-Net — tracing money as motion.

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.