03 / Protocol And Proof$BTD
Read settlement, $BTD, and exact accounting
Settlement docs connect Source Shares to $BTD-denominated accounting, fit-quality receipts, journal completeness, wallet readiness, and payment-mode posture.
Use this page when you read to understand how accepted source-to-shares evidence becomes attributable settlement rather than just a successful analysis run.
After reading
You can explain how Bitcode moves from measured source and fit into exact accounting and staged or live payment posture.
Settlement converts accepted source-to-shares evidence into exact accounting
Bitcode allocates BTD-denominated accounting from contribution, fit, participation, and proof posture. It must preserve exactness, normalization, journal completeness, and payment-observation coherence.
The user-facing idea is simple: useful measured source can become attributable value. The protocol detail is strict: allocation conservation, quantized fit-quality receipting, journals, receipts, and policy-bound execution all have to agree.
Why this matters
Settlement is where Source Shares become economically meaningful instead of just technically interesting.
- Fit quality affects settlement posture.
- Journals and receipts make allocation rereadable.
- Wallet and signer readiness decide whether settlement can move beyond staged review.
Base-layer, repeated-read, and sidechain modes are interface postures
V26 records bitcoin mainchain execution, repeated-read payment execution, and sidechain execution as hardened interface responsibilities, not marketing labels.
In launch mode these may be mocked or boundary-only. The product must still teach what the modes mean, which receipts would prove them, and which blockers prevent live settlement.
Why this matters
Commercial credibility depends on users seeing the difference between modeled readiness and live execution.
Public docs expose guidance and proof posture, not protected source
Public Bitcode docs derive from the active Protocol, package-owned catalogs, route contracts, and source-safe generated artifacts. They can explain usage, measurements, event ids, proof roots, docs links, runbook links, redaction posture, testnet rollout readiness, fee boundaries, and settlement posture.
They must not reveal protected source payloads, raw protected prompts, secret values, provider tokens, wallet private material, or unpaid AssetPack source. Source-bearing AssetPack contents cross to the reader only after settlement and rights transfer.
Why this matters
This keeps the public product understandable while preserving the boundary that makes Source Shares economically and operationally safe.
- Allowed: usage guidance, route links, state labels, source-safe measurements, proof roots, dashboard/runbook ids, redacted incident posture, testnet rollout readiness, LocalStagingTelemetryDocumentationRehearsal evidence, and fee/right boundaries.
- Interface docs may surface event ids, proof roots, docs links, runbook links, and redaction posture from TelemetryDocumentationInterfaceIntegration without revealing source-bearing payloads.
- Local and staging-testnet rehearsal docs may surface documentation discovery, telemetry event emission, dashboard/runbook lookup, docs QA, incident drill, source-safe proof-root review, and blocked value-bearing mainnet posture.
- Blocked: secrets, provider tokens, wallet private material, raw protected prompts, protected source payloads, and unpaid AssetPack source.
- Docs QA fails closed when public docs, internal docs, route docs, interface docs, generated artifacts, proof posture, or workflow checks drift.
- Deferred boundaries stay explicit: V35 documents Exchange and Conversations usage while deeper product depth remains future-canon work.