When I talk about compliance infrastructure, people tend to hear one of two things.
Some hear "documentation system": a well-organised folder structure, consistent naming, a SharePoint everyone agrees on. That is not what I mean.
Others hear "compliance tracking tool": something that manages status and sends reminders. Still not it.
Compliance infrastructure is the structured relationship between three things: what you are required to demonstrate, what you claim to demonstrate, and the evidence that supports the claim. Maintained live, continuously, across the full programme.
Here is a practical test. Pick any requirement in your current project. Can you tell me right now: what is the compliance method, what is the specific evidence, what are the activities related to it, planned vs. actual and does all that reflect the design as it stands today. Or the design as it stood when the document was last revised?
What does the compliance infrastructure in your DOA actually look like? Which tools do you use for it?