Oh fuck this is genius. Here's how it works: it _moves_ the original block to the new date, and leaves an aliased copy in its original place. So ((ABCD)) from today moves to tomorrow, leaves ((YHDZ)) with identical content and link to ((ABCD)) in its place. This is _amazing_.
Some usability things I'm noticing: since this actually moves blocks to a future daily page, these can get cluttered _really_ fast. Starting a day with a daily page that already has 50 bullet points on there is a very different feeling from starting each day with a blank page.
UI for the increment is currently unclear, but I expect that to change fairly soon. Standard increment atm is 2 days, changing the value in {{[[∆]]:3}} manually is possible, but counts from original entry point (?) so requires thinking, has friction.
You can add these anywhere in your graph, incrementing still works. So a TODO on [[Some Project]] will then show up on a future daily page.
When you do queries, you absolutely have to specify the date range. A query for {{[[query]]: {and: [[flashcard]] [[∆]]}}} will otherwise return every time you answered the card in the past.
What do I mean here? {{[[∆]]:3}} means "we're three days from original occurrence" _not_ "next increment is 3 days". Next increment is +2, if you want to see it in three days you have to {{[[∆]]:3}} -> {{[[∆]]:4}} and then click delta. (I think)
The roam/css hackers will be pleased to know that occurrences of [[∆]] are also marked by "rm-orbit-tag" in the css.
I'm also confused by this behavior. When are child-blocks transported versus kept in place? @Conaw ?
Solution to problem above: Shift-Clicking the delta transports the children in subsequent movements
