01 / Product RoutesOperator map
Orient on Packs, Deposit, and Read
Understand the commercial product as three focused routes: Deposit for supply, Read for demand and delivery, Packs for durable activity and proof readback.
Use this page when you need to know where to write, where to buy, where to audit, and when to open Auxillaries or Conversations as supporting modes.
After reading
You can identify deposit write posture, read demand posture, packs activity reread, and when to open Auxillaries.
Packs is the durable ledger; Deposit and Read are the write paths
Treat /packs as the activity master-detail you reread after work, /deposits as supply synthesis and listing, and /reads as demand measurement and paid delivery.
Deeper modes — Auxillaries and Conversations — support readiness and drafting. They must not invent a second ledger. Every bounded write should leave source-safe activity that /packs can reopen.
Why this matters
One map keeps the product learnable: write on Deposit or Read, audit on Packs, configure in Auxillaries.
- Packs owns searchable activity and expandable proof/settlement detail.
- Deposit and Read own the shortest seller and buyer loops.
- Auxillaries and Conversations are deliberate follow-through, not parallel products.
Read window
The read surfaces on product routes show whether a Bitcode action actually changed proof-bearing state.
Exchange owns the market-wide master-detail loop. Terminal keeps a focused read/write loop for recent Deposit, Read, proof, and closure results; deeper proof, conversation, and auxillary surfaces should remain deliberate follow-through rather than parallel primaries.
Why this matters
Operators learn whether work completed by rereading evidence, not by button feedback alone.
Write posture
Writes stay bounded because Bitcode has proof, wallet, repository, disclosure, and settlement consequences.
This is where click-based and chat-based write paths meet. Conversations can draft, but the ledger-facing write posture still belongs to deposit, read, deposit, branch, and closure so writes land in Bitcode Exchange and remain auditable against Bitcode Protocol canon.
Why this matters
Bounded writes keep commercial and proof posture coherent across product and interface surfaces.
Auxillaries and Conversations must not erase pack activity context
Mode changes are useful only when the reader never loses the active /packs activity or deposit/read work context.
Use the rail to open conversations or Auxillaries deliberately, while recent activity and the selected result remain the primary Terminal read surface.
Why this matters
Supporting modes exist to configure or draft — not to replace the ledger.
- Keeps deeper drafting deliberate
- Avoids splitting attention away from recent activity results
- Preserves orientation when switching modes
Repository scope is the deposit-side boundary
Permitted source comes from authorized repositories. Every deposit and downstream proof depends on that scope staying explicit.
This is where you set the boundary for deposit-side supply. It should read as a clean source selection surface, not as infrastructure plumbing.
Why this matters
Without clear repository attachment, synthesis and settlement readiness cannot be trusted.
- Anchors deposit-side supply to one repository boundary
- Keeps provider posture visible
- Supports continuing straight into Deposit and Read
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.