Map the active Protocol canon

V48 is the draft-target commercial protocol; public docs teach, they do not legislate

Product routes and public docs follow the V48 commercial protocol story: AssetPacks, BTD volume and rights, BTC settlement, source safety, and plural product routes. Formal law lives in the BITCODE_SPEC family, not in docs prose.

When docs and specification disagree, specification wins. Docs exist so operators, partners, and interface authors can learn the system in product order without reading every formal gate first. Promotion of a version into BITCODE_SPEC.txt is a separate, proof-gated workflow.

• Prefer BITCODE_SPEC / version-family notes for legal and implementation truth.
• Public docs must not overclaim mainnet settlement or unlocked source delivery.
• Proof readback — not UI optimism — decides commercial state.

Every subsystem is learnable from source supply to proof readback

The protocol spans repository supply, deposit synthesis, Read measurement, fit and selection, AssetPacks, identity, disclosure, settlement, proof families, telemetry, persistence, and admitted interfaces.

A docs reader should be able to drop into any subsystem and answer: what it owns, what fails closed, and what evidence proves a state advance. Product routes surface the same objects without inventing parallel vocabularies.

The chain ends in validation and rereadable evidence — not a success toast

Bitcode does not end when a button returns OK. It reconciles telemetry, persistence, failure semantics, generated artifacts, and promotion posture so a later surface can audit what happened.

That is why docs teach proof and settlement beside product actions. The commercial claim depends on operators being able to audit AssetPack paths after the fact, including when work started from Chat, MCP, or GitHub.

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.

• 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.