Governance codes have matured into a serious body of work. Listed companies answer to the UK Corporate Governance Code. Large private companies report against the Wates Principles. Public bodies work within the CIPFA/IFAC good governance framework and the Seven Principles of Public Life. Each is principles-based, each is respected, and each relies on disclosure rather than enforcement: comply or explain, apply and explain. And below all of them sits the overwhelming majority of British businesses, the SMEs to whom no code applies at all.
Underneath all of them sits the same unstated assumption: that boards and leadership teams will behave under pressure the way the principles describe. The codes can require an audit committee. They can require a culture statement, a risk framework, an evaluation cycle. What no provision can require is that anyone tells the truth when the meeting turns tense.
The record of governance failure says this is exactly where the codes are vulnerable. When organisations with compliant structures fail, the post-failure inquiry rarely finds a missing committee. It finds unspoken truths, behaviour that drifted from stated values, decisions deferred past their natural point, and accountability that fragmented into functional self-protection. That sequence has a name here: it is the Failure Sequence, and the five disciplines exist to interrupt it.
The relationship between RESOLVE and the codes is therefore straightforward. The code supplies the architecture, and RESOLVE supplies the behaviour under load. An organisation needs both, and neither substitutes for the other. RESOLVE claims no compliance status and replaces nothing. It makes the behavioural assumption behind every code explicit, measurable, and trainable.
A code can require a culture statement. It cannot make anyone tell the truth in a tense meeting.