Standard (BT-RS)
Bitcoin Treasury Decision Record Standard
Standard Version: BT-RS v1.0 · February 2026
Bitcoin Treasury Analysis is an independent, structured decision-record instrument that evaluates how a Bitcoin treasury decision would alter an organization's financial, operational, governance, regulatory, and reputational exposure under explicitly stated assumptions. It produces a Bitcoin Treasury Decision Record: a fixed, versioned set of reference documents recording how a Bitcoin treasury decision was considered, bounded, and concluded at a specific moment in time under those stated assumptions.
What this instrument is
The instrument produces a Decision Record package consisting of seven primary artifacts that together constitute a complete governance record of a Bitcoin treasury decision process.
It records declared assumptions, organizational constraints, governance posture, and a bounded conclusion rule-resolved from those inputs under a fixed Standard Version (BT-RS).
This instrument is non-advisory. It does not provide investment advice, allocation optimization, implementation guidance, vendor recommendations, execution steps, or prescriptive remediation.
Each analysis is issued under a specific Standard Version (BT-RS) and analysis date. New inputs require a new analysis with a new reference ID. Prior records are not revised.
Standard architecture
Instrument shape
The instrument follows a fixed path: structured questionnaire → domain findings → domain classifications → conclusion → artifact package. The question set consists of 52 fixed analytical questions plus a non-analytical acceptance gate. The question set does not expand or contract based on user profile or answers.
Would this Bitcoin treasury decision be treated as an exception to existing treasury or investment policy?
If a Bitcoin treasury position results in material loss, where is responsibility for that outcome understood to reside?
Why this is rule-based
Outputs are produced by fixed rule resolution defined within the Standard Version (BT-RS). No interpretive override, discretionary adjustment, or post-classification modification is applied after domain classification. For a given Standard Version, identical inputs produce identical outputs. Results are reproducible under the same version.
Independence qualifiers
Bitcoin Treasury Analysis includes a limited set of independence qualifiers that record whether (a) outcome-contingent external incentives were disclosed, (b) operational readiness assessment relies primarily on representations from a single external service provider or includes independent validation, and (c) legal review was performed by counsel without a financial interest in the Bitcoin allocation outcome.
These qualifiers do not alter or replace legal, custody, or advisory work. They do not introduce optimization or recommendation logic. They record whether independence and disclosure conditions were assessed and documented at the time of analysis.
Governance records frequently omit incentive exposure and reliance concentration even when other diligence is performed. Recording these conditions increases the evidentiary integrity of the Decision Record without introducing advisory interpretation.
Domain model
The instrument evaluates six domains, each representing a distinct precondition for a considered Bitcoin treasury decision:
- Context & Intent
- Financial Constraints
- Governance Readiness
- Operational Capacity
- Custody & Execution Assumptions
- Regulatory & Reputational Posture
Strength in one domain does not compensate for insufficiency in another. The instrument does not aggregate domain strength into a composite score.
Equal weighting
The instrument does not embed normative judgments about which preconditions matter more. Each domain is treated as a separate condition for defensibility. This is a structural constraint, not a simplification.
Has the organization prepared for stakeholder communications following a material Bitcoin valuation decline (≥50%)?
Has leadership considered how Bitcoin adoption would be explained if the decision attracted regulatory, media, or stakeholder scrutiny unrelated to price?
Resolution logic
Domain classifications
Each domain resolves to SUFFICIENT, MARGINAL, or INSUFFICIENT based on the count and severity of declared gaps and concerns recorded in that domain.
Domain thresholds are rule-defined within the Standard Version and do not vary by organization profile, size, or industry.
Insufficiency conditions override sufficiency in conclusion resolution according to fixed rule precedence defined within the Standard Version.
CONCERN Evaluation triggered by market conditions
CONCERN No volatility threshold defined
CONCERN Accounting treatment not determined
CONCERN Indefinite hold removes exit optionality
CONCERN No written treasury policy exists
CONCERN Treasury not regularly reported
CONCERN Policy exception status not considered
CONCERN Treasury operations not documented
CONCERN No incident response process
CONCERN No internal Bitcoin experience
CONCERN Vendor dependency not evaluated
CONCERN Tax treatment not addressed
CONCERN Non-price scrutiny narrative not considered
Conclusion outcomes
The instrument is structurally limited to issuing exactly three conclusions:
- Proceed
- Not Ready to Proceed
- Do Not Proceed
These conclusions are conditional, assumption-bound, and time-specific. They do not instruct how to proceed, what to buy, or how to implement.
Finality
Each issued conclusion is final under the recorded assumptions, declared inputs, and the stated Standard Version. Any change to inputs requires a new analysis with a new reference ID.
Issued Classification
Not Ready to Proceed
Acceptance at issuance: Accepted with reservations
Reservations: Governance gaps in operational documentation and incident response are acknowledged. The organization intends to remediate these within 90 days and re-evaluate.
Determinism
Bitcoin Treasury Analysis is a deterministic instrument. For a given Standard Version: identical inputs produce identical conclusions, artifacts are reproducible, and records are citable and comparable over time.
There is no personalization, learning, optimization, or adaptive behavior.
Governance records require stable semantics. Adaptive systems change interpretation over time, which undermines the evidentiary value of historical records. Determinism ensures repeatability, not correctness.
Identical declared conditions cannot produce different interpretive outcomes across time or reviewers.
The instrument contains no optimization logic, scoring model tuning, adaptive weighting, or outcome targeting. The standard is rule-bound and does not attempt to maximize or minimize any conclusion.
Deterministic Rule Trace (BT-RS Execution Log)
Mechanically traces recorded inputs to domain classifications and the applied conclusion rule.
Decision records issued under the same major Standard Version are structurally comparable across issuers when based on equivalent declared assumptions and recorded inputs.
| Domain | Classification | Classification Threshold Met | Concerns | Contribution Under Applied Rule |
|---|---|---|---|---|
| Context & Intent | sufficient | Threshold recorded: <2 critical gaps and <3 concerns | 1 | Does not contribute to Not Ready to Proceed under applied rule |
| Financial Constraints | marginal | Threshold recorded: ≥3 concerns | 3 | Contributes to conclusion under applied rule: ≥3 marginal, <4 sufficient produces Not Ready to Proceed |
| Governance Readiness | marginal | Threshold recorded: ≥3 concerns | 3 | Contributes to conclusion under applied rule: ≥3 marginal, <4 sufficient produces Not Ready to Proceed |
| Operational Capacity | marginal | Threshold recorded: ≥3 concerns | 3 | Contributes to conclusion under applied rule: ≥3 marginal, <4 sufficient produces Not Ready to Proceed |
| Custody & Execution | sufficient | Threshold recorded: <2 critical gaps and <3 concerns | 1 | Does not contribute to Not Ready to Proceed under applied rule |
| Regulatory & Reputational | sufficient | Threshold recorded: <2 critical gaps and <3 concerns | 2 | Does not contribute to Not Ready to Proceed under applied rule |
- No volatility threshold defined
- Accounting treatment not determined
- No written treasury policy exists
- Treasury operations not documented
- No incident response process
- No internal Bitcoin experience
Documentation closure and record sufficiency
The Decision Record package is intentionally complete. Each artifact closes a specific documentation loop:
- Bitcoin Treasury Decision Record (BT-DR) — Records executive context, scope, attestation, and the issued conclusion.
- Assumptions & Constraints Register — Closes the dependency loop by recording what the conclusion relies on.
- Decision Threshold & Stability Profile — Records proximity to the decision threshold and whether marginal domains share common drivers.
- Governance Posture Summary — Records governance and operational posture at time of analysis.
- Deterministic Rule Trace (BT-RS Execution Log) — Closes the interpretability loop by mechanically tracing how recorded inputs resolved to domain classifications and the applied conclusion rule.
- Decision Validity Register — Closes the temporal loop by recording when the record stops applying.
- Analysis Powerpoint Presentation — Structures the Decision Record in presentation format for board review.
No additional narrative, commentary, or interpretive supplementation is required to understand the issued conclusion within the stated scope.
Record integrity
The instrument computes a deterministic integrity digest locally at issuance time. The digest binds the declared inputs and Standard Version to the issued artifacts. The integrity digest is recorded in the Decision Record and the Deterministic Rule Trace. Other artifacts reference the Decision Record for verification.
If any declared input or standard parameter is altered, the digest changes, allowing independent verification that the issued record no longer corresponds to the original declared state.
Bitcoin Treasury Analysis does not store inputs and does not monitor or re-verify records after issuance.
Input consistency enforcement
Contradictory selections are prevented at entry time. Incompatible dependent answers are cleared when upstream answers change. The instrument is structurally prevented from issuing a record containing internally contradictory declared positions.
Structural limits and explicit exclusions
This instrument does not model:
- Future market behavior
- Execution quality or operational skill under stress
- Hidden intentions or omissions
- Legal sufficiency or regulatory approval
- Comparative benchmarking against other organizations
It records declared exposure under stated assumptions only.
Authorship and responsibility
Bitcoin Treasury Analysis artifacts are authored by the instrument under the stated Standard Version, not by the organization whose inputs are recorded. Each artifact explicitly states the producing entity, the organization whose inputs were recorded, the analysis date, and the immutable reference ID.
Inputs are provided by the organization. Conclusions are issued by the instrument. Responsibility for decisions remains with the organization.
Assumptions & Constraints Register
Records declared and derived premises underlying the issued conclusion.
Reliance indicates whether a change to the assumption would invalidate the conclusion (Critical) or weaken its basis (Contributing).
| Description | Conclusion Reliance |
|---|---|
| Primary motivation: Treasury diversification | Critical |
| Holding period: 3–5 years | Critical |
| Allocation range: 1–5% of treasury | Critical |
| Liquid reserves: 12–24 months operating expenses | Critical |
| Decision authority: Executive committee | Contributing |
| Custody model: Qualified custodian | Critical |
| Regulatory status: Review underway | Critical |
| Loss ownership: Executive leadership | Contributing |
| Decision irreversibility explicitly acknowledged | Contributing |
| Description | Conclusion Reliance |
|---|---|
| Indefinite hold with no exit conditions assumed | Critical |
This register records assumptions relied upon by the analysis. Changes invalidate the conclusion.
Citation and Reference Language
Bitcoin Treasury Decision Records issued under BT-RS are designed to be referenced in board materials, governance memoranda, audit documentation, internal policy records, and professional files without requiring reinterpretation or explanatory narrative.
When referencing a record, the following citation structure may be used:
Short form citation
Bitcoin Treasury Decision Record issued under BT-RS vX.X.X.
Full reference citation
Bitcoin Treasury Decision Record issued under BT-RS vX.X.X, Reference ID [XXXX], dated [Month Year].
Where relevant, references may specify the issued conclusion:
Bitcoin Treasury Decision Record issued under BT-RS vX.X.X concluding "Proceed" (or "Not Ready to Proceed" / "Do Not Proceed").
Citation of a Decision Record does not imply endorsement, adequacy, regulatory approval, or correctness. It identifies that the decision process was recorded under a fixed Standard Version (BT-RS) with deterministic resolution logic and bounded assumptions.
Professionals may reference the Standard itself as:
Bitcoin Treasury Decision Record Standard (BT-RS) vX.X.X.
The Standard is version-bound. Interpretation of any Decision Record is valid only within the Standard Version under which it was issued.
Standard versioning and change policy
Each analysis is tagged with a Standard Version (BT-RS). Results are interpretable only within the Standard Version (BT-RS) under which they were produced.
Prior records retain their original meaning. New Standard versions expand coverage without changing historical interpretation. Any meaning-changing modification requires a Standard Version (BT-RS) increment.
No semantic modification affecting domain classification thresholds, conclusion resolution rules, or artifact structure may occur without an explicit Standard Version (BT-RS) increment.
A detailed Standard Lock & Change Policy is maintained for reference. A public BT-RS Standard Change Log records versioned clarifications and corrections.
Privacy and data handling
Bitcoin Treasury Analysis processes all inputs locally in the browser. No assessment inputs or generated artifacts are transmitted to Bitcoin Treasury Analysis servers. No data is retained by the instrument. No accounts are required.
Organizations are responsible for retaining their own copies of generated artifacts.
Interpretability and comparability
Results produced by this instrument are not intended to be compared across organizations or used as benchmarks. Each analysis is valid only within its own stated assumptions and context.
- A Proceed conclusion is not an endorsement.
- A Do Not Proceed conclusion is not a prohibition.
- The analysis does not certify adequacy or compliance.
- The analysis is not a substitute for fiduciary, legal, accounting, or regulatory judgment.
- Re-running the analysis produces a new record, not a revision.
To see how common treasury decision patterns emerge across organizations, see Observed Decision Patterns — recurring patterns in how companies frame, evaluate, and review Bitcoin treasury decisions.
Bitcoin Treasury Decision Record — Terminology standard
The following terms are used with specific meanings in Bitcoin Treasury Analysis artifacts and standard text.
Bitcoin Treasury Decision Record
A fixed, reference-grade set of documents produced by Bitcoin Treasury Analysis that records declared assumptions and constraints, evaluation outcomes across defined domains, and the bounded conclusion at time of issuance. A Decision Record is time-specific, assumption-bound, and versioned.
Decision Record Package
The complete set of artifacts issued upon completion of a Bitcoin Treasury Analysis. The package constitutes the formal decision record of the decision process.
Declared Inputs
Answers provided by the organization through the structured questionnaire. Declared inputs are the sole basis for domain classification and conclusion resolution.
Declared Assumption
A condition explicitly stated by the organization as true at the time of analysis. Assumptions bound the validity of conclusions.
Domain
A distinct decision precondition category used by Bitcoin Treasury Analysis to assess exposure. The six evaluation domains are: Context and Intent, Financial Constraints, Governance Readiness, Operational Capacity, Custody and Execution Assumptions, and Regulatory and Reputational Posture. Domains carry equal weight in conclusion logic.
Domain Classification
The final categorical outcome issued by Bitcoin Treasury Analysis under its conclusion rules. Permitted classifications are: Proceed, Not Ready to Proceed, and Do Not Proceed. A classification describes readiness, not desirability, performance, or correctness.
Sufficient
A domain state indicating that recorded conditions meet minimum requirements for a considered decision under the standard. Sufficient does not imply optimality or absence of risk.
Marginal
A domain state indicating that recorded conditions introduce material uncertainty, unresolved constraints, or cumulative fragility. Marginal domains may contribute to a Not Ready to Proceed classification.
Insufficient
A domain state indicating that recorded conditions fail to meet minimum requirements for a defensible decision. Insufficient domains may trigger Do Not Proceed classifications depending on interaction rules.
Bounded Conclusion
A conclusion issued under explicitly stated assumptions, a fixed Standard Version (BT-RS), and a specific analysis date. A bounded conclusion does not generalize beyond its recorded scope.
Standard Version (BT-RS)
A locked definition of questions, thresholds, classifications, and interaction rules. Results are interpretable only within their version context.
Integrity Digest
A deterministic digest computed locally at issuance time that binds declared inputs and Standard Version (BT-RS) to the issued artifacts. If altered, the digest changes.
Decision Validity Register
The artifact that records the conditions under which the Decision Record remains applicable and the specific triggers that would invalidate it.
Invalidation Condition
The condition under which a Decision Record no longer applies due to time expiration, assumption change, governance change, or recorded trigger conditions. Invalidation does not imply error in the original analysis.
Independent Authorship
The principle that artifacts are authored by Bitcoin Treasury Analysis, not by the organization. Inputs originate from the organization; conclusions originate from the instrument.
Non-Advisory
A classification indicating that the instrument does not recommend actions, does not optimize outcomes, does not certify adequacy, and does not endorse decisions.
Reference Material
The reference library documents observed Bitcoin treasury decision behaviors, dependencies, and governance conditions. The materials are descriptive and non-advisory. See the Reference Library for independent memos on treasury governance, decision framing, and fiduciary exposure.
The Scenario Atlas maps 2,898 Bitcoin treasury decision contexts across company type, cash reserve level, decision position, and allocation intention — illustrating how governance, financial, and operational conditions interact across the framework.
