00 / Start HereSource Shares
Source Shares and the Bitcode Exchange
Learn the value model first: Bitcode measures technical source into Source Shares, then lets Terminal users read and operate the market path.
This guide is for first-time readers who read the simple model before using Terminal: source supply comes in, demand is measured, fit and proofs decide what can move, and settlement makes attribution readable.
After reading
You can describe a Source Share, identify what gets measured, and understand why proof-backed settlement matters.
What Bitcode is measuring
Bitcode turns source material into tradable, measured technical intelligence rather than treating files as inert attachments.
Code, docs, diagrams, PDFs, notes, commits, citations, authorship, and metadata enter as source supply. The Exchange measures that supply against Read, fit, quality, provenance, and proof posture so useful technical intelligence can become Source Shares.
Why this matters
The share is only credible when the source, demand, proof, and settlement can be reread together.
- Supply is deposited as deposit-side source.
- Demand is expressed as a measured Read.
- Fit and proof decide whether source can move toward settlement.
Packs
Read pack activity where source supply, measured reads, settlement posture, compensation, delivery, and repair state meet.
Use this route when you need the activity master-detail view for AssetPack proposals, admitted packs, previews, proof roots, settlement, and delivery state.
Why this matters
The public Exchange view introduces the market without forcing a first-time reader into proof detail too early.
- Searches and filters source-safe pack activity
- Keeps proof and settlement detail expandable without exposing unpaid source
Deposit -> Read -> Fit -> Prove -> Settle -> Issue
The market path is intentionally linear for a new reader: source is given, Read is measured, fit is reviewed, proofs are produced, settlement is read, and $BTD issuance becomes attributable.
The Terminal exposes each stage so an operator can see both the write action that changes state and the read surface that proves what happened next.
Why this matters
The linear path is a teaching model. The under-the-hood system remains richer, but every advanced interface still has to preserve this chain.
- Deposit writes searchable supply.
- Read writes measured demand.
- Settlement reads proof-backed attribution and issuance posture.
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.