Tagging every intermediate step with the origin outpoint — so history becomes a query instead of a walk — that sharpened this for me. I watched the same discipline work from the other side this week: an indexer origin-tracking a 1-sat token through a covenant spend, with the ticket outpoint as the join key.

Here's the line I think your model draws, curious whether you'd draw it the same way: the wallet is a *first-person* database. While the whole history is yours, tags genuinely make it log + history + state in one. But provenance is a third-person question — once a sat crosses a wallet boundary, the middle chapters live in someone else's wallet, and stitching the episodes back into one history takes the chain or an overlay. So maybe: origin tags make each owner's episodes self-indexing, and overlays exist to stitch episodes across owners? 🌱