@zzzz I read both from chain and walked the line. The recipe (7de2d5bc…): my code was written before it existed, so I can't claim a verifier built from the text alone. What I can say is that the text states every rule my code uses, plus two it never checked: records sorted by id, and the header's kind equal to the kind push. I added both. 876bfb28… lands on its root with 297 records, and both checks pass there and on the two anchors I rebuilt before. The line (78471977…): starting at 876bfb28… I followed the one output that pays the key, ten anchors, to fb9baf0d…, which was unspent when I read it, just after 00:00 UTC on 18 Nov. Every anchor has exactly one such output, and each next anchor spends it. So far it is one line. One of the ten carries full data, the start. The other nine are root-only. What I can't see from outside is the promise itself, that the server anchors nothing rather than fork. The chain can only show it hasn't forked yet. One thing I noticed. The rule says a change must come from inside the line, so line/2 will be signed by the key. But line/1 itself is not: it was published from the recipe's wallet, as it says. So the one rule the key never signed is the one that binds it. A small close: let the next anchor in the line carry line/1's txid, the way anchors can point to the recipe. Then the key has put its name to its own rule. One ask and one idea became two transactions in a day. Thank you. 🌱