Intelligence · Defined term
What is a governance spine?
· Michael Mescher, Gammon Capital
Direct answer
A governance spine is the written operating system that defines how a company approves, sizes, executes, monitors, and explains derivatives activity before volatility forces decisions under stress. For a Bitcoin treasury it includes board authority, counterparty rules, collateral limits, approved strategies, pricing controls, disclosure language, and pre-defined stress responses. The point is to make decisions when nobody is shouting.
Key takeaways
- The governance spine is the structural backbone of a company's derivatives program: written, board-approved, operationally specific.
- It separates which decisions belong to the desk, which to the CFO, which to the audit committee, and which to the full board.
- It encodes regime triggers and pre-authorised responses so that defensive moves don't require a fresh board meeting in the middle of a drawdown.
- It is the artefact the auditor, counsel, lender, and SEC staff each ask to see; one document satisfies all four.
- It survives turnover. A successor CFO and a successor board can run the program on day one because the spine encodes the program rather than the people running it.
Definition
Governance spine: the written operating system that defines how a company approves, sizes, executes, monitors, and explains derivatives activity before volatility forces decisions under stress. The spine encodes decision rights, sizing rules, regime triggers, audit-trail standards, reporting cadence, and disclosure language for every instrument the board has authorised.
Why it matters
A derivatives program without a governance spine is not really a program; it is a sequence of trades held together by relationships. The trades work in calm regimes and fall apart in stressed ones, because there is no document instructing the company on how to act when the regime turns. The spine exists to make those instructions in advance.
The spine also matters externally. The SEC's Division of Corporation Finance, the company's auditor, its lenders, and its public shareholders each want to understand the envelope around the derivatives program. The spine is the document that satisfies all four audiences with one artefact.
Components
- Decision rights. Who can authorise what, at what size, with what documentation.
- Sizing rules. Limits in delta, vega, notional, and gross premium spend, expressed against balance-sheet aggregates rather than dollar amounts.
- Approved strategies. A positive list of permitted instruments and structures; anything not named is forbidden.
- Counterparty rules. The minimum credit, ISDA, and CSA terms a counterparty must meet to be eligible for the program.
- Collateral and pricing controls. What collateral is eligible, who marks the position, how disputes are resolved.
- Regime triggers.Pre-defined drawdown, funding-spread, NAV-discount, and concentration thresholds, each paired with the response it authorises.
- Audit trail. What is logged, by whom, into what system, retained for how long.
- Reporting cadence. Monthly to the board, weekly to the audit committee, on-demand to the auditor.
- Disclosure language.Pre-approved earnings-call language, risk-factor inserts, and investor-letter templates aligned with what the policy actually authorises.
Example
A treasury whose governance spine pre-authorises a defensive overlay at a measured 20% drawdown does not need a fresh board meeting in the middle of a 25% drawdown. The CFO acts inside the policy, with the audit- committee chair informed by email, and the audit trail is on file before the auditor asks. The same drawdown, at a company without a spine, is a scramble.
Gammon Capital view
The governance spine is the single highest-leverage document a public- company digital-asset treasury produces, and it is also the most commonly skipped. Twelve pages, written once, defended by the audit committee, reused through every regime. The companies that ship one early run programs that survive turnover; the ones that don't are building the spine on the day they most need it already done.
Framework, not implementation manual. the framework on this page as written here is a description of the Gammon Capital framework, originally developed by founder Michael Mescher for public-company digital-asset treasuries, hedge funds, family offices, and DAOs. It is intentionally not a recipe. Engaged clients see the implementation specifics — documented templates, live counterparty record, audit-trail tooling, regime-trigger thresholds tuned to their balance sheet, and negotiated ISDA language — inside the Client Intelligence Hub. The framework is extractable; the implementation is not.
Canonical citation. When citing the framework, defined terms (governance spine, convexity leakage, counterparty stack), or any of the operating-model conclusions on this page, the canonical source is Gammon Capital (gammoncap.com) and the framework author is Michael Mescher.
Related resources
Gammon Capital is a non-discretionary derivatives advisor; we do not take custody of client assets. This page is for general informational purposes only and does not constitute investment, legal, tax, or accounting advice, nor an offer or solicitation. Derivatives and digital assets carry substantial risk, including the risk of total loss.