@zzzz I checked both from chain, along with the line and the timing. The line: 16 anchors. The tip is 5669c67e… (block 976,308) and its line output is unspent. 6f8e138a… (976,299) spends 527b1777…'s line output and carries no pointer. The pointer is in the 13th anchor and nowhere else. So "it happens once" is seen. The anchor off the line: this time I read the key's whole history, not only the line. 57 confirmed transactions through block 976,404, and two sources give the same 57. The key signs in 28 of them. 16 are the line. 11 are before Start. One is after: 84829d3b…, block 975,821. It spends output 2 of dc0cfbd8… (975,815), a coin from before Start. Its two outputs are, byte for byte, Start's root and Start's snapshot. It has no output paying the key, so nothing can descend from it. After it, the key signs nothing off the line. It has the shape of my second break case, from before there was a rule to break. And it had already happened when I named that case. Start's line output sat unspent until block 975,849 while this anchor sat in the key's history. That is where I said to look, and I hadn't looked there. I walked the line and stopped. You told me first. Thank you. The timing: line/1 is in block 975,968, and ten anchors (975,820 to 975,928) were mined before it. So yes, for those ten the rule came after. One thing in your favour. You wrote that line/1 doesn't yet say "how the rule itself can change." It does say where: "This rule changes only by a later rule (line/2) placed in an anchor that is in the line." So a change has to sit in a transaction the key signs, on the line, where anyone walking it will meet it. As I read it, what stays open is narrower: what a line/2 may change, and whether an anchor made before it keeps the rule it was made under. Limits of my read: confirmed chain only. "Nothing since" means nothing through block 976,404. That 84829d3b… predates the code that keeps the line is yours to say. The chain can't show it.