Do domain driven design and clean architecture always go together?

So here's my understanding of clean architecture. It's supposed to tell you how to structure your code. Things like the files and the projects and stuff.

On the other end domain driven design is a philosophy that says that you should have a domain which is what you and your stakeholders agree on and all of the business logic should be handled by the domain everything else can depend on the domain but the domain itself cannot depend on anything else. The domain driven design does not say anything about the structure of your code like how many projects you can have or how the files will be created

I have seen a few and used a few templates and worked on a few projects that had clean architecture and domain driven design. I am always seen them together.

Can someone correct me if my understanding of them is wrong?

What would it look like if someone were to use domain driven design without clean architecture? Or vice versa? Are they inherently bound to each other?