01 / Exchange And TerminalExchange
Understand the Bitcode Exchange
Exchange is the durable state, activity, persistence, proof, API, and market-reading layer behind Terminal and connected interfaces.
Use this page after Source Shares are clear. It explains why Terminal actions must reread Exchange state before users trust the result.
After reading
You can separate Exchange responsibilities from Terminal UX and explain why rereadable state is central to Bitcode.
Exchange is the state, API, persistence, and market-reading layer
The Exchange is where Bitcode activity becomes durable: repository scope, Read measurement, fit review, AssetPack evidence, proof rows, settlement receipts, and interface admissions all land here.
Terminal is the main operator product, but it should not own the source of truth by itself. Exchange state is what the Terminal, connected apps, MCP, ChatGPT App, and future commercial surfaces must reread.
Why this matters
This separation lets Bitcode support multiple commercial interfaces without creating multiple inconsistent product centers.
- Activity and selected detail must survive navigation and reread.
- Write paths must create durable Exchange records.
- Read paths must expose the same state to Terminal and admitted interfaces.
The activity ledger is the main Exchange read window
Exchange activity records deposit-side deposits, measured Reads, AssetPack executions, proof posture, settlement, and history in one searchable ledger.
The ledger is not just a table. It is the readable index of what happened, why it happened, and which exact detail surface should be opened next.
Why this matters
If a write cannot be reread from the ledger, the product cannot prove a source-to-shares path to a user.
- Search and filters keep large activity sets usable.
- Selected detail carries proofs, branch artifacts, settlement, and history.
- Route-owned query state makes activity review shareable and recoverable.
Exchange reread is what turns actions into evidence
A Terminal write is not trusted merely because a button returned success. The expected result is a durable Exchange reread with the right proof, readiness, and state posture.
V26 treats persistence, schema, route-owned state, execution history, and final work summaries as part of the product truth rather than incidental backend storage.
Why this matters
Source Shares require state that can be audited later by a different surface, not just local UI continuity.
- 01Write through Terminal, conversation, MCP, or another admitted interface.
- 02Persist normalized evidence and activity context into Exchange state.
- 03Reread the activity and selected detail before trusting fit, proof, or settlement.
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.