Understand Exchange activity and /exchange compatibility

/exchange redirects to /exchange

/exchange is retained only as a compatibility redirect. /exchange is the durable master-detail surface for DataPack activity, proof roots, settlement, compensation, delivery, and repair.

The compatibility path must not become a parallel product. MCP, ChatGPT App, Bitcode Chat, GitHub, and future interfaces must reread the same proof-backed activity exposed through /exchange.

• Activity and selected detail must survive navigation and reread through /exchange.
• Write paths must create durable source-safe records.
• Read paths must expose the same proof readback to admitted interfaces.

The activity ledger is the main /exchange read window

/exchange records deposits, measured Reads, DataPack executions, proof posture, settlement, and history in one searchable ledger.

The ledger is not only a table. It is the readable index of what happened, why it happened, and which detail panel to open next — seller and buyer views of the same commercial object.

• Search and filters keep large activity sets usable.
• Selected detail carries proofs, settlement, BTD/BTC posture, and history.
• Route-owned query state makes review shareable and recoverable.

/exchange reread is what turns actions into evidence

A write is not trusted merely because a control returned success. The expected result is durable /exchange reread with the right proof, readiness, and state posture.

Protocol treats persistence, schema, route-owned state, execution history, and work summaries as product truth — not incidental backend storage.

1. 01Write through /deposits, /reads, Bitcode Chat, MCP, or another admitted interface.
2. 02Persist normalized, source-safe activity evidence.
3. 03Reread the activity and selected detail in /exchange 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 DataPack source. Source-bearing DataPack 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 DataPack 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 /exchange and does not create a parallel current product surface.