Bitcoin Treasury Scorecard as a Decision Summary
The Artifact That Crosses the Table
This memo is published by Bitcoin Treasury Analysis, an independent decision-record instrument for Bitcoin treasury governance.
What the Board Actually Receives
A bitcoin treasury scorecard is the artifact that crosses the table. Some organizations refer to it as a bitcoin treasury rating—a bounded classification that reduces a complex governance evaluation to a structured summary. The full evaluation record—the recorded inputs, the domain-level analysis, the Assumptions and Constraints Register, the Deterministic Rule Trace, the Decision Validity Register—constitutes the institutional record. The scorecard constitutes what the board sees in the meeting. Six domain classifications. A count of identified gaps. An issued conclusion. A structural stability indicator. Enough to anchor discussion, not enough to reconstruct the analysis.
The distinction matters because organizations frequently treat the scorecard as the evaluation. The CFO presents the scorecard to the board. The board reviews the classifications, notes the conclusion, and votes. The full evaluation record exists somewhere in the documentation package but receives less attention than the summary. This creates a governance condition in which the board has technically been presented with the findings but has interacted primarily with a summary that omits the reasoning, the assumptions, and the conditions under which the conclusion becomes invalid.
Structural Stability and What It Tells the Board
The scorecard records a property that most summary formats omit: whether the conclusion is structurally stable. A structurally stable conclusion means that no single domain reclassification would alter the issued determination. The conclusion holds even if one domain improves or degrades by one classification level. A structurally sensitive conclusion means that the reclassification of a single domain—one domain moving from marginal to sufficient, or from sufficient to marginal—would change the outcome.
This information changes how the board interprets the result. A scorecard that reads “Not Ready to Proceed” with a structural stability designation of “sensitive” and a notation that Governance Readiness is the load-bearing domain tells the board something specific: targeted remediation in governance—adopting a written treasury policy, formally disclosing conflicts of interest, establishing a reporting cadence—could move the classification. The same conclusion with a stability designation of “locked” tells the board that remediation across multiple domains would be required and that the determination reflects broadly distributed institutional constraints rather than a single addressable gap.
Without the stability property, the board knows the answer but not how firmly the answer is determined. Two organizations with identical classifications of “Not Ready to Proceed” may face fundamentally different remediation paths. The scorecard communicates this difference. A spreadsheet summary of domain ratings does not.
Comparability Across Time
Organizations that conduct assessments at multiple points in time produce scorecards that can be compared. The comparison reveals which domains improved, which degraded, which remained unchanged, and whether the issued conclusion shifted. An organization classified as Not Ready to Proceed in Q1 that remediates its governance gaps and is reclassified as Proceed in Q3 possesses a documented trajectory—evidence that the institution identified its constraints, addressed them, and re-evaluated under the same framework.
Comparability requires that both scorecards were produced under the same major Standard Version. The scorecard records the version number, and decision records issued under the same major version are structurally comparable when based on equivalent declared assumptions and recorded inputs. Version changes that alter classification rules, domain definitions, or conclusion logic produce scorecards that cannot be directly compared—the framework itself has changed, and the same organizational conditions might produce different classifications under different versions. The version constraint is recorded on the scorecard for this reason: it tells the reader which comparisons are valid and which are not.
Scope and Limitations
The scorecard is a summary artifact. It does not substitute for the full evaluation record. Scorecard comparability across time periods requires consistent Standard Version and equivalent assessment methodology. Domain classifications and the resulting determination reflect conditions as documented at the time of assessment. An organization relying solely on the scorecard without reference to the underlying evaluation record possesses a conclusion without its basis—a governance posture that is complete for communication purposes and incomplete for institutional reliance.
Framework References
Bitcoin vs Gold Corporate Treasury
Bitcoin Treasury Strategic Reserve Rationale
What Could Go Wrong Bitcoin Treasury?
Relevant Scenario Contexts
Bootstrapped Saas — Considering (1M) →
← Return to Bitcoin Treasury Analysis
Explore Related Scenario Contexts →
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 →