From the ScrumInc website: https://www.scruminc.com/definition-of-done/
Definition of Done
The moment a Product Backlog item meets the Definition of Done, an Increment is born. The Definition of Done (DoD) represents the organization’s formal definition of quality for all Product Backlog Items (PBIs).
I would recommend to make the DoD product-specific and not having a generic One-Size-Fits-All.
You might have an organization wide DoD, and on top of that should every product have their specific criteria.
If an organization does not have one, the Scrum team should set its own. The Definition of Done is the commitment contained within the Increment artifact. Think of the DoD as what the organization requires before it can deliver a PBI to the end user.
This sounds very rigid to me.
Instead of discussing endlessly and establishing DoDs and a stringent process (that nobody follows), I would rather focus on shipping working software.
And, Yes, Working and Done Software is defined in your build pipeline and enables you to continuously deploy and release on demand.
–> Doing over Talking
–> Experimentation over Rigid Process