03 / Protocol And Proof$BTD
Read settlement, $BTD, and exact accounting
Settlement docs connect AssetPacks to BTD volume and rights, Bitcoin settlement money, needs-fits receipts, journals, wallet readiness, finality, and delivery posture.
Use this page to understand how accepted AssetPack evidence becomes attributable settlement rather than only a successful analysis run.
After reading
You can explain how Bitcode moves from measured source and fits into exact accounting, BTC finality, BTD rights transfer, and staged or live payment posture.
Settlement turns accepted AssetPack evidence into exact, rereadable accounting
BTD records knowledge volume and rights from contribution, needs-fits measurement, participation, and proof posture. Bitcoin is settlement money: it pays the quote and unlocks rights transfer only after finality.
User-facing truth is simple: measured knowledge can become attributable pack value. Protocol truth is strict: volume conservation, fit-quality receipts, journals, finality, rights transfer, and policy-bound execution must agree. Settlement is proven on a fully open-source, decentralized, and auditable ledger — not by a UI success state alone.
Why this matters
Settlement is where AssetPacks become economically meaningful instead of only technically interesting.
- Needs-fits quality affects BTD volume posture and BTC quote posture.
- Journals and receipts make allocation rereadable on /packs.
- Wallet readiness, BTC finality, and BTD rights decide whether delivery may unlock.
Base-layer, repeated-read, and sidechain modes are interface responsibilities
Protocol records mainchain execution, repeated-read payment execution, and sidechain execution as hardened interface duties — not marketing labels.
In commercial testnet, BTC amounts are free testnet units while ordering and proof rules still follow production-intended law. Value-bearing mainnet remains blocked until a promoted version authorizes it. Docs teach what each mode would prove and which blockers keep it staged.
Why this matters
Commercial credibility depends on distinguishing rehearsal money from live value-bearing 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 AssetPacks 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.
- Compatibility boundaries stay explicit: /exchange redirects to /packs and does not create a parallel current product surface.