Assumption Surfaces Register
Invisible expectations activated when Bitcoin enters institutional systems.
When an organization adds Bitcoin to its treasury, a set of institutional assumptions activate across professional domains. These assumptions are rarely stated, rarely verified, and rarely assigned to any specific function. They persist silently until a stress event exposes them.
This register names those assumptions. It does not evaluate whether any assumption is correct or incorrect. It documents what is expected but not formally confirmed.
Assumption surfaces are not failures. They are expectations that have not been formally assigned, verified, or documented.
What an Assumption Surface Is
An assumption surface is an unstated expectation that transfers across professional domains without verification. Unlike a scope boundary — which marks where a function's responsibility ends — an assumption surface marks where an expectation exists that no function has formally accepted.
Assumption surfaces are structural. They are not the result of negligence. They emerge because institutional systems were designed for intermediated assets where most of these expectations are met automatically by custodians, clearinghouses, and regulatory frameworks.
Assumption Surfaces Activated by Bitcoin Treasury Decisions
Recoverability Assumption
Assumption type: Operational / Custody
The expectation that the asset can be recovered if access is lost, credentials are compromised, or operational failure occurs. Traditional treasury assets are recoverable through institutional channels. Bitcoin held in self-custody is not.
Activated when: audit confirms balance exists but does not test whether the organization can actually move it.
Reversibility Assumption
Assumption type: Operational
The expectation that a transaction can be reversed, corrected, or disputed after execution. Traditional payment and transfer systems include reversal mechanisms. Bitcoin transactions are final upon confirmation.
Activated when: treasury operations assume the same error-correction process that applies to wire transfers or ACH.
Institutional Intermediation Assumption
Assumption type: Governance / Custody
The expectation that an intermediary exists to translate legal authority into asset control. For traditional assets, banks, brokerages, and custodians perform this function automatically. For self-custody Bitcoin, no intermediary bridges the gap between legal ownership and cryptographic access.
Activated when: board authorizes allocation but assumes the custodian handles all operational dimensions, including governance documentation and succession.
Documentation Sufficiency Assumption
Assumption type: Governance
The expectation that existing governance documentation — board minutes, policy frameworks, internal memos — adequately covers Bitcoin-specific decision rationale, authority structures, and custody arrangements. Standard corporate documentation templates were not designed for bearer cryptographic assets.
Activated when: organization treats a general treasury policy as sufficient documentation for a Bitcoin-specific allocation decision.
See Decision Record, Retroactive Documentation, Audit-Ready Documentation
Exit Liquidity Assumption
Assumption type: Liquidity
The expectation that a treasury asset can be liquidated at or near its reported value within normal operational timelines. Bitcoin's liquidity varies by position size, market conditions, custody arrangement, and banking relationship status.
Activated when: financial models assume Bitcoin can be converted to fiat within the same settlement window as traditional treasury instruments.
Successor Competence Assumption
Assumption type: Succession
The expectation that the next person to hold a role — CFO, controller, custodian, board member — will have the technical knowledge required to manage or oversee Bitcoin treasury operations. Traditional treasury roles assume domain continuity across personnel transitions. Bitcoin introduces technical competence requirements that do not transfer automatically with the role.
Activated when: no onboarding protocol exists for incoming officers regarding Bitcoin custody, reporting, or governance obligations.
Arrangement Persistence Assumption
Assumption type: Temporal
The expectation that a governance or custody arrangement remains valid over time without active maintenance. Institutional arrangements degrade silently as assumptions age, personnel change, regulatory posture evolves, and custody infrastructure shifts. A governance arrangement that was sound at authorization may no longer reflect current conditions 12, 24, or 36 months later.
Activated when: an organization treats a decision record or custody arrangement as permanently valid without scheduled re-evaluation.
See No One Remembers Why, No Monitoring Process, Nobody Knows Why
Control Environment Assumption
Assumption type: Control
The expectation that existing internal controls — segregation of duties, access restrictions, approval workflows — extend to Bitcoin operations without modification. Standard control environments assume intermediated custody, institutional counterparties, and auditable transaction trails. Self-custody Bitcoin operates outside those assumptions.
Activated when: SOX compliance framework is applied to Bitcoin holdings without evaluating whether control objectives are achievable under the custody model in use.
See SOX Compliance, Material Weakness Risk, Internal Audit Scope
Disclosure Adequacy Assumption
Assumption type: Disclosure
The expectation that standard disclosure frameworks — 10-K filings, shareholder communications, board reports — adequately represent the risk profile of Bitcoin treasury positions. Bitcoin introduces custody risk, governance risk, and operational risk categories that standard disclosure templates do not address.
Activated when: disclosure references Bitcoin as a treasury asset without addressing custody architecture, key-person dependencies, or governance documentation status.
Counterparty Coverage Assumption
Assumption type: Operational / Governance
The expectation that third-party service providers — custodians, exchanges, wallet infrastructure vendors — cover operational, legal, and governance dimensions beyond their stated scope. Service agreements typically define narrow operational obligations. Governance integration, succession planning, and documentation sufficiency are rarely within scope.
Activated when: organization treats custodian engagement as comprehensive coverage of Bitcoin-related institutional risk.
Why Assumptions Transfer Without Verification
In institutional systems, responsibility is defined formally. Assumptions are not. Each professional domain operates within its stated scope and assumes adjacent domains cover what it does not. When Bitcoin enters an institutional system, these assumptions transfer across professional boundaries without verification — not because of negligence, but because no coordination mechanism exists to surface them.
This register documents where that transfer commonly occurs. The Professional Scope Boundary Matrix documents who assumes coverage exists. This register documents what is assumed.
When Assumption Surfaces Become Visible
Assumption surfaces typically remain invisible during normal operations. They become visible when an external event applies pressure to the arrangement: audit engagement, litigation discovery, leadership transition, banking review, regulatory examination, shareholder inquiry, or corporate transaction due diligence. The assumption was always present. The stress event is what exposes it.
This register documents observed assumption surfaces. It does not evaluate the validity of any assumption or recommend changes to institutional arrangements.
Version 1.0 — Published February 2026. Assumption surfaces may evolve as institutional standards evolve.
The risk is often not the decision itself, but the absence of a durable record explaining how it was made.
Generate Decision Record$995 · 12-month access · Unlimited analyses
An independent readiness classification and permanent governance document. Structured for board review, audit workpapers, and future scrutiny. Completed in 30–60 minutes.
View a completed Decision Record →Framework References
COO Responsible for Bitcoin Custody
How to Document Prior Bitcoin Allocation?
How to Cite Bitcoin Treasury Analysis Reports?
Relevant Scenario Contexts
Professional Services — Holding (5M) →
