3.3 — Governance Architecture for Boards

Domain 3: Legal & Compliance Risk · Advanced · 28–35 min

What this covers

This course addresses the full governance architecture — before, during, and after a high-stakes commitment. Pre-commitment intelligence surfaces risks before approval. The commitment record survives scrutiny. Post-commitment governance enables course correction while it is still cheap.

Learning objectives:

• Understand pre-commitment governance intelligence and how to apply it before IC vote
• Learn the stress-testing protocols boards should run before approving high-consequence decisions
• See how commitment records are created to survive regulatory, investor, and litigation scrutiny
• Understand post-commitment governance cadence and customer-operated artifact custody

Pre-commitment governance intelligence

Most institutional failures pass through multiple commit moments where risks were known but normalized. The question before IC vote is not "does this look good?" It is:

• What are the hidden risks? What assumptions, if wrong, would materially change this decision?
• Is dissent being suppressed? Are contrarian views visible to decision-makers, or has social pressure created apparent consensus?
• Are governance thresholds being bypassed? Is a high-consequence decision being treated as routine?
• What would have to be true for this to work? Which of those conditions is genuinely uncertain?

Governance intelligence is the practice of asking these questions systematically, before approval.

Stress-testing before approval

Five tests a board should run before approving any high-consequence decision:

Frame test. Is the real question clear, or are we solving for the wrong problem?

Assumption test. What would have to be true for this to work? Which assumptions are most uncertain?

Risk test. If each key assumption fails, what happens? How bad? How reversible?

Alignment test. Do the stakeholders actually agree, or are they quiet? Is apparent alignment actual agreement?

Governance test. Are we treating this decision with the process rigor its consequence warrants?

Creating the commitment record

The record that survives scrutiny documents:

• The Frame: what question, what constraints, what success looks like
• The Plan: what alternatives, why this one, what tradeoffs were accepted
• The Decision: what was committed, who approved, what conditions apply
• The Risks: what the board knows it does not know, what metrics to monitor

This record allows the board to say, under scrutiny: "We defined the question precisely. We examined the alternatives. We identified the key assumptions and the conditions under which we would revisit them. We documented the risks we accepted."

Post-commitment governance cadence

Governance does not end at approval. A sound architecture includes:

• Monthly operating reviews: metrics against Frame assumptions, not general performance updates
• Quarterly assumption reviews: is the thesis still sound? Have conditions changed?
• Trigger mechanisms: if metric X drifts by Y, assumption Z is formally re-tested
• Annual governance review: does the board still have the authority and appetite for this commitment?

This cadence prevents silent failure. Course correction happens while reversal is still possible.

Customer-operated custody

Boards and IC committees should not rely on vendor-held decision records. The artifacts — Frame, Plan, DIR — should be exportable to the organization's own systems: Obsidian, Notion, Confluence, or the board's own data infrastructure.

One-way export of commitment artifacts in portable format means the governance record belongs to the institution, not the vendor. No ongoing access dependency. Full audit trail under institutional control.

---

You have completed Domain 3. Return to the Academy overview to review all nine courses or select a certification path.