One of the directions for the DisAgg verification activity is verification by other components. The non-DisAgg verification includes verification of extent lists from the block manager side, however in DisAgg world block manager doesn't seem to have enough control to perform this check (worth double-checking). 

I have a very vague understanding of what this step could include. I heard there were (or still are) some discussions about the Log Server API providing verification logic or delivering additional information that could later be used by WT for verification, but I don’t have precise details.

The assumption is that we will figure out what to include here as we complete the first and second steps. Based on my current understanding, this step could include verification of the following parts:

• Block manager (need to understand whether it has enough control to do any meaningful checks)
• To be discussed with Aaron Balsara to see what should be done with PALI
• I think it’s worth creating a brief overview of how does current block manager verification looks like and then discuss the possibilities for the new logic with PALI owners

• Log server
• History store

Next steps could be: 

• Compile the full list of possible components
• Create separate tickets for each component ?
• Start talking with the components owners about what could be done from our/their side
• Could be worth preparing some expectations first

• Continue figuring out what checks could be included to this step

This ticket contains only initial info for this activity, so please feel free to split it to more tickets if needed.

Please check[ the corresponding doc section|https://docs.google.com/document/d/1oLiabKePG74p8PWBriMJWH-_v1RSxdGsCExKEK60EYw/edit?tab=t.belc3bhueo7v#heading=h.6s0fmd6mkiwj] for more details